It's all about the answers!

Ask a question

Intermittent java.net.SocketTimeoutException error on loading local workspace


Jaygee Santos (272811) | asked Jul 23 '13, 7:25 p.m.
retagged Jul 24 '13, 8:46 a.m. by Laura W. Hinson (16126)

We only see this issue on our RTC production environment and it happens intermittently when loading a local workspace.  The error is not limited to one project area or component as it has been seen when loading other workspaces with different components from other project areas.

The main symptom is that as you select to Load your repository workspace into your Eclipse workspace, the load process gets stuck on the "Acquiring file list for <component>" step and it is at the 10% progress level.

It gets stuck there for a long time (15-20 minutes) and then it errors out with the message:

CRJAZ0099I When accessing the URL "https://jazzserver:9443/ccm/service/com.ibm.team.filesystem.common.IFilesystemService" the following HTTP error occurred: "java.net.SocketTimeoutException"

I have opened a PMR already for this but wanted to post this in case anyone else has experienced the problem.  The only workaround right now is to retry loading again later, which is not always convenient when you're on a deadline.

Server on JTS/RTC 4.0.0 on Windows 2008, Oracle db and using WAS 7.0.0.17.

Error has been seen on all these clients - RTC 3.0.1.2 standalone client; RTC 3.0.1.2 Ext on RAD8.0; RTC 4.0.0.0 Ext on RAD8.5; RTC 4.0.0 Windows shell

com.ibm.team.repository.common.transport.TeamServiceException: CRJAZ0099I When accessing the URL "https://jazzserver:9443/ccm/service/com.ibm.team.filesystem.common.IFilesystemService" the following HTTP error occurred: "java.net.SocketTimeoutException"

at com.ibm.team.repository.transport.client.ClientHttpUtil.executePrimitiveRequest(ClientHttpUtil.java:1192)

at com.ibm.team.repository.transport.client.ClientHttpUtil.executeHttpMethod(ClientHttpUtil.java:328)

at com.ibm.team.repository.transport.client.ClientHttpUtil.executeHttpMethod(ClientHttpUtil.java:290)

at com.ibm.team.repository.transport.client.ClientHttpUtil.executeHttpMethod(ClientHttpUtil.java:204)

at com.ibm.team.repository.transport.client.RemoteTeamService.executeCancelableHttpMethod(RemoteTeamService.java:566)

at com.ibm.team.repository.transport.client.RemoteTeamService.invokePost(RemoteTeamService.java:545)

at com.ibm.team.repository.transport.client.RemoteTeamService.executeMethod(RemoteTeamService.java:485)

at com.ibm.team.repository.transport.client.RemoteTeamService.invoke(RemoteTeamService.java:202)

at com.ibm.team.repository.transport.client.ServiceInvocationHandler.invoke(ServiceInvocationHandler.java:43)

at $Proxy30.compareWorkspaces(Unknown Source)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:618)

at com.ibm.team.repository.client.internal.ServiceInterfaceProxy.invokeServiceCall(ServiceInterfaceProxy.java:164)

at com.ibm.team.repository.client.internal.ServiceInterfaceProxy.invoke(ServiceInterfaceProxy.java:88)

at $Proxy30.compareWorkspaces(Unknown Source)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:618)

at com.ibm.team.scm.client.internal.ScmServiceInterfaceProxy$2.run(ScmServiceInterfaceProxy.java:168)

at com.ibm.team.repository.client.internal.TeamRepository$3.run(TeamRepository.java:1261)

at com.ibm.team.repository.common.transport.CancelableCaller.call(CancelableCaller.java:79)

at com.ibm.team.repository.client.internal.TeamRepository.callCancelableService(TeamRepository.java:1254)

at com.ibm.team.scm.client.internal.ScmClientLibraryContext.callCancelableService(ScmClientLibraryContext.java:70)

at com.ibm.team.scm.client.internal.ScmServiceInterfaceProxy.invokeCancelableService(ScmServiceInterfaceProxy.java:164)

at com.ibm.team.scm.client.internal.ScmServiceInterfaceProxy.invoke(ScmServiceInterfaceProxy.java:92)

at $Proxy30.compareWorkspaces(Unknown Source)

at com.ibm.team.filesystem.client.internal.FileSystemServiceProxy.compareAsWorkspaces(FileSystemServiceProxy.java:654)

