It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,884

question asked: Aug 07 '09, 3:39 p.m.
question was seen: 13,091 times
last updated: Aug 07 '09, 3:39 p.m.

Related questions

Error 500: Failed to determine authentication method

0
Thaddee Bourque (61●2●6●4) | asked Aug 07 '09, 3:39 p.m.
Hi,

We recently upgraded RTC from 1.0.1.1 to 2.0 using Installation Manager. We are running RTC with WAS & DB2. Since the upgrade, we've not been able to get RTC running properly. After correcting a few of the issues, we're are now able to log into RTC via the admin page (https://<server>/jazz/admin) and access the project areas from there however, when trying to access RTC via https://<server>/jazz/web, we receive a 500 Internal Error with the message "Error 500: Failed to determine authentication method". This exception and it's stack is also found in the SystemOut.log file.

We are also seeing the following error message repeatedly in the jazz.log file -> "Error while fetching and parsing the root services document".

Any insight would be greatly appreciated.

Thanks,
Thaddee

10 answers

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Anthony Kesterton (7.5k●9●180●136) | answered Aug 07 '09, 6:00 p.m.
JAZZ DEVELOPER
Hi,

We recently upgraded RTC from 1.0.1.1 to 2.0 using Installation Manager. We are running RTC with WAS & DB2. Since the upgrade, we've not been able to get RTC running properly. After correcting a few of the issues, we're are now able to log into RTC via the admin page (https://<server>/jazz/admin) and access the project areas from there however, when trying to access RTC via https://<server>/jazz/web, we receive a 500 Internal Error with the message "Error 500: Failed to determine authentication method". This exception and it's stack is also found in the SystemOut.log file.

We are also seeing the following error message repeatedly in the jazz.log file -> "Error while fetching and parsing the root services document".

Any insight would be greatly appreciated.

Thanks,
Thaddee


Something that has fixed other problems, and you might want to try, is clear out your browser cache. Also - try accessing https://<server>:<port>/jazz - forget the /web on the end. I am running on the default https port of 9443 - you may be using something different.

anthony
0
permanent link
Christophe Elek (2.9k●1●30●21) | answered Aug 08 '09, 12:58 a.m.
JAZZ DEVELOPER
tbourque@ca.ibm-dot-com.no-spam.invalid (tbourque) wrote in news:h5i0mp$k61
$1@localhost.localdomain:

We are running RTC with WAS & DB2. Since the upgrade,
we've not been able to get RTC running properly.

Hello Thadde,
Before we dig in the diagnosis, can you make sure we have the WAS setup ok
for 2.0 ?
We need 6.1.0.23 or 7.0.0.3, and on top of the WAS version weneed the JDK
iFix for RTC (search WAS RTC JDK Fix on the IBM Support page)

Then , check the log , usually the 500 is caused by... and the last embeded
stack trace reveals the error

Finally, check you setup the new JAZZ_HOME and you setup the new WAS
security option as as per the infocenter

Regarding "Error while fetching and parsing the root
services document".... umm, that may be a red hering or a consequence of
the setup above

--
Christophe Elek
Jazz L3
IBM Software Group - Rational
0
permanent link
Thaddee Bourque (61●2●6●4) | answered Aug 10 '09, 8:06 a.m.


Something that has fixed other problems, and you might want to try, is clear out your browser cache. Also - try accessing https://<server>:<port>/jazz - forget the /web on the end. I am running on the default https port of 9443 - you may be using something different.

anthony


Thanks Anthony,

We've tried clearing the cache and accessing the URL https://<server>:<port>/jazz and still receive the 500 Internal error.

Thaddee
0
permanent link
Thaddee Bourque (61●2●6●4) | answered Aug 10 '09, 9:52 a.m.
Thanks Christophe - please see the answers to your questions below.

We need 6.1.0.23 or 7.0.0.3, and on top of the WAS version weneed the JDK iFix for RTC (search WAS RTC JDK Fix on the IBM Support page)

We have the following installed.
AppServer: WebSphere Platform 6.1
JVM: C:\Program Files\IBM\WebSphere\AppServer\java\bin>java -fullversion
java full version "J2RE 1.5.0 IBM Windows 32 build pwi32devifx-20090505 (SR9-0 + IZ49764)"

Then , check the log , usually the 500 is caused by... and the last embeded stack trace reveals the error

00000025 ServletWrappe E SRVE0068E: Uncaught exception thrown in one of the service methods of the servlet: equinoxbridgeservlet. Exception thrown : javax.servlet.ServletException: Failed to determine authentication method
at com.ibm.team.repository.service.internal.identity.UserIdentityHelper.getAuthMethod(UserIdentityHelper.java:243)
at com.ibm.team.repository.servlet.AbstractTeamServerServlet.service(AbstractTeamServerServlet.java:1426)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at org.eclipse.equinox.http.registry.internal.ServletManager$ServletWrapper.service(ServletManager.java:180)
at org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:59)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at org.eclipse.equinox.servletbridge.BridgeServlet.service(BridgeServlet.java:121)
at com.ibm.team.repository.server.servletbridge.JazzServlet.service(JazzServlet.java:54)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1143)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:591)
at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:481)
at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3453)
at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:267)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:815)
at com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContainer.java:1466)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:119)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:458)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:387)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:267)
at com.ibm.ws.ssl.channel.impl.SSLConnectionLink.determineNextChannel(SSLConnectionLink.java:1037)
at com.ibm.ws.ssl.channel.impl.SSLConnectionLink$MyReadCompletedCallback.complete(SSLConnectionLink.java:644)
at com.ibm.ws.ssl.channel.impl.SSLReadServiceContext$SSLReadCompletedCallback.complete(SSLReadServiceContext.java:1818)
at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)
at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:136)
at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:196)
at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:751)
at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:881)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1473)
---- Begin backtrace for Nested Throwables
java.net.SocketException: Operation timed out: connect:could be due to invalid address
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:391)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:252)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:239)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:385)
at java.net.Socket.connect(Socket.java:543)
at com.ibm.jsse2.jc.connect(jc.java:135)
at com.ibm.team.repository.service.internal.identity.NaiveSSLSocketFactory.connectSocket(NaiveSSLSocketFactory.java:97)
at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:129)
at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:164)
at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:119)
at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:349)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:555)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:487)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:465)
at com.ibm.team.repository.service.internal.identity.UserIdentityHelper.determineAuthMethod(UserIdentityHelper.java:145)
at com.ibm.team.repository.service.internal.identity.UserIdentityHelper.determineAuthMethod(UserIdentityHelper.java:122)
at com.ibm.team.repository.service.internal.identity.UserIdentityHelper.getAuthMethod(UserIdentityHelper.java:241)
at com.ibm.team.repository.servlet.AbstractTeamServerServlet.service(AbstractTeamServerServlet.java:1426)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at org.eclipse.equinox.http.registry.internal.ServletManager$ServletWrapper.service(ServletManager.java:180)
at org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:59)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at org.eclipse.equinox.servletbridge.BridgeServlet.service(BridgeServlet.java:121)
at com.ibm.team.repository.server.servletbridge.JazzServlet.service(JazzServlet.java:54)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1143)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:591)
at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:481)
at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3453)
at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:267)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:815)
at com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContainer.java:1466)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:119)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:458)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:387)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:267)
at com.ibm.ws.ssl.channel.impl.SSLConnectionLink.determineNextChannel(SSLConnectionLink.java:1037)
at com.ibm.ws.ssl.channel.impl.SSLConnectionLink$MyReadCompletedCallback.complete(SSLConnectionLink.java:644)
at com.ibm.ws.ssl.channel.impl.SSLReadServiceContext$SSLReadCompletedCallback.complete(SSLReadServiceContext.java:1818)
at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)
at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:136)
at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:196)
at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:751)
at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:881)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1473)

