July 2009 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-2660) Remove Smooks Shutdown Hook removal AOP

by Tom Fennelly (JIRA)

Remove Smooks Shutdown Hook removal AOP --------------------------------------- Key: JBESB-2660 URL: https://jira.jboss.org/jira/browse/JBESB-2660 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Transformation Service Reporter: Tom Fennelly Fix For: 4.6 Some AOP code was added to disable the Smooks Shutdown Hook (pre Smooks v1.2). This Shutdown Hook was removed in Smooks v1.2, so this AOP code can now be removed. -- 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

16 years, 10 months

2
2
0 / 0

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

by Kevin Conner (JIRA)

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

16 years, 10 months

1
4
0 / 0

[JBoss JIRA] Created: (JBESB-2681) InVMCourier pickup notifies waiting threads

by Kevin Conner (JIRA)

InVMCourier pickup notifies waiting threads ------------------------------------------- Key: JBESB-2681 URL: https://jira.jboss.org/jira/browse/JBESB-2681 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.4 CP2 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.4 CP3 The pickup method of the InVMCourier issues a notify when returning from the invocation. The consequence is that a different InVMCourier pickup is then told to terminate early. An increase in the number of listeners causes, in essence, a busy wait to occur as each thread notifies the subsequent one. -- 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

16 years, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-2680) Handle JBM client/server mismatch through delivery

by Kevin Conner (JIRA)

Handle JBM client/server mismatch through delivery -------------------------------------------------- Key: JBESB-2680 URL: https://jira.jboss.org/jira/browse/JBESB-2680 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.4 CP2 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.4 CP3 -- 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

16 years, 10 months

1
2
0 / 0

[JBoss JIRA] Closed: (JBESB-2679) JmsConnectionPool no longer recovers connection

by Kevin Conner (JIRA)

[ https://jira.jboss.org/jira/browse/JBESB-2679?page=com.atlassian.jira.plu... ] Kevin Conner closed JBESB-2679. ------------------------------- Resolution: Done Updated in revision 27572. > JmsConnectionPool no longer recovers connection > ----------------------------------------------- > > Key: JBESB-2679 > URL: https://jira.jboss.org/jira/browse/JBESB-2679 > 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 > > > Cleaning the session pool previously cleared out the pool information, finally closing down the connection. A new attempt to acquire a session would have re-established the missing connection. > The session handling has been moved to a new class but the connection creation is still in the original. We need to move this under the new class so that missing connections can be re-established. -- 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

16 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-2678) JmsConnectionPool getSession method should clean pool on error

by Kevin Conner (JIRA)

JmsConnectionPool getSession method should clean pool on error -------------------------------------------------------------- Key: JBESB-2678 URL: https://jira.jboss.org/jira/browse/JBESB-2678 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.4 CP2 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.4 CP3 It currently destroys the pool rather than cleaning. -- 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

16 years, 10 months

1
2
0 / 0

[JBoss JIRA] Updated: (JBESB-2679) JmsConnectionPool no longer recovers connection

by Kevin Conner (JIRA)

[ https://jira.jboss.org/jira/browse/JBESB-2679?page=com.atlassian.jira.plu... ] Kevin Conner updated JBESB-2679: -------------------------------- Fix Version/s: 4.6 (was: 4.4 CP3) Affects Version/s: 4.5 (was: 4.4 CP2) > JmsConnectionPool no longer recovers connection > ----------------------------------------------- > > Key: JBESB-2679 > URL: https://jira.jboss.org/jira/browse/JBESB-2679 > 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 > > > Cleaning the session pool previously cleared out the pool information, finally closing down the connection. A new attempt to acquire a session would have re-established the missing connection. > The session handling has been moved to a new class but the connection creation is still in the original. We need to move this under the new class so that missing connections can be re-established. -- 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

16 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-2504) Identify any issues with using IBM MQ and provide direct support within the ESB codebase

by Kevin Conner (JIRA)

Identify any issues with using IBM MQ and provide direct support within the ESB codebase ---------------------------------------------------------------------------------------- Key: JBESB-2504 URL: https://jira.jboss.org/jira/browse/JBESB-2504 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.2.1 CP4 Reporter: Kevin Conner Fix For: 4.2.1 CP5 TomF has already done some work on this task, in relation to a customer enquiry. The solution he created was to provide an adapter to the MQ ConnectionFactory/Connection classes which could then be referred to from within the ESB configuration. The main purpose of the adapter was to handle the requirement that there only be a single session per connection when executing within a transactional context. We need to move this requirement back into the ESB codebase and support it directly within the JMS connection pool. An additional part of this task will be to identify any further issues which arise and create appropriate JIRAs. -- 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

16 years, 10 months

1
4
0 / 0

[JBoss JIRA] Created: (JBESB-2677) JmsConnectionPool: Add support for "max-xa-sessions-per-connection" config

by Kevin Conner (JIRA)

JmsConnectionPool: Add support for "max-xa-sessions-per-connection" config -------------------------------------------------------------------------- Key: JBESB-2677 URL: https://jira.jboss.org/jira/browse/JBESB-2677 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.4 CP2 Reporter: Tom Fennelly Assignee: Tom Fennelly Fix For: 4.4 CP3 The JmsConnectionPool currently supports a "max-sessions-per-connection" config. Add support for a "max-xa-sessions-per-connection", allowing specific control over XA resources. So "max-sessions-per-connection" will be the total number of sessions allowed per connection (XA + non-XA) and "max-xa-sessions-per-connection" will be a specific max for XA Sessions. -- 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

16 years, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-2676) JmsConnectionPool: Add support for managing JMS Session instances across multiple JMS Connection instances

by Kevin Conner (JIRA)

JmsConnectionPool: Add support for managing JMS Session instances across multiple JMS Connection instances ---------------------------------------------------------------------------------------------------------- Key: JBESB-2676 URL: https://jira.jboss.org/jira/browse/JBESB-2676 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.4 CP2 Reporter: Tom Fennelly Assignee: Tom Fennelly Fix For: 4.4 CP3 Currently, the JmsConnectionPool only supports a single JMS Connection instance, with all Sessions (up to the pool size) being created off this Connection. Some providers have limits on the number of sessions per connection (e.g. WMQ), so the pool needs to accommodate this. -- 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

16 years, 10 months

1
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues July 2009