Exceptions in re-deploying on 3.2.2 final release

[rdefalco]

When I redeploy an application in jboss (jetty and tomcat) I have the following exceptions (same for all my ejbjars and wars). This worked with 3.2.1. Do JBoss 3.2.2 enforce some validations on j2ee xml descriptors that were not in 3.2.1 ? What "is not regsitered" means ?
Do not know, if this has something to do, but i noticed that my ejbs and webapps appears multiple time in jboss console.

16:51:55,562 INFO [EARDeployer] Init J2EE application: file:/C:/jboss-3.2.2_jetty-4.2.11/server/default/deploy/openserv
er.ear
16:51:58,640 ERROR [STDERR] javax.management.InstanceNotFoundException: jboss.management.local:J2EEApplication=openserve
r.ear,J2EEServer=Local,j2eeType=EJBModule,name=configurationmanager-ejb.jar is not registered.
16:51:58,656 ERROR [STDERR] at org.jboss.mx.server.registry.BasicMBeanRegistry.get(BasicMBeanRegistry.java:354)
16:51:58,656 ERROR [STDERR] at org.jboss.mx.server.MBeanServerImpl.getMBeanInfo(MBeanServerImpl.java:557)
16:51:58,656 ERROR [STDERR] at org.jboss.console.plugins.JSR77Lister.createDeployedObjects(JSR77Lister.java:172)
16:51:58,671 ERROR [STDERR] at org.jboss.console.plugins.JSR77Lister.createServer(JSR77Lister.java:197)
16:51:58,671 ERROR [STDERR] at org.jboss.console.plugins.JSR77Lister.createServers(JSR77Lister.java:223)
16:51:58,671 ERROR [STDERR] at org.jboss.console.plugins.JSR77Lister.createDomain(JSR77Lister.java:237)
16:51:58,671 ERROR [STDERR] at org.jboss.console.plugins.JSR77Lister.createDomains(JSR77Lister.java:255)
16:51:58,687 ERROR [STDERR] at org.jboss.console.plugins.JSR77Lister.getTreeForResource(JSR77Lister.java:265)
16:51:58,687 ERROR [STDERR] at org.jboss.console.plugins.helpers.AbstractPluginWrapper.getSubTreeForResource(Abstrac
tPluginWrapper.java:201)
16:51:58,687 ERROR [STDERR] at org.jboss.console.manager.PluginManager.getTreesForResource(PluginManager.java:392)
16:51:58,687 ERROR [STDERR] at org.jboss.console.manager.PluginManager.getTreeForProfile(PluginManager.java:192)
16:51:58,703 ERROR [STDERR] at org.jboss.console.manager.PluginManager.getUpdateTreeForProfile(PluginManager.java:27
5)
16:51:58,703 ERROR [STDERR] at sun.reflect.GeneratedMethodAccessor87.invoke(Unknown Source)
16:51:58,703 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

16:51:58,718 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:324)
16:51:58,718 ERROR [STDERR] at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java
:284)
16:51:58,718 ERROR [STDERR] at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546)
16:51:58,734 ERROR [STDERR] at org.jboss.console.remote.InvokerServlet.processRequest(InvokerServlet.java:86)
16:51:58,953 ERROR [STDERR] at org.jboss.console.remote.InvokerServlet.doPost(InvokerServlet.java:123)
16:51:58,953 ERROR [STDERR] at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
16:51:58,953 ERROR [STDERR] at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
16:51:58,953 ERROR [STDERR] at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:356)
16:51:58,953 ERROR [STDERR] at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:2
94)
16:51:58,968 ERROR [STDERR] at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:567)
16:51:58,968 ERROR [STDERR] at org.mortbay.http.HttpContext.handle(HttpContext.java:1723)
16:51:58,968 ERROR [STDERR] at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:514
)
16:51:58,984 ERROR [STDERR] at org.mortbay.http.HttpContext.handle(HttpContext.java:1673)
16:51:58,984 ERROR [STDERR] at org.mortbay.http.HttpServer.service(HttpServer.java:879)
16:51:58,984 ERROR [STDERR] at org.jboss.jetty.Jetty.service(Jetty.java:459)
16:51:58,984 ERROR [STDERR] at org.mortbay.http.HttpConnection.service(HttpConnection.java:783)
16:51:59,000 ERROR [STDERR] at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:945)
16:51:59,000 ERROR [STDERR] at org.mortbay.http.HttpConnection.handle(HttpConnection.java:800)
16:51:59,000 ERROR [STDERR] at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:201)
16:51:59,000 ERROR [STDERR] at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:289)
16:51:59,015 ERROR [STDERR] at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:454)

[adrian.brock]

This is JSR77 looking for the ejb deployment.

There should be a previous error showing you why the
ejb didn't deploy.

Regards,
Adrian

[rdefalco]

Adrian, this is strange because at start time the deployment just go fine. It's when I redeploy with copying my.ear in deploy directory that things go bad. Whe I redeploy, undeploy seems to be ok and then the exceptions starts on some modules (not always the same), i did not notice in the log that something went wrong before it breaks.
It breaks but it works :-), i.e my app just run fine with the new deployed ear.
Anyway, don't know if it has a side effect but i use commit option A on all my entity bean, as it is supported on 3.2.2 (which, BTW, is great).

I've attached to this post two DEBUG server.log : one with a normal start --> deployment is ok, and one with the log starting with re-deployemnt of the same ear (ie copy of the file in deploy) --> exceptions.

Thank you for any clues,

Richard

[adrian.brock]

Actually, looking more carefully at the stacktrace
this is the web-console refreshing the info for an ejb
that has just been undeployed.

Post a bug at www.sf.net/projects/jboss,
but it is really just noise.

Regards,
Adrian

[rdefalco]

done, bug 833668.

Richard