00000025 WebApp E -: java.net.SocketException: Operation timed out: connect:could be due to invalid address
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:391)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:252)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:239)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:385)
at java.net.Socket.connect(Socket.java:543)
at com.ibm.jsse2.jc.connect(jc.java:135)
at com.ibm.team.repository.service.internal.identity.NaiveSSLSocketFactory.connectSocket(NaiveSSLSocketFactory.java:97)
at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:129)
at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:164)
at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:119)
at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:349)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:555)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:487)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:465)
at com.ibm.team.repository.service.internal.identity.UserIdentityHelper.determineAuthMethod(UserIdentityHelper.java:145)
at com.ibm.team.repository.service.internal.identity.UserIdentityHelper.determineAuthMethod(UserIdentityHelper.java:122)
at com.ibm.team.repository.service.internal.identity.UserIdentityHelper.getAuthMethod(UserIdentityHelper.java:241)
at com.ibm.team.repository.servlet.AbstractTeamServerServlet.service(AbstractTeamServerServlet.java:1426)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at org.eclipse.equinox.http.registry.internal.ServletManager$ServletWrapper.service(ServletManager.java:180)
at org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:59)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at org.eclipse.equinox.servletbridge.BridgeServlet.service(BridgeServlet.java:121)
at com.ibm.team.repository.server.servletbridge.JazzServlet.service(JazzServlet.java:54)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1143)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:591)
at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:481)
at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3453)
at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:267)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:815)
at com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContainer.java:1466)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:119)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:458)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:387)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:267)
at com.ibm.ws.ssl.channel.impl.SSLConnectionLink.determineNextChannel(SSLConnectionLink.java:1037)
at com.ibm.ws.ssl.channel.impl.SSLConnectionLink$MyReadCompletedCallback.complete(SSLConnectionLink.java:644)
at com.ibm.ws.ssl.channel.impl.SSLReadServiceContext$SSLReadCompletedCallback.complete(SSLReadServiceContext.java:1818)
at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)
at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:136)
at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:196)
at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:751)
at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:881)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1473)

Finally, check you setup the new JAZZ_HOME and you setup the new WAS security option as as per the infocenter

JAZZ_HOME = file:///D:/Program%20Files/IBM/JazzTeamServer/server/conf


Please let me know if anything in here sticks out or if you require additional information.

Thanks again!
Thaddee
0
permanent link
Christophe Elek (2.9k●1●30●21) | answered Aug 10 '09, 10:23 p.m.
JAZZ DEVELOPER
tbourque@ca.ibm-dot-com.no-spam.invalid (tbourque) wrote in news:h5p8nt$ves
$1@localhost.localdomain:

Please let me know if anything in here sticks out or if you require
additional information.

Ahhhh, I seem to recall that the server is calling itself upon
authentication. And it seems the strack trace states that it cannot connect
to itself.

Is taht enough info for you to check teh IP Stack and DNS or do you want me
to clarify ?

--
Christophe Elek
Jazz L3
IBM Software Group - Rational
0
permanent link
Christophe Elek (2.9k●1●30●21) | answered Aug 11 '09, 7:26 a.m.
JAZZ DEVELOPER
tbourque@ca.ibm-dot-com.no-spam.invalid (tbourque) wrote in news:h5s1gh$6eb
$2@localhost.localdomain:

So it sounds
like the application is trying to call itself by using the client's
URL and not localhost which may be causing this issue. Should it be
this way? This did not seem to be the case in the previous version.

Thanks again for your assistance.
Thaddee


Correct, it did not work that way in 2.0
I am wondering if the property 'Host Name' set to localhost, would not help
?

--
Christophe Elek
Jazz L3
IBM Software Group - Rational
0
permanent link
Thaddee Bourque (61●2●6●4) | answered Aug 11 '09, 11:01 a.m.

Ahhhh, I seem to recall that the server is calling itself upon
authentication. And it seems the strack trace states that it cannot connect
to itself.


Thanks for the response Christophe.

I performed a few tests based on the information you provided and found that when I access the application directly from the server using either https://localhost:9444/jazz/web or https://10.x.x.x:9444/jazz/web, the application responds properly however, when trying to access the application from outside the customer's network using the NAT'd address (https://96.x.x.x:9444/jazz/web), I get the 500 error. So it sounds like the application is trying to call itself by using the client's URL and not localhost which may be causing this issue. Should it be this way? This did not seem to be the case in the previous version.

Thanks again for your assistance.
Thaddee
0
permanent link
Clement Liu (1.5k●5●43●49) | answered Aug 29 '10, 2:38 p.m.
We had the same issue during our upgrade from 2.0 to 2002 ifix2 and we found it was because after we redeployed the jazz.war on WAS, our setting on WAS automatically kicked off a script to regenerate the IHS plug-in and the regeneration messed up and pointed to a wrong folder of SSL certificate. This is why we got a lot of SSL and 500 errors. Once we fixed the plug-in xml file and everything is fine now... :D
0
permanent link
Omprakash Thammishety (146●1●17●8) | answered Nov 08 '11, 11:06 a.m.
I am facing the similar kind of error after reboot of my server. How does it fixed your problem. Can you please let me know the resolution. Its really gr8 help to me.

Thanks,
Om
0
permanent link
Omprakash Thammishety (146●1●17●8) | answered Nov 08 '11, 2:50 p.m.
There was internal firewall enabled. I ran the below 2 commands then worked fine.

service iptables off
chkconfig iptables off

It may help and save other life.

Thanks,
Om

Your answer

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.