You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by "François Courtault (Jira)" <ji...@apache.org> on 2020/04/01 11:20:00 UTC

[jira] [Commented] (TOMEE-2770) ActiveMQ dynamic producer not destroyed

    [ https://issues.apache.org/jira/browse/TOMEE-2770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17072661#comment-17072661 ] 

François Courtault commented on TOMEE-2770:
-------------------------------------------

Hello Jonathan,

 

Forget to add the following line in the sample I have provided to you:

{color:#808000}@TransactionAttribute{color}(TransactionAttributeType.{color:#660e7a}NEVER{color})

Using JConsole, you will see that the number of dynamicProducer increases at each GET call.

 

> ActiveMQ dynamic producer not destroyed
> ---------------------------------------
>
>                 Key: TOMEE-2770
>                 URL: https://issues.apache.org/jira/browse/TOMEE-2770
>             Project: TomEE
>          Issue Type: Bug
>          Components: TomEE Core Server
>    Affects Versions: 8.0.0-Final, 8.0.1
>            Reporter: François Courtault
>            Priority: Blocker
>
> Hello,
> In an stateless EJB, I inject JMSContext (working) and in a method, I have the following code:
>     *jmsContext*.createProducer().send(*messageQueue*, *jmsContext*.createTextMessage(*"Test"*));
> 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.
> I don’t get that because, 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: this is not I am seing :(
>  
> Best Regards.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)