June 2007 - esb-issues - Jboss List Archives

[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

16 years, 11 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

16 years, 11 months

2
5
0 / 0

[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

16 years, 11 months

3
7
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

16 years, 11 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

16 years, 11 months

2
7
0 / 0

[JBoss JIRA] Created: (JBESB-611) org.jboss.soa.esb.actions.StaticRouter reports a fatal error - but it seems to work

by Len DiMaggio (JIRA)

org.jboss.soa.esb.actions.StaticRouter reports a fatal error - but it seems to work ----------------------------------------------------------------------------------- Key: JBESB-611 URL: http://jira.jboss.com/jira/browse/JBESB-611 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2 Environment: RHEL5 Sun Java 1.5 ESB built from svn on June 6 Reporter: Len DiMaggio Assigned To: Mark Little Priority: Minor Potential bug: In trying a simple static router - with org.jboss.soa.esb.actions.StaticRouter - and text messages going thru a gateway listener - I'm seeing this error in the server log: ERROR [STDERR] [Fatal Error] :1:1: Content is not allowed in prolog. This is with code and a jboss-esb.xml that worked with MR2 - also - although the error says fatal, the router seems to be working fine. A known problem? Thanks! Note - commenting out all the: [code] <target class="NotifyConsole" /> [/code] statements in the jboss-esb has no effect. See also: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=110548 -- 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

16 years, 11 months

4
14
0 / 0

[JBoss JIRA] Created: (JBESB-648) Service configurations without an ESB Message Aware listener should cause an error on startup/redeploy

by Tom Fennelly (JIRA)

Service configurations without an ESB Message Aware listener should cause an error on startup/redeploy ------------------------------------------------------------------------------------------------------ Key: JBESB-648 URL: http://jira.jboss.com/jira/browse/JBESB-648 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2 Milestone Release 2 Reporter: Tom Fennelly Assigned To: Mark Little Fix For: 4.2 Otherwise the Action Pipeline has no delivery endpoint. -- 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

16 years, 11 months

2
7
0 / 0

[JBoss JIRA] Created: (JBESB-635) Documentation does not include information on running ESB Server and JBossAS on same machine

by Mark Little (JIRA)

Documentation does not include information on running ESB Server and JBossAS on same machine -------------------------------------------------------------------------------------------- Key: JBESB-635 URL: http://jira.jboss.com/jira/browse/JBESB-635 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Configuration, Documentation Affects Versions: 4.2 Milestone Release 2 Reporter: Mark Little Assigned To: Mark Little 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

16 years, 11 months

1
4
0 / 0

[JBoss JIRA] Created: (JBESB-589) Smooks decoders do not handle superclasses/interfaces of a specified type

by Kevin Conner (JIRA)

Smooks decoders do not handle superclasses/interfaces of a specified type ------------------------------------------------------------------------- Key: JBESB-589 URL: http://jira.jboss.com/jira/browse/JBESB-589 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transformation Service Reporter: Kevin Conner Assigned To: Tom Fennelly Fix For: 4.2 The XML2POJO and XML2XML_date_manipulation QSes have recently been changed to decode types related to the target class. One of the changes was to decode a Calendar object in the OrderDate class. Unfortunately smooks fails to identify the setter as the CalendarDecoder returns a GregorianCalendar which AbstractBeanPopulator uses to identify the setter. I have spoken with Tom and he has a fix for this. In the meantime I have updated the QSes to use Dates instead of Calendars. -- 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

16 years, 11 months

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-638) Transient registry errors caused by jUDDI race condition

by Kevin Conner (JIRA)

Transient registry errors caused by jUDDI race condition -------------------------------------------------------- Key: JBESB-638 URL: http://jira.jboss.com/jira/browse/JBESB-638 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Registry and Repository Reporter: Kevin Conner Assigned To: Kurt Stam Fix For: 4.2 Kurt, can you raise the following with jUDDI and have it fixed? Thanks. There is a race condition in the jUDDI codebase which causes transient registry failures. The symptom of the race condition is the following error message E_busy (10400) The request cannot be processed at the current time. The Registry is currently unavailable. The class containing the race condition is org.apache.juddi.registry.local.Registry Every call to Registry.getRegistry() results in the recreation and initialisation of a global variable (registry). As the assignment of the global variable is made *before* the initialisation method is called there exists a window of opportunity whereby a caller can obtain a reference to an uninitialised registry. The consequence of this is that calls to RegistryEngine.isAvailable() can return false. I'm not sure why the RegistryEngine is being recreated on every call but the current code is unsafe (even if ignoring multiprocessor memory models). There should be not be a global reference to the registry if it is a requirement to recreate it on every invocation. If it is not a requirement then the initialisation should really be occurring within a static block. -- 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

16 years, 11 months

3
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues June 2007