Someone has already answered about the service so I will pass over
that issue and warn you of another problem in your architecture.
Sun's JDBC-ODBC bridge is not thread safe. If you attempt two
concurrent connections then you will get a crash (Dr. Watson or GPF
depending on version of Windows). You can read about this in the Bug Parade
(I don't have the number currently). Sun's response is that the JDBC-ODBC
bridge is experimental and should not be used in a production environment.
I would suggest you find other drivers, either ODBC or otherwise for your
application.
Randy
> -----Original Message-----
> From: Alexandre Bouchard [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, June 06, 2001 7:59 PM
> To: [EMAIL PROTECTED]
> Subject: I need an advice to make Tomcat a NT service
>
>
> At business, they were using IIS running on NT4 with ASP as
> the scripting
> language... until I arrived :) With the help of this mailing
> list's archive
> and users, I set up a JDBC-ODBC bridge, and I make IIS give
> Tomcat the JSP
> job (no more ASP ! relief !).
>
> Now, all I have to do is to make Tomcat a NT service so that
> when the server
> administrator logs off, the server will still run. I am using
> java version
> 1.3, and I faced the bug #4323062. I read the information
> available at the
> url:
> http://developer.java.sun.com/developer/bugParade/bugs/4323062.html
> and I saw many solutions proposed. What I need is a
> simple-to-setup, yet
> reliable, solution. Bill Giel's solution seems good for me.
> Should I use it?
> Is it simple enough?
>
> So I need feedbacks from people who installed successfully Tomcat as a
> service that do not die if the user logs off. How did you
> avoided the bug?
> What solution did you used? Was that simple to setup? And how
> reliable is
> your server now?
>
> Thx
>
> Alexandre Bouchard,
> Intranet administrator
> Bell
>
