You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Mladen Turk (Resolved) (JIRA)" <ji...@apache.org> on 2011/11/04 11:17:00 UTC
[jira] [Resolved] (DAEMON-219) prunsrv error 1067 and crash on
Windows 7
[ https://issues.apache.org/jira/browse/DAEMON-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mladen Turk resolved DAEMON-219.
--------------------------------
Resolution: Fixed
Fix Version/s: 1.0.8
Fixed in the trunk.
You were missing --StopClass which was causing procrun to crash. Now it defaults to java.lang.System, and stopping
service will call System.exit.
Implement your own StopClass that will exit the main method cleanly. If you need further assistance use commons users list.
> prunsrv error 1067 and crash on Windows 7
> -----------------------------------------
>
> Key: DAEMON-219
> URL: https://issues.apache.org/jira/browse/DAEMON-219
> Project: Commons Daemon
> Issue Type: Bug
> Components: Procrun
> Affects Versions: 1.0.7
> Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 12:31:09-0500)
> Maven home: C:\Java\apache-maven-3.0.3\bin\..
> Java version: 1.6.0_24, vendor: Sun Microsystems Inc.
> Java home: C:\Program Files\Java\jdk1.6.0_24\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
> Reporter: Gary D. Gregory
> Assignee: Mladen Turk
> Fix For: 1.0.8
>
> Attachments: Daemon-219.zip, Daemon-219.zip, LdeServer3.reg, NoKey.PNG, SystemLdeService3.txt, WER8D3F.tmp.WERInternalMetadata.xml, WERA3BC.tmp.appcompat.txt, WERA3BD.tmp.mdmp, commons-daemon.2011-10-03.log, install-lde-service.cmd, ldeservice3-stderr.2011-10-03.log, ldeservice3-stdout.2011-10-03.log, register.cmd, unregister.cmd
>
>
> I've defined attached cmd file on Windows 7 to install a service.
> I try to run the service with "prunsrv //TS/LdeService3" and I get "Commons Daemon Service Runner has stopped working"
> Attaching all details.
> Is there more debug logging I can turn on? The current debug output seems minimal.
> This is probably a configuration user error but I cannot tell due to the lack of logging.
> Thank you.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira