All of these stack traces simply mean that something failed on the server
side without sending a response. Consequently the client side waits until it
times out (assuming that you aren't doing anything that takes longer than
the default 30 minute timeout in a single request).
You really need to look on the server side (GlassFish hopefully) and see
if there are any related log messages from the server. In particular, all
recent versions of GlassFish should catch any exception that escapes
all the way out to the ThreadPool worker thread and log it, precisely to
handle this sort of problem.
The GlassFish ORB should NEVER let exceptions propagate all the way
out to the worker thread, so if that is happening, it's a bug in the server side
code.
[Message sent by forum member 'kcavanaugh' (kcavanaugh)]
http://forums.java.net/jive/thread.jspa?messageID=319715