Bug 778845 (SOA-1289) - JBESB: JMS JCA mapper sets maxMessages instead of maxSession
Summary: JBESB: JMS JCA mapper sets maxMessages instead of maxSession
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-1289
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: JBossESB
Version: 4.2 CP03
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.2 CP04
Assignee: Kevin Conner
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-04-17 13:52 UTC by Kevin Conner
Modified: 2009-06-15 12:59 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-06-15 12:59:18 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-1289 0 None None None Never

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
Note You need to log in before you can comment on or make changes to this bug.