[JBoss-dev] [ jboss-Bugs-909896 ] Can't undeploy destination with open connections

[SourceForge.net <no...@so...>]

Bugs item #909896, was opened at 2004-03-04 16:15
Message generated for change (Comment added) made by ejort
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=909896&group_id=22866

Category: JBossMQ
Group: v3.2
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Tim McCune (javajedi)
>Assigned to: Adrian Brock (ejort)
Summary: Can't undeploy destination with open connections

Initial Comment:
Undeploying a JMS destination with open client
connections fails with the following exception:

2004-03-03 15:06:34,938 ERROR
[org.jboss.mq.server.jmx.Queue.TestWork] Destroying failed
javax.jms.JMSException: The destination is being used.
at
org.jboss.mq.server.JMSDestinationManager.closeDestination(JMSDestinationManager.java:807)
at
org.jboss.mq.server.jmx.DestinationMBeanSupport.destroyService(DestinationMBeanSupport.java:142)
at
org.jboss.system.ServiceMBeanSupport.destroy(ServiceMBeanSupport.java:284)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546)
at
org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:976)
at $Proxy40.destroy(Unknown Source)
at
org.jboss.system.ServiceController.destroy(ServiceController.java:531)
at sun.reflect.GeneratedMethodAccessor48.invoke(Unknown
Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546)
at
org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
at $Proxy4.destroy(Unknown Source)
at
org.jboss.deployment.SARDeployer.destroy(SARDeployer.java:408)
at
org.jboss.deployment.MainDeployer.destroy(MainDeployer.java:522)
at
org.jboss.deployment.MainDeployer.destroy(MainDeployer.java:538)
at
org.jboss.deployment.MainDeployer.undeploy(MainDeployer.java:473)
at
org.jboss.deployment.MainDeployer.undeploy(MainDeployer.java:467)
at
org.jboss.deployment.MainDeployer.undeploy(MainDeployer.java:440)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546)
at
org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
at $Proxy38.undeploy(Unknown Source)
at
org.jboss.deployment.scanner.URLDeploymentScanner.undeploy(URLDeploymentScanner.java:332)
at
org.jboss.ha.framework.server.FarmMemberService.undeploy(FarmMemberService.java:434)
at
org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:452)
at
org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:201)
at
org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:212)
at
org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:191)


Instead of throwing an exception, the destination
should just close the open connections.

----------------------------------------------------------------------

>Comment By: Adrian Brock (ejort)
Date: 2004-03-15 17:59

Message:
Logged In: YES 
user_id=9459

This has been fixed for 3.2.4RC2

Regards,
Adrian

----------------------------------------------------------------------

Comment By: Adrian Brock (ejort)
Date: 2004-03-05 12:55

Message:
Logged In: YES 
user_id=9459

It should not close the connections, it should remove the
client's
subscription.
The client may have other subscriptions that are still valid.

Regards,
Adrian

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=909896&group_id=22866