I haven't updated yet today, but does a thread dump reveal what the
server is doing?
Does this happen reliably? I ask because there is a corner case in
which the file is in the process of being copied when the autodeployer
runs and tries to autodeploy the file. There is logic to handle this
case which will (as a side effect) report an unrecognized module type in
the server log but then in a subsequent attempt the autodeployment
should succeed - once the file copy operation has completed. But unless
you are copying a large file from a remote system it's unlikely you'd
hit this very often.
- Tim
Bobby Bissett wrote:
> I just updated this morning, and while trying to debug a failing
> compatibility test I'm seeing the server hang during deployment. (Or
> at least hang for 120 seconds till the test times out.)
>
> The log looks normal until this:
>
> [#|2009-10-20T11:20:49.314-0400|INFO|glassfish|null|_ThreadID=27;_ThreadName=Thread-3;|DOL
> Loading time470|#]
>
> [#|2009-10-20T11:20:52.280-0400|INFO|glassfish|javax.enterprise.system.core.transaction.com.sun.jts.CosTransactions|_ThreadID=27;_ThreadName=Thread-3;|JTS5014:
> Recoverable JTS instance, serverId = [3699]|#]
>
> Then it just stops and deployment doesn't complete. I'm deploying by
> copying the ear to the autodeploy directory. After doing that and
> seeing the server log hang with the above message for 5 minutes, I
> check the admin console and do not see the app listed. (I also see a
> ton of errors in the log related to admin console, but that's another
> issue I'll check.) Is there a known issue with deployment right now?
>
> Thanks,
> Bobby
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>