My application was running a a Linux box, but all of the application's JAR files were available via NFS. By moving the application's JAR files to local disk, the described problem seems to have disappeared.
Unfortunately, I was unable to try the aforemented tests (turning on synchronous replication) before this change was made, so I do not know what that might have produced. If the problem reappears, I will try this to see what it produces. My theory is that the classloader was failing to load class information across the NFS-mounted file system and causing the issue. Has anyone else experienced this type of strange behavior in their Java applications when utilizing NFS? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3856589#3856589 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3856589 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
