Bugzilla – Full Text Bug Listing
| Summary: | error 500 when starting orion with orion.storage.admin.default.password option | ||
|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Krzysztof Kazmierczyk <kkazmierczyk+eclipse> |
| Component: | Client | Assignee: | Mark Macdonald <mamacdon> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | bokowski, john.arthorne, kkazmierczyk+eclipse, mamacdon, Szymon.Brandys |
| Version: | 0.2 | ||
| Target Milestone: | 0.2 | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| See Also: | https://bugs.eclipse.org/bugs/show_bug.cgi?id=340811 | ||
| Whiteboard: | |||
|
Description
Krzysztof Kazmierczyk
Can you try putting the option in the eclipse.ini file (residing in the same directory as the executable) instead of passing it from the command line? The stack trace tells me that the Jetty port number is not set; it might be that passing the vm arguments on the command line causes the vm arguments from the ini file not to be used. Hello Boris, Thank you for fast reply. It helped :) I have modified http://wiki.eclipse.org/Orion/Server_admin_guide#Creating_an_admin_user with your tip. See difference on http://wiki.eclipse.org/index.php?title=Orion%2FServer_admin_guide&diff=246937&oldid=244758 (In reply to comment #1) > Can you try putting the option in the eclipse.ini file (residing in the same > directory as the executable) instead of passing it from the command line? The > stack trace tells me that the Jetty port number is not set; it might be that > passing the vm arguments on the command line causes the vm arguments from the > ini file not to be used. > (In reply to comment #1)
> > Can you try putting the option in the eclipse.ini file (residing in the same
> > directory as the executable) instead of passing it from the command line? The
> > stack trace tells me that the Jetty port number is not set; it might be that
> > passing the vm arguments on the command line causes the vm arguments from the
> > ini file not to be used.
I was able to run Orion with the option passed as a system property. And it should be able to work this way. So I would revert the change to the wiki and investigate where the problem is first.
If any vm argument is added on the command line, it replaces all vm arguments from eclipse.ini. so this is expected behaviour. Krzysztof, thanks for updating the wiki. Mark, can you just improve the error message in this case. Rather than a NumberFormatException it should be something along the lines of "Server configuration error. Port not specified". (In reply to comment #4) > If any vm argument is added on the command line, it replaces all vm arguments > from eclipse.ini. so this is expected behaviour. My point was to use the same wording as we have in Eclipse SDK Help. In the Eclipse runtime options section we have: Listed below are the command line arguments processed by various parts of the Eclipse runtime. Many of these values can also be specified using System properties either on the command line using -D VM arguments, by specifying their values in a config.ini file or by using a <launcher>.ini file. Using the two latter techniques it is possible to customize your Eclipse without using command line arguments at all. So I thought we could follow this pattern in the Orion documentation. (In reply to comment #4) > Mark, can you just improve the error message in this case. Rather than a > NumberFormatException it should be something along the lines of "Server > configuration error. Port not specified". In Bug 340811 I made it default to 8080 if the port isn't specified, which prevents you from getting into this state. So you should be able to follow the steps Krzysztof was doing, and the hosting bundle won't kill your server. Marking fixed because the 500 error problem has been resolved. Szymon if you'd like to clean up the wiki documentation, go ahead. |