DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=34851>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=34851 Summary: [commons-daemon]: jsvc should instantiate server only once Product: Commons Version: 1.0 Final Platform: Other OS/Version: Linux Status: NEW Severity: major Priority: P2 Component: Daemon AssignedTo: commons-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] Configuration: Red Hat Linux 9 j2sdk-1_4_2_07 jsvc 1.0 Expected behavior: jsvc should call the constructor of the java class implementing the Daemon interface only once. Actual behavior: jsvc calls the constructor 2 times. Notes: It may well be justifiable to instantiate the class more than once from the jsvc programmer's point of view. However this is in conflict with the requirements of a Java demon/service. The double successive instantiation of the same Java server can create severe resource problems. There is no guarantee that these problems are not created because there is no convention that documents this double instantiation. Apart from possible resource contention issues, there is a more undisputable obvious problem: Performance. The instantiation of a server is typically a time consuming process. The server startup time has to be kept at a minimum to minimise service disruptions due to re-starts. In this context it is extremely hard to accept if not unaceptable that this task is performed more than once. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]