Yes, these are traces from the AMX layer, which is still in
development mode, regardless of the fact that it is TP2.
They can be disabled.
On Apr 21, 2008, at 9:33 PM, Ludovic Champenois wrote:
> Deploy a web app from the b10 v3 build, Log file contains:
>
>
> INFO: AMXConfigLoader.sortAndDispatch: 2 events
> Apr 21, 2008 9:29:14 PM com.sun.enterprise.web.WebApplication start
> INFO: Loading application ttt-java at /ttt-java
> Apr 21, 2008 9:29:14 PM
> com.sun.enterprise.v3.deployment.DeployCommand execute
> INFO: Deployment of ttt-java done is 60 ms
> Apr 21, 2008 9:29:14 PM INFO: AMXConfigLoader.sortAndDispatch: 14
> events
> Apr 21, 2008 9:29:14 PM INFO: AMXConfigLoader.sortAndDispatch:
> process new ConfigBean: com.sun.enterprise.config.serverbeans.Engine
> Apr 21, 2008 9:29:14 PM INFO: AMXConfigLoader.sortAndDispatch:
> process new ConfigBean: com.sun.enterprise.config.serverbeans.Engine
> Apr 21, 2008 9:29:14 PM INFO: AMXConfigLoader.sortAndDispatch:
> process new ConfigBean:
> com.sun.enterprise.config.serverbeans.ApplicationRef
> Apr 21, 2008 9:29:14 PM INFO: AMXConfigLoader.sortAndDispatch:
> process new ConfigBean:
> com.sun.enterprise.config.serverbeans.Application
>
> It seems to be traces for the V3 internal developer, not the V3
> user...
>
> Do we plan to do a log cleanup in the final TP2 bits?
>
> Ludo
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>
---
Lloyd L Chambers
lloyd.chambers_at_sun.com
Sun Microsystems, Inc