running the Jetty Release 1 server
Hi
I'm having trouble getting the Jetty server launched from RTC. I am using the launch configuration from the wiki (JazzServer-06-RTC10-Maximal.launch) and in my runtime I have the license plugin from server zip (in jazz/server/license-update-site/com.ibm.team.rtc.server.license.standard-trial) I keep getting an error saying at the Setup Step 4: An error occurred while saving the configuration properties. Please check your server log for more details. However, I don't see any errors written in the Tomcat server log. Please help! Thanks! Annie |
16 answers
Unfortunately, there is a mismatch between the error message and what is
actually happening. The full error is being reported to the web UI, but the web UI does not present the full error to the user. About your situation, unless you have modified the launch configuration to point to a new teamserver.properties file, running through the setup wizard will only change the settings until the server is restarted. You can specify a external teamserver.properties file by adding a VM argument to the launch configuration in the form of -Dcom.ibm.team.server.configURL=file:<your>. If you do that, then configuration modifications will be persisted from launch to launch. What settings were you trying to change through the setup wizard? aying wrote: Hi |
|
Thanks so much for your reply. Actually, I wasn't trying to change the settings of my Jetty server launched from RTC. I thought the set up wizard is a necessary step to initialize the server properly. And I thought the other 2 problems I run into are related to this server error.
Anyways, the 2 problems I'm having are related to user accounts. First, only ADMIN can log into the Jetty server launched from RTC. Any other user accounts just can't log in. A perhaps related problem that any user I created have the repository permissions check boxes grayed out (the repository permission under the User Management tab in ADMIN's page). My user accounts do have the Developer license assigned (I got the licenses from the plugin in the jazz/server/license-update-site directory from the server installation zip). I'm experiencing these problems in both the Express and the Standard Editions of the Release 1 server. Unfortunately, there is a mismatch between the error message and what is Hi |
|
In the development mode of the Jazz Team Server (using Jetty), every
user in the system is treated as having the password 'password'. Having the repository permissions checkboxes grayed out does sound like a problem. On the 'Advanced Properties' page in the Admin perspective of the web UI, what is the value of the "User Registry Type" property? In your setup, I would expect it to be 'DETECT'. aying wrote: Anyways, the 2 problems I'm having are related to user accounts. |
|
Great! My JOE user can log in now!!!!!!!!! Is there a chance that this information can be documented, like on the wiki page on "JazzServerRunAndDebug"? Or did I miss some piece of documentation that tells me this?
Regarding the User Registry Type, it is DETECT as you expected. Any other ideas of why the repository permissions are screwed up? Thanks again! Annie In the development mode of the Jazz Team Server (using Jetty), every Anyways, the 2 problems I'm having are related to user accounts. |
|
Are they grayed out for every user? When I tried it locally, I had no
problem changing the roles for the user I created. aying wrote: Great! My JOE user can log in now!!!!!!!!! Is there a chance that |
|
Thanks for help again. Yes, the repository permissions are grayed out for every user. I just realized this text may help pinpoint the issue, but I have no idea what I should do to fix it:
Notice: You are using a directory service that is not writable. User roles cannot be modified. Annie Are they grayed out for every user? When I tried it locally, I had no Great! My JOE user can log in now!!!!!!!!! Is there a chance that |
|
I was afraid that you were in that situation (a not writable user
registry), but when running in Jetty with the Detect mode, it should be writable. Could you try manually changing the property value to 'JETTY'? If there is a problem, then it should output an exception to the server console. aying wrote: Thanks for help again. Yes, the repository permissions are grayed out |
|
Do you mean modifying the User Registry Type under the Advanced Properties tab to JETTY? I tried, but when I pressed "Preview", the field automatically changed back to DETECT, and the Save button is disabled...
|
|
Sorry, I should have gave more precise directions. Yes, I meant
modifying the 'User Registry Type' property on the 'Advanced Properties' page of the admin web UI. After updating the property value, don't click 'Preview' but click 'Save' immediately. aying wrote: Do you mean modifying the User Registry Type under the Advanced |
|
Sorry... in my last message I meant to say I tried saving the User Registry property (even without hitting Preview) but it doesn't let me -- the save button is grayed out...
|
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.