You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by "Adam C. Ehlis" <ad...@ehlis.com> on 2000/04/25 03:20:52 UTC

Tomcat & Apache Missing Session Information

Hello Everyone,
 My name is Adam Ehlis and I am somewhat new to Tomcat.  The project
I'm currently working on used Java Server Pages and it had been decided
to use Tomcat for the JSPs and Apache for SSL before I got onto the
project.  I've currently got Apache 1.3.11, JServ 1.1, and Tomcat 3.0
talking to each other and Apache is doing the JSPs okay except that the
session information being lost between the Tomcat/Apache session
somewhere.  I noticed a lot of email generated on this subject but
couldn't
find any answers if anyone has overcome this problem or not.  Can anyone

out there help me figure out what's going on between Apache & Tomcat
or if there are any other ways of getting my Java Server Pages working
some other way.  I've currently got our developers using just Tomcat
until
I can come up with a solution to get SSL enabled on the site, okay for
now
but three months from now it will be a problem.  Thanks in advance.

Adam


Re: Tomcat & Apache Missing Session Information

Posted by Jun Inamori <j-...@osa.att.ne.jp>.
Hi Adam,

> I've currently got Apache 1.3.11, JServ 1.1, and Tomcat 3.0
> talking to each other and Apache is doing the JSPs okay except that the
> session information being lost between the Tomcat/Apache session
> somewhere.
In my case, JSP is handled by Tomcat though JServ module, even in case
that the request to Apache is SSL based. My configuration is:
1. Apache
	Apache 		Version1.3.12(DSO enabled)
	mod_ssl 	Version2.6.2
	OpenSSL 	Version0.9.5
	mod_jserv	compiled from source supplied with Tomcat3.1

2. mod_jserv
Compiled form the source which is supplied with Tomcat3.1, by APXS of
Apache.
This version of JServ module works well with Tomcat3.1, so I start
Tomcat from JServ module when Apache boots up. (In jserv.conf or
tomcat.conf, 'ApJServManual' directive is set to 'off'.) The protocol
between mod_jserv and Tomcat is 'ajpv12'.

3. Browser
Configured to accept cookies.

I can't guess what's wrong with your Apache, but comparing your
configuration to above one will help you.

Happy Java programming!

Jun Inamori
E-mail: j-office@osa.att.ne.jp
URL:    http://www.oop-reserch.com

Re: JAXP Question and Ant suggestion

Posted by "Craig R. McClanahan" <Cr...@eng.sun.com>.
External Lists wrote:

> Question about JAXP:
> Where can I learn more about JAXP and how it will be used in Jakarta
> projects?  The only ugly I have right now with the 3.1 release of Tomcat is
> the clash between xml.jar and xerces.jar, and I'd like everything to use
> Xerces, if possible.  I had even changed XmlMapper.java last week, but then
> aborted because the scope of com.sun.xml was much broader in the code.
>

Info about JAXP, as well as the reference implementation, is at
<http://java.sun.com/xml>.

For Tomcat, Ant has already been modified to be JAXP-compatible.  The same
change will be needed for Tomcat as well, making it possible to substitute your
own favoriate JAXP-compatible parser at runtime.

At the moment, Tomcat's code still works with the JAXP reference implementation
because the parser classname is the same.


> Suggestion for Ant:
> There is an unintended difference on Windows in the <exec> task when a
> directory *is* vs. *is not* specified and different from ".".  In one case,
> the command goes through "cmd.exe /c" vs. being run directly.  This can
> change what command syntax is legal, such as slashes, multiple commands,
> setting env. vars, etc.).  In any case, the process's working directory is
> not changed when the specified dir when Ant recurses into a new base
> directory using the <ant> built-in task, so a recursive build will fail.  My
> proposed change is to simply always change directories before running the
> command:
>
> <             if (!dir.equals(project.resolveFile(".")))
> <                 command = "cmd /c cd " + dir + " && " + command;
> ---
> >              command = "cmd /c cd " + dir + " && " + command;
>
> Thanks for your help and consideration.
>

You might want to join the ANT-DEV mailing list and point this issue out.

>
> John W. Cocula

Craig McClanahan



JAXP Question and Ant suggestion

Posted by External Lists <ex...@ManagedObjects.com>.
Question about JAXP:
Where can I learn more about JAXP and how it will be used in Jakarta
projects?  The only ugly I have right now with the 3.1 release of Tomcat is
the clash between xml.jar and xerces.jar, and I'd like everything to use
Xerces, if possible.  I had even changed XmlMapper.java last week, but then
aborted because the scope of com.sun.xml was much broader in the code.

Suggestion for Ant:
There is an unintended difference on Windows in the <exec> task when a
directory *is* vs. *is not* specified and different from ".".  In one case,
the command goes through "cmd.exe /c" vs. being run directly.  This can
change what command syntax is legal, such as slashes, multiple commands,
setting env. vars, etc.).  In any case, the process's working directory is
not changed when the specified dir when Ant recurses into a new base
directory using the <ant> built-in task, so a recursive build will fail.  My
proposed change is to simply always change directories before running the
command:

<             if (!dir.equals(project.resolveFile(".")))
<                 command = "cmd /c cd " + dir + " && " + command;
---
>              command = "cmd /c cd " + dir + " && " + command;

Thanks for your help and consideration.

John W. Cocula
Managed Objects
john@ManagedObjects.com