Whilst trying to use procrun to launch a 3rd party java application that made use of RMI within Windows I ran into a few issues with the current release (actually tested against the latest code from SVN). They can be summarised as follows:
1) Lack of support for wildcards in classpaths as per Java 1.6 launcher (this caused the initial problem in that it wasn’t finding all classes it required to even begin starting up). Created as an improvement in DAEMON-166 2) No thread context classloader set for the thread executing the main method (this cause the RMI code to fail with "class not found" exceptions. Update an existing issue DAEMON-100 with note and a code sample 3) Hiding of uncaught exceptions thrown as a result of executing the main method (this obscured the exceptions being thrown from issues 1 and 2 which made the initial diagnosis a problem).. Created a new issue DAEMON-165 with a simple one line removal I have been able to fix all these by minimaly modifying the current code base. However I havent had time to verify whether it has broken anything else, theorecticaly it shouldn’t have done. I have logged more specifics in the issues tracker entries mentioned above,. I hope these can be introduced as a matter of course as I believe they should be generic enough to benefit other people wishing to use procrun in this manner. Tony
