srikanthradix
asked on
Thread times out. Please suggest
I am making a JDBC Call which is taking like 15 - 20 minutes, meanwhile the thread seems to be hung up or timed out. Here are the logs. Please suggest.
[6/24/08 10:21:12:747 EDT] 00000033 ThreadMonitor W WSVR0605W: Thread "WebContainer : 0" (0000002c) has been active for 748389 milliseconds and may be hung. There is/are 1 thread(s) in total in the server that may be hung.
[6/24/08 10:24:54:943 EDT] 00000031 ServletWrappe E SRVE0068E: Uncaught exception thrown in one of the service methods of the servlet: Faces Servlet. Exception thrown : javax.faces.FacesException : Error parsing multipart/form-data
at com.ibm.faces.context.Mult ipartExter nalContext Impl$Multi PartServle tRequestWr apper.<ini t>(Multipa rtExternal ContextImp l.java:405 )
at com.ibm.faces.context.Mult ipartExter nalContext Impl.<init >(Multipar tExternalC ontextImpl .java:100)
at com.ibm.faces.context.Mult ipartFaces ContextFac toryImpl.g etFacesCon text(Multi partFacesC ontextFact oryImpl.ja va:66)
at javax.faces.webapp.FacesSe rvlet.serv ice(FacesS ervlet.jav a:192)
at com.ibm.ws.cache.servlet.S ervletWrap per.servic eProxied(S ervletWrap per.java:2 75)
at com.ibm.ws.cache.servlet.C acheHook.h andleFragm ent(CacheH ook.java:4 61)
at com.ibm.ws.cache.servlet.C acheHook.h andleServl et(CacheHo ok.java:28 3)
at com.ibm.ws.cache.servlet.S ervletWrap per.servic e(ServletW rapper.jav a:255)
at com.ibm.ws.webcontainer.se rvlet.Serv letWrapper .service(S ervletWrap per.java:9 89)
at com.ibm.ws.webcontainer.se rvlet.Serv letWrapper .service(S ervletWrap per.java:9 30)
at com.ibm.ws.webcontainer.fi lter.WebAp pFilterCha in.doFilte r(WebAppFi lterChain. java:145)
at com.wellpoint.edl.filter.A pplication SessionExp iryFilter. doFilter(U nknown Source)
at com.ibm.ws.webcontainer.fi lter.Filte rInstanceW rapper.doF ilter(Filt erInstance Wrapper.ja va:190)
at com.ibm.ws.webcontainer.fi lter.WebAp pFilterCha in.doFilte r(WebAppFi lterChain. java:130)
at com.ibm.ws.webcontainer.fi lter.WebAp pFilterCha in._doFilt er(WebAppF ilterChain .java:87)
at com.ibm.ws.webcontainer.fi lter.WebAp pFilterMan ager.doFil ter(WebApp FilterMana ger.java:7 61)
at com.ibm.ws.webcontainer.fi lter.WebAp pFilterMan ager.doFil ter(WebApp FilterMana ger.java:6 73)
at com.ibm.ws.webcontainer.se rvlet.Serv letWrapper .handleReq uest(Servl etWrapper. java:498)
at com.ibm.ws.wswebcontainer. servlet.Se rvletWrapp er.handleR equest(Ser vletWrappe r.java:464 )
at com.ibm.ws.webcontainer.se rvlet.Cach eServletWr apper.hand leRequest( CacheServl etWrapper. java:90)
at com.ibm.ws.webcontainer.We bContainer .handleReq uest(WebCo ntainer.ja va:744)
at com.ibm.ws.wswebcontainer. WebContain er.handleR equest(Web Container. java:1433)
at com.ibm.ws.webcontainer.ch annel.WCCh annelLink. ready(WCCh annelLink. java:111)
at com.ibm.ws.http.channel.in bound.impl .HttpInbou ndLink.han dleDiscrim ination(Ht tpInboundL ink.java:4 54)
at com.ibm.ws.http.channel.in bound.impl .HttpInbou ndLink.han dleNewInfo rmation(Ht tpInboundL ink.java:3 83)
at com.ibm.ws.http.channel.in bound.impl .HttpInbou ndLink.rea dy(HttpInb oundLink.j ava:263)
at com.ibm.ws.tcp.channel.imp l.NewConne ctionIniti alReadCall back.sendT oDiscrimin ators(NewC onnectionI nitialRead Callback.j ava:214)
at com.ibm.ws.tcp.channel.imp l.NewConne ctionIniti alReadCall back.compl ete(NewCon nectionIni tialReadCa llback.jav a:113)
at com.ibm.ws.tcp.channel.imp l.AioReadC ompletionL istener.fu tureComple ted(AioRea dCompletio nListener. java:165)
at com.ibm.io.async.AbstractA syncFuture .invokeCal lback(Abst ractAsyncF uture.java :217)
at com.ibm.io.async.AsyncChan nelFuture. fireComple tionAction s(AsyncCha nnelFuture .java:161)
at com.ibm.io.async.AsyncFutu re.complet ed(AsyncFu ture.java: 136)
at com.ibm.io.async.ResultHan dler.compl ete(Result Handler.ja va:195)
at com.ibm.io.async.ResultHan dler.runEv entProcess ingLoop(Re sultHandle r.java:743 )
at com.ibm.io.async.ResultHan dler$2.run (ResultHan dler.java: 873)
at com.ibm.ws.util.ThreadPool $Worker.ru n(ThreadPo ol.java:14 69)
Caused by: java.net.SocketTimeoutExce ption: Async operation timed out
at com.ibm.ws.tcp.channel.imp l.AioTCPRe adRequestC ontextImpl .processSy ncReadRequ est(AioTCP ReadReques tContextIm pl.java:15 7)
at com.ibm.ws.tcp.channel.imp l.TCPReadR equestCont extImpl.re ad(TCPRead RequestCon textImpl.j ava:109)
at com.ibm.ws.http.channel.im pl.HttpSer viceContex tImpl.fill ABuffer(Ht tpServiceC ontextImpl .java:4122 )
at com.ibm.ws.http.channel.im pl.HttpSer viceContex tImpl.read SingleBloc k(HttpServ iceContext Impl.java: 3366)
at com.ibm.ws.http.channel.im pl.HttpSer viceContex tImpl.read BodyBuffer (HttpServi ceContextI mpl.java:3 471)
at com.ibm.ws.http.channel.in bound.impl .HttpInbou ndServiceC ontextImpl .getReques tBodyBuffe r(HttpInbo undService ContextImp l.java:160 6)
at com.ibm.ws.webcontainer.ch annel.WCCB yteBufferI nputStream .bufferIsG ood(WCCByt eBufferInp utStream.j ava:109)
at com.ibm.ws.webcontainer.ch annel.WCCB yteBufferI nputStream .read(WCCB yteBufferI nputStream .java:79)
at com.ibm.ws.webcontainer.sr t.http.Htt pInputStre am.read(Ht tpInputStr eam.java:2 92)
at java.io.BufferedInputStrea m.fill(Buf feredInput Stream.jav a:229)
at java.io.BufferedInputStrea m.read(Buf feredInput Stream.jav a:246)
at com.ibm.faces.fileupload.u til.Conten tLineReade r.readLine (ContentLi neReader.j ava:69)
at com.ibm.faces.fileupload.u til.Multip artContent .getConten ts(Multipa rtContent. java:71)
at com.ibm.faces.context.Mult ipartExter nalContext Impl$Multi PartServle tRequestWr apper.<ini t>(Multipa rtExternal ContextImp l.java:385 )
... 35 more
Caused by: com.ibm.io.async.AsyncTime outExcepti on(Async operation timed out, [Timeout, rc=0])
at com.ibm.io.async.AbstractA syncFuture .waitForCo mpletion(A bstractAsy ncFuture.j ava:359)
at com.ibm.io.async.AsyncFutu re.getByte Count(Asyn cFuture.ja va:216)
at com.ibm.ws.tcp.channel.imp l.AioSocke tIOChannel .readAIOSy nc(AioSock etIOChanne l.java:214 )
at com.ibm.ws.tcp.channel.imp l.AioTCPRe adRequestC ontextImpl .processSy ncReadRequ est(AioTCP ReadReques tContextIm pl.java:15 0)
... 48 more
I am using WebSphere App Server, Is there anyway to say not to make assumptions that the thread is hung up or something. Please suggest.
[6/24/08 10:21:12:747 EDT] 00000033 ThreadMonitor W WSVR0605W: Thread "WebContainer : 0" (0000002c) has been active for 748389 milliseconds and may be hung. There is/are 1 thread(s) in total in the server that may be hung.
[6/24/08 10:24:54:943 EDT] 00000031 ServletWrappe E SRVE0068E: Uncaught exception thrown in one of the service methods of the servlet: Faces Servlet. Exception thrown : javax.faces.FacesException
at com.ibm.faces.context.Mult
at com.ibm.faces.context.Mult
at com.ibm.faces.context.Mult
at javax.faces.webapp.FacesSe
at com.ibm.ws.cache.servlet.S
at com.ibm.ws.cache.servlet.C
at com.ibm.ws.cache.servlet.C
at com.ibm.ws.cache.servlet.S
at com.ibm.ws.webcontainer.se
at com.ibm.ws.webcontainer.se
at com.ibm.ws.webcontainer.fi
at com.wellpoint.edl.filter.A
at com.ibm.ws.webcontainer.fi
at com.ibm.ws.webcontainer.fi
at com.ibm.ws.webcontainer.fi
at com.ibm.ws.webcontainer.fi
at com.ibm.ws.webcontainer.fi
at com.ibm.ws.webcontainer.se
at com.ibm.ws.wswebcontainer.
at com.ibm.ws.webcontainer.se
at com.ibm.ws.webcontainer.We
at com.ibm.ws.wswebcontainer.
at com.ibm.ws.webcontainer.ch
at com.ibm.ws.http.channel.in
at com.ibm.ws.http.channel.in
at com.ibm.ws.http.channel.in
at com.ibm.ws.tcp.channel.imp
at com.ibm.ws.tcp.channel.imp
at com.ibm.ws.tcp.channel.imp
at com.ibm.io.async.AbstractA
at com.ibm.io.async.AsyncChan
at com.ibm.io.async.AsyncFutu
at com.ibm.io.async.ResultHan
at com.ibm.io.async.ResultHan
at com.ibm.io.async.ResultHan
at com.ibm.ws.util.ThreadPool
Caused by: java.net.SocketTimeoutExce
at com.ibm.ws.tcp.channel.imp
at com.ibm.ws.tcp.channel.imp
at com.ibm.ws.http.channel.im
at com.ibm.ws.http.channel.im
at com.ibm.ws.http.channel.im
at com.ibm.ws.http.channel.in
at com.ibm.ws.webcontainer.ch
at com.ibm.ws.webcontainer.ch
at com.ibm.ws.webcontainer.sr
at java.io.BufferedInputStrea
at java.io.BufferedInputStrea
at com.ibm.faces.fileupload.u
at com.ibm.faces.fileupload.u
at com.ibm.faces.context.Mult
... 35 more
Caused by: com.ibm.io.async.AsyncTime
at com.ibm.io.async.AbstractA
at com.ibm.io.async.AsyncFutu
at com.ibm.ws.tcp.channel.imp
at com.ibm.ws.tcp.channel.imp
... 48 more
I am using WebSphere App Server, Is there anyway to say not to make assumptions that the thread is hung up or something. Please suggest.
it may just be that your longjdbc call is being detected and that thread gets timed out.
ASKER
I am thinking about this one. Hopefully this link will resolve it.
http://publib.boulder.ibm.com/infocenter/wsdoc400/v6r0/index.jsp?topic=/com.ibm.websphere.iseries.doc/info/ae/ae/ctrb_hangdetection.html
http://publib.boulder.ibm.com/infocenter/wsdoc400/v6r0/index.jsp?topic=/com.ibm.websphere.iseries.doc/info/ae/ae/ctrb_hangdetection.html
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for your time. Increasing the thread monitor threshold time worked.