Bug 777660 (SOA-170) - ServiceInvoker.deliverSync hangs
Summary: ServiceInvoker.deliverSync hangs
Keywords:
Status: CLOSED NOTABUG
Alias: SOA-170
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: JBossWS
Version: 4.2 IR6
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 4.2 IR8
Assignee: Jiri Pechanec
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-11-22 12:36 UTC by Jiri Pechanec
Modified: 2007-11-25 16:01 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-11-25 16:01:29 UTC
Type: Bug


Attachments (Terms of Use)
test.log (59.51 KB, text/plain)
2007-11-22 12:38 UTC, Jiri Pechanec
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-170 0 None None None Never

Description Jiri Pechanec 2007-11-22 12:36:07 UTC
project_key: SOA

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

Comment 1 Jiri Pechanec 2007-11-22 12:38:33 UTC
Attachment: Added: test.log


Comment 2 Jiri Pechanec 2007-11-22 12:43:25 UTC
Link: Added: This issue depends JBESB-1360



Note You need to log in before you can comment on or make changes to this bug.