Sudden error condition this morning

[Bryan Wooten]

I am seeing this on occasion also, but not with Shib. I get it with CAS.

Like this:

localhost.2014-09-20.log-20140920-221501.gz:SEVERE: Servlet.service() for servlet [cas] in context with path [/cas] threw exception [Request processing failed; nested exception is org.springframework.webflow.conversation.impl.LockTimeoutException: Unable to acquire conversation lock after 30 seconds] with root cause
localhost.2014-09-20.log-20140920-221501.gz:org.springframework.webflow.conversation.impl.LockTimeoutException: Unable to acquire conversation lock after 30 seconds

This apparently a very difficult problem to solve. It involves finding a slow running process. This thread showing the error is not the issue. It is something before it.

See this:

http://stackoverflow.com/questions/9533786/spring-web-flow-locktimeoutexception

I am still fighting this issue, it is hard to figure out because I can’t recreate it at will and is only random in production….



Bryan Wooten
Tel: (801)585-9323
Email: bryan.wooten at utah.edu<mailto:bryan.wooten at utah.edu>

[Identity & Access Management_combined centered]

From: users [mailto:users-bounces at shibboleth.net] On Behalf Of Jeffrey Crawford
Sent: Tuesday, September 22, 2015 11:21 AM
To: users at shibboleth.net
Subject: Sudden error condition this morning

As things ramp up for the fall quarter, we started getting more traffic on our shibboleth servers. However this morning something broke loose and I'm trying to figure out what it is. These messages started up around 7:35

2015-09-22 07:35:04,898 - WARN [org.ldaptive.AbstractOperation$ReopenOperationExceptionHandler:277] - [xxx.xxx.xx.xx] - Operation ex
ception encountered, reopening connection
2015-09-22 07:38:07,356 - ERROR [org.springframework.webflow.conversation.impl.LockTimeoutException:76] - [xxx.xxx.xx.x] -
org.springframework.webflow.conversation.impl.LockTimeoutException: Unable to acquire conversation lock after 30 seconds
        at org.springframework.webflow.conversation.impl.JdkConcurrentConversationLock.lock(JdkConcurrentConversationLock.java:44)
2015-09-22 07:38:11,964 - ERROR [org.springframework.webflow.conversation.impl.LockTimeoutException:76] - [xxx.xxx.xx.x] -
org.springframework.webflow.conversation.impl.LockTimeoutException: Unable to acquire conversation lock after 30 seconds
        at org.springframework.webflow.conversation.impl.JdkConcurrentConversationLock.lock(JdkConcurrentConversationLock.java:44)
2015-09-22 07:38:34,675 - ERROR [org.springframework.webflow.conversation.impl.LockTimeoutException:76] - [xxx.xxx.xx.x] -
org.springframework.webflow.conversation.impl.LockTimeoutException: Unable to acquire conversation lock after 30 seconds
        at org.springframework.webflow.conversation.impl.JdkConcurrentConversationLock.lock(JdkConcurrentConversationLock.java:44)
2015-09-22 07:38:39,649 - ERROR [org.springframework.webflow.conversation.impl.LockTimeoutException:76] - [xxx.xxx.xx.x] -
org.springframework.webflow.conversation.impl.LockTimeoutException: Unable to acquire conversation lock after 30 seconds
        at org.springframework.webflow.conversation.impl.JdkConcurrentConversationLock.lock(JdkConcurrentConversationLock.java:44)
2015-09-22 07:38:41,777 - ERROR [org.springframework.webflow.conversation.impl.LockTimeoutException:76] - [xxx.xxx.xx.x] -
org.springframework.webflow.conversation.impl.LockTimeoutException: Unable to acquire conversation lock after 30 seconds
        at org.springframework.webflow.conversation.impl.JdkConcurrentConversationLock.lock(JdkConcurrentConversationLock.java:44)
2015-09-22 07:38:42,126 - ERROR [org.springframework.webflow.conversation.impl.LockTimeoutException:76] - [xxx.xxx.xx.x] -
org.springframework.webflow.conversation.impl.LockTimeoutException: Unable to acquire conversation lock after 30 seconds
        at org.springframework.webflow.conversation.impl.JdkConcurrentConversationLock.lock(JdkConcurrentConversationLock.java:44)
I saw from an earlier thread that this means that the db (ldap in this case) transaction is taking a long time to being hung. However this just started this morning and we are not using a DB, just LDAP We didn't seem to have any ldap issues so I'm wondering what could cause something like this.

Jeffrey
Both pilots and IT professionals require training and currency before charging into clouds!
---------------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20150922/d9d9b5b3/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 6378 bytes
Desc: image002.jpg
URL: <http://shibboleth.net/pipermail/users/attachments/20150922/d9d9b5b3/attachment-0001.jpg>