Hi, Markus.
I wish I could say that the "sleep mode" was part of our "green" initiative to save energy as part of environmentally-responsible software, but what you are seeing is entirely unintentional as far as I know.
A good first step will be to find out whether the stall is actually happening in the ACC or in the GlassFish server. When you say there is no LAN usage, have you used WireShark or something similar to monitor the network messaging between the ACC and the server? If you have done that, and no message emerges from the ACC to the server until many seconds after you expect, then that suggests the problem is in the client-side code. If a message does leave the client and arrive at the server, but the server does not respond for a long time, then that narrows it down to the server side.
Also, with such a long time between when you expect the messages from client to server and back and when they actually go, you should have time during this delay to capture thread dumps on both sides, the client and the server. If you could attach those dumps to this topic that would give people something to look at to try to understand what is happening.
- Tim
[Message sent by forum member 'tjquinn' (tjquinn)]
http://forums.java.net/jive/thread.jspa?messageID=338962