[
http://jira.jboss.com/jira/browse/JBESB-1540?page=comments#action_12415743 ]
Tom Fennelly commented on JBESB-1540:
-------------------------------------
Jiri, would it possible for you to test this again in the env you were able to produce it
in, but this time use 4.3.GA of the ESB? Kevin thinks the JBossRemoting CoyoteInvoker may
have changed since.
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: Tom Fennelly
Priority: Minor
Fix For: 4.2.1 CP4
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