RE: I need an advice to make Tomcat a NT service
-Original Message- From: Alexandre Bouchard [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 07, 2001 6:01 PM To: [EMAIL PROTECTED] Subject: Re: I need an advice to make Tomcat a NT service Thx for the warning Randy (about the JDBC-ODBC) I didn't know that JDBC-ODBC was experimental and instable. I already asked to the mailing list which kind of driver (1,2,3 or 4) I should use for my database accessing, and many adviced me not to use JDBC-ODBC. But in my testing environment (tomcat is not yet deployed, i am still testing it on my pc before risking me on the big servers of the company) I tested JDBC-ODBC and it worked fine. I am not sure of the meaning of thread safe. Does that mean that if 2 users try at the same time to send queries then the server will crash? Or that if I log out and let tomcat+IIS run as a service then the server will crash? Or both? Yes 2 users will cause it to crash, one user controlling two threads can cause it to crash (rather unlikely on Tomcat, but more possible with other desktop applications). Running with IIS doesn't help or hurt the situation - there is still one Tomcat process running, and thus one JDBC-ODBC dll instance. thx But the more I use Access DBs, the more I want to get rid of them (I did not chose this weak technology, it's the one i replaced that did) I think I will replace it by SQLServer [ if I'd be alone, the architecture would be BSD-Apache-Tomcat-mySQL, but the office is full of microsoft-certified guys ]. I've got two more questions about that: -is it hard to install (how many hours approx) ? //scuse me if this one is not related to jakarta Installing SQL Server or setting up SQL Server and Tomcat? SQL Server can be installed in about a half an hour, but I would suggest letting one of those Microsoft certifieds install and tune it - they'll probably take two days to do what you could do in an hour. (No, I'm not a big fan of Microsoft certifications). To get Tomcat to work with SQL Server took me about 20 minutes - look at the example your JDBC drivers provide and then change your existing code (it should only be the Class.forName). -is it it easy to communicate from JDBC to SQLServer DBs ? Yes. We use the drivers from inetsoftware.de - they work wonderfully and are fairly cheap. Thx (Again) 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
RE: I need an advice to make Tomcat a NT service
I just spent most of yesterday trying to set Tomcat up as a service that wouldn't die when you log off. The solution I found (with the help of others on the list) was to use JDK1.3.1 but you have to make sure that you read this document: http://java.sun.com/j2se/1.3/relnotes.html There it is stated that: Bug 4323062: Any Windows NT Service embedding Java VM aborts when user logs out This bug has been fixed in J2SDK 1.3.1. ***In order to enable the fix, the -Xrs command-line option must be passed to the JVM. The additional command line argument is necessary because the fix necessarily disables the J2SDK 1.3 shutdown hooks mechanism and forbids the use of the sun.misc.Signal class***. So you do download jdk1.3.1, do exactly what the Tomcat user guide says to do to set up tomcat as an NT service. The only additional thing you need to do is add the option -Xrs to the last line of wrapper.properties (as well as changing the tomcat_home and java_home as you are instructed in the userguide). Tim Hughes Cap Gemini Ernst Young Sandbrugt. 5-7 Postboks 3950, Dreggen 5835 Bergen Norway Tel: +47 55 90 66 24 / +47 48 10 06 38 Email: [EMAIL PROTECTED] Web: http://no.cgey.com -Original Message- From: Alexandre Bouchard [mailto:[EMAIL PROTECTED]] Sent: 7. juni 2001 01:59 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
RE: I need an advice to make Tomcat a NT service
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
Re: I need an advice to make Tomcat a NT service
Thx for the warning Randy (about the JDBC-ODBC) I didn't know that JDBC-ODBC was experimental and instable. I already asked to the mailing list which kind of driver (1,2,3 or 4) I should use for my database accessing, and many adviced me not to use JDBC-ODBC. But in my testing environment (tomcat is not yet deployed, i am still testing it on my pc before risking me on the big servers of the company) I tested JDBC-ODBC and it worked fine. I am not sure of the meaning of thread safe. Does that mean that if 2 users try at the same time to send queries then the server will crash? Or that if I log out and let tomcat+IIS run as a service then the server will crash? Or both? thx But the more I use Access DBs, the more I want to get rid of them (I did not chose this weak technology, it's the one i replaced that did) I think I will replace it by SQLServer [ if I'd be alone, the architecture would be BSD-Apache-Tomcat-mySQL, but the office is full of microsoft-certified guys ]. I've got two more questions about that: -is it hard to install (how many hours approx) ? //scuse me if this one is not related to jakarta -is it it easy to communicate from JDBC to SQLServer DBs ? Thx (Again) 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
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
