You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Charles Souillard (JIRA)" <ji...@apache.org> on 2006/04/04 07:52:58 UTC

[jira] Created: (SM-378) JMS sessions are not singleThread

JMS sessions are not singleThread
---------------------------------

         Key: SM-378
         URL: https://issues.apache.org/activemq/browse/SM-378
     Project: ServiceMix
        Type: Bug

  Components: servicemix-jms  
    Versions: incubation    
    Reporter: Charles Souillard


MultiplexingProviderProcessor classes creates a jms session in the doStart method (deployment time : Thread 1) and reuses this one at execution time (Thread 2). This is not JMS compliant. JMS sessions must be created just before using them and closed before the end of the thread.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

Re: [jira] Resolved: (SM-378) JMS sessions are not singleThread

Posted by Charles Souillard <Ch...@ext.bull.net>.
Thank you very much Guillaume !!!
My test is now successfull without any source code modification.

It is a real pleasure to work on a project with a guys like you !

Charles

Guillaume Nodet (JIRA) wrote:
>      [ https://issues.apache.org/activemq/browse/SM-378?page=all ]
>      
> Guillaume Nodet resolved SM-378:
> --------------------------------
>
>     Fix Version: 3.0-M1
>      Resolution: Fixed
>       Assign To: Guillaume Nodet
>
> Adding the processorName="standard" attribute to the jms endpoint should now work.
> This can also be configured on the component using a jmx console to change the processorName attribute on the jms component configuration mbean.
>
> Author: gnodet
> Date: Wed Apr  5 13:46:49 2006
> New Revision: 391800
>
> URL: http://svn.apache.org/viewcvs?rev=391800&view=rev
> Log:
> SM-378: Add a fully JMS compliant processor set
>
> Added:
>     incubator/servicemix/trunk/servicemix-jms/src/main/java/org/apache/servicemix/jms/standard/
>     incubator/servicemix/trunk/servicemix-jms/src/main/java/org/apache/servicemix/jms/standard/StandardConsumerProcessor.java
>     incubator/servicemix/trunk/servicemix-jms/src/main/java/org/apache/servicemix/jms/standard/StandardProviderProcessor.java
>     incubator/servicemix/trunk/servicemix-jms/src/main/resources/META-INF/services/org/apache/servicemix/jms/standard
>
>
>
>   
>> JMS sessions are not singleThread
>> ---------------------------------
>>
>>          Key: SM-378
>>          URL: https://issues.apache.org/activemq/browse/SM-378
>>      Project: ServiceMix
>>         Type: Bug
>>     
>
>   
>>   Components: servicemix-jms
>>     Versions: incubation
>>     Reporter: Charles Souillard
>>     Assignee: Guillaume Nodet
>>      Fix For: 3.0-M1
>>     
>
>   
>> Original Estimate: 1 hour
>>         Remaining: 1 hour
>>
>> MultiplexingProviderProcessor classes creates a jms session in the doStart method (deployment time : Thread 1) and reuses this one at execution time (Thread 2). This is not JMS compliant. JMS sessions must be created just before using them and closed before the end of the thread.
>>     
>
>

[jira] Resolved: (SM-378) JMS sessions are not singleThread

Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/SM-378?page=all ]
     
Guillaume Nodet resolved SM-378:
--------------------------------

    Fix Version: 3.0-M1
     Resolution: Fixed
      Assign To: Guillaume Nodet

Adding the processorName="standard" attribute to the jms endpoint should now work.
This can also be configured on the component using a jmx console to change the processorName attribute on the jms component configuration mbean.

Author: gnodet
Date: Wed Apr  5 13:46:49 2006
New Revision: 391800

URL: http://svn.apache.org/viewcvs?rev=391800&view=rev
Log:
SM-378: Add a fully JMS compliant processor set

Added:
    incubator/servicemix/trunk/servicemix-jms/src/main/java/org/apache/servicemix/jms/standard/
    incubator/servicemix/trunk/servicemix-jms/src/main/java/org/apache/servicemix/jms/standard/StandardConsumerProcessor.java
    incubator/servicemix/trunk/servicemix-jms/src/main/java/org/apache/servicemix/jms/standard/StandardProviderProcessor.java
    incubator/servicemix/trunk/servicemix-jms/src/main/resources/META-INF/services/org/apache/servicemix/jms/standard



> JMS sessions are not singleThread
> ---------------------------------
>
>          Key: SM-378
>          URL: https://issues.apache.org/activemq/browse/SM-378
>      Project: ServiceMix
>         Type: Bug

>   Components: servicemix-jms
>     Versions: incubation
>     Reporter: Charles Souillard
>     Assignee: Guillaume Nodet
>      Fix For: 3.0-M1

>
> Original Estimate: 1 hour
>         Remaining: 1 hour
>
> MultiplexingProviderProcessor classes creates a jms session in the doStart method (deployment time : Thread 1) and reuses this one at execution time (Thread 2). This is not JMS compliant. JMS sessions must be created just before using them and closed before the end of the thread.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira