theprofessorx
Programmer
hello Tomcat peoples.
I'm running Tomcat as a servlet container connected to Apache HTTP Server through the WarpConnector on NT. I've configured a DataSource using Tomcat. I have servlets that use the DataSource deployed in a web application.
Now when I run the servlets directly through Tomcat (ie port 8080), they connect to the DataSource fine. However, when I go through Apache via WarpConnector, a NullPointerException error is thrown.
I've been conversing with a knoweledgeable Tomcat fella on this, and from what I understand, the context for the web application is not resolved when it passes through the WarpConnector, resulting in a newly created context which defaults to null. This fella seemed to have fixed the problem on Linux by removing the "/" from the WebAppDeploy path in httpd.conf and the Context path tag in server.xml.
This doesn't work for Windows. NullPointerException is still thrown. Has anybody encountered this problem and successfully fixed it? Thanks for any input.
I'm running Tomcat as a servlet container connected to Apache HTTP Server through the WarpConnector on NT. I've configured a DataSource using Tomcat. I have servlets that use the DataSource deployed in a web application.
Now when I run the servlets directly through Tomcat (ie port 8080), they connect to the DataSource fine. However, when I go through Apache via WarpConnector, a NullPointerException error is thrown.
I've been conversing with a knoweledgeable Tomcat fella on this, and from what I understand, the context for the web application is not resolved when it passes through the WarpConnector, resulting in a newly created context which defaults to null. This fella seemed to have fixed the problem on Linux by removing the "/" from the WebAppDeploy path in httpd.conf and the Context path tag in server.xml.
This doesn't work for Windows. NullPointerException is still thrown. Has anybody encountered this problem and successfully fixed it? Thanks for any input.
