Winsw == Windows Service Wrapper == a Kenai project. It is a .NET C# project that is located here:
http://projectkenai.com/projects/winsw
=====================================
"Allow service to interact with Desktop" is almost always a bad idea. We don't need or want it in V3. It is **not** used in V2 either.
=====================================
The V3 service is using this:
asadmin start-domain --verbose
V2 service uses this:
asadmin start-domain
There is a huge difference. When verbose is on, the asadmin JVM starts the server JVM. The asadmin JVM hangs around like a watchdog and also echoes server log messages. When the asadmin JVM is killed the Server dies. If the server is killed, the asadmin JVM is killed. They live together. They die together. They are like the two musketeers.
Try it in a console window -- start the domain with verbose. Kill the server from a different window. Watch what happens. Try running "asadmin restart-domain" from another windows and see even more amazing results!
In V2 the asadmin JVM fires off the server and promptly dies.
As a result in V2 -- Windows Services has no clue if the server dies.
In V3 Windows Services detects it immediately. Try it. Start V3 as a Service. Then kill the server from a command prompt (asadmin stop-domain) -- note that Windows detected it.
==================
-Xrs ought to work. This is a JVM & System level setting. I'll try to free up some time next week to experiment with it. You may want to try setting the logon to YOU rather than "Local System"..
[Message sent by forum member 'bnevins' (byron.nevins_at_sun.com)]
http://forums.java.net/jive/thread.jspa?messageID=386511