unnivm / jwebsocket

Automatically exported from code.google.com/p/jwebsocket
1 stars 0 forks source link

Service can not be launched without reboot in WinXP SP3 #116

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
There is a problem with service in WinXP SP3.
Due to [url]http://support.microsoft.com/kb/821761[/url] after you
1. Create JWEBSOCKET_HOME env. var.
2. Install service jWebSocketInstallService32.bat
3. Launch service NET START "jWebSocket Service"
service is launched successfully but does not respond and does not write to log 
file. You need to reboot to get it working properly.

Why can't be used something like that
return new 
File(MyClass.class.getProtectionDomain().getCodeSource().getLocation().getPath()
);
to get current directory if JWEBSOCKET_HOME is absent or not visible to program?

Known workaround: you can set another account from LocalSystem to be used for 
launching service. In that case JWEBSOCKET_HOME is visible

Original issue reported on code.google.com by boq...@gmail.com on 24 Dec 2010 at 6:07

GoogleCodeExporter commented 9 years ago
Also: JWEBSOCKET_HOME env. variable is not very convenient if you want to have 
several installations of jWebSocket on a Windows machine.
I think its better to get rid of JWEBSOCKET_HOME or at least make it optional

Original comment by boq...@gmail.com on 24 Dec 2010 at 10:38

GoogleCodeExporter commented 9 years ago
We started to work on this, the environment variable is not required anymore 
and we can start the service with command line arguments to specify the home 
folder to support multiple instances.

Original comment by fivefeetfurther@gmail.com on 14 Apr 2012 at 11:01