[closed] Upgrading Server 1.0 to 1.0.1: Error 404: ProxyServlet: /ja
Tom Frauenhofer (1.3k●5●84●35)
| asked Nov 10 '08, 7:48 p.m.
closed Sep 16 '15, 6:50 a.m. by Krzysztof Kaźmierczyk (7.5k●4●80●103)
I've just upgraded a working RTC 1.0 server (WAS, DB2, Linux) using the
Installation Manager. I saved the previous teamserver.properties file. I have also restored provision_profile files. No DB migration was done (or needed I believe). WAS still has the all the JVM properties still set. Now, my Linux admin confessed that the hostname of the Linux server has changed over the weekend; not sure if that's relevant to a Jazz server. When try to use the Web UI I get: Error 404: ProxyServlet: /jazz If I use the Admin Web UI like so https://host:9443/jazz/admin I then get the UI going but errors are being reported: Provision Status CRJAZ0310I The feature with an id of "com.ibm.team.rtc.server.license.standard-trial.feature" could not be found in the update site "file:/opt/IBM/JazzTeamServer/server/update-site" referenced in the profile file "/opt/IBM/JazzTeamServer/server/provision_profiles/license-profile.ini". Verify that the feature id is correct and available in the update-site. CRJAZ0303I The profile install from "file:/opt/IBM/JazzTeamServer/server/update-site" was started at "Mon Nov 10 19:23:03 EST 2008". CRJAZ0300I Installing the feature "com.ibm.team.rtc.server.feature_0.7.0.I200810162107-28X797yV9RGrcGcCFsz-vN-3Hb1V". CRJAZ0300I Installing the feature "com.ibm.team.repository.server.feature_0.6.1.I200810162107-28a7DAtLgsJu-z-6545NDmL5YD". CRJAZ0300I Installing the feature "com.ibm.team.repository.server.emf.feature_0.6.0.I200805291754-7D7J5CYQCD4CQClK4XC". CRJAZ0299I Installing bundle from the URL "file:/opt/IBM/JazzTeamServer/server/update-site/plugins/org.eclipse.emf.common_2.3.2.v200802051830.jar". CRJAZ0299I Installing bundle from the URL "file:/opt/IBM/JazzTeamServer/server/update-site/plugins/org.eclipse.emf.commonj.sdo_2.3.0.v200802051830.jar". CRJAZ0299I Installing bundle from the URL "file:/opt/IBM/JazzTeamServer/server/update-site/plugins/org.eclipse.emf.ecore_2.3.2.v200802051830.jar". CRJAZ0299I Installing bundle from the URL "file:/opt/IBM/JazzTeamServer/server/update-site/plugins/org.eclipse.emf.ecore.change_2.3.0.v200802051830.jar". CRJAZ0299I Installing bundle from the URL "file:/opt/IBM/JazzTeamServer/server/update-site/plugins/org.eclipse.emf.ecore.sdo_2.3.0.v200802051830.jar". CRJAZ0299I Installing bundle from the URL "file:/opt/IBM/JazzTeamServer/server/update-site/plugins/org.eclipse.emf.ecore.xmi_2.3.2.v200802051830.jar". CRJAZ0299I Installing bundle from the URL "file:/opt/IBM/JazzTeamServer/server/update-site/plugins/org.eclipse.emf.mapping.ecore2xml_2.3.0.v200802051830.jar". |
The question has been closed for the following reason: "This was the question about upgrading old, not supported version." by krzysztofkazmierczyk Sep 16 '15, 6:50 a.m.
2 answers
Matt Lavin wrote:
From that error, it looks like the "license-profile.ini" file was First fixing the DB2 problem and then doing the server reset fixed the problem. Thanks for your help Dave I've just upgraded a working RTC 1.0 server (WAS, DB2, Linux) using the |
From that error, it looks like the "license-profile.ini" file was "server/license-update-site". That alone should not result in the ProxyServlet error, but it should be fixed. To solve the ProxyServlet error, can you try going to https://<yourserver>:9443/jazz/admin?internal=true#action=com.ibm.team.repository.admin.serverReset and then restating your server? In the past, the ProxyServlet error has been a result of two copies of some plugins getting installed at the same time and resetting your server should clean out the old plugins. - Matt Lavin Jazz Server Team On Mon, 2008-11-10 at 19:39 -0500, David Ward wrote: I've just upgraded a working RTC 1.0 server (WAS, DB2, Linux) using the Comments Hi Matt From that error, it looks like the "license-profile.ini" file was
Matt Lavin
commented Nov 11 '08, 10:18 a.m.
| edited Sep 16 '15, 6:49 a.m.
FORUM MODERATOR / JAZZ DEVELOPER
That error definitely won't help anything. It looks like DB2 was either Hi Matt |