[closed] JazzTalk can't run in 0.6M1?
Ding Jian (16●1)
| asked Aug 17 '07, 4:59 a.m.
closed Apr 30 '15, 2:29 a.m. by Krzysztof Kaźmierczyk (7.4k●3●56●99)
When I launch JazzTalk in my environment which is 0.6M1, a exception sayed that The name (Message) and namespace URI (com.example.jazztalk) do not resolve to a IItemType.
How can I fix it? Should I migrate my platform to 0.6M2.The exceptions are: WARN .team.repository.servlet.AbstractTeamServerServlet - Exception executing modelled rest service com.example.jazztalk.common.IJazzTalkService.getAllMessages java.lang.IllegalArgumentException: The name (Message) and namespace URI (com.example.jazztalk) do not resolve to a IItemType at com.ibm.team.repository.common.internal.querypath.AbstractQueryPathModel$Implementation.getItemType(AbstractQueryPathModel.java:129) at com.ibm.team.repository.common.query.IQuery$Factory.newInstance(IQuery.java:91) at com.example.jazztalk.service.JazzTalkService.getAllMessages(JazzTalkService.java:95) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:615) at com.ibm.team.repository.servlet.AbstractTeamServerServlet.doModelledRestService(AbstractTeamServerServlet.java:326) at com.ibm.team.repository.servlet.AbstractTeamServerServlet.service(AbstractTeamServerServlet.java:1047) at javax.servlet.http.HttpServlet.service(HttpServlet.java:689) at org.eclipse.equinox.http.registry.internal.ServletManager$ServletWrapper.service(ServletManager.java:177) at org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:91) at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:110) at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:76) at javax.servlet.http.HttpServlet.service(HttpServlet.java:689) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:428) at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:473) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:568) at org.mortbay.http.HttpContext.handle(HttpContext.java:1530) at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:633) at org.mortbay.http.HttpContext.handle(HttpContext.java:1482) at org.mortbay.http.HttpServer.service(HttpServer.java:909) at org.mortbay.http.HttpConnection.service(HttpConnection.java:820) at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:986) at org.mortbay.http.HttpConnection.handle(HttpConnection.java:837) at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:245) at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357) at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534) |
The question has been closed for the following reason: "Question regarding beta version" by krzysztofkazmierczyk Apr 30 '15, 2:29 a.m.
3 answers
|
thanks very much. I migranted my jazz platform to 0.6M2 then it can work very well. I found that the repotools in 0.6M1 can't process "component" child named "model". So I think the key reason for this problem is the old version's repotools is conflicted with the current plugin.xml.
Does the repotools can supply a debug option? then, we can get some detail informations during the execution. |
bld wrote:
When I launch JazzTalk in my environment which is 0.6M1, a There are two basic reasons I can think of that you might see this: 1) something is wrong with the launch 2) database was built incorrectly (JazzTalk is not in there) Look at the console for the server and see if there are any messages in there that mention jazztalk. You might see a message indicating jazztalk is in the database but not on the server (which would tend to rule out #2). One trick I've used to sanity-check the database creation is to put a System.out.println() message in JazzTalkInitializer and watch for it when repotools is running - this will help you know that you've done the right thing when juggling your plugins from the dev workspace over to the workspace that repotools uses. I actually had a problem with this same exception stack earlier this week as I updated JazzTalk for M2. My problem turned out to be #1 and it was the result of using the "Add Required Bundles" button in the launch configuration dialog. Whatever algorithm "Add Required Bundles" uses can sometimes add bundles that aren't really necessary but cause havoc for the Jazz initialization process. I've revised the advice here: https://jazz.net/wiki/bin/view/Main/JazzServerRunAndDebug to warn about using "Add Required Bundles" and I made some other clarifications, so you may want to reread that wiki topic. If you suspect the launch might be bad, I would start over with a clean launch and carefully add the bundles you think you need without using "Add Required Bundles". I hope this helps, Chris |
wirebird@163-dot-com.no-spam.invalid (bld) wrote in news:fa3ohh$kjj$1
@localhost.localdomain: How can I fix it? Should I migrate my platform to 0.6M2. Hello, I do not have an answer, but can you open a work item and subscribe me ? I want to know if we can not only fix the issue, but also improve the error message :) thanks -- Christophe Elek Serviceability Architect IBM Software Group - Rational |