December 2010 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-3549) Race in jUDDI UDDIClientContainer

by Kevin Conner (JIRA)

Race in jUDDI UDDIClientContainer --------------------------------- Key: JBESB-3549 URL: https://issues.jboss.org/browse/JBESB-3549 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Registry and Repository Affects Versions: 4.9 CP1 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.9 CP1 Results in failures during ESB service registration Exception detected by:`Caused by: org.jboss.soa.esb.services.registry.RegistryException: org.apache.ws.scout.transport.TransportException: java.lang.Exception: Cannot locate configuration source META-INF/uddi.xml -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-3550) Aggregator doesn't work with XA transaction rollback

by Michael Burman (JIRA)

Aggregator doesn't work with XA transaction rollback ---------------------------------------------------- Key: JBESB-3550 URL: https://issues.jboss.org/browse/JBESB-3550 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.9 Reporter: Michael Burman If Aggregator's service fails, it will rollback one instance of the message, and thus in the following round when reading the messages from queue, it will never finish as it expects several messages. Patched Aggregator with printing out the MessageId (for better logs): 2010-12-20 15:06:17,162 INFO [STDOUT] (Thread-12 (group:HornetQ-client-global-threads-320732754)) Received message: 7c7b6080-485c-4f6e-9f40-8c49f676cb76 2010-12-20 15:06:17,984 INFO [STDOUT] (Thread-3 (group:HornetQ-client-global-threads-320732754)) Received message: 7c7b6080-485c-4f6e-9f40-8c49f676cb76 2010-12-20 15:06:18,305 ERROR [org.hornetq.ra.inflow.HornetQMessageHandler] (Thread-3 (group:HornetQ-client-global-threads-320732754)) Failed to deliver message java.lang.RuntimeException: 2010-12-20 15:06:18,356 INFO [STDOUT] (Thread-12 (group:HornetQ-client-global-threads-320732754)) Received message: 7c7b6080-485c-4f6e-9f40-8c49f676cb76 So not everything is rolled back to the original queue and thus when Aggregator waits for the other message, it will fail. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-3548) BeanContainerAction not returning null when process method returns null

by Tom Fennelly (JIRA)

BeanContainerAction not returning null when process method returns null ----------------------------------------------------------------------- Key: JBESB-3548 URL: https://issues.jboss.org/browse/JBESB-3548 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Reporter: Tom Fennelly Assignee: Tom Fennelly Priority: Blocker Which means the action is not able to terminate the pipeline. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-3547) BeanContainerAction not rethrowing RuntimeException

by Tom Fennelly (JIRA)

BeanContainerAction not rethrowing RuntimeException --------------------------------------------------- Key: JBESB-3547 URL: https://issues.jboss.org/browse/JBESB-3547 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Reporter: Tom Fennelly Assignee: Tom Fennelly Priority: Blocker Is taking all InvocationTargetExceptions, wrapping and rethrowing. Should not be wrapping RuntimeExceptions. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
1
0 / 0

[JBoss JIRA] Updated: (JBESB-3548) BeanContainerAction not returning null when process method returns null

by Tom Fennelly (JIRA)

[ https://issues.jboss.org/browse/JBESB-3548?page=com.atlassian.jira.plugin... ] Tom Fennelly updated JBESB-3548: -------------------------------- Description: Which means the action is not able to terminate the pipeline. Note... process methods with a void return type will not terminate the pipeline. The method must have a non-void return type. was:Which means the action is not able to terminate the pipeline. > BeanContainerAction not returning null when process method returns null > ----------------------------------------------------------------------- > > Key: JBESB-3548 > URL: https://issues.jboss.org/browse/JBESB-3548 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Rosetta > Reporter: Tom Fennelly > Assignee: Tom Fennelly > Priority: Blocker > > Which means the action is not able to terminate the pipeline. > Note... process methods with a void return type will not terminate the pipeline. The method must have a non-void return type. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-3546) Update Programmers Guide: remoteFileSystemStrategy-configFile and remoteFileSystemStrategy-class are spelled wrong.

by Per Lilja (JIRA)

Update Programmers Guide: remoteFileSystemStrategy-configFile and remoteFileSystemStrategy-class are spelled wrong. ------------------------------------------------------------------------------------------------------------------- Key: JBESB-3546 URL: https://issues.jboss.org/browse/JBESB-3546 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.9, 4.3 Reporter: Per Lilja Priority: Minor In the programmers guide for 4.3 remoteFileSystemStrategy-class is spelled wrong, and is spelled like remoteFilesystemStrategy-class. When I had a look at the documentation for 4.9, both remoteFileSystemStrategy-configFile and remoteFileSystemStrategy-class are spelled wrong. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-3545) jboss-esb.xml configuration is not validated against the appropriate schema

by Kevin Conner (JIRA)

jboss-esb.xml configuration is not validated against the appropriate schema --------------------------------------------------------------------------- Key: JBESB-3545 URL: https://issues.jboss.org/browse/JBESB-3545 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployment Affects Versions: 4.9 Reporter: Kevin Conner Assignee: Kevin Conner Priority: Blocker Fix For: 4.9 CP1 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-3544) Same bus-id's in jboss-esb.xml are allowed

by Johan Kumps (JIRA)

Same bus-id's in jboss-esb.xml are allowed ------------------------------------------ Key: JBESB-3544 URL: https://issues.jboss.org/browse/JBESB-3544 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.9 Reporter: Johan Kumps Strange behavior can be experienced when you configure multiple jms-bus 's in jboss-esb.xml having the same bus-id. In this case multiple services are listining to the same channel. The component validating the jboss-esb.xml configuration file should report this as an error. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-3543) Remove Logger.error from BaseWebService

by Kevin Conner (JIRA)

Remove Logger.error from BaseWebService --------------------------------------- Key: JBESB-3543 URL: https://issues.jboss.org/browse/JBESB-3543 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.9 CP1 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.9 CP1 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-3497) Investiage SOA-2117

by Kevin Conner (JIRA)

Investiage SOA-2117 ------------------- Key: JBESB-3497 URL: https://jira.jboss.org/browse/JBESB-3497 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.9 Reporter: Kevin Conner Assignee: Tom Fennelly Fix For: 4.9 CP1 An example test does not work as expected using WSMQ, perhaps a configuration issue. We need to investigate and see whether we have a problem or not. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

2
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 December 2010