Good day, Looking for some help in debugging a situation that I encountered this morning (and how to diagnose in the future)
I have a http component that contains both consumers (tied to jsr181 services) and outgoing producers to external endpoints. One of these messages is a test message (basically the ping message from the examples) that responds right away - echoing the payload that I pass in. I was notified that servicemix was no longer receiving messages in via http. I then tried the test message above (called from SoapUI) and, as reported, it also timed out. This leads me to believe that the http service was locked up. I stopped and restarted serviceMix and the test message was now working. So, I have a few questions. 1) In the http component, is there any relationship between incoming and outgoing messages. For example, if I am having network issues with messages being delivered to external web services, would that have any effect on incoming messages into SM? I'm thinking in terms of threads, pooling, and the like. Would it make any difference to separate the consumers and producers in separate service units? 2) Is there any way to diagnose this problem 'in the wild'. This is on the production system, so I don't have debugging enabled. I do have logging running, currently at a debug level for most things. I am also able to connect via jmx with jConsole. Btw, I looked at the log messages from this morning and I didn't see any abnormal error messages. Thanks, James -- View this message in context: http://www.nabble.com/http-lock-up-tf3488493s12049.html#a9741395 Sent from the ServiceMix - User mailing list archive at Nabble.com.
