Jaroslaw Cwiklik wrote:
Jorn, I need more information to determine the cause of the problem. Can you
clarify your deployment? I understand you have worker nodes running UIMA AS
services. These services connect to a remote Web Service. I presume that
this connection is done your code in the AE. Is this correct?
Your pasted log messages that indicate that a service is stopping. Any
exceptions in the log? Also, can you increase log level to see if there is
more revealing information. Another idea, is to attach jConsole to the UIMA
AS service that is not processing messages and look at the JVM threads to
see if there is a hang somewhere. Also, check UIMA JMX MBeans. There should
be MBeans for CM and their CasPools. Are the pools empty indicating that
CASes are stuck somewhere?
It happened again.
This time I checked the process with JMX, the CAS pools where all empty, and
11 CASes where waiting in the input queue of an AE. Does that mean that
the AE.process
method blocks ?
Can my hang be explained by blocking AE.process methods ? Is there a default
timeout for that case ?
Actually since I last reported the hang issue it happened two more
times, today
and a few days ago. I have a core dump of the process from a few days ago.
I checked the stack traces and it looked like the CM at the beginning of
the pipe
was waiting in next() -> getEmptyCAS(), but it locked because the CAS
pools where empty (?).
All other threads where waiting in framework code, and not in my
implementation code.
The stopping message in the log file occurs always if an exception is
thrown from an
AE which is behind a CM. I opened a jira issue to demonstrate that.
Jörn
