IllegalStateException when logging to RTC
Hi we are using RTC 1.0.1 running on ubuntu 8.10 (desktop) and everything worked fine and dandy until recently.
Using the RTC cilent in RAD 7.5 (on winXP) I get the following error:
Done a few googles and searched the forum but no clues, anyone got any ideas?
The only thing that changed around a similar time is that i apllyed the ubuntu updates.
Cheers,
Scotty
Using the RTC cilent in RAD 7.5 (on winXP) I get the following error:
An internal error occurred during: "Logging into 130.1.4.52".
java.lang.IllegalStateException: Authentication state already initialized.
Done a few googles and searched the forum but no clues, anyone got any ideas?
The only thing that changed around a similar time is that i apllyed the ubuntu updates.
Cheers,
Scotty
3 answers
Do you have the complete trace? I've never seen this before.
Jea-Michel
Here we go, it seems to be my machine/RAD has the issue as my colleague can connect ok (any help is appreciated)
!ENTRY org.eclipse.core.jobs 4 2 2009-05-26 14:13:58.749
!MESSAGE An internal error occurred during: "Logging into 130.1.4.52".
!STACK 0
com.ibm.team.repository.common.transport.ServiceMethodInvocationError: java.lang.IllegalStateException: Authentication state already initialized
at com.ibm.team.repository.transport.client.RemoteTeamService.getAppropriateException(Unknown Source)
at com.ibm.team.repository.transport.client.RemoteTeamService.executeMethod(Unknown Source)
at com.ibm.team.repository.transport.client.RemoteTeamService.invoke(Unknown Source)
at com.ibm.team.repository.transport.client.ServiceInvocationHandler.invoke(Unknown Source)
at $Proxy0.describe(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.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(Unknown Source)
at com.ibm.team.repository.client.internal.ServiceInterfaceProxy.invoke(Unknown Source)
at $Proxy0.describe(Unknown Source)
at com.ibm.team.repository.client.internal.TeamRepository$4.run(Unknown Source)
at com.ibm.team.repository.client.internal.TeamRepository$4.run(Unknown Source)
at com.ibm.team.repository.client.internal.TeamRepository$3.run(Unknown Source)
at com.ibm.team.repository.common.transport.CancelableCaller.call(Unknown Source)
at com.ibm.team.repository.client.internal.TeamRepository.callCancelableService(Unknown Source)
at com.ibm.team.repository.client.internal.TeamRepository.internalLogin(Unknown Source)
at com.ibm.team.repository.client.internal.TeamRepository.login(Unknown Source)
at com.ibm.team.process.internal.rcp.ui.LoginAction$1.run(Unknown Source)
at org.eclipse.core.internal.jobs.Worker.run(Unknown Source)
Caused by: java.lang.IllegalStateException: Authentication state already initialized
at org.apache.commons.httpclient.auth.AuthState.setPreemptive(Unknown Source)
at org.apache.commons.httpclient.HttpMethodDirector.executeConnect(Unknown Source)
at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(Unknown Source)
at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(Unknown Source)
at org.apache.commons.httpclient.HttpClient.executeMethod(Unknown Source)
at org.apache.commons.httpclient.HttpClient.executeMethod(Unknown Source)
at com.ibm.team.repository.transport.client.ClientHttpUtil.executeHttpMethod(Unknown Source)
at com.ibm.team.repository.transport.client.RemoteTeamService.executeCancelableHttpMethod(Unknown Source)
at com.ibm.team.repository.transport.client.RemoteTeamService.invokePost(Unknown Source)
... 20 more
com.ibm.team.repository.client.internal.ServiceInterfaceProxy.invokeServiceCall(Unknown Source)
at com.ibm.team.repository.client.internal.ServiceInterfaceProxy.invoke(Unknown Source)
at $Proxy0.describe(Unknown Source)
This got me thinking about proxy server and proxy auth and figured out the problem.
1)I'd changed my windows password and so the cached version on eclispe was old password - which is causing the error
2)The RTC server should be added to the "No Proxy for" list as don't need to go via proxy for internal network traffic.
Maybe a more meaningful error message is needed?