Hi all, I haven't seen connection pool in the new JMS implementation. However, the current JMS implementation uses connectors within which vendor-specific pool is checked and created if found none.
Also, as far as I've seen from the new JMS implementation code, each time a request is made - Initial context is created - Connection factory is retrieved from the JNDI - A new connection is created Are these, somehow, normal/expected behaviour? If yes, shouldn't we expect it become slower than the current implementation? Could someone please shed some light on JMS implementations? Regards, Ali Sadik Kumlali --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
