Why can't I access my Team Repository while testing and debugging an RTC extension.
I have been building an RTC extension and today while "stepping" through the extension in debug mode the extension failed while attempting to access the Derby based Team Repository. I haven't had this happen before. I am debugging using the Jetty RTC Server. I logged into the Server Administration and checked the Component Status. I found 2 Components and their services were not functioning:
- com.ibm.teamz.supa.admin
- com.ibm.teamz.supa.search
I ran the diagnostics on Database and Database Indicies and both checked out ok.
What is causing this problem?
Accepted answer
Hi Andrew,
I have and added the following to the features list to "[RTCExt] Create RTC Test Database":
- com.ibm.teamz.supa.server.feature
- com.ibm.teamz.langdef.feature.server
- com.ibm.teamz.langdef.feature.common
- com.ibm.teamz.dsdef.feature.server
- com.ibm.teamz.dsdef.feature.common
I then have ran the launch to generate this new database. The components list now appears OK. The errors you list in your second comment ( like "10:27:29,257 [1896116484@qtp-1533631337-2] ERROR ComponentNotInstalled - Component has not been installed in the database: com.ibm.teamz.dsdef ...")
No longer appear.
I have and added the following to the features list to "[RTCExt] Create RTC Test Database":
- com.ibm.teamz.supa.server.feature
- com.ibm.teamz.langdef.feature.server
- com.ibm.teamz.langdef.feature.common
- com.ibm.teamz.dsdef.feature.server
- com.ibm.teamz.dsdef.feature.common
I then have ran the launch to generate this new database. The components list now appears OK. The errors you list in your second comment ( like "10:27:29,257 [1896116484@qtp-1533631337-2] ERROR ComponentNotInstalled - Component has not been installed in the database: com.ibm.teamz.dsdef ...")
No longer appear.
Comments
showing 5 of 6
show 1 more comments
One other answer
Hi Andrew,
I have followed https://jazz.net/library/article/1000 and the underlying principles many times and I was always able to debug, when I managed to set up Jetty and the projects following the workflow of the workshop.
One thing you have to watch for is not to clear your workspace and the dev environment on a subsequent start. If you do this, you could loose your development/test repository. If errors happen, look into the logs.
If you connected to a Tomcat with your plugin deployed I would suggest looking into the logs as well.
I have followed https://jazz.net/library/article/1000 and the underlying principles many times and I was always able to debug, when I managed to set up Jetty and the projects following the workflow of the workshop.
One thing you have to watch for is not to clear your workspace and the dev environment on a subsequent start. If you do this, you could loose your development/test repository. If errors happen, look into the logs.
If you connected to a Tomcat with your plugin deployed I would suggest looking into the logs as well.
Comments
Andrew Soloninka
Feb 12 '13, 10:49 a.m.Andrew Soloninka
Feb 12 '13, 12:30 p.m.Andrew Soloninka
Feb 12 '13, 2:54 p.m.