The Machines have identical configuration since test environment is cloned from production, I can't figure out what's happening. Consider I've done the test with only one user working (me). And the error occurs only in logout.
________________________________ Da: Marvin Addison <[email protected]> A: [email protected] Inviato: Lunedì 11 Febbraio 2013 15:37 Oggetto: Re: [cas-user] Cas LOGUT Rejected Concurrent Exception > com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:751) > at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:881) > at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1497) > Caused by: java.util.concurrent.RejectedExecutionException Here's that the javadocs say about RejectedExecutionException: Exception thrown by an Executor when a task cannot be accepted for execution. Based on that description and that the stack trace is coming from the HTTP connection handling machinery, I'd expect that you're hitting some kind of connection limit. I have no experience whatever with Websphere, but many containers use an executor with a bounded queue to dispatch requests onto a worker pool. I'd imagine you're exceeding the queue limit or something similar. M -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
