Bugs item #610223, was opened at 2002-09-16 23:49
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=610223&group_id=22866
Category: JBossMX
Group: v3.2
Status: Open
Resolution: Accepted
Priority: 7
Submitted By: Michael Bartmann (bartmann)
Assigned to: David Jencks (d_jencks)
Summary: Classloader NPE in dependent redeploy
Initial Comment:
There is a problem under 3.2 when
redeploying an ear with several dependent ears.
When redeploying the dependent ears "manually"
everything works ok.
When instead I redeploy the ear they depend on, they
get re-created,
but after the destroy nulled their classloader.
This results in an NPE during redeployment.
Tested under Branch_3_2, checkout 16.09.2002.
OS Windows NT 4.0, JDK 1.4.0_01
----------------------------------------------------------------------
>Comment By: Michael Bartmann (bartmann)
Date: 2002-09-17 07:14
Message:
Logged In: YES
user_id=69300
Below comes the blurb from jboss.xml. Only the MDB in the
dependent ear is declared to be dependent of the "common" ear.
Each of the dependent ears also contains a custom JMSProvider
with its container-configuration. Did I mention that all my
ears have
their own scope?
BTW: Starting any stoping the contained JMSProvider through JMX
is another problem, cause the server doesn't provide the correct
TCL when calling the management methods from remote.
But in the bug we are just discussing this is no problem,
cause the
JMSProvider is not restarted.
<message-driven>
<ejb-name>ACTControlSystemReceiver</ejb-name>
<configuration-name>ACT Message Driven
Bean</configuration-name>
<destination-jndi-name>queue/ACTFLS</destination-jndi-name>
<mdb-user>FLS</mdb-user>
<mdb-passwd>geheim</mdb-passwd>
<ejb-ref>
<ejb-ref-name>ejb/ControlSystemManager</ejb-ref-name>
<jndi-name>transport/ControlSystemManager</jndi-name>
</ejb-ref>
<depends>fs4p.act:service=MS4PMessageService</depends>
<depends>fs4p.act:service=JMSProviderLoader,name=ACTJMSProvider</depends>
<depends>fs4p.act:service=ServerSessionPoolMBean,name=ACTJMSPool</depends>
<depends>jboss.j2ee:service=EJB,jndiName=transport/ControlSystemManager</depends>
<depends>jboss.j2ee:service=EJB,jndiName=material/Material</depends>
</message-driven>
----------------------------------------------------------------------
Comment By: David Jencks (d_jencks)
Date: 2002-09-17 00:26
Message:
Logged In: YES
user_id=60525
I see what causes some of the problem, I think it shows up
if you stop, destroy, create, and start an ejb through the
jmx console. However, could you be more specific about how
you are specifying the dependency between the ears? I'm not
quite sure why the references to the containers in the
dependent .ear are getting saved.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=610223&group_id=22866
-------------------------------------------------------
Sponsored by: AMD - Your access to the experts on Hammer Technology!
Open Source & Linux Developers, register now for the AMD Developer
Symposium. Code: EX8664 http://www.developwithamd.com/developerlab
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
