ActiveMQ wasn't my decision and it's not easily changeable (politically).
It's hard to believe that no one would have run across this if it was a widespread problem given how many people are using ActiveMQ with JBoss. I'm guessing it's something with my configuration. Or...
Let me ask this a different way:
Does the CachedConnectionManager assume that a JMS connection created inside a method should always be closed when that method returns?
It's working fine with the CachedConnectionManager auto-close turned off so I don't think there's a fundamental problem with how I'm using JMS. I'm not seeing zombie JMS connections on the server.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4224530#4224530
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4224530
We are currently using Jboss 4 and we would like to migrate to Jboss 5. I have following questions:
1. Are there any issues that we need to be aware of during migration?
2. We use Mbean to stop Session and Message Beans. Message Beans are stopped using Delivery Active.
3. We use clustering and have Singleton Services
4. We use Caching
5. We use clustered beans
6. We use hibernate API
7. We use Jgroups
7. Jboss remoting
We probably use more services provided by Jboss but I was wondering what impact it would have, what kind of changes we need to make etc.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4224515#4224515
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4224515
