-
1. Re: Failed to process async modifications: java.io.EOFExcept
genman Jul 9, 2007 9:12 PM (in response to jsaraiva)Do you have a stack trace? Are you sharing the file system across the cluster? What operations are you doing?
-
2. Re: Failed to process async modifications: java.io.EOFExcept
jsaraiva Jul 11, 2007 10:44 PM (in response to jsaraiva)This error message does not generate any stack trace. It only repeats itself many times. I have set the debug level for the org.jboss.cache class to TRACE and don't get any stack trace.
The file system is not being shared across the cluster, every member has it's own local cache loader directory.
I have many concurrent read/write operations. I can't quantify the number of read/write operations per second, but it's a production system, it has really a lot of those.
JS -
3. Re: Failed to process async modifications: java.io.EOFExcept
manik Jul 12, 2007 6:27 AM (in response to jsaraiva)Is this only with the file cache loader? Does this go away with, say, a BdbjeCacheLoader? I know this may not be the ideal cache loader for you due to licensing though, but testing it with this will help pinpoint the problem.
-
4. Re: Failed to process async modifications: java.io.EOFExcept
manik Jul 12, 2007 6:48 AM (in response to jsaraiva)Hmm, if your log level is DEBUG or TRACE you should see the full stack trace. From the code:
private void put(List mods) { try { delegateTo.put(mods); } catch (Exception e) { if (log.isWarnEnabled()) log.warn("Failed to process async modifications: " + e); log.debug("Exception: ", e); } }