This sounds to me like a misbehaving connection pool. Maybe jax-jms has a bug?
I'd try to get a count of open and recently-closed sockets on the client host (e.g. via netstat) to try to confirm that. If you see tens of thousands, you'll want to try to dig into why they're being closed and re-opened rather than just reused. Tim On Mon, Jun 3, 2019, 1:55 AM cooshal <kushal.gau...@gmail.com> wrote: > Hi again: > > has anyone encountered and resolved similar issue ? > > My activemq configuration has the default stuffs. Should I configure > something there as well? > > After I update my pax-jms configuration by adding pool=transx, I get > following log events: > > INFO Updating configuration from org.ops4j.connectionfactory-consumer.cfg > 09:48:10.597 INFO [CM Configuration Updater (Update: > pid=org.ops4j.connectionfactory.34183829-76f2-4bf7-8209-c265780d57b9)] Lost > service dependency: > > (&(objectClass=org.ops4j.pax.jms.service.ConnectionFactoryFactory)(type=activemq)) > 09:48:10.611 INFO [CM Configuration Updater (Update: > pid=org.ops4j.connectionfactory.34183829-76f2-4bf7-8209-c265780d57b9)] > Waiting for service dependency: > > (&(objectClass=org.ops4j.pax.jms.service.PooledConnectionFactoryFactory)(pool=transx)(xa=false)) > > It would be great if somebody could point me to some direction in resolving > this issue. > > Regards, > Cooshal. > > > > -- > Sent from: > http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html >
