JMS JCA mapper sets maxMessages instead of maxSession
-----------------------------------------------------
Key: JBESB-2509
URL:
https://jira.jboss.org/jira/browse/JBESB-2509
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Transports
Affects Versions: 4.2.1 CP4
Reporter: Kevin Conner
Assignee: Kevin Conner
Fix For: 4.2.1 CP5
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: