Anonymous | Login | Signup for a new account | 12-17-2024 12:00 PST |
Main | My View | View Issues | Change Log | Docs |
Viewing Issue Advanced Details [ Jump to Notes ] | [ View Simple ] [ Issue History ] [ Print ] | ||||||||
ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
0001913 | [Resin] | major | always | 07-30-07 11:34 | 08-22-07 15:51 | ||||
Reporter | briandeng | View Status | public | ||||||
Assigned To | ferg | ||||||||
Priority | normal | Resolution | fixed | Platform | |||||
Status | closed | OS | |||||||
Projection | none | OS Version | |||||||
ETA | none | Fixed in Version | 3.1.3 | Product Version | 3.1.2 | ||||
Product Build | |||||||||
Summary | 0001913: Cannot get my Resin installation to run as a Windows Service | ||||||||
Description |
I can invoke httpd.exe to run Resin interactively, but using the same script to install as a service (i.e. same CLASSPATH), the watchdog service starts, but my Resin server never does. I can see a javaw.exe process start momentarily in the task manager but it quickly goes away. Also, I can't find any log files to determine why it's not starting. I've passed in the -stdout and -stderr arguments when installing the service, but the files I point to are never created. In the default installation, I can start Resin as a service, but I do not see any stdout/stderr files whether or not I pass in the -stdout/-stderr overrides. |
||||||||
Steps To Reproduce | |||||||||
Additional Information | |||||||||
Attached Files | |||||||||
|
Notes | |
(0002166) briandeng 07-31-07 11:47 |
I figured this one out. My resin.conf had a dependency on an environment variable that wasn't present when running as a service. This issue can be closed. |
Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
31 total queries executed. 26 unique queries executed. |