Re: URGENT! TomCat won't run my servlets.
Without more information about your setup it's difficult to guess... Could you send any configurations you changed from the defaults? Some wild guesses: - Your HTTPConnectionHandler still uses the default port 8080 instead of 80. From the default server.xml: !-- Normal HTTP -- Connector className="org.apache.tomcat.service.PoolTcpConnector" Parameter name="handler" value="org.apache.tomcat.service.http.HttpConnectionHandler"/ Parameter name="port" value="8080"/ /Connector Change the 8080 to 80 - You changed the port of the Ajp12ConnectionHandler to 80 instead of the HttpConnectionHandler... - On the production server, tomcat does not have the rights to open port 80. On unix the application needs root access to open ports 1024 Luc Vanlerberghe "Cato, Christopher" wrote: Hi all. I'm deploying my applications to the production server. The production server (a DELL system running 2 processors) silently refuses to run my applications. They init okay (can see it in the tomcat log and also in the database log) but they won't run the doGet method for some reason. On the development server, they run just fine. Both systems run RedHat 6.2 and TomCat 3.21. The development server runs TomCat thru Apache and mod_jk, the production server runs TomCat standalone. I found a bug report on redhat.com that stated that in some cases glibc can break java, so I upgraded glibc to the latest version. Still doesn't work. Question is: am I overlooking something simple here? Could it be the difference between running as mod_jk and running standalone? All other files are served as they should through TomCat standalone. So, to reiterate the problem: machine A (development server) - rh 6.2 - tomcat 3.21 - apache 1.3.12 - mod_jk: runs ok machine B (production server) - rh 6.2 - tomcat 3.21 standalone: doesn't run. WHY?? What's the friggin' problem here, I just can't get it! Please help me if you can, deadline is overdrawn and decapitation is moving in rapidly :( regards, christopher cato - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
URGENT! TomCat won't run my servlets.
Hi all. I'm deploying my applications to the production server. The production server (a DELL system running 2 processors) silently refuses to run my applications. They init okay (can see it in the tomcat log and also in the database log) but they won't run the doGet method for some reason. On the development server, they run just fine. Both systems run RedHat 6.2 and TomCat 3.21. The development server runs TomCat thru Apache and mod_jk, the production server runs TomCat standalone. I found a bug report on redhat.com that stated that in some cases glibc can break java, so I upgraded glibc to the latest version. Still doesn't work. Question is: am I overlooking something simple here? Could it be the difference between running as mod_jk and running standalone? All other files are served as they should through TomCat standalone. So, to reiterate the problem: machine A (development server) - rh 6.2 - tomcat 3.21 - apache 1.3.12 - mod_jk: runs ok machine B (production server) - rh 6.2 - tomcat 3.21 standalone: doesn't run. WHY?? What's the friggin' problem here, I just can't get it! Please help me if you can, deadline is overdrawn and decapitation is moving in rapidly :( regards, christopher cato - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
URGENT! TomCat won't run my servlets - part 2
To add to my problem description. I installed Resin 1.2.2 on the same machine, it runs my servlets okay out of the box. So, it must be tomcat. But, what is the problem? *slowly going crazy* -Original Message- From: Cato, Christopher [mailto:[EMAIL PROTECTED]] Sent: den 15 februari 2001 19:07 To: [EMAIL PROTECTED] Subject: URGENT! TomCat won't run my servlets. Hi all. I'm deploying my applications to the production server. The production server (a DELL system running 2 processors) silently refuses to run my applications. They init okay (can see it in the tomcat log and also in the database log) but they won't run the doGet method for some reason. On the development server, they run just fine. Both systems run RedHat 6.2 and TomCat 3.21. The development server runs TomCat thru Apache and mod_jk, the production server runs TomCat standalone. I found a bug report on redhat.com that stated that in some cases glibc can break java, so I upgraded glibc to the latest version. Still doesn't work. Question is: am I overlooking something simple here? Could it be the difference between running as mod_jk and running standalone? All other files are served as they should through TomCat standalone. So, to reiterate the problem: machine A (development server) - rh 6.2 - tomcat 3.21 - apache 1.3.12 - mod_jk: runs ok machine B (production server) - rh 6.2 - tomcat 3.21 standalone: doesn't run. WHY?? What's the friggin' problem here, I just can't get it! Please help me if you can, deadline is overdrawn and decapitation is moving in rapidly :( regards, christopher cato - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: URGENT! TomCat won't run my servlets - part 2
Well, I'll start by covering the obvious basic things first: 1. Are you sure that you are hitting the Tomcat Server (if its not using mod_jk you have to edit the default server.xml file to make Tomcat listen to port 80) 2. Have you moved the web.xml file over (if you are using servlet mappings)? If these aren't the problem, then the question to you is, what is happening? 404 Errors? 500 Errors? Anything in the logs of Tomcat? Is it possible that your servlets are hanging (and thus not giving a response - this would be characterized as a the web browser timing out)? Is Tomcat crashing? Randy -Original Message- From: Cato, Christopher [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 15, 2001 1:25 PM To: '[EMAIL PROTECTED]' Subject: URGENT! TomCat won't run my servlets - part 2 To add to my problem description. I installed Resin 1.2.2 on the same machine, it runs my servlets okay out of the box. So, it must be tomcat. But, what is the problem? *slowly going crazy* -Original Message- From: Cato, Christopher [mailto:[EMAIL PROTECTED]] Sent: den 15 februari 2001 19:07 To: [EMAIL PROTECTED] Subject: URGENT! TomCat won't run my servlets. Hi all. I'm deploying my applications to the production server. The production server (a DELL system running 2 processors) silently refuses to run my applications. They init okay (can see it in the tomcat log and also in the database log) but they won't run the doGet method for some reason. On the development server, they run just fine. Both systems run RedHat 6.2 and TomCat 3.21. The development server runs TomCat thru Apache and mod_jk, the production server runs TomCat standalone. I found a bug report on redhat.com that stated that in some cases glibc can break java, so I upgraded glibc to the latest version. Still doesn't work. Question is: am I overlooking something simple here? Could it be the difference between running as mod_jk and running standalone? All other files are served as they should through TomCat standalone. So, to reiterate the problem: machine A (development server) - rh 6.2 - tomcat 3.21 - apache 1.3.12 - mod_jk: runs ok machine B (production server) - rh 6.2 - tomcat 3.21 standalone: doesn't run. WHY?? What's the friggin' problem here, I just can't get it! Please help me if you can, deadline is overdrawn and decapitation is moving in rapidly :( regards, christopher cato - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: URGENT! TomCat won't run my servlets - part 2
Well, I'll start by covering the obvious basic things first: 1. Are you sure that you are hitting the Tomcat Server (if its not using mod_jk you have to edit the default server.xml file to make Tomcat listen to port 80) It's configured correctly. 2. Have you moved the web.xml file over (if you are using servlet mappings)? Yes. I'm using ANT to manage that, but yes, I've checked that and it's moved over together with the rest of the files. I've got the same file structure on both servers and the files are the same. If these aren't the problem, then the question to you is, what is happening? 404 Errors? 500 Errors? Anything in the logs of Tomcat? Is it possible that your servlets are hanging (and thus not giving a response - this would be characterized as a the web browser timing out)? My servlets are hanging for sure. The web browser times out after a lng time. Is Tomcat crashing? Not as far as I can see - All debug parameters are set to level 9 and also the contexts are debugged. Still, nothing except the usual destroy/init messages in the logs. The database logfile shows that all servlets open their connections okay. /christopher - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: URGENT! TomCat won't run my servlets - part 2
A couple of thoughts: Can you get a Hello World Servlet to run? Is there one common place where your sevlets are hanging (in other words, what do they share in common)? Is is possible that there is some sort of deadlock because of waiting for file locks or sockets that might not have shown up in the other system? (Are you reading to/from sockets or files or serialized/pooled database connections?) Just a few thoughts. If the config is the same its something strange in the sevlets or the underlying system. Randy -Original Message- From: Cato, Christopher [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 15, 2001 1:51 PM To: '[EMAIL PROTECTED]' Subject: RE: URGENT! TomCat won't run my servlets - part 2 Well, I'll start by covering the obvious basic things first: 1. Are you sure that you are hitting the Tomcat Server (if its not using mod_jk you have to edit the default server.xml file to make Tomcat listen to port 80) It's configured correctly. 2. Have you moved the web.xml file over (if you are using servlet mappings)? Yes. I'm using ANT to manage that, but yes, I've checked that and it's moved over together with the rest of the files. I've got the same file structure on both servers and the files are the same. If these aren't the problem, then the question to you is, what is happening? 404 Errors? 500 Errors? Anything in the logs of Tomcat? Is it possible that your servlets are hanging (and thus not giving a response - this would be characterized as a the web browser timing out)? My servlets are hanging for sure. The web browser times out after a lng time. Is Tomcat crashing? Not as far as I can see - All debug parameters are set to level 9 and also the contexts are debugged. Still, nothing except the usual destroy/init messages in the logs. The database logfile shows that all servlets open their connections okay. /christopher - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: URGENT! TomCat won't run my servlets - part 2
A couple of thoughts: Can you get a Hello World Servlet to run? Is there one common place where your sevlets are hanging (in other words, what do they share in common)? The only thing they share is: JDBC - mm.mysql-2.0.2-bin.jar Is is possible that there is some sort of deadlock because of waiting for file locks or sockets that might not have shown up in the other system? (Are you reading to/from sockets or files or serialized/pooled database connections?) neither pooled or serialized db connections, no file reads. when the servlets (or rather their db connection) starts up i can see the query SHOW VARIABLES go through to MySQL. On shutdown of tomcat, JDBC quits the connections. Alas, no errors there. Just a few thoughts. If the config is the same its something strange in the sevlets or the underlying system. It's strange indeed. That the system was flawed was my first guess, but since I've upgraded glibc and the kernel and also reinstalled JDK1.3, I know that part is correct at least. X is also present so that's not the problem either. As I said, I installed Resin 1.2.2 on this server and that runs the servlets okay. Since Resin is using the same underlying system, I don't think the system is the problem. Unless it's a very strange and rare problem like a race condition in JDK1.3 in correlation to the SMP kernel. Cause the SMP kernel (and the extra CPU, duh) is the only real difference between the development server (which works fine) and the production server. I just don't get it. I'll try installing the TomCat 3.3 Milestone 1 and see if that works better for me. It's either that or I'll have to switch to Resin, because my timeframe is shrinking by the minute. thanks for the help anyway /christopher - over and out. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
