It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Follow this question
Question details

×42,788

question asked: Dec 10 '10, 4:14 a.m.
question was seen: 9,220 times
last updated: Dec 10 '10, 4:14 a.m.

Related questions

FAQ - How this Forum works

JTS Error 404: CRJZS0218E The server has not found anything

0
Milan Krivic (980●10●172●140) | asked Dec 10 '10, 4:14 a.m.
Hi,

When I try to connect to Jazz part (CCM) at RTC 3.0, by clicking on Home menu, I get this message:

A problem communicating with the Jazz Team Server discovery service has prevented the home menu from loading. Your Jazz Team Server my be configured incorrectly.

When I look at logs, I see this message:

2010-12-10 09:21:26,451 WARN net.jazz.web.app.internal.about.ConsolidatedAbout - Unable to resynconize about services: Unable to query JTS discovery :https://rtc_server:9444/jts/discovery?type=http%3A%2F%2Fjazz.net%2Fxmlns%2Fprod%2Fjazz%2Fdiscovery%2F1.0%2FApplication: HTTP status:500:Internal Server Error

Also, when I check component status, I don't get any service errors.
Any help would be appreciated,

Also, I tested it with firebug, and got this message:

The proxy is not configured to allow the request to https://rtc_server:9444/jazz/service/com.ibm.team.dashboard.common.internal.service.IDashboardRestService/viewletDefinitions?definitionIds=com.ibm.team.workitem.viewlet.statistics&webUIRoot=https%3A%2F%2Frtc_server%3A9444%2Fjazz. There may be a missing friend entry for this server.

Error: Unable to load /jts/proxy?uri=https%3A%2F%2Frtc_server%3A9444%2Fjazz%2Fservice%2Fcom.ibm.team.dashboard.common.internal.service.IDashboardRestService%2FviewletDefinitions%3FdefinitionIds%3Dcom.ibm.team.workitem.viewlet.statistics%26amp%3BwebUIRoot%3Dhttps%253A%252F%252Frtc_server%253A9444%252Fjazz status:403
Error(undefined=""Unable to load /jts/pr...44%252Fjazz status:403"") (line 0)
undefined = ""Unable to load /jts/pr...44%252Fjazz status:403""
(undefined="")E:?eta...B_en_US (line 17)
undefined = ""
()E:?eta...B_en_US (line 17)
(undefined="-19")E:?eta...B_en_US (line 17)
undefined = "-19"

Thanks,

6 answers

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Gabriel Jonsson (106●4●4) | answered Dec 10 '10, 8:20 a.m.
What have you done after the installation?

Did you run the server setup at https://<serverhostname>:<port>/jts/setup
Run this if you haven't and if you have, you can rerun it and se if it fixes any problems. That missing friend entry might be caused by CCM not being registered correctly as an application of JTS, which is a part of that setup.

Why do you use port 9444? Is there another server running at 9443 already? If you switch you have to make sure you switch ports at all appropriate locations, both in advanced server settings, and in the tomcat configuration files.
0
permanent link
Milan Krivic (980●10●172●140) | answered Dec 10 '10, 8:59 a.m.
What have you done after the installation?

Did you run the server setup at https://<serverhostname>:<port>/jts/setup
Run this if you haven't and if you have, you can rerun it and se if it fixes any problems. That missing friend entry might be caused by CCM not being registered correctly as an application of JTS, which is a part of that setup.

Why do you use port 9444? Is there another server running at 9443 already? If you switch you have to make sure you switch ports at all appropriate locations, both in advanced server settings, and in the tomcat configuration files.


It was migration from RTC 2.x. First, we were running Jazz Team Server under Tomcat, then migrated to WAS 7. I think this is not problem, because everything else works fine. Actually, this is our separated environment. In real, we should use 9443 port, and now, we want to investigate why this message happened.
I run setup after all migration steps, actually, after deploying jazz.war, jts.war and clmhelp.war applications under was.

I didn't get any error messages on setup. I rerun setup again, but problem still exists.
0
permanent link
Milan Krivic (980●10●172●140) | answered Dec 15 '10, 3:59 a.m.
What have you done after the installation?

Did you run the server setup at https://<serverhostname>:<port>/jts/setup
Run this if you haven't and if you have, you can rerun it and se if it fixes any problems. That missing friend entry might be caused by CCM not being registered correctly as an application of JTS, which is a part of that setup.

Why do you use port 9444? Is there another server running at 9443 already? If you switch you have to make sure you switch ports at all appropriate locations, both in advanced server settings, and in the tomcat configuration files.


It was migration from RTC 2.x. First, we were running Jazz Team Server under Tomcat, then migrated to WAS 7. I think this is not problem, because everything else works fine. Actually, this is our separated environment. In real, we should use 9443 port, and now, we want to investigate why this message happened.
I run setup after all migration steps, actually, after deploying jazz.war, jts.war and clmhelp.war applications under was.

