Frequent server exceptions - 503 from HTTP request: Service
I get the following exception regularly after the move from M3a to Beta 2.
It's happened about 20 times today: com.ibm.team.repository.common.transport.TeamServiceException: return code 503 from HTTP request: Service Temporarily Unavailable at com.ibm.team.repository.transport.client.RemoteTeamService.executeHttpMethod(RemoteTeamService.java:612) at com.ibm.team.repository.transport.client.RemoteTeamService.executeCancelableHttpMethod(RemoteTeamService.java:462) at com.ibm.team.repository.transport.client.RemoteTeamService.invokePost(RemoteTeamService.java:452) at com.ibm.team.repository.transport.client.RemoteTeamService.executeMethod(RemoteTeamService.java:402) at com.ibm.team.repository.transport.client.RemoteTeamService.invoke(RemoteTeamService.java:196) at com.ibm.team.repository.transport.client.ServiceInvocationHandler.invoke(ServiceInvocationHandler.java:43) at $Proxy38.fetchRootFolderDescriptors(Unknown Source) at sun.reflect.GeneratedMethodAccessor170.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at com.ibm.team.repository.client.internal.ServiceInterfaceProxy.invokeServiceCall(ServiceInterfaceProxy.java:145) at com.ibm.team.repository.client.internal.ServiceInterfaceProxy.invoke(ServiceInterfaceProxy.java:80) at $Proxy38.fetchRootFolderDescriptors(Unknown Source) at com.ibm.team.reports.client.internal.ReportManager.fetchRootFolderDescriptors(ReportManager.java:158) at com.ibm.team.reports.rcp.ui.internal.queries.RepositoryFolderQuery.fetchResult(RepositoryFolderQuery.java:149) at com.ibm.team.repository.rcp.ui.internal.viewers.RepositoryQuery.computeResult(RepositoryQuery.java:83) at com.ibm.team.repository.rcp.ui.internal.viewers.Query$1.run(Query.java:60) at com.ibm.team.repository.rcp.ui.operations.JobRunner.run(JobRunner.java:184) at com.ibm.team.repository.rcp.ui.operations.JobRunner.access$0(JobRunner.java:158) at com.ibm.team.repository.rcp.ui.operations.JobRunner$1.run(JobRunner.java:54) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) Any ideas what could be causing this? I'm connected physically to the network our repo is on. Thanks. |
2 answers
A 503 error usually means that the requested service from the client wasn't found on the server. From your trace it looks like the reports service isn't available on the server.
We talked about making this fail less intrusively, instead of logging the repository out automatically, see 41100. |
Hi
503 = Service unavailable So, you must have some component with errors (no deployed yet). Try to check the status Jin |
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.