search

rbeckman-nextgen / test-mc4

0 stars 0 forks source link

When starting the Mirth service in windows, the service says started even if Mirth failed to start #996

Closed rbeckman-nextgen closed 4 years ago

rbeckman-nextgen commented 4 years ago

When starting the Mirth service in windows, the service says started even if Mirth failed to start. This happens on port conflicts or any other exception.

Imported Issue. Original Details: Jira Issue Key: MIRTH-1016 Reporter: jacobb Created: 2009-01-08T13:13:05.000-0800

rbeckman-nextgen commented 4 years ago

install4j 5 which is to be released in about 3 weeks will display the service as stopped immediately when this happens. For install4j 4 there is unfortunately no workaround.

Imported Comment. Original Details: Author: geraldb Created: 2010-06-04T15:43:15.000-0700

rbeckman-nextgen commented 4 years ago

Tested with install4j 5.0 and the issue still exists. We have contacted the support for a resolution.

Imported Comment. Original Details: Author: geraldb Created: 2010-06-23T16:02:17.000-0700

rbeckman-nextgen commented 4 years ago

From the install4j developers:

"We currently don't display an error message if the VM is stopped. That does not fit very well in our model. The status should be updated correctly nevertheless. The service control manager doesn't update its state automatically that might be the problem. You would have to hit F5 (and there is a bug when the service in question is selected so you might have to select a different one)."

In the server manager this is addressed by pinging the ports once the service has started.

Imported Comment. Original Details: Author: geraldb Created: 2010-07-09T15:29:18.000-0700