I didn't get any error messages on setup. I rerun setup again, but problem still exists.

Hi gabri,

I also tried to remove registered /jazz application, restarted server, and rerun setup again, but problem still exists.

Any suggestions how to solve this?

Regards,
0
permanent link
Milan Krivic (980●10●172●140) | answered Dec 15 '10, 8:10 a.m.
What have you done after the installation?

Did you run the server setup at https://<serverhostname>:<port>/jts/setup
Run this if you haven't and if you have, you can rerun it and se if it fixes any problems. That missing friend entry might be caused by CCM not being registered correctly as an application of JTS, which is a part of that setup.

Why do you use port 9444? Is there another server running at 9443 already? If you switch you have to make sure you switch ports at all appropriate locations, both in advanced server settings, and in the tomcat configuration files.


It was migration from RTC 2.x. First, we were running Jazz Team Server under Tomcat, then migrated to WAS 7. I think this is not problem, because everything else works fine. Actually, this is our separated environment. In real, we should use 9443 port, and now, we want to investigate why this message happened.
I run setup after all migration steps, actually, after deploying jazz.war, jts.war and clmhelp.war applications under was.

I didn't get any error messages on setup. I rerun setup again, but problem still exists.

Hi gabri,

I also tried to remove registered /jazz application, restarted server, and rerun setup again, but problem still exists.

Any suggestions how to solve this?

Regards,


I cann also add this to post:

this is message response which I got from firefox firebug:

<rdf>
<rdf>
<err>com.ibm.team.jfs.app.http.HttpInternalServerErrorException: Not Found
Error 404: CRJZS0218E The server has not found anything matching the Request-URI.

at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:44)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:516)
at com.ibm.team.jfs.app.util.ErrorUtils.handleErrorResponse(ErrorUtils.java:441)
at com.ibm.team.jfs.discovery.service.internal.DiscoveryService.performQuery(DiscoveryService.java:494)
at com.ibm.team.jfs.discovery.service.internal.DiscoveryService.perform_GET(DiscoveryService.java:133)
at com.ibm.team.repository.service.TeamRawService.service(TeamRawService.java:82)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:578)
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 $Proxy269.service(Unknown Source)
at com.ibm.team.repository.servlet.AbstractTeamServerServlet.doRestService(AbstractTeamServerServlet.java:813)
at com.ibm.team.repository.servlet.AbstractTeamServerServlet.handleRequest2(AbstractTeamServerServlet.java:1829)
at com.ibm.team.repository.servlet.AbstractTeamServerServlet.handleRequest(AbstractTeamServerServlet.java:1688)
at com.ibm.team.repository.servlet.AbstractTeamServerServlet.service(AbstractTeamServerServlet.java:1598)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
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:75)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
at org.eclipse.equinox.servletbridge.BridgeServlet.service(BridgeServlet.java:120)
at com.ibm.team.repository.server.servletbridge.JazzServlet.service(JazzServlet.java:62)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1657)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:939)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:502)
at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:179)
at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:91)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:864)
at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1583)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:186)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:445)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:504)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:301)
at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:83)
at com.ibm.ws.ssl.channel.impl.SSLReadServiceContext$SSLReadCompletedCallback.complete(SSLReadServiceContext.java:1772)
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:138)
at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)
at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775)
at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1563)
</err>
<err>Not Found
Error 404: CRJZS0218E The server has not found anything matching the Request-URI.
</err>
<err>500</err>
</rdf>
</rdf>


Any help or suggestion?
0
permanent link
Gabriel Jonsson (106●4●4) | answered Dec 16 '10, 5:14 a.m.
I'm not sure if I can give any specific help, as I haven't seen exactly those error messages. I haven't actually installed any Websphere server either.

If it is the migration part that has gone wrong, I might be able to give some tips. What versions are you using (RTC 3 release?, DB2 or derby?), and what commands did you run when migrating?
0
permanent link
Milan Krivic (980●10●172●140) | answered Dec 16 '10, 9:19 a.m.
I'm not sure if I can give any specific help, as I haven't seen exactly those error messages. I haven't actually installed any Websphere server either.

If it is the migration part that has gone wrong, I might be able to give some tips. What versions are you using (RTC 3 release?, DB2 or derby?), and what commands did you run when migrating?


Hi gabri,

I reinstalled *.war applications on WAS, changed some properties in teamserver.properties files, like hostnames etc.
I did only first migration step again (copying properties from RTC 2.x teamserver.properties to RTC 3.0 jazz an jts), deployed *.war applications on was again, and rerun setup.
I am using DB2 ESE 9.7. Everything works well now.

Thanks for your info anyway.

Regards,

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.