Thanks,
We have the Http invoker layer working, but we are getting the following exception
when using the UIL2 invocation layer. It looks to be occurring when the client tries
to close the connection after sending the message. When we use the UIL invocation
layer, the exception does not occur. The client is a servlet that establishes a
connection each time, sends a message then closes out the connection. Are clients
only allowed to establish one connection with the UIL2 layer?
- Destroying failedjavax.jms.JMSException: The destination is being used.
at
org.jboss.mq.server.JMSDestinationManager.closeDestination(JMSDestinationManager.java:804)
at
org.jboss.mq.server.jmx.DestinationMBeanSupport.destroyService(DestinationMBeanSupport.java:122)
at org.jboss.system.ServiceMBeanSupport.destroy(ServiceMBeanSupport.java:271)
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:549)
at
org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:966)
at $Proxy11.destroy(Unknown Source)
at org.jboss.system.ServiceController.destroy(ServiceController.java:521)
at org.jboss.system.ServiceController.destroy(ServiceController.java:513)
at org.jboss.system.ServiceController.destroy(ServiceController.java:513)
at org.jboss.system.ServiceController.destroy(ServiceController.java:513)
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:549)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
at $Proxy5.destroy(Unknown Source)
at org.jboss.deployment.SARDeployer.destroy(SARDeployer.java:424)
at org.jboss.deployment.MainDeployer.destroy(MainDeployer.java:530)
at org.jboss.deployment.MainDeployer.undeploy(MainDeployer.java:481)
at org.jboss.deployment.MainDeployer.undeploy(MainDeployer.java:475)
at org.jboss.deployment.MainDeployer.undeploy(MainDeployer.java:448)
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:549)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
at $Proxy7.undeploy(Unknown Source)
at
org.jboss.deployment.scanner.URLDeploymentScanner.undeploy(URLDeploymentScanner.java:310)
at
org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:406)
at
org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:200)
at
org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:211)
at
org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:190)
-----Original Message-----
From: Sebastian Hauer [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 08, 2003 6:37 PM
To: [EMAIL PROTECTED]
Subject: RE: [JBoss-user] JMS behind a firewall.
Hi Billy,
You can tunnel all your RMI calls through HTTP/S, this would include
JNDI lookup calls. So you would only need one port for that and than use
something like UIL or better UIL2 for JMS which will also need just one
port.
We have a setup like this in production using JBoss 3.0.x.
Regards,
Sebastian
-------------------------------------------------------
This SF.Net email sponsored by: Parasoft
Error proof Web apps, automate testing & more.
Download & eval WebKing and get a free book.
www.parasoft.com/bulletproofapps
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
-------------------------------------------------------
This SF.Net email sponsored by: Parasoft
Error proof Web apps, automate testing & more.
Download & eval WebKing and get a free book.
www.parasoft.com/bulletproofapps
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
