Hi,

We are facing the below error rapidly on production. The application is deployed in websphere server. The application performance also down & weekly 2 times the application is down due to below error:-

[6/5/13 14:37:30:398 CEST] 00000059 ThreadMonitor W WSVR0605W: Thread "WebContainer : 2479" (0000128e) has been active for 606205 milliseconds and may be hung. There is/are 4 thread(s) in total in the server that may be hung.
at com.icesoft.faces.webapp.http.servlet.SessionDispatcher.checkSession(SessionDispatcher.java:100)
at com.icesoft.faces.webapp.http.servlet.SessionDispatcher.service(SessionDispatcher.java:69)
at com.icesoft.faces.webapp.http.servlet.PathDispatcher.service(PathDispatcher.java:55)
at com.icesoft.faces.webapp.http.servlet.MainServlet.service(MainServlet.java:192)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.icesoft.faces.webapp.xmlhttp.BlockingServlet.service(BlockingServlet.java:67)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1146)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1087)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:145)
at com.ge.dms.web.security.servlets.UserAccessFilter.processResponse(UserAccessFilter.java:113)
at com.ge.dms.web.security.servlets.UserAccessFilter.doFilter(UserAccessFilter.java:279)
at org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:138)
at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:190)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:130)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:87)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:848)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:691)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:588)
at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:525)
at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:90)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:764)
at com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContainer.java:1478)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:133)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:458)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:387)
at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:102)
at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)
at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:136)
at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:196)
at 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)

Whether the aplication is down due to ice faces related or not?
We are using the below jars those are required in our application:-

application is deployed based on Websphere application server version :- 6.1.0.31

Can you please check the issue? Please tell me if we required any information.

Regards,
RSY Narayan

Try to implement Websphere fixpack latest version 45 .

Hi,

I came cross similar errors not long ago.

Form WAS perspective, what you can do is:

1. To check current webcontainer settings in Threadpool, you may need to increase it when necessary.


2. Check HTTP inbound channel (HTTP_2) read/write timeout setting and TCP inbound channel (TCP_2) Inactivity timeout setting, again, you may need to increase it when necessary

But most probably the root cause of the issue comes from source code, for my case, the root cause is that developer created additional sessions in the code but without proper management of it, when I suggested them to find a work around without using session, the problem solved and the issue gone.

Hope above can shed a bit light to you.

Hi All,

Thanks for your reply.

As per your suggestion, I will check and update to you ASAP.

Regards,
RSY Narayan

I guess, you should take thread dump during the issue. As I see hung threads in logs posted by you. After analyzing thread dump and first symptom of error in logs you will be able to pin point exact root cause.. As you said, application goes down twice a week. this clearly indicates this one is working setup..
Also check with Developers for session related error in your logs..