Can you collect a jstack trace when the server hangs? This will tell us
what the server is doing (is it trying to clean up tables and repopulate
it etc?)
forums_at_java.net wrote:
> Hi,
>
> I've recently upgraded to 3.1.2 b23 on Windows 7 x64.
>
> If I deploy my application with the database tables all deleted the
> deployment proceeds correctly, and returns to the application page in
> a short
> period of time (a second or two)
>
> If I undeploy the application, then redeploy it, without clearing the
> database out, the deploy page hangs, and does so forever. If I click
> on the
> "Applications" node it shows that the application has deployed.
> Checking in
> the server log I get a heap of the following message:
>
> WARNING|glassfish3.1.2|com.sun.grizzly.config.GrizzlyServiceListener|_ThreadID=27;_ThreadName=Thread-2;|GRIZZLY0023:
>
> Interrupting idle Thread: admin-thread-pool-4848(6).|#]
>
> If I cycle the log file before deploying I'll have a heap of these
> messages
> in there before anything starts to happen, on both successul and
> stalled (yet
> successful) deployments. The logs indicate a successful deployment in
> both
> cases.
>
> My previous install of 3.1.1 did not have these Grizzly log messages.
>
> Is there any potential reason for this behaviour, and any way to get
> rid of
> the Grizzly problem?
>
> Thanks,
> Geoff
>
>
> --
>
> [Message sent by forum member 'GeoffC']
>
> View Post: http://forums.java.net/node/884320
>
>