|
The connection factory is created and bound very early on, even before the deployment of the users archive.
Based on what I see here, the connection is not created for every request, simply retrieved, only the session is. Looking at the code for HSEARCH-668, the TX use case does seem to call createQueueConnection for every request and also seems like it would a JNDI lookup of the queue for every request. I think no longer eagerly initializing the CF and Queue object during initialize() is a good way to solve this, it just needs a little tweak so it doesn't create a connection or lookup the queue every time.
Something like, because in the case of the queue, being transnational is not relevant.
if ( jmsQueue == null ) {
return initializeJMSQueue( factory, props );
}
else {
return jmsQueue;
}
|
