It's all about the answers!

Ask a question

Interop Manager timesout while invoking InteropServices


khayati ohri (1644) | asked Sep 19 '11, 2:16 p.m.
We have CMVC-RTC Connector which was working perfectly fine till RTC 3.0iFix 1.After upgrading our server to RTC 3.0.1 we have been facing continuous problems of defect and features not getting synced.On debugging we observed that we are continuous facing Socket Timeout from SyncIncomingAndWait() .InteropManager class is trying to invoke Rest Services through ServiceInterfaceProxy class .The call goes to invoke() method of this class which in some case or in some service is falling and thus causing Invocation Exception .The Invocation exception is caused due to SocketTimeout .It seems its trying to invoke some service which its unable to find and thus resulting into this issue .
We removed this method to use saveProxyWithStateAndUri() but the sync_status of all defects and features are always in UNINITILAIZED state which never gets changed.

More over I have been seeing the below error in my jts.log file :-

2011-09-19 00:08:23,734 ERROR service.internal.discovery.ServiceRegistrationTask - CRJAZ1678E Error during service contribution registration from https://l3aa6gt.in.ibm.com:9443/qm/scr
com.ibm.team.repository.common.TeamRepositoryException: CRJAZ1670E Error updating service contributions for application 57e12db9-f3a5-4ccb-85d1-d07c1fd8ae9a from https://l3aa6gt.in.ibm.com:9443/qm/scr
at com.ibm.team.repository.service.internal.discovery.DiscoveryService.updateServiceContributions(DiscoveryService.java:217)
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 org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:370)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:356)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)
at $Proxy431.updateServiceContributions(Unknown Source)
at com.ibm.team.repository.service.internal.discovery.ServiceRegistrationTask.updateAppServiceContributions(ServiceRegistrationTask.java:144)
at com.ibm.team.repository.service.internal.discovery.ServiceRegistrationTask.runTask(ServiceRegistrationTask.java:74)
at com.ibm.team.repository.service.async.AbstractAutoScheduledTask.executeTask(AbstractAutoScheduledTask.java:86)
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 org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:370)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:356)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)
at $Proxy432.executeTask(Unknown Source)
at com.ibm.team.repository.service.internal.scheduler.AsynchronousTaskRunner.runTask(AsynchronousTaskRunner.java:136)
at com.ibm.team.repository.service.internal.scheduler.AsynchronousTaskRunner.run(AsynchronousTaskRunner.java:99)
at java.lang.Thread.run(Thread.java:811)
Caused by:
java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:155)
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 org.apache.http.impl.io.AbstractSessionInputBuffer.fillBuffer(AbstractSessionInputBuffer.java:130)
at org.apache.http.impl.io.SocketInputBuffer.fillBuffer(SocketInputBuffer.java:127)
at org.apache.http.impl.io.AbstractSessionInputBuffer.readLine(AbstractSessionInputBuffer.java:233)
at org.apache.http.impl.conn.DefaultResponseParser.parseHead(DefaultResponseParser.java:98)
at org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:210)
at org.apache.http.impl.AbstractHttpClientConnection.receiveResponseHeader(AbstractHttpClientConnection.java:271)
at org.apache.http.impl.conn.DefaultClientConnection.receiveResponseHeader(DefaultClientConnection.java:227)
at org.apache.http.impl.conn.AbstractClientConnAdapter.receiveResponseHeader(AbstractClientConnAdapter.java:209)
at org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:292)
at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:126)
at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:483)
at com.ibm.team.jfs.app.http.client.internal.ExtensibleRequestDirector.execute(ExtensibleRequestDirector.java:145)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:641)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:576)
at com.ibm.team.repository.service.internal.discovery.DiscoveryHttpClient.getResource(DiscoveryHttpClient.java:131)
at com.ibm.team.repository.service.internal.discovery.DiscoveryService.updateSCRInfo(DiscoveryService.java:712)
at com.ibm.team.repository.service.internal.discovery.DiscoveryService.updateServiceContributions(DiscoveryService.java:214)


Also the log is full with the below exception :-

2011-09-19 00:18:54,125 WARN org.apache.http.impl.client.DefaultHttpClient - Authentication error: Unable to respond to any of these challenges: {oauth=WWW-Authenticate: OAuth realm="Jazz%20Team%20Server", oauth_problem="invalid_consumer_key"}


Since there are various other applications also which gets installed with RTC 3.0.1 we only install ccm and ldap_user application for our purpose.Could this be a problem ?

Be the first one to answer this question!


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.