|
From: Leif M. <le...@ta...> - 2003-10-11 17:11:28
|
Sona,
Unfortunately, you have encountered what appears to be a bug of some
kind.
Another user has also run into this and has opened the following bug:
http://sourceforge.net/tracker/index.php?func=detail&aid=812467&group_id=39428&atid=425187
I have been trying to track down the cause but unfortunately I have
also been
unable to reproduce this so far on any of my machines.
What version of Windows are you running? The other user is running
under
Windows 2000. If you could read over that bug and see if you may have any
new information I would appreciate it.
The information about switching to the "Administrator" is useful.
I'll see if the
other user is seeing the same thing.
The other user has also found that if you start your other
application before
starting the app running under the Wrapper then everything works fine. From
that point on, you can restart your app as many times as you like.
Could you monitor that bug and post any new information that you find?
I'll keep looking into this and hopefully figure out a way to reproduce it.
Good to know that there is a workaround with the user. That may also be
a big clue toward finding a solution.
Cheers,
Leif
sna...@gm... wrote:
>I am experiencing a weird problem using Wrapper service to install a Java app as System service. I installed the sample service application provided in the binary distribution. Restart the system, the service starts. Now if I try to start a different JAVA GUI (Swing) program, the program holds up at startup and never comes up. I appears to have never entered the program that I am trying to run, it looks like to be struck in java.exe somewhere in initialization. Has anyone seem this?
>Now if I were to stop the "test ..." service and run the swing program, it works fine. After that start the service everything works fine. It appears to be related to starting the Java service for the first time after a system boot.
>Not all machines have this problem.
>Another interesting thing is, if one goes to the Services control panel, double click on the installed test service and in the "log on" tab force the service to be run as "Administrator" everything works fine.
>I am totally clueless as to where the problem is. Any help in this regard is appreciated
>thanks
>sona
>
>
|