Using release version 3.0, I have a file, 40-user-service.xml, which
contains deployment instructions for a series of MBeans. I declare its
dependency on a jar file like so:
<classpath codebase="deploy" archives="allocations.jar"/>
If I roll out a new version of allocations.jar in my build process, it
shuts down all of the dependent MBeans, but it will not restart them. (On
the other hand, if I touch 40-user-service.xml, it successfully stops and
restarts all of the MBeans)
Question #1: Why won't my MBeans restart when a new version of
allocations.jar is rolled out?
I also have a file called 30-Allocation.ear. It contains a set of EJBs that
use the classes in allocations.jar. If I touch or replace the .ear file, it
inexplicably attempts to reploy all of my (already started) MBeans,
resulting in exceptions like this:
13:11:59,691 INFO [ServiceController] Exception when trying to deploy
waiting mbean<mbean name="Allocations:service=AllocationRequestCache" code
="com.duke.realtime.model.flowinggas.AllocationRequestCache"><attribute
name="ExpirationMinutes">0</attribute></mbean>
org.jboss.deployment.DeploymentException: Trying to install an already
registered mbean: Allocations:service=AllocationRequestCache
Everything ends up redeploying correctly, it's just that these ugly
exceptions end up all over my log.
Question #2: Why would redeploying the .ear file by itself cause a
re-deploy of my MBeans, when I have not declared any explicit relationship
between my EJB's and my MBeans?
Thanks,
Corby
----------------------------------------------------------------------------
Bringing you mounds of caffeinated joy
>>> http://thinkgeek.com/sf <<<
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
