[Building Sakai] Unresponsive jvm .. any suggestions?

[Kenwrick Chan]

Folks,
As it turns out ... we still have a "unresponsive jvm".  From the ldap
server side of the house we don't see errors so we were looking for where
the source is for the openldap portion of the code that the jldap provider
uses?  Is it okay to update to a newer version.

We're still not sure how this relates to our jvm in a unresponsive state
but right now that's the only marker in our logs that we have to go by.

Any suggestions on how we can solve this or what approaches we can take to
try and look for the source of the issue?

Thanks,
Ken




On Tue, May 6, 2014 at 4:59 PM, Kenwrick Chan <kchan at hawaii.edu> wrote:

> Folks,
> We're been running the same sakai codebase with no changes for well over a
> year.  (2.7.x, we haven't had the resources to migrate yet).  Recently
> we've run into an issue where an individual front end app server becomes
> unresponsive.  In the days following we've upped the available memory to
> the OS and the tomcat app server, but eventually it just fails to respond.
>
> There seems to be a correlation in our catalina.out file to the following
> error:
>
> Exception in thread "Thread-29287" java.lang.RuntimeException:
> Connection.freeWriteSemaphore(28847): semaphore not owned by any thread
>  at com.novell.ldap.Connection.freeWriteSemaphore(Unknown Source)
> at com.novell.ldap.Message.putReply(Unknown Source)
>  at com.novell.ldap.Connection$ReaderThread.run(Unknown Source)
> at java.lang.Thread.run(Thread.java:662)
>
> which is pretty much like:
> https://jira.sakaiproject.org/browse/SAK-23292
>
> ... enough of these errors and the jvm becomes unresponsive.
>
> There are no errors on the ldap side of the house and our network guys say
> there isn't an issue there impacting access to our ldap servers.  Any
> suggestions?
>
> -Kenwrick
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20140508/8b58700d/attachment.html