Time out while sharing projects
Hi,
I have about 5291 files (135 projects) in my workspace. I tried to share them all to the Jazz Source Control. After about 6 minutes I got the following error "Sharing Projects -- Read Timed Out" The following exception is logged into the .log file. The projects I shared are displayed in the Pending Changes view under "unresolved" folder. Is it possible to increase the timeout time? What does it mean when the projects are under "unresolved" folder? Note: Auto Check-in local changes is checked in my WS. Your help would be greatly appreciated. Thanks. Stack Trace =========== !ENTRY com.ibm.team.filesystem.ide.ui 4 0 2007-08-14 12:35:35.312 !MESSAGE Error Sharing !STACK 0 com.ibm.team.repository.common.TeamRepositoryException: Read timed out at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:67) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:521) at com.ibm.team.repository.transport.client.RemoteTeamService.getAppropriateException(RemoteTeamService.java:651) at com.ibm.team.repository.transport.client.RemoteTeamService.executeMethod(RemoteTeamService.java:428) at com.ibm.team.repository.transport.client.RemoteTeamService.invoke(RemoteTeamService.java:180) at com.ibm.team.repository.transport.client.ServiceInvocationHandler.invoke(ServiceInvocationHandler.java:43) at $Proxy20.commit(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:615) at com.ibm.team.repository.client.internal.ServiceInterfaceProxy.invokeServiceCall(ServiceInterfaceProxy.java:117) at com.ibm.team.repository.client.internal.ServiceInterfaceProxy.invoke(ServiceInterfaceProxy.java:56) at $Proxy20.commit(Unknown Source) at com.ibm.team.scm.client.internal.WorkspaceConnection.commit(WorkspaceConnection.java:1196) at com.ibm.team.filesystem.rcp.core.operations.NewCheckInOperation.execute(NewCheckInOperation.java:169) at com.ibm.team.filesystem.client.operations.FileSystemOperation.run(FileSystemOperation.java:85) at com.ibm.team.filesystem.rcp.core.operations.EclipseWorkspaceCommitOperation.execute(EclipseWorkspaceCommitOperation.java:58) at com.ibm.team.filesystem.client.operations.FileSystemOperation.run(FileSystemOperation.java:85) at com.ibm.team.internal.filesystem.ui.wizards.sharing.SharingWizard$1.run(SharingWizard.java:254) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) Caused by: com.ibm.team.repository.common.transport.TeamServiceException: Read timed out at com.ibm.team.repository.transport.client.RemoteTeamService.executeHttpMethod(RemoteTeamService.java:522) at com.ibm.team.repository.transport.client.RemoteTeamService.invokePost(RemoteTeamService.java:456) at com.ibm.team.repository.transport.client.RemoteTeamService.executeMethod(RemoteTeamService.java:404) ... 17 more Caused by: java.net.SocketTimeoutException: Read timed out at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:155) 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:77) at org.apache.commons.httpclient.HttpParser.readLine(HttpParser.java:105) at org.apache.commons.httpclient.HttpConnection.readLine(HttpConnection.java:1115) at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.readLine(MultiThreadedHttpConnectionManager.java:1373) at org.apache.commons.httpclient.HttpMethodBase.readStatusLine(HttpMethodBase.java:1832) at org.apache.commons.httpclient.HttpMethodBase.readResponse(HttpMethodBase.java:1590) at org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:995) at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:397) at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:170) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:324) at com.ibm.team.repository.transport.client.RemoteTeamService.executeHttpMethod(RemoteTeamService.java:492) ... 19 more |
5 answers
On Tue, 14 Aug 2007 17:07:56 +0000, bhadrim wrote:
Is it possible to increase the timeout time? Yes, select the repository in the Team Artifacts view, open properties from the context menu, you can change the timeout in there. What does it mean when the If you hover over the icon it will tell you what it means. In this case it means that the files have not been committed to the repository. What you can do is select the unresolved node and run Check-in All. - Dmitry |
|
Thanks for the reply.
It looks like the time out issue is caused by cloudscape lock issues. Probably the server side errors must be displayed to the client which will be helpful in doing the PD. |
bhadrim@ca.ibm-dot-com.no-spam.invalid (bhadrim) wrote in news:f9v3mu$l5a$2
@localhost.localdomain: Thanks for the reply. Hello, Could you open a work item in Jazz.net and Subscribe me ? I will make sure we improve the error message and log to help troubleshoot the problem Thanks :) -- Christophe Elek Serviceability Architect IBM Software Group - Rational |
I noticed something similar when trying to load a workspace that contains
a large amount of projects and files when connected remotely via the AT&T dialer (which IBM'ers use to tunnel into the IBM intranet from remote locations or from home). The Load operation keeps dying due to 10 "connection reset by peer" errors and the AT&T dialer disconnects from the network (citing heartbeat failure). Not sure if this is a problem with the Jazz networking implementation or with AT&T dialer. I'll open a defect so you guys can investigate. |
|
Are there any exception on the server logs like SQL exception?
|
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.