gnodet wrote:
>
> Have you tried a thread dump to see if all the threads were waiting on
> a particular resource ?
>
>
I have been encountering another lock up this morning. It appears that alot
of the threads are waiting for a response from a sendSync message that is
going out to a http endpoint (external webservice)
Here is a example stack
"pool-flow.seda.Esb-thread-1020" prio=6 tid=0x2b4a7430 nid=0x3a0 in
Object.wait() [0x2fb9f000..0x2fb9fb1c]
at java.lang.Object.wait(Native Method)
- waiting on <0x261b2440> (a
org.apache.servicemix.jbi.messaging.InOptionalOutImpl)
at
org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.waitForExchange(DeliveryChannelImpl.java:679)
at
org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.sendSync(DeliveryChannelImpl.java:458)
- locked <0x261b2440> (a
org.apache.servicemix.jbi.messaging.InOptionalOutImpl)
at
org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.sendSync(DeliveryChannelImpl.java:428)
at
org.apache.servicemix.components.util.PojoSupport.sendSync(PojoSupport.java:201)
at
esb.SheetMgmtServiceESB.sendStringMessage(SheetMgmtServiceESB.java:1824)
at esb.SheetMgmtServiceESB.outOfUv(SheetMgmtServiceESB.java:1012)
at
sheetmgmt.esb.SheetMgmtServiceESB.onMessageExchange(SheetMgmtServiceESB.java:445)
at
org.apache.servicemix.components.util.ComponentAdaptorMEListener.onMessageExchange(ComponentAdaptorMEListener.java:47)
at
org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:593)
at
org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:174)
at
org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:176)
at
org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
at java.lang.Thread.run(Thread.java:595)
Any suggestions of where to start looking for problems?
Would I make the situation better by moving from a seda queue to a jms type
flow? (I don't think that it would but I want to verify)
Is there any sort of timeout for a message (http bc) that would fail the
message?
I've not done any special configuration for the http bc endpoint. As such,
what are the default number of threads that I can expect for outgoing calls.
Would a blocking of threads caused by outgoing calls have an effect on
incoming calls?
Thanks,
James
--
View this message in context:
http://www.nabble.com/http-lock-up-tf3488493s12049.html#a10142439
Sent from the ServiceMix - User mailing list archive at Nabble.com.
