Yep, Thats the problem. I'm not sure how to fix this?
First I made it always read the content. The log now makes more sense, the stop isn't done until after the JSP init. But looking at the code, it always reads the content anyway and closes the stream. So all I'm doing is delaying the stop by doing more work. I put a sleep into the JSP to confirm it wasn't completing. Now it always NPEs. Any ideas why readLine returns null when it hasn't finished? I still haven't determined why JNDI becomes deadlocked. It happens when the ear is stopped and something is still running. I'll revert the url. That automated message is really annoying! Regards, Adrian ______________________________________________________________________ View this jboss-dev thread in the online forums: http://jboss.org/forums/thread.jsp?forum=66&thread=6187 _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
