Even simpler than that - re-hot-deploying (i.e. copying into /deploy/, removing and 
recopying) will cause these errors.

I guess some MBeans that should be destroyed on an undeploy are not getting cleaned up.



Jules


Julian Gosnell wrote:

> These were not caused by the update, I just rolled back.
>
> They occr when I hot-deploy (copy into /deploy) the ear, the run the WebIntegration 
>testsuite (does this use the jmx deployer?), then redeploy the ear.
>
> Jules
>
> Julian Gosnell wrote:
>
> > I just updated, and don't think these are mine - I get them when
> > hot-deploying jbosstest-web.ear from the testsuite....
> >
> > Anyone recognise them as their own ?
> >
> > Jules
> >
> > 23:32:41,788 ERROR [EjbModule] Could not create JSR-77 EjbModule:
> > jbosstest-web.ear
> > javax.management.MBeanException: Exception thrown in the MBean's
> > constructor
> >  at
> > 
>com.sun.management.jmx.MBeanServerImpl.internal_instantiate(MBeanServerImpl.java:2229)
> >
> >  at
> > com.sun.management.jmx.MBeanServerImpl.createMBean(MBeanServerImpl.java:627)
>
> ...snip....
>
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-development


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to