 Relationships |
|
| Anonymous | Login | 2024-04-19 22:33 CEST |
| Main | My View | View Issues |
| Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | ||||||
| ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||
| 0000081 | [jetty] regular use | minor | always | 2003-04-01 07:32 | 2003-08-11 07:00 | ||
| Reporter | james | View Status | public | ||||
| Assigned To | james | ||||||
| Priority | normal | Resolution | fixed | ||||
| Status | closed | ||||||
| Summary | 0000081: \'/etc/init.d/cswjetty stop\' does not stop | ||||||
| Description |
/etc/init.d/cswjetty and the rc scripts call $JETTY_HOME/bin/jetty.sh The default start mode is demo which does not save the PID in $JETTY_PID, so subsequent call of stop fails. When called with action \"start\" the pid is saved (line 478 of jetty.sh) but when called with action \"demo\" as default init.d there is no save (nothing after line 515), so the kill for the stop has no pid (line 485 and 487). Either jetty.sh needs fixing or the init should not use action \"demo\". I think that its good to start in demo mode the frst time so I think the jetty.sh needs fixing. I don\'t know why \"demo\" needs a separate start action, by the switch all its work is done, the case option could be: start|run|demo) and all of the run|demo part removed. |
||||||
| Additional Information |
(2nd attempt to file report, first seems to have got lost.) |
||||||
| Tags | No tags attached. | ||||||
| Attached Files | |||||||
|
|
|||||||
|
Relationships |
|
|
Notes |
|
|
(0000097) phil (reporter) 2003-04-01 11:15 |
Do you have a fair amount of experience using Jetty? Or using the java EJB type stuff in general? If so, would you like to become the jetty maintainer? I am only the jetty maintainer because no-one else stepped up. |
|
(0000100) james (manager) 2003-04-03 11:43 |
With JSP tools in general more than specifically Jetty but I\'ve moving to Jetty - partly because of the ease of the CSW packing. Tomcat gets updated every few weeks and I want updates to be easier. Actually this highlights that Jetty is a trickier one to package and maintain being bleeding edge and needing frequent attention. I see the latest version is 4.2.9 and CSW is at 4.2.3. That and the preservation of configuration - the \"you have 15 seconds to save the universe\" could be better. This is certainly a project in which I\'m interested, OK, I\'ll have a go. I\'ve already prepared some packages I want to submit to CSW. Unfortunately the first one I chose has a problem on the Intel version, the audio hangs - could it be something to do with a dodgy third party audio driver?? ;-). I\'ll continue this in the maintainer-signup... |
|
(0000142) james (manager) 2003-08-11 07:00 |
The new package for Jetty-4.2.11 includes a new jetty.sh which solves this problem. |
| Copyright © 2000 - 2008 Mantis Group |  |
