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

sudden failure, jfs discovery, Express-c, fixed

I see the following error in the jazz.log

http-9080-Processor25] ERROR .ibm.team.jfs.app.discovery.utils.RootServicesUtil - While fetching the root services document from "http://0.0.0.0:9080/jazz/rootservices" a "404" HTTP status code was recieved

my Enterprise setup works ok..

this was working fine at midnight last night. system has not been shutdown.

Sam

http://127.0.0.1:9080/jazz/rootservices
or
http://localhost:9080/jazz/rootservices
work fine.
Sam

Windows 7, 64 bit. latest security patches (yesterday) applied. but worked after that without problem.

0 votes



3 answers

Permanent link
This sounds similar to

https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/124546

It only occurred on Windows 7, and only when the public URI is not set. You really should not be running without the public URI set, using a real, fully-qualified host name. More recent builds will be more insistent on that (you'll see warnings in the web UI and in the logs).

I see the following error in the jazz.log

http-9080-Processor25] ERROR .ibm.team.jfs.app.discovery.utils.RootServicesUtil - While fetching the root services document from "http://0.0.0.0:9080/jazz/rootservices" a "404" HTTP status code was recieved

my Enterprise setup works ok..

this was working fine at midnight last night. system has not been shutdown.

Sam

http://127.0.0.1:9080/jazz/rootservices
or
http://localhost:9080/jazz/rootservices
work fine.
Sam

Windows 7, 64 bit. latest security patches (yesterday) applied. but worked after that without problem.

0 votes


Permanent link
thanks..
|fixed by adding http://localhost as the public URI.
|
|all I have in this environment.

well.. not so fast.

I am running on my private machine which has an open port to the internet, and a fixed IP address, with a registered text name.

I added the dns name to the local hosts file, so that the use of the name on the internal machine will map to localhost.

all the internal stuff is working now.

however, the external rest based apis now are having trouble.

I did this
http://dnsname:9080/jazz/rootservices
which generated the proper document.
the service providers entry looks good,

<oslc_cm:cmServiceProviders rdf:resource="http://dnsname:9080/oslc/workitems/catalog"/>

but now produces a 404 error,
http://localhost:9080/oslc/workitems/catalog

also fails with a 404

Sam

0 votes


Permanent link
Ok, the root URI should end with the web app name

http://uri:port/jazz in my case..

Personally I think this fixed name is a very bad idea. If u have a machine that is viewed from both internal and external resources, like mine could be, there is no guaranty that I can map the names to the same string on my production network.

sam

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
× 10,936

Question asked: Oct 15 '10, 8:50 a.m.

Question was seen: 6,414 times

Last updated: Oct 15 '10, 8:50 a.m.

Confirmation Cancel Confirm