The usage is within a servlet request (user performs an action that queues a message) so leaving the producer open would result in the resources leaking. Or am I misunderstanding what you mean?
I'm finding that if my message data length exceed 952 bytes when enqueueing a message to WMQ 7, the performance of javax.jms.MessageProducer.close() suffers. When the length is 952 bytes, the method ...
I'm using Websphere MQ 7.0.1.0 and connecting JavaEE Message Driven
Beans to it from Glassfish 2.1 using IBM's JCA adapter. Â I have a
cluster of 4 Glassfish servers running an MDB (400 pooled ins ...