May 2007 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-568) ActionUtils.getTaskObject NullPointerException when message is null

by Daniel Bevenius (JIRA)

ActionUtils.getTaskObject NullPointerException when message is null ------------------------------------------------------------------- Key: JBESB-568 URL: http://jira.jboss.com/jira/browse/JBESB-568 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Daniel Bevenius Assigned To: Mark Little Priority: Minor Test method: public void testGetTaskObjectNegative() { ActionUtils.getTaskObject( null ); } ActionUtils : public static Object getTaskObject(Message message) { Object payload = (null==message)? null : message.getBody().get(CURRENT_OBJECT); if(payload == null) { payload = message.getBody().getByteArray(); } return payload; } I'm not sure if it is ever possible for the message object passed in to be null but perhaps the code should be modified anyway just in case. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 9 months

3
7
0 / 0

[JBoss JIRA] Created: (JBESB-580) JMS synchronous replies are not correlated with request

by Kevin Conner (JIRA)

JMS synchronous replies are not correlated with request ------------------------------------------------------- Key: JBESB-580 URL: http://jira.jboss.com/jira/browse/JBESB-580 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2 JMS synchronous requests do not initialise a correlation ID for identifying responses. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-586) JMS courier can leak sessions (part two)

by Kevin Conner (JIRA)

JMS courier can leak sessions (part two) ---------------------------------------- Key: JBESB-586 URL: http://jira.jboss.com/jira/browse/JBESB-586 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2 When an error is detected by a JMS courier it attempts to reconnect to the message consumer. The logic to reconnect involves a loop to retry, current hardcoded to 5 attempts. Unfortunately this loop does not terminate if the courier successfully reconnected, resulting in another leak of sessions. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 9 months

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-577) JMS courier can leak sessions

by Kevin Conner (JIRA)

JMS courier can leak sessions ----------------------------- Key: JBESB-577 URL: http://jira.jboss.com/jira/browse/JBESB-577 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2 Milestone Release 2 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2 The JMS courier can leak sessions from the pool if an error occurs when attempting to configure the message consumer -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-560) Store the original filename for messages originating on file or FTP gateways

by Derek Adams (JIRA)

Store the original filename for messages originating on file or FTP gateways ---------------------------------------------------------------------------- Key: JBESB-560 URL: http://jira.jboss.com/jira/browse/JBESB-560 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.2 Milestone Release 2 Reporter: Derek Adams Assigned To: Mark Little Priority: Minor Fix For: 4.2 When file and FTP gateways create messages to put on the bus, the original filename should be made available as part of the message. An example use-case for this would be polling a group of files on an FTP server at a given interval, doing some manipulation of the contents inside the ESB, then writing the message back out to FTP with the original file name plus a timestamp to make the file unique. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 9 months

2
7
0 / 0

[JBoss JIRA] Created: (JBESB-578) Quickstarts still refer to jbosshome.dir

by Kevin Conner (JIRA)

Quickstarts still refer to jbosshome.dir ---------------------------------------- Key: JBESB-578 URL: http://jira.jboss.com/jira/browse/JBESB-578 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Kevin Conner Assigned To: Kevin Conner Priority: Minor Fix For: 4.2 The jbosshome.dir property was renamed to org.jboss.esb.server.home but it is still referenced in at least two of the quickstarts. fun_cbr and webservice_war1 need updating, the others double checking. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-504) Add a SOAP adapter for Axis

by Tom Fennelly (JIRA)

Add a SOAP adapter for Axis --------------------------- Key: JBESB-504 URL: http://jira.jboss.com/jira/browse/JBESB-504 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.2 Reporter: Tom Fennelly Assigned To: Tom Fennelly Fix For: 4.2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-552) Create documentation around ActiveBPEL integration

by Tom Fennelly (JIRA)

Create documentation around ActiveBPEL integration -------------------------------------------------- Key: JBESB-552 URL: http://jira.jboss.com/jira/browse/JBESB-552 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.2 Milestone Release 2 Reporter: Tom Fennelly Assigned To: Tom Fennelly Fix For: 4.2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 9 months

2
8
0 / 0

[JBoss JIRA] Created: (JBESB-553) Create documentation around the JBossWSAdapter action

by Tom Fennelly (JIRA)

Create documentation around the JBossWSAdapter action ----------------------------------------------------- Key: JBESB-553 URL: http://jira.jboss.com/jira/browse/JBESB-553 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.2 Milestone Release 2 Reporter: Tom Fennelly Assigned To: Tom Fennelly Fix For: 4.2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 9 months

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-452) Refactor Notifiers

by Kurt Stam (JIRA)

Refactor Notifiers ------------------ Key: JBESB-452 URL: http://jira.jboss.com/jira/browse/JBESB-452 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.0 Environment: any Reporter: Kurt Stam Assigned To: Mark Little Priority: Critical Fix For: 4.2 These comments are based on the JMS notifiers but will probably apply to the other notifiers as well: 1. The notifiers should be more like listeners where you get one (or more instances). Until they get recycled when there is a config change. Right now the JMS onces connected and disconnect with every message, which causes stress on the JMS provider when running in high load mode. 2. They should get their 'provider' configuration from the configuration, just like the listeners. Right now you cannot connect to other JMS providers. 3. The notifiers should get hooked up to the same life cycle management as the listener infrastructure. In other words: They really should be 'inverse gateways', the model is broken and there shouldn't be a distinction between notifying and sending a message via couriers+listeners. The fact we support different transports (and in different ways) for notifiers than for the "core" ESB is just wrong. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 9 months

3
12
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues May 2007