at com.ibm.team.filesystem.client.internal.FileSystemView.compareAsWorkspaces(FileSystemView.java:136)

at com.ibm.team.filesystem.rcp.core.internal.changes.model.SyncCache.fetch(SyncCache.java:132)

at com.ibm.team.filesystem.rcp.core.internal.changes.operations.CompareToOperation.compareChangeHistoryQuery(CompareToOperation.java:506)

at com.ibm.team.filesystem.rcp.core.internal.changes.operations.CompareToOperation.execute(CompareToOperation.java:110)

at com.ibm.team.filesystem.client.internal.operations.FileSystemOperation.run(FileSystemOperation.java:89)

at com.ibm.team.filesystem.rcp.core.internal.changes.util.CompareToNode$1.computeItemsAndChildren(CompareToNode.java:147)

at com.ibm.team.filesystem.rcp.core.internal.changes.util.mutator.ModelMutator$MutateQueryVisitor.visit(ModelMutator.java:401)

at com.ibm.team.filesystem.rcp.core.internal.changes.util.mutator.ModelMutator$MutateQueryVisitor.start(ModelMutator.java:395)

at com.ibm.team.filesystem.rcp.core.internal.changes.util.mutator.ModelMutator$MutateQueryVisitor.start(ModelMutator.java:387)

at com.ibm.team.filesystem.rcp.core.internal.changes.util.mutator.ModelMutator.refreshImpl(ModelMutator.java:177)

at com.ibm.team.filesystem.rcp.core.internal.changes.util.mutator.ModelMutator.refresh(ModelMutator.java:158)

at com.ibm.team.filesystem.rcp.core.internal.changes.util.ComponentSyncContext.refreshCompare(ComponentSyncContext.java:845)

at com.ibm.team.filesystem.rcp.core.internal.changes.util.ComponentSyncContext.refreshCompare(ComponentSyncContext.java:827)

at com.ibm.team.filesystem.rcp.core.internal.changes.model.ComponentCollaborationUtil.setCollaboration(ComponentCollaborationUtil.java:92)

at com.ibm.team.filesystem.rcp.core.internal.changes.model.ComponentCollaborationUtil.updateCollaborations(ComponentCollaborationUtil.java:223)

at com.ibm.team.filesystem.rcp.core.internal.changes.util.listeners.UpdateChangesJob.run(UpdateChangesJob.java:242)

at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

Caused by: java.net.SocketTimeoutException

at sun.nio.ch.SocketAdaptor$SocketInputStream.read(SocketAdaptor.java:250)

at sun.nio.ch.ChannelInputStream.read(ChannelInputStream.java:103)

at com.ibm.team.repository.transport.client.InterruptableSocket$InterruptableSocketInputStream.read(InterruptableSocket.java:583)

at com.ibm.jsse2.a.a(a.java:56)

at com.ibm.jsse2.a.a(a.java:238)

at com.ibm.jsse2.jc.a(jc.java:121)

at com.ibm.jsse2.jc.a(jc.java:249)

at com.ibm.jsse2.e.read(e.java:34)

at java.io.BufferedInputStream.fill(BufferedInputStream.java:229)

at java.io.BufferedInputStream.read(BufferedInputStream.java:246)

at org.apache.commons.httpclient.HttpParser.readRawLine(HttpParser.java:78)

at org.apache.commons.httpclient.HttpParser.readLine(HttpParser.java:106)

at org.apache.commons.httpclient.HttpConnection.readLine(HttpConnection.java:1116)

at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.readLine(MultiThreadedHttpConnectionManager.java:1413)

at org.apache.commons.httpclient.HttpMethodBase.readStatusLine(HttpMethodBase.java:1973)

at org.apache.commons.httpclient.HttpMethodBase.readResponse(HttpMethodBase.java:1735)

at org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:1098)

at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:398)

at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)

at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)

at com.ibm.team.repository.transport.client.ClientHttpUtil.executePrimitiveRequest(ClientHttpUtil.java:1141)

... 46 more

One answer



permanent link
Krzysztof Ka┼║mierczyk (7.4k35499) | answered Jul 24 '13, 2:56 a.m.
Hello Jaygee,
I would use WAIT Tool to see the stress on your server in RTC client when the issue happens. Probably you will be asked for doing that in the PMR.

Your answer


Register or to post your answer.