db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Samuel Andrew McIntyre (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-187) Starting derby network server as a service in Win OS
Date Tue, 29 Mar 2005 06:41:18 GMT
     [ http://issues.apache.org/jira/browse/DERBY-187?page=comments#action_61703 ]
Samuel Andrew McIntyre commented on DERBY-187:

Another, probably better solution than my previous suggestion would be one based around the
Jakarta Commons Daemon project, which lives here:



> Starting derby network server as a service in Win OS
> ----------------------------------------------------
>          Key: DERBY-187
>          URL: http://issues.apache.org/jira/browse/DERBY-187
>      Project: Derby
>         Type: New Feature
>   Components: Services
>     Versions:
>  Environment: OS will be only any flavour of Windows.
>     Reporter: Amit Handa
>     Priority: Minor

> The Derby Network Server Database could be started/stopped as a service in Windows OS.
> This may involve updating the win registry. Further work needs to be done to understand
what all will it require to do such a thing.
> I am putting below Andrew McIntyre's comments if they can help in getting a solution
to this problem.
> If you would like to see this functionality added, please add a JIRA entry for it.  The
easiest way to do this would be to provide a registry key file for Derby Network Server and
provide instructions on how to install it as a Windows service using instsrv and srvany. However,
we obviously can't redistribute those two utilities, but it would be nice to provide all the
parts to the solution. So, a little searching turned up this public domain srvany replacement:
> http://iain.cx/src/nssm/
> I haven't tried it, but I suggest trying it out to see how well it works. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
If you want more information on JIRA, or have a bug to report see:

View raw message