Bug 778845 (SOA-1289)

Summary: JBESB: JMS JCA mapper sets maxMessages instead of maxSession
Product: [JBoss] JBoss Enterprise SOA Platform 4 Reporter: Kevin Conner <kevin.conner>
Component: JBossESBAssignee: Kevin Conner <kevin.conner>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 4.2 CP03   
Target Milestone: ---   
Target Release: 4.2 CP04   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-1289
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-06-15 12:59:18 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Kevin Conner 2009-04-17 13:52:55 UTC 
Date of First Response: 2009-06-04 03:47:08
project_key: SOA

Platform issue for JBESB-2509
Comment 1 Kevin Conner 2009-04-17 13:53:33 UTC 
Link: Added: This issue depends JBESB-2509
Comment 2 Kevin Conner 2009-04-17 13:55:06 UTC 
Fix applied to ESB branch, will be in next merge to platform.
Comment 3 Dana Mison 2009-06-04 07:47:08 UTC 
Release Notes:

The JMS/JCA adapter (JmsListenerMapper) now maps the maximum thread count variable onto the maxSession attribute.  Previously it was incorrectly being mapped onto the maxMessages attribute.
Comment 4 Kevin Conner 2009-06-15 12:59:18 UTC 
Verified present in CP04