[esb-issues] [JBoss JIRA] Commented: (JBESB-2507) JMS JCA mapper sets maxMessages instead of maxSession

Tue May 19 04:34:05 EDT 2009

    [ https://jira.jboss.org/jira/browse/JBESB-2507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12468119#action_12468119 ] 

Kevin Conner commented on JBESB-2507:
-------------------------------------

We need to upgrade the base server at the same time to pull in the JBPAPP fix.

> JMS JCA mapper sets maxMessages instead of maxSession
> -----------------------------------------------------
>
>                 Key: JBESB-2507
>                 URL: https://jira.jboss.org/jira/browse/JBESB-2507
>             Project: JBoss ESB
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Transports
>    Affects Versions: 4.5
>            Reporter: Kevin Conner
>            Assignee: Kevin Conner
>             Fix For: 4.6
>
>
> The JMS/JCA adapter initialises some variables in the activation spec and, until now, mapped the max threads count onto maxMessages.
> This was the wrong attribute to specify but has worked so far due to a bug in the base app server jms-ra.rar code, now fixed in JBPAPP-1045.
> We should have been setting the maxSession attribute instead.

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