Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

upgrade to 2.0 - browsers OK, 2.0 RTC clients cannot login

We did a server upgrade test from 1.0 to 2.0. All appears to be fine with repository and with LDAP config. Server starts happily, setup is content with DB/mail/ldap, browser-based users can login, administer and use with delight, but attempts to login with a 2.0 RTC client result in login failures, with variations of this error message at the client, depending on platform (win/mac):

java.io.IOException: Server returned HTTP response code: 503 for URL: http://www.w3.org/TR/html4/strict.dtd

I see a similar report entered last week at http://jazz.net/forums/viewtopic.php?p=20020&sid=0f385feb766e7475172128c62999b1d6, but against 1.1.0.1, with a claim that the client operates correctly after dismissing the error. Our 2.0 users cannot continue.

Will paste full exception in a reply

0 votes



4 answers

Permanent link
jeffo@us.ibm-dot-com.no-spam.invalid (jeffo) wrote in news:h59fc2$suq$1
@localhost.localdomain:

java.io.IOException: Server returned HTTP response code: 503 for URL:
http://www.w3.org/TR/html4/strict.dtd

Jeff, 503 is ServiceUnavailable:
http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html

This means http://www.w3.org/TR/html4/strict.dtd
returns 503 - Not Jazz.

Unless there is a firewall on the server machine that prevents connection
from the server to http://www.w3.org/TR/html4/strict.dtd ?

--
Christophe Elek
Jazz L3
IBM Software Group - Rational

0 votes


Permanent link
log content from a Mac client:

!ENTRY com.ibm.team.process.rcp.ui 4 0 2009-08-04 09:37:42.437
!MESSAGE Error logged from Process RCP UI:
!STACK 0
com.ibm.team.repository.common.TeamRepositoryException: java.io.IOException: Server returned HTTP response code: 503 for URL: http://www.w3.org/TR/html4/strict.dtd
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
at com.ibm.team.repository.transport.client.RemoteTeamService.getAppropriateException(RemoteTeamService.java:681)
at com.ibm.team.repository.transport.client.RemoteTeamService.executeMethod(RemoteTeamService.java:492)
at com.ibm.team.repository.transport.client.RemoteTeamService.invoke(RemoteTeamService.java:197)
at com.ibm.team.repository.transport.client.ServiceInvocationHandler.invoke(ServiceInvocationHandler.java:43)
at $Proxy0.describe(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.ibm.team.repository.client.internal.ServiceInterfaceProxy.invokeServiceCall(ServiceInterfaceProxy.java:149)
at com.ibm.team.repository.client.internal.ServiceInterfaceProxy.invoke(ServiceInterfaceProxy.java:84)
at $Proxy0.describe(Unknown Source)
at com.ibm.team.repository.client.internal.TeamRepository$4.run(TeamRepository.java:1377)
at com.ibm.team.repository.client.internal.TeamRepository$4.run(TeamRepository.java:1)
at com.ibm.team.repository.client.internal.TeamRepository$3.run(TeamRepository.java:1164)
at com.ibm.team.repository.common.transport.CancelableCaller.call(CancelableCaller.java:79)
at com.ibm.team.repository.client.internal.TeamRepository.callCancelableService(TeamRepository.java:1157)
at com.ibm.team.repository.client.internal.TeamRepository.internalLogin(TeamRepository.java:1370)
at com.ibm.team.repository.client.internal.TeamRepository.login(TeamRepository.java:566)
at com.ibm.team.process.internal.rcp.ui.LoginAction$1.run(LoginAction.java:89)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: com.ibm.team.repository.common.internal.marshal.MarshallingException: java.io.IOException: Server returned HTTP response code: 503 for URL: http://www.w3.org/TR/html4/strict.dtd
at com.ibm.team.repository.common.internal.marshal.impl.EObjectMarshaller.demarshalInputStreamToObject(EObjectMarshaller.java:486)
at com.ibm.team.repository.transport.client.RemoteTeamService.demarshallEnvelope(RemoteTeamService.java:579)
at com.ibm.team.repository.transport.client.RemoteTeamService.invokePost(RemoteTeamService.java:528)
at com.ibm.team.repository.transport.client.RemoteTeamService.executeMethod(RemoteTeamService.java:467)
... 19 more
Caused by: java.io.IOException: Server returned HTTP response code: 503 for URL: http://www.w3.org/TR/html4/strict.dtd
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1187)
at org.eclipse.emf.ecore.resource.impl.URIHandlerImpl.createInputStream(URIHandlerImpl.java:178)
at org.eclipse.emf.ecore.resource.impl.ExtensibleURIConverterImpl.createInputStream(ExtensibleURIConverterImpl.java:301)
at org.eclipse.emf.ecore.xmi.impl.XMLHandler.resolveEntity(XMLHandler.java:810)
at com.sun.org.apache.xerces.internal.util.EntityResolverWrapper.resolveEntity(EntityResolverWrapper.java:148)
at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.resolveEntity(XMLEntityManager.java:701)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$DTDDispatcher.dispatch(XMLDocumentScannerImpl.java:1019)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1242)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:375)
at org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load(XMLLoadImpl.java:181)
at com.ibm.team.repository.common.internal.marshal.util.WebServicesXMLLoadImpl.load(WebServicesXMLLoadImpl.java:76)
at org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.doLoad(XMLResourceImpl.java:180)
at com.ibm.team.repository.common.internal.marshal.impl.EObjectMarshaller.demarshalInputStreamToObject(EObjectMarshaller.java:483)
... 22 more

0 votes


Permanent link
jeffo@us.ibm-dot-com.no-spam.invalid (jeffo) wrote in news:h59fc2$suq$1
@localhost.localdomain:

java.io.IOException: Server returned HTTP response code: 503 for URL:
http://www.w3.org/TR/html4/strict.dtd

Jeff, 503 is ServiceUnavailable:
http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html

This means http://www.w3.org/TR/html4/strict.dtd
returns 503 - Not Jazz.

Unless there is a firewall on the server machine that prevents connection
from the server to http://www.w3.org/TR/html4/strict.dtd ?

--
Christophe Elek
Jazz L3
IBM Software Group - Rational

Thanks Christophe, you posted so fast that I missed it!

I can successfully wget that url from command line, so no obvious physical barrier/firewall. Are there any other diags I can do to prove that my Jazz process is able to reach the internet?

The error is only reported through the client UI/log - I find no error on the server. Should I be looking somewhere other than <jazzinstalldir>/server/logs and <jazzinstalldir>/server/tomcat/logs/catalina.log?

0 votes


Permanent link
Found it! Reasonably cool User Error, with some misdirection from the error messages. The key is in the URL used in configuring the repo connection...

URL to use for browsers - https://<servername>:<port>/jazz/web
URL to use for clients - https://<servername>:<port>/jazz

If you happen to make the mistake of pasting the browser URL (.../web) into a repository config field in the RTC client, you wind up with the mystifying 503 errors.

I'm inclined to think that there may be something worth fixing in that flow - don't really want my server generating unintended outbound web requests (if that's really what happens in this case), and certainly could have benefited from a more relevant error message somewhere.

0 votes

Your answer

Register or log in 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.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details

Question asked: Aug 04 '09, 9:57 a.m.

Question was seen: 7,030 times

Last updated: Aug 04 '09, 9:57 a.m.

Confirmation Cancel Confirm