I know that ActiveMQ doesn't cover all JMS 2.0 specification.
Could you tell me, please, how far ActiveMQ is close to JMS 2.0 ?
I am asking this question because I am using TomEE 8.0.0 or 8.0.1 with ActiveMQ 5.15.10 embedded.
In an stateless EJB, I inject JMSContext (working) and in a method, I have the following code:
The issue I have is that each time I send a text message a DynamicProducer is created which could be the root cause of a memory leak.
But I also don't get that, according to the JMS 2.0 specification, the JMSContext injected has a Transaction scope => this mean that after the end of the method, the JMSContext should be closed so that the dynamic producer.
Do you agree with the behavior described above. If so, Is it an ActiveMQ issue or a TomEE issue ?
I notice you're using TomEE, and asked on the TomEE mailing list. TomEE
uses ActiveMQ 5, and provides a bridge for the JMS 2.0 functionality you're
using. The issue is more likely on the TomEE side, and I'll follow up there.
On Mon, Feb 10, 2020 at 8:11 AM COURTAULT Francois <
[hidden email]> wrote: