Solved

Thread times out. Please suggest

Posted on 2008-06-24
4
2,440 Views
Last Modified: 2013-12-10
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.MultipartExternalContextImpl$MultiPartServletRequestWrapper.<init>(MultipartExternalContextImpl.java:405)
      at com.ibm.faces.context.MultipartExternalContextImpl.<init>(MultipartExternalContextImpl.java:100)
      at com.ibm.faces.context.MultipartFacesContextFactoryImpl.getFacesContext(MultipartFacesContextFactoryImpl.java:66)
      at javax.faces.webapp.FacesServlet.service(FacesServlet.java:192)
      at com.ibm.ws.cache.servlet.ServletWrapper.serviceProxied(ServletWrapper.java:275)
      at com.ibm.ws.cache.servlet.CacheHook.handleFragment(CacheHook.java:461)
      at com.ibm.ws.cache.servlet.CacheHook.handleServlet(CacheHook.java:283)
      at com.ibm.ws.cache.servlet.ServletWrapper.service(ServletWrapper.java:255)
      at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:989)
      at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:930)
      at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:145)
      at com.wellpoint.edl.filter.ApplicationSessionExpiryFilter.doFilter(Unknown Source)
      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:761)
      at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:673)
      at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:498)
      at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:464)
      at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:90)
      at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:744)
      at com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContainer.java:1433)
      at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:111)
      at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:454)
      at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:383)
      at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:263)
      at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminators(NewConnectionInitialReadCallback.java:214)
      at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:113)
      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:195)
      at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:743)
      at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:873)
      at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1469)
Caused by: java.net.SocketTimeoutException: Async operation timed out
      at com.ibm.ws.tcp.channel.impl.AioTCPReadRequestContextImpl.processSyncReadRequest(AioTCPReadRequestContextImpl.java:157)
      at com.ibm.ws.tcp.channel.impl.TCPReadRequestContextImpl.read(TCPReadRequestContextImpl.java:109)
      at com.ibm.ws.http.channel.impl.HttpServiceContextImpl.fillABuffer(HttpServiceContextImpl.java:4122)
      at com.ibm.ws.http.channel.impl.HttpServiceContextImpl.readSingleBlock(HttpServiceContextImpl.java:3366)
      at com.ibm.ws.http.channel.impl.HttpServiceContextImpl.readBodyBuffer(HttpServiceContextImpl.java:3471)
      at com.ibm.ws.http.channel.inbound.impl.HttpInboundServiceContextImpl.getRequestBodyBuffer(HttpInboundServiceContextImpl.java:1606)
      at com.ibm.ws.webcontainer.channel.WCCByteBufferInputStream.bufferIsGood(WCCByteBufferInputStream.java:109)
      at com.ibm.ws.webcontainer.channel.WCCByteBufferInputStream.read(WCCByteBufferInputStream.java:79)
      at com.ibm.ws.webcontainer.srt.http.HttpInputStream.read(HttpInputStream.java:292)
      at java.io.BufferedInputStream.fill(BufferedInputStream.java:229)
      at java.io.BufferedInputStream.read(BufferedInputStream.java:246)
      at com.ibm.faces.fileupload.util.ContentLineReader.readLine(ContentLineReader.java:69)
      at com.ibm.faces.fileupload.util.MultipartContent.getContents(MultipartContent.java:71)
      at com.ibm.faces.context.MultipartExternalContextImpl$MultiPartServletRequestWrapper.<init>(MultipartExternalContextImpl.java:385)
      ... 35 more
Caused by: com.ibm.io.async.AsyncTimeoutException(Async operation timed out, [Timeout, rc=0])
      at com.ibm.io.async.AbstractAsyncFuture.waitForCompletion(AbstractAsyncFuture.java:359)
      at com.ibm.io.async.AsyncFuture.getByteCount(AsyncFuture.java:216)
      at com.ibm.ws.tcp.channel.impl.AioSocketIOChannel.readAIOSync(AioSocketIOChannel.java:214)
      at com.ibm.ws.tcp.channel.impl.AioTCPReadRequestContextImpl.processSyncReadRequest(AioTCPReadRequestContextImpl.java:150)
      ... 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.
0
Comment
Question by:srikanthradix
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
  • 2
4 Comments
 
LVL 92

Expert Comment

by:objects
ID: 21861281
it may just be that your longjdbc call is being detected and that thread gets timed out.

0
 
LVL 92

Accepted Solution

by:
objects earned 500 total points
ID: 21862353
increasing the thread monitor threshold may be the go if you expect queries to be long

0
 

Author Closing Comment

by:srikanthradix
ID: 31470212
Thanks for your time. Increasing the thread monitor threshold time worked.
0

Featured Post

Quiz: What Do These Organizations Have In Common?

Hint: Their teams ended up taking quizzes, too.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

-Xmx and -Xms are the two JVM options often used to tune JVM heap size.   Here are some common mistakes made when using them:   Assume BigApp is a java class file for the below examples. 1.         Missing m, M, g or G at the end …
This exercise is about for the following scenario: Dmgr and One node with 2 application server. Each application server contains it owns application. Application server name as follows server1 contains app1 server2 contains app1 Prereq…
The viewer will learn how to implement Singleton Design Pattern in Java.
This tutorial covers a practical example of lazy loading technique and early loading technique in a Singleton Design Pattern.

728 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question