Hi,
Those are just effect, not the cause itself. The real reason is elsewhere.
>From those stack traces I may assume that your CAS may be overload or
processing some requests longer than usual. When server is busy, processing
something and client tries to refresh, or open another site the connection
is broken and you may observe "java.lang.IllegalStateException: Cannot
create a session after the response has been committed"
Please create few thread dumps and analyse long running threads. You may
use such script to do so:
for i in {1..10} do; kill -3 $(ps -efww|grep [j]ava| awk '{print $2}');
sleep 5; done
It takes thread dump and wait for 5 seconds, after it it takes another
threaddump and waits for another 5 seconds... Taking summary 10 thread
dumps.
Thread dumps are written to standard output (console, or where application
server writes console output).
Only knowing what the application is currently doing may solve your issue,
and that may be in thread dumps.
Hope it helps.
Augustyn
On 8 September 2015 at 18:20, Bryan Wooten <bryan.woo...@utah.edu> wrote:
> I have also posted this to cas-users but I think you guys might have more
> experience with this type of issue. Sorry for the cross-post.
>
>
>
> In our localhost log file we occasionally get into a state where we get
> large occurrences of these 2 errors:
>
>
>
> SEVERE: Servlet.service() for servlet [cas] in context with path [/cas]
> threw exception [Request processing failed; nested exception is
> java.lang.IllegalStateException: Ca
>
> nnot create a session after the response has been committed] with root
> cause
>
> java.lang.IllegalStateException: Cannot create a session after the
> response has been committed
>
>
>
> And:
>
>
>
> 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
>
> org.springframework.webflow.conversation.impl.LockTimeoutException: Unable
> to acquire conversation lock after 30 seconds
>
>
>
> Has anyone seen this before. This causes our CASified Peoplesoft portal to
> become unstable. It usually takes several days of activity before this
> occurs.
>
>
>
> Thanks
>
>
>
>
>
> *Bryan Wooten*
>
> Tel: (801)585-9323
>
> Email: bryan.woo...@utah.edu
>
>
>
> [image: Identity & Access Management_combined centered]
>
>
>
> --
> You are currently subscribed to cas-dev@lists.jasig.org as:
> augustynw...@gmail.com
> To unsubscribe, change settings or access archives, see
> http://www.ja-sig.org/wiki/display/JSG/cas-dev
>
>
--
You are currently subscribed to cas-dev@lists.jasig.org as:
arch...@mail-archive.com
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/cas-dev
