So can you show the server.log
You should see this message from the ServiceController
when you redeploy B:
// Remove the context, unless it is still recording
dependencies
if (ctx.dependsOnMe.size() == 0)
nameToServiceMap.remove(objectName);
else
{
log.debug("Context not removed, it is recording " +
"dependencies: " + ctx);
ctx.proxy = null;
}
There is are tests for this in the JMX part of the testsuite.
On Thu, 2006-02-02 at 09:20, Bill Burke wrote:
> Adrian Brock wrote:
> > On Wed, 2006-02-01 at 16:42, Bill Burke wrote:
> >
> >>I'm seeing start being
> >>called twice for a particular MBean and thus, I'm getting an error. I
> >>think what is happening is this:
> >>
> >>1. deploy 'A' MBean, its dependency 'B' has not been resolved
> >>2. Deploy 'B', resolve 'A''s dependency, call create/start
> >>3. Undeploy 'B'
> >>4. Deploy 'B'
> >>
> >>Is this the correct behavior? Is the 4.0.4 kernel attempting to do
> >>redploys correct?
> >
> >
> > It doesn't sound like correct behaviour to me. :-)
> > Do you know what is triggering the "undeploy"?
> >
>
>
> :) Yes, my test code! I'm testing to make sure dependencies work.
--
xxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss Inc.
xxxxxxxxxxxxxxxxxxxxxxxx
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
