It's all about the answers!

Ask a question

Why there are Operation timed out messages in logs


Guowei Jim Hu (1.0k810353) | asked Mar 26 '10, 7:57 a.m.
We start to see a few Operation time out messages in logs from remote users. Not sure the cause and how to treat them.

Any tip is appreciated.



2010-03-25 19:13:53,399 WARN .team.repository.servlet.AbstractTeamServerServlet - CRJAZ1165I Marshalling exception processing request for service "com.ibm.team.scm.common.IScmService". CRJAZ1170I The request was made by user "dinkarr@us.ibm.com" from "svl-dinkar-009030149146.svl.ibm.com". CRJAZ1166I The stack trace hash is F33158A8EF3A956C50D6A37EF9A80B435C90912F.
com.ibm.team.repository.common.internal.marshal.MarshallingException: java.net.SocketTimeoutException: Async operation timed out
at com.ibm.team.repository.common.internal.marshal.impl.EObjectMarshaller.demarshalInputStreamToObject(EObjectMarshaller.java:504)
at com.ibm.team.repository.common.internal.marshal.impl.WebServicesMarshaller.demarshalInputStreamToServiceRequest(WebServicesMarshaller.java:102)
at com.ibm.team.repository.servlet.AbstractTeamServerServlet.doPost(AbstractTeamServerServlet.java:682)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:738)
at com.ibm.team.repository.servlet.AbstractTeamServerServlet.handleRequest2(AbstractTeamServerServlet.java:1754)
at com.ibm.team.repository.servlet.AbstractTeamServerServlet.handleRequest(AbstractTeamServerServlet.java:1623)
at com.ibm.team.repository.servlet.AbstractTeamServerServlet.service(AbstractTeamServerServlet.java:1536)
.....

..... at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1550)
Caused by:
java.net.SocketTimeoutException: Async operation timed out
at com.ibm.ws.tcp.channel.impl.AioTCPReadRequestContextImpl.processSyncReadRequest(AioTCPReadRequestContextImpl.java:189)
at com.ibm.ws.tcp.channel.impl.TCPReadRequestContextImpl.read(TCPReadRequestContextImpl.java:111)
at com.ibm.ws.ssl.channel.impl.SSLReadServiceContext.read(SSLReadServiceContext.java:264)
at com.ibm.ws.http.channel.impl.HttpServiceContextImpl.fillABuffer(HttpServiceContextImpl.java:4135)
at com.ibm.ws.http.channel.impl.HttpServiceContextImpl.readSingleBlock(HttpServiceContextImpl.java:3367)

....
at com.ibm.ws.ssl.channel.impl.SSLReadServiceContext.read(SSLReadServiceContext.java:264)
at com.ibm.ws.http.channel.impl.HttpServiceContextImpl.fillABuffer(HttpServiceContextImpl.java:4135)
at com.ibm.ws.http.channel.impl.HttpServiceContextImpl.readSingleBlock(HttpServiceContextImpl.java:3367)
at com.ibm.ws.http.channel.impl.HttpServiceContextImpl.readBodyBuffer(HttpServiceContextImpl.java:3473)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundServiceContextImpl.getRequestBodyBuffer(HttpInboundServiceContextImpl.java:1704)
at com.ibm.ws.webcontainer.channel.WCCByteBufferInputStream.bufferIsGood(WCCByteBufferInputStream.java:122)
at com.ibm.ws.webcontainer.channel.WCCByteBufferInputStream.read(WCCByteBufferInputStream.java:88)
at com.ibm.ws.webcontainer.srt.http.HttpInputStream.fill(HttpInputStream.java:528)
at com.ibm.ws.webcontainer.srt.http.HttpInputStream.read(HttpInputStream.java:241)
at java.io.FilterInputStream.read(FilterInputStream.java:77)
at com.ibm.team.repository.servlet.internal.CountingInputStream.read(CountingInputStream.java:68)
at org.apache.xerces.impl.XMLEntityManager$RewindableInputStream.read(Unknown Source)
at org.apache.xerces.impl.XMLEntityManager.setupCurrentEntity(Unknown Source)
at org.apache.xerces.impl.XMLVersionDetector.determineDocVersion(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl.parse(Unknown Source)
at org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load(XMLLoadImpl.java:181)
at com.ibm.team.repository.common.internal.marshal.util.WebServicesXMLLoadImpl.load(WebServicesXMLLoadImpl.java:76)
at org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.doLoad(XMLResourceImpl.java:180)
at com.ibm.team.repository.common.internal.marshal.impl.EObjectMarshaller.demarshalInputStreamToObject(EObjectMarshaller.java:501)
... 37 more
Caused by:
com.ibm.io.async.AsyncTimeoutException(Async operation timed out, )
at com.ibm.io.async.AbstractAsyncFuture.waitForCompletion(AbstractAsyncFuture.java:359)
at com.ibm.io.async.AsyncFuture.getByteCount(AsyncFuture.java:218)
at com.ibm.ws.tcp.channel.impl.AioSocketIOChannel.readAIOSync(AioSocketIOChannel.java:215)
at com.ibm.ws.tcp.channel.impl.AioTCPReadRequestContextImpl.processSyncReadRequest(AioTCPReadRequestContextImpl.java:182)
... 62 more

4 answers



permanent link
Anthony Kesterton (7.5k7180136) | answered Mar 26 '10, 9:17 a.m.
JAZZ DEVELOPER
We start to see a few Operation time out messages in logs from remote users. Not sure the cause and how to treat them.


Try increasing the timeout in the repo connection. The user would do this via the Repository Timeout connection field in the connection properties. If doubling the number does not work - try using the Metronome on the Eclipse client to check if there is a poor connection, or problems with specific operations.

Is the end user noticing any difference or any problems?

anthony

permanent link
Guowei Jim Hu (1.0k810353) | answered Mar 29 '10, 7:39 a.m.
No complaints heard from end user yet.

The default timeout with Eclipse client is 480 seconds. Is there a different one for remote web client?

permanent link
r vijay (3676) | answered Nov 24 '10, 8:11 a.m.
Hi,

We are also facing a similar issue with same messages. Any idea why this happens?

permanent link
Pavithra Kasturirangan (42955956) | answered Oct 04 '11, 12:19 p.m.
Hi,

We are also facing a similar issue with same messages. Any idea why this happens?


Hi, Anyone knows the reason why this marshalling error occurs ?..... Even find this kind of error...When the marshalling error starts, automatically in sometime, connection to RTC drops down.

Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.