(apologies, the rest of my post was cut off)
Is this known behavior in Glassfish/SJSAS that is manageable with config changes or resolved/planned in a later updated? Does anyone have a suggestion of what to look for in our code that could be causing this situation?
Any help would be greatly appreciated!
Peter
[Message sent by forum member 'porterpe' (porterpe)]
http://forums.java.net/jive/thread.jspa?messageID=286528