September 2009 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-2853) SOAPProxy should have more clear failure when encountering zero-lengh payloads

by David Ward (JIRA)

SOAPProxy should have more clear failure when encountering zero-lengh payloads ------------------------------------------------------------------------------ Key: JBESB-2853 URL: https://jira.jboss.org/jira/browse/JBESB-2853 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.6 Reporter: David Ward Assignee: David Ward Priority: Minor Fix For: 4.7 If a zero-length byte[] or String Message payload gets sent to the SOAPProxy, the error message should be point this out instead of being cryptic. -- 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

14 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-2837) Handcrafted FTP EPR causes failure if not escaped

by Kevin Conner (JIRA)

Handcrafted FTP EPR causes failure if not escaped ------------------------------------------------- Key: JBESB-2837 URL: https://jira.jboss.org/jira/browse/JBESB-2837 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.4 CP2 Reporter: Julian Coleman Assignee: Kevin Conner Fix For: 4.4 CP3 FtpListenerMapper hand crafts a URI based on the information from the jboss-esb.xml but makes no attempt to escape special characters. The consequence is that some of the information can no longer be parsed correctly, leading to failure in deployment. One example is a password starting with '#', which leads to the following error on deployment. Caused by: org.jboss.soa.esb.ConfigurationException: No username specified for FTP -- 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

14 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-2848) Programer's guide update: Composer class and exception handling

by Boris Belovic (JIRA)

Programer's guide update: Composer class and exception handling --------------------------------------------------------------- Key: JBESB-2848 URL: https://jira.jboss.org/jira/browse/JBESB-2848 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.4 CP2 Reporter: Boris Belovic Fix For: 4.4 CP3 I think that there should be some note in Programer's Guide about handling exceptions in custom composer class implementation. It should be mentioned that it is a composer class responsibility to handle exceptions that are thrown in methods of this composer. The creator of the composer should take care of exceptions that can be thrown in the composer class. -- 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

14 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-2847) Routing a message to multiple services inVM message reference

by Mika Leino (JIRA)

Routing a message to multiple services inVM message reference ------------------------------------------------------------- Key: JBESB-2847 URL: https://jira.jboss.org/jira/browse/JBESB-2847 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.5 Environment: Both Linux and Windows XP, JDK1.5 Reporter: Mika Leino Using StaticRouter to route a message to several services fails when services are set up as inVM. All services to which the message is routed receive a reference to the same object and as such only the first one to pick up the message can be sure of the message format, all others receive a message possibly transformed by the first service. -- 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

14 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-2791) JBossRemotingMessageComposer assumes the payload is a String

by Tom Fennelly (JIRA)

JBossRemotingMessageComposer assumes the payload is a String ------------------------------------------------------------ Key: JBESB-2791 URL: https://jira.jboss.org/jira/browse/JBESB-2791 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.6 Reporter: Tom Fennelly Fix For: 4.7 JBossRemotingGatewayListener#JBossRemotingMessageComposer.populateMessage() assumes the JBR Invocation payload is a String when attempting to extract WS-S info. It might not be a String!! -- 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

14 years, 8 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-1540) WebService invocation is sometimes handled by CoyoteInvoker belonging to undeployed package

by Jiri Pechanec (JIRA)

WebService invocation is sometimes handled by CoyoteInvoker belonging to undeployed package ------------------------------------------------------------------------------------------- Key: JBESB-1540 URL: http://jira.jboss.com/jira/browse/JBESB-1540 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.2.1 Reporter: Jiri Pechanec Assigned To: Kevin Conner Priority: Minor Attachments: server.log.gz There were multiple packages deployed/undeployed in the test. The deployment of Quickstart_webservice_mtom.esb is started on line 413471. This package starts coyote invoker with hashCode 17a4c54 at the line 413681. The undeploymetn of this package starts on line 414408. The CoyoteInvoker with the given hashCode is stopped at line 414457. The Quickstart_webservice_wsa.esb package deployment starts at line 414599. The CoyotInvoker with hashCode d93db8 is started at line 414806. Then the test message is sent via HTTP/SOAP and this request fails on line 515535 because it was served by the CoyoteInvoker with hashCode 17a4c54 so the one that belongs to previously undeployed package. -- 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

14 years, 8 months

4
12
0 / 0

[JBoss JIRA] Created: (JBESB-2752) Message lost in case of exception in Message Composer

by Boris Belovic (JIRA)

Message lost in case of exception in Message Composer ----------------------------------------------------- Key: JBESB-2752 URL: https://jira.jboss.org/jira/browse/JBESB-2752 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.4 CP2 Environment: Fedora 11, 4.3.0.GA_CP01_SOA Reporter: Boris Belovic I have written (very simple) custom composer class. It just receives a JMSObjectMessage and according to message contents it creates an ESB-aware message or throws an exception. The creation of ESB aware message works fine and the message is properly delivered to receiver. In the second case an exception is thrown and the original message should be redelivered, but this is not happening. Instead of redelivery, message is lost. In case that an exception is thrown, the original message should be routed to deadletter queue. But when I try to obtain this message from the deadletter queue (either queue/DLQ or using a MessageStore instance), the queue is empty. It contains no messages and the message is lost. I also tried to use jca-provider instead of jms-provider. This provider was also unable to deliver message to proper receiver. JCA provider tried several times to redeliver message, but after all the message ended up in DLQ queue (queue/DLQ). -- 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

14 years, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-2841) Document HttpRouter configuration parameter

by Len DiMaggio (JIRA)

Document HttpRouter configuration parameter ------------------------------------------- Key: JBESB-2841 URL: https://jira.jboss.org/jira/browse/JBESB-2841 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.6 Reporter: Len DiMaggio See SOA-1470 - we should add a description of max-connections-per-host to programmers' guide section on Apache Commons HttpRouter. -- 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

14 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-2828) Handcrafted FTP EPR causes failure if not escaped

by Kevin Conner (JIRA)

Handcrafted FTP EPR causes failure if not escaped ------------------------------------------------- Key: JBESB-2828 URL: https://jira.jboss.org/jira/browse/JBESB-2828 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.4 CP2 Reporter: Julian Coleman Assignee: Kevin Conner Fix For: 4.4 CP3 FtpListenerMapper hand crafts a URI based on the information from the jboss-esb.xml but makes no attempt to escape special characters. The consequence is that some of the information can no longer be parsed correctly, leading to failure in deployment. One example is a password starting with '#', which leads to the following error on deployment. Caused by: org.jboss.soa.esb.ConfigurationException: No username specified for FTP -- 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

14 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-2823) Update ESB to support jBPM-3.2.7 CR2

by Kevin Conner (JIRA)

Update ESB to support jBPM-3.2.7 CR2 ------------------------------------ Key: JBESB-2823 URL: https://jira.jboss.org/jira/browse/JBESB-2823 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.4 CP2 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.4 CP3 The jBPM integration, copied from jbpm-3.2.5-SP5, refers to a method that is no longer present within the current SOA platform version of jBPM. JobSession.loadJobs has been removed from jBPM, along with ExecuteJobsCommand. We need to reflect these changes within our codebase. -- 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

14 years, 8 months

1
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues September 2009