Help - Lost jts after server reset!
Help! I am doing a pilot of RTC 3.0. I installed the CodeCollaborator plug-in per http://smartbear.com/docs/manual/6.0/index.html?rtc_server_plugin_install.html. After doing this and selecting "Server Reset" to re-provision the server (which I believe rescans update repositories and installs any new plug-ins?), and then restarting the server, RTC is "dead in the water." I'm not sure if it was the CodeCollaborator plug-in itself that did it, or just doing a server reset...
When I try to log in via the web page (https://<server>:9443/ccm), it logs me in, and then takes me to the page https://<server>:9443/ccm/admin. This looks fine. In the middle area, under "Application Information," it says "Jazz Team Server Location: Connected to: https://<server>:9443/jts". If I click that link to jts, I get a Tomcat error page titled "HTTP Status 404 - ProxyServlet: /jts" with the description "The requested resource (ProxyServlet: /jts) is not available." Then lots of other problems occur - for example, when clicking the "Users"link, I get a list of users, with a red box above them that says "Not Found" with a "Details" link, which has a large stack trace in it. Also on the "About" dialog box, RTC can't get license server info - it shows "An error occurred while trying to load the Client Access License Type assignments from the Jazz Team Server. Please ensure that this application is connected to the Jazz Team Server.ID CRJAZ1788E" and the details state: Unable to load /ccm/proxy?uri=https%3A%2F%2F<server>%3A9443%2Fjts%2Fservice%2Fcom.ibm.team.repository.service.internal.ILicenseAdminRestService%2FlicenseInfo status:500 I'm not even sure where to start diagnosing this or fixing it. Help! Thanks in advance, Mike Johnson |
One answer
|
Uh, OK, now it gets stranger -- I got it working again. Here's how:
My Jazz server was running as a Windows service. (Was working fine prior to the install of the CC plugin/server reset). In order to see if the server was having any errors, I shut down the Windows service, and then ran it from the "Start Jazz Server" shortcut (so I could see the Tomcat output window). Then magically everything worked fine! So I said, "that's crazy... why would running it that way have an effect?" So I shut down the window (which shut down my server), then restarted the Windows service, to see if it would "fail" again. Lo and behold, everything now works fine! Any ideas on what happened?? Thanks, Mike |
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.