[JBoss JIRA] Created: (JBAS-4380) Deployers are not working when deploying/undeploying different JARS with the same name
1:45 p.m.
Deployers are not working when deploying/undeploying different JARS with the same name
--------------------------------------------------------------------------------------
Key: JBAS-4380
URL: http://jira.jboss.com/jira/browse/JBAS-4380
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: ClassLoading
Affects Versions: JBossAS-5.0.0.Beta3
Reporter: Clebert Suconic
Assigned To: Scott M Stark
Priority: Blocker
Fix For: JBossAS-5.0.0.Beta3
Suppose you have two distinct jars with the same name..
You deploy the first one (using deployers on JMX) and undeploy it.
You deploy the second one (using deployers on JMX again)... you will get an exception...
and the first jar will be deployed sometimes, as something is cached somewhere.
(I will add a replication test for this issue, and a description for how to do it)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:47 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-4380) Deployers are not working when deploying/undeploying different JARS with the same name
[ http://jira.jboss.com/jira/browse/JBAS-4380?page=all ]
Clebert Suconic updated JBAS-4380:
----------------------------------
Attachment: integration.zip
I'm using this modified version of jboss-messaging integration.
This is affecting some MDB tests but this issue would happen on any duplicated name jars.
Deployers are not working when deploying/undeploying different JARS
with the same name
--------------------------------------------------------------------------------------
Key: JBAS-4380
URL: http://jira.jboss.com/jira/browse/JBAS-4380
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: ClassLoading
Affects Versions: JBossAS-5.0.0.Beta3
Reporter: Clebert Suconic
Assigned To: Scott M Stark
Priority: Blocker
Fix For: JBossAS-5.0.0.Beta3
Attachments: integration.zip
Suppose you have two distinct jars with the same name..
You deploy the first one (using deployers on JMX) and undeploy it.
You deploy the second one (using deployers on JMX again)... you will get an exception...
and the first jar will be deployed sometimes, as something is cached somewhere.
(I will add a replication test for this issue, and a description for how to do it)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:54 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-4380) Deployers are not working when deploying/undeploying different JARS with the same name
[ http://jira.jboss.com/jira/browse/JBAS-4380?page=comments#action_12360739 ]
Clebert Suconic commented on JBAS-4380:
---------------------------------------
How to replicate this issue:
- unzip integration.zip
- Edit ./integration/build.properties and set jboss-home to a jboss-5 output.
- ant -f build-thirdparty.xml
- start jboss using default configuration.
$/trunk/build/output/jboss-5.0.0.Beta2/bin$ ./run.sh -c default
Now execute tests:
(I belive you need junit.jar at your ant/lib for this to work)
ant -Dtest-mask=TransactionedMDBTest run
ant -Dtest-mask=SimpleMDBTest run
(if you want to look at junit-report for this execute ant tests-report)
You should see an exception on JBoss console output:
2:50:46,286 ERROR [AbstractKernelController] Error installing to Create:
name=jboss.j2ee:jndiName=local/QueueAdapterA@29742564,service=EJB state=Configured
mode=Manual requiredState=Create
java.lang.ClassNotFoundException: No ClassLoaders found for:
org.jboss.test.jms.integration.support.ejb20.TestMessageDriven
at org.jboss.mx.loading.LoadMgr3.beginLoadTask(LoadMgr3.java:310)
at
org.jboss.mx.loading.UnifiedClassLoader.loadClassImpl(UnifiedClassLoader.java:290)
at
org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassLoader.java:409)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at
org.jboss.util.loading.DelegatingClassLoader.loadClass(DelegatingClassLoader.java:89)
at
org.jboss.mx.loading.LoaderRepositoryClassLoader.loadClass(LoaderRepositoryClassLoader.java:90)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at
org.jboss.util.loading.DelegatingClassLoader.loadClass(DelegatingClassLoader.java:89)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at org.jboss.ejb.Container.createService(Container.java:819)
at
org.jboss.ejb.MessageDrivenContainer.createService(MessageDrivenContainer.java:171)
at
org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:260)
at
org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:243)
at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:167)
at $Proxy0.create(Unknown Source)
at
org.jboss.system.microcontainer.CreateDestroyLifecycleAction.installAction(CreateDestroyLifecycleAction.java:42)
Deployers are not working when deploying/undeploying different JARS
with the same name
--------------------------------------------------------------------------------------
Key: JBAS-4380
URL: http://jira.jboss.com/jira/browse/JBAS-4380
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: ClassLoading
Affects Versions: JBossAS-5.0.0.Beta3
Reporter: Clebert Suconic
Assigned To: Scott M Stark
Priority: Blocker
Fix For: JBossAS-5.0.0.Beta3
Attachments: integration.zip
Suppose you have two distinct jars with the same name..
You deploy the first one (using deployers on JMX) and undeploy it.
You deploy the second one (using deployers on JMX again)... you will get an exception...
and the first jar will be deployed sometimes, as something is cached somewhere.
(I will add a replication test for this issue, and a description for how to do it)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:36 a.m.
New subject: [JBoss JIRA] Updated: (JBAS-4380) Deployers are not working when deploying/undeploying different JARS with the same name
[ http://jira.jboss.com/jira/browse/JBAS-4380?page=all ]
Scott M Stark updated JBAS-4380:
--------------------------------
JBoss Forum Reference:
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4042518
Deployers are not working when deploying/undeploying different JARS
with the same name
--------------------------------------------------------------------------------------
Key: JBAS-4380
URL: http://jira.jboss.com/jira/browse/JBAS-4380
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: ClassLoading
Affects Versions: JBossAS-5.0.0.Beta3
Reporter: Clebert Suconic
Assigned To: Scott M Stark
Priority: Blocker
Fix For: JBossAS-5.0.0.Beta3
Attachments: integration.zip
Suppose you have two distinct jars with the same name..
You deploy the first one (using deployers on JMX) and undeploy it.
You deploy the second one (using deployers on JMX again)... you will get an exception...
and the first jar will be deployed sometimes, as something is cached somewhere.
(I will add a replication test for this issue, and a description for how to do it)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:56 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-4380) Deployers are not working when deploying/undeploying different JARS with the same name
[ http://jira.jboss.com/jira/browse/JBAS-4380?page=all ]
Clebert Suconic updated JBAS-4380:
----------------------------------
Priority: Critical (was: Blocker)
Deployers are not working when deploying/undeploying different JARS
with the same name
--------------------------------------------------------------------------------------
Key: JBAS-4380
URL: http://jira.jboss.com/jira/browse/JBAS-4380
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: ClassLoading
Affects Versions: JBossAS-5.0.0.Beta3
Reporter: Clebert Suconic
Assigned To: Scott M Stark
Priority: Critical
Fix For: JBossAS-5.0.0.Beta3
Attachments: integration.zip
Suppose you have two distinct jars with the same name..
You deploy the first one (using deployers on JMX) and undeploy it.
You deploy the second one (using deployers on JMX again)... you will get an exception...
and the first jar will be deployed sometimes, as something is cached somewhere.
(I will add a replication test for this issue, and a description for how to do it)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:42 a.m.
New subject: [JBoss JIRA] Resolved: (JBAS-4380) Deployers are not working when deploying/undeploying different JARS with the same name
[ http://jira.jboss.com/jira/browse/JBAS-4380?page=all ]
Scott M Stark resolved JBAS-4380.
---------------------------------
Resolution: Won't Fix
Since this is not reproducible with jdk source, and we are moving away from the URLHandler
usage in the VFS, I'm marking this as won't fix.
Deployers are not working when deploying/undeploying different JARS
with the same name
--------------------------------------------------------------------------------------
Key: JBAS-4380
URL: http://jira.jboss.com/jira/browse/JBAS-4380
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: ClassLoading
Affects Versions: JBossAS-5.0.0.Beta3
Reporter: Clebert Suconic
Assigned To: Scott M Stark
Priority: Critical
Fix For: JBossAS-5.0.0.Beta3
Attachments: integration.zip
Suppose you have two distinct jars with the same name..
You deploy the first one (using deployers on JMX) and undeploy it.
You deploy the second one (using deployers on JMX again)... you will get an exception...
and the first jar will be deployed sometimes, as something is cached somewhere.
(I will add a replication test for this issue, and a description for how to do it)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6587
days inactive
6734
days old
5 comments
2 participants
participants (2)
-
Clebert Suconic (JIRA) -
Scott M Stark (JIRA)