-
15. Re: Warning in standalone esb client with messaging
The ESB is a distributed piece of software, your "client" is just one node. So it is the container for all it cares. So it comes with it's own connection pools. Someone will need to close those on shutdown.
--Kurt -
16. Re: Warning in standalone esb client with messaging
Hi Kurt,
For example, 2 clients are using a same esb application. When the first client finish, it call JmsConnectionPoolContainer.removeAllPools(). This won´t affect the second client?
Is there a way close only the connection of specificy client?
If I don´t add JmsConnectionPoolContainer.removeAllPools() before first client finish I get the warning in jboss console.
Thanks -
17. Re: Warning in standalone esb client with messaging
Yes these pools are running on each client.
-some background info-
When you specify a service destination, it goes and looks up the EPR in the registry, it then goes and uses the esb internals to send that message over the right protocol of to its destination. These internals setup a JmsConnectionPool (if JMS is used). So basically this client is a lightweight esb node (just for sending).
--Kurt -