[esb-issues] [JBoss JIRA] Reopened: (JBESB-1360) ServiceInvoker.deliverSync hangs
[ http://jira.jboss.com/jira/browse/JBESB-1360?page=all ]
Kevin Conner reopened JBESB-1360:
---------------------------------
This is similar to the issue that was solved a couple of weeks back for the QSes.
I have reopened this issue as I believe it will be a problem for the work that Trev and
Mike are doing with the build system.
Trev and I have been discussing how to run the ESB testsuites against the EAP, during the
SOA-P build process, so that we
can have confidence of the build before uploading it for general availability. This will
certainly affect this work.
ServiceInvoker.deliverSync hangs
--------------------------------
Key: JBESB-1360
URL: http://jira.jboss.com/jira/browse/JBESB-1360
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta, Web Services
Affects Versions: 4.2.1
Reporter: Jiri Pechanec
Assigned To: Kevin Conner
Priority: Critical
Fix For: 4.2.1 CP1
Attachments: test.log
Sometimes deliverSync blocks indefinitely. If the calling thread is terminated then it
prints
WARN [Thread-1][CourierFactory] Calling cleanup on existing couriers for identity
ID-DEFAULT and hangs !!
The last lines in log are
2007-11-22 12:03:10,776 DEBUG [Thread-1][org.jboss.soa.esb.lifecycle.LifecycleResource]
Cleaning up resource using factory:
org.jboss.soa.esb.couriers.CourierFactory$LifecycleCourierFactory@16cd83d8 with identity
ID-DEFAULT
2007-11-22 12:03:10,776 WARN [Thread-1][org.jboss.soa.esb.couriers.CourierFactory]
Calling cleanup on existing couriers for identity ID-DEFAULT
2007-11-22 12:03:10,784 DEBUG [Thread-1][org.jboss.soa.esb.couriers.CourierFactory]
Courier allocation stacktrace
java.lang.Exception: Courier Assignment stacktrace
at org.jboss.soa.esb.couriers.CourierFactory.registerCourier(CourierFactory.java:148)
at org.jboss.soa.esb.couriers.CourierFactory.getCourier(CourierFactory.java:134)
at org.jboss.soa.esb.couriers.CourierFactory.getMessageCourier(CourierFactory.java:96)
at org.jboss.soa.esb.client.ServiceInvoker.getCourier(ServiceInvoker.java:338)
at
org.jboss.soa.esb.client.ServiceInvoker$EPRInvoker.attemptDelivery(ServiceInvoker.java:404)
at org.jboss.soa.esb.client.ServiceInvoker$EPRInvoker.access$200(ServiceInvoker.java:370)
at org.jboss.soa.esb.client.ServiceInvoker.post(ServiceInvoker.java:259)
at org.jboss.soa.esb.client.ServiceInvoker.deliverSync(ServiceInvoker.java:155)
at
org.jboss.soa.esb.samples.quickstart.webservice_consumer1.WebServiceConsumerTest.postESBMessage(WebServiceConsumerTest.java:60)
at
org.jboss.soa.esb.samples.quickstart.webservice_consumer1.WebServiceConsumerTest.testWSConsumer(WebServiceConsumerTest.java:71)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.testng.internal.MethodHelper.invokeMethod(MethodHelper.java:604)
at org.testng.internal.InvokeMethodRunnable.run(InvokeMethodRunnable.java:36)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
at java.util.concurrent.FutureTask.run(FutureTask.java:123)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
The whole log is attached
--
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