[esb-issues] [JBoss JIRA] Closed: (JBESB-884) webservice_consumer1 and webservice_consumer2 QSes fail to deliver message
[ http://jira.jboss.com/jira/browse/JBESB-884?page=all ]
Kevin Conner closed JBESB-884.
------------------------------
Resolution: Done
This has been fixed in revision 14532.
The JMS classes accessed via JNDI are pulling in AOP classes. There is now a dependency
on AspectManager (present in the aop-client jar) which in turn depends on PointcutStats
(not present in the aop-client jar).
Whether this existed before or not is uncertain, the jbossesb-server previously had the
full aop jar under client.
I have changed the QS base-build.xml to include the full aop jar from the jboss-aop
deployer.
webservice_consumer1 and webservice_consumer2 QSes fail to deliver
message
--------------------------------------------------------------------------
Key: JBESB-884
URL: http://jira.jboss.com/jira/browse/JBESB-884
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Examples
Affects Versions: 4.2 Milestone Release 3
Reporter: Kevin Conner
Assigned To: Kevin Conner
Fix For: 4.2
Both these quickstarts deploy and run but the message delivery always fails.
[echo] Send ESB message that triggers webservice call
[java] Exception in thread "main"
org.jboss.soa.esb.listeners.message.MessageDeliverException: Failed to deliver message to
Service [JBossESB-Internal:DeadLetterService]. Check for errors.
[java] at org.jboss.soa.esb.client.ServiceInvoker.post(ServiceInvoker.java:262)
Haven't checked other QSes yet.
--
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