[ https://issues.apache.org/jira/browse/DAEMON-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Thomas resolved DAEMON-312. -------------------------------- Resolution: Fixed Fix Version/s: 1.1 There were two issues here. Both have been fixed. 1. When using //MS or //MQ the calling process did not exit until after the called process had completed the processing. 2. When using //MQ when an existing process had the configuration dialog showing, the exisiting process did not exit. > prunmgr: //MQ fails to kill multiple instances > ---------------------------------------------- > > Key: DAEMON-312 > URL: https://issues.apache.org/jira/browse/DAEMON-312 > Project: Commons Daemon > Issue Type: Bug > Components: Procrun > Affects Versions: 1.0.9, 1.0.15 > Environment: Windows 7, 64-bit > Reporter: Tim Anderson > Fix For: 1.1 > > > Issuing the following commands starts two instances of prunmgr: > {code} > prunmgr //MS//SomeServiceName > prunmgr //MS//SomeServiceName > {code} > Running: > {code} > prunmgr //MQ//SomeServiceName > {code} > kills the second instance of prunmgr, but fails to kill the first. It does > however remove the icon from the system tray. > This can be reproduced running Tomcat7w.exe from Tomcat 7.0.50 in a command > prompt: > {code} > Tomcat7w.exe //MS//Tomcat7 > Tomcat7w.exe //MS//Tomcat7 > Tomcat7w.exe //MQ//Tomcat7 > {code} > Running: > {code} > Tomcat7w.exe //MS//Tomcat7 > {code} > again, displays an "Application System Error" dialog with the message: > {quote} > "An instance of 'Tomcat7' application is already running. > {quote} > See also DAEMON-187 -- This message was sent by Atlassian JIRA (v6.4.14#64029)