Status: Accepted
Owner: [email protected]
CC: [email protected]
Labels: Type-Defect Priority-Medium Affected-Version-3.0.0-Final
New issue 114 by [email protected]: Mediaserver stop responding
http://code.google.com/p/mediaserver/issues/detail?id=114
Media server installed on an Amazon EC2 instance (m1.large) together with
MSS, but same issue occurred when MMS was the only running jvm process on
the instance (seperate server).
After few days uptime (last time issue happened server was running for 5
days) the media server stop responding to any requests. Even the server's
heartbeat that is suppose to execute every 1 min, stops. Also notice that
there was almost no traffic to the server (only 2 calls few days before the
server stopped)
When in that condition, i got the jstack and jmap trace along with logs and
OS statistics such as open ports (+udp receive queue), memory and cpu
consuption.
Inspecting the jstack trace, the WorkerThread threads are not waiting to
acquire the lock that ConcurrentLinkedList currently has locked as it
supposed to be so they don't wake up on notify.
Checking the CriticalWorkingThread threads, they are blocked waiting for
the object that ConcurrentLinkedList has acquired and this is the correct
behavior as they will wake up on a notify when a new task arrive.
Find attached the jstack trace and i can send jmap, mms logs and OS logs.
Attachments:
mms_jstack_Jan_09_2013-15_58 7.4 KB
