AEM 6.4 + SP2 - Server hang issue very frequently | Community
Skip to main content
Praveen_RV
Level 2
February 5, 2019
Solved

AEM 6.4 + SP2 - Server hang issue very frequently

  • February 5, 2019
  • 3 replies
  • 1408 views

Hi Team,

We are using AEM 6.4 + SP2 on Linux environment and observing server hanging issues very frequently 2-3 times per week with the below thread block stack trace.

Is it a problem with Jetty or anyother?

java.lang.Thread.State: RUNNABLE

at sun.nio.ch.ServerSocketChannelImpl.accept0(Native Method)

at sun.nio.ch.ServerSocketChannelImpl.accept(ServerSocketChannelImpl.java:422)

at sun.nio.ch.ServerSocketChannelImpl.accept(ServerSocketChannelImpl.java:250)

- locked <0x00000005c1e8dd38> (a java.lang.Object)

at org.eclipse.jetty.server.ServerConnector.accept(ServerConnector.java:369)

at org.eclipse.jetty.server.AbstractConnector$Acceptor.run(AbstractConnector.java:639)

at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:762)

at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:680)

at java.lang.Thread.run(Thread.java:748)

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by joerghoh

This is nothing to worry about this marked lock, as this is a thread ready to pick up an incoming request, also the thread state is RUNNABLE.

Jörg

3 replies

joerghoh
Adobe Employee
joerghohAdobe EmployeeAccepted solution
Adobe Employee
February 5, 2019

This is nothing to worry about this marked lock, as this is a thread ready to pick up an incoming request, also the thread state is RUNNABLE.

Jörg

smacdonald2008
Level 10
February 5, 2019

Nice response!

Praveen_RV
Level 2
February 6, 2019

Thanks Jorg for your reply, may be my question was incomplete.

you are right, this thread is at runnable condition and ready to accept any incoming requests. but there are other threads in BLOCKED state for this thread to release the lock on java.lang.Object.

Please let me know for any possible way to diagnose this.

java.lang.Thread.State: BLOCKED (on object monitor)

at sun.nio.ch.ServerSocketChannelImpl.accept(ServerSocketChannelImpl.java:233)

- waiting to lock <0x00000005c1e8dd38> (a java.lang.Object)

at org.eclipse.jetty.server.ServerConnector.accept(ServerConnector.java:369)

at org.eclipse.jetty.server.AbstractConnector$Acceptor.run(AbstractConnector.java:639)

at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:762)

at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:680)

at java.lang.Thread.run(Thread.java:748)