Hide Forgot
Help Desk Ticket Reference: https://c.na7.visual.force.com/apex/Case_View?id=500A0000006n9NI&sfdc.override=1 SourceForge Reference: http://fisheye.jboss.org/viewrep/JBossESB/trunk/product/rosetta/src/org/jboss/soa/esb/actions/routing/http/HttpRouter.java?r1=29277&r2=30080&u=3 Steps to Reproduce: Use an HTTP Router with a non-existent URL. You should see an Error in the log, but the Action Pipeline won't know any different. project_key: SOA
Please vote for inclusion of this JIRA. Thanks, Rick
Approved for SOA 4.3 CP05
Link: Added: This issue Cloned from JBESB-3599
Release Notes Text: Added: Changed printStackTraces to throw new exceptions so that exceptions are propagated up.
Changed printStackTraces to throw new exceptions so that exceptions are propagated up.
Release Notes Text: Removed: Changed printStackTraces to throw new exceptions so that exceptions are propagated up.
The issue is still present in SOA-P 4.3 CP05 ER2
Attached a reproducer. Run ant deploy, ant runtest. There is an invalid URL in HttpRouter. After HttpRouter there is an echo action that should not be executed according to information in project JIRA.
Attachment: Added: ebws_proxy.tar.bz2
The test case below does not hit either of the catch cases that were switched from e.printStackTrace -> throw new ActionProcessingException. It doesn't really apply to this bug or the client case attached. Changing the behavior of HttpRouter to throw an Exception on a non-successful http code is outside the scope of this bug and the client case attached to it. You could file a separate issue against that, but I believe the warning message in that case is intended behavior.
As we discussed the issue with Tom, this is really resolved in 4.3 CP05 ER2.
Link: Added: This issue relates to SOA-3039
Temporarily reopening to update release note info.
Release Notes Docs Status: Added: Not Yet Documented Writer: Added: dlesage
Release Notes Docs Status: Removed: Not Yet Documented Added: Documented as Resolved Issue Release Notes Text: Added: https://issues.jboss.org/browse/SOA-3013 The org/jboss/soa/esb/actions/routing/http/HttpRouter.java process() method was logging exceptions in stderr but not propagating them back to the action chain. As a result of this, there is no indication that an invalid URL was used. To fix this problem, printStackTraces has been modified so that it now throws new exceptions back to the action chain. Therefore, users will now see that an invalid URL was used as they will encounter an error.