why does apache procrun fail to start service - hang on waiting for all threads to exit
===

I have a java app that implements the LoaderDeamon which we install and launch with Apache procrun.  Recently when we try to run the service, windows manager claims that it can start the service and that it is running, however, it is not working (no log file, unable to connect to designated socket, etc).  When I run the service from the command line via //TS the console hangs and the service does not start.

The only helpful logging is provided by procrun, below.  It gives a worker thread status of 6, and then hangs on the 'waiting for all threads to exit'.

    [2012-07-24 07:16:13] [debug] ( javajni.c:880 ) DLL search path set to 'C:\PROGRA~2\XPRESS~2\jre\bin'
    [2012-07-24 07:16:13] [debug] ( javajni.c:897 ) Java Worker thread started com/capitaliq/loader/loaderservice/LoaderService:start
    [2012-07-24 07:16:13] [debug] ( javajni.c:914 ) Java Worker thread finished com/capitaliq/loader/loaderservice/LoaderService:start with status=6
    [2012-07-24 07:16:14] [debug] ( prunsrv.c:1148) Java started com/capitaliq/loader/loaderservice/LoaderService
    [2012-07-24 07:16:14] [info]  ( prunsrv.c:1244) Service started in 1160 ms.
    [2012-07-24 07:16:14] [debug] ( prunsrv.c:1496) Waiting for worker to finish...
    [2012-07-24 07:16:14] [debug] ( prunsrv.c:1501) Worker finished.
    [2012-07-24 07:16:14] [debug] ( prunsrv.c:1524) Waiting for all threads to exit

I've been googling this problem for a few days now with no success.  Does anyone happen to know why I would see a hang while waiting for threads to exit?  Or why I am unable to run the service even from the command line?