Hi.
Have you tried deploying and redeploying the app using the asadmin deploy command instead of autodeploying it, just to see what results you get?
I'm not suggesting that you abandon the autodeploy feature; it's just that this additional experiment might give us some more information about the problem.
If you are able and willing to make your WAR available, even though you cannot reproduce this problem 100% of the time, it might be best to open an issue using IssueTracker (
https://glassfish.dev.java.net/servlets/ProjectIssues) and attach your WAR to the issue. Set the component in the issue to "admin" at least as a starting point.
- Tim
[Message sent by forum member 'tjquinn' (tjquinn)]
http://forums.java.net/jive/thread.jspa?messageID=215051