I managed to find a BLOCKED state example that clearly shows that the monitoring plugin is not helping in these cases.

Monitoring plugin:
"Thread-127432" daemon prio=5 BLOCKED
com.sun.jndi.ldap.Connection.getInputStream(Connection.java:710)
com.sun.jndi.ldap.Connection.run(Connection.java:832)
java.lang.Thread.run(Thread.java:722)

jenkins-url/threadDump:
"Thread-127432" Id=193884 Group=main BLOCKED on com.sun.jndi.ldap.Connection@77b338dc owned by "Jenkins cron thread" Id=23
at com.sun.jndi.ldap.Connection.getInputStream(Connection.java:710)

  • blocked on com.sun.jndi.ldap.Connection@77b338dc
    at com.sun.jndi.ldap.Connection.run(Connection.java:832)
    at java.lang.Thread.run(Thread.java:722)
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to