Hello there,
Is there any way of deleting a durable subscription from an existing topic via
JMX console?
I'm looking for an MBean operation that allows me to delete a durable
subscription in case a faulty JMS client forgot to close it when it was no
longer needed.
I'm using JBoss AS 4.2.3.GA
Shame :-(
Thanks for the quick reply.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4268982#4268982
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4268982
___
jboss-user mailing
Hello Ron,
Thank you for your quick response!
I have downloaded Remoting release 2.2.3.SP1 and replace the existing one in my
standalone client and in JBoss As 4.2.3.GA server's libs (in the server
configuration for JBoss Messaging 1.4.4.GA)
I have configured remoting-bisocket-service.xml
Hello Ron,
Please ignore my last post. Ping is sent on that port and firewall does not
time it out.
Thank you for help!
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4258129#4258129
Reply to the post :
Hello there.
I've duplicated this post here from the Messaging forum
(http://www.jboss.org/index.html?module=bbop=viewtopict=161838) in case it
fits better in this one.
We are running Jboss AS 4.2.3.GA with JBoss Messaging 1.4.4.GA on one box
behind a firewall, and we are connecting to one
Just to give a bit of more information, once the port TCP 4458 times out at the
firewall and a new message comes in, this is what we get in the trace file
| 762021 [Timer-1] TRACE org.jboss.remoting.MicroRemoteClientInvoker -
SocketClientInvoker[a89ce3, bisocket://192.168.6.1:4457] received
Hello there,
We are running Jboss AS 4.2.3.GA with JBoss Messaging 1.4.4.GA on one box
behind a firewall, and we are connecting to one of the topics in the server
using a stand alone client running on a different box.
In remoting-bisocket-service.xm we have configured the secondaryBindPort to
Hello there,
I'm running JBoss 4.2.3 GA default server (no mods) and have a EJB 2.1 bean
deployed in it. Have created a stand-alone remote client to access the bean.
The client tries to do exactly the same as discussed in this post, that is, it
only depends the jar file containing the bean
