Re: JSF errors when upgrading Tomcat and Eclipse: com.sun.faces.config.JavaClassScanningAnnotationScanner$ConstantPoolInfo.containsAnnotation Unknow type constant pool XX at position XX

[Brian Braun]

Hi,

I replaced JSF 2.2.1 with 2.2.20 and the problem is gone! It seems that the
old  2.2.1 JAR had some kind of old format that crushed with the way the
latest Eclipse works. And since 2.2.1 to 2.2.20 is not a huge upgrade, my
old JSF pages still work. Nice!
Thanks!

On Thu, Oct 12, 2023 at 4:35 PM Christopher Schultz <
ch...@christopherschultz.net> wrote:

> Brian,
>
> On 10/12/23 16:55, Brian Braun wrote:
> > Hello,
> >
> > First of all, I apologize if maybe my issue is not exclusively related to
> > Tomcat, but I think it is.
> >
> > I started my website many years ago, using Struts 1.2.4 and since then I
> > have been using it. Some years after that I had the intention to migrate
> to
> > JSF (version 2.2.X) and combine both frameworks for a while until I
> > migrated everything to JSF and Struts was gone. I started learning it,
> > created a few pages on my site but then I realized that it was not the
> > ideal framework for me, so I stopped creating more pages with JSF and
> > continued developing my site with Struts, letting those few JSF pages
> that
> > work coexist with the rest of the site running using Struts. Since then,
> I
> > haven't touched JSF. I haven't created even one page with it, never
> > upgraded its version but the JSF JAR and pages are still there. Years
> > passed and nothing made me think about JSF.
> >
> > Now I'm using:
> > - Mac with the M2 chip
> > - Eclipse (ARM version)
> > - Tomcat, when developing with Eclipse
> > - Tomcat 9.0.58 at my production server (which runs Ubuntu 22.04, x86/64)
> > - Azul's Java 11.0.19+7-LTS aarch64, when developing with Eclipse
> > - Java 11.0.20.1+1-post-Ubuntu-0ubuntu122.04, at the production server
> >
> > Well, a few days ago I upgraded Eclipse to Version: 2023-09 (4.29.0) and
> at
> > the same time upgraded to Azul's Java 11.0.19+7-LTS aarch64 and to Tomcat
> > 9.0.71 when developing. And since then, I get these "SEVERE" JSF error
> > messages (many of them) when I start Tomcat:
> >
> > SEVERE [main]
> >
> com.sun.faces.config.JavaClassScanningAnnotationScanner$ConstantPoolInfo.containsAnnotation
> > Unknow type constant pool NN at position XX
> >
> > Why is that? Could someone please give me a clue? I just upgraded Eclipse
> > and Tomcat, didn't do anything else relevant and now I get these
> messages.
> > And when I create the WAR file and deploy it on my production server, I
> get
> > the same error messages as well over there. It seems like the class files
> > that gets generated are now different, since I didn't upgrade anything on
> > my production server, so it is the WAR file that gets generated with
> > something problematic now.
> >
> > Thanks in advance!
> >
> > Here is the complete stuff that Tomcat shows, as a reference:
> >
> > 12-Oct-2023 14:47:18.676 INFO [main]
> > org.apache.catalina.startup.VersionLoggerListener.log Server version
> name:
> > Apache Tomcat/9.0.71
> > 12-Oct-2023 14:47:18.678 INFO [main]
> > org.apache.catalina.startup.VersionLoggerListener.log Server built: Jan 9
> > 2023 22:33:01 UTC
> > 12-Oct-2023 14:47:18.678 INFO [main]
> > org.apache.catalina.startup.VersionLoggerListener.log Server version
> > number: 9.0.71.0
> > 12-Oct-2023 14:47:18.678 INFO [main]
> > org.apache.catalina.startup.VersionLoggerListener.log OS Name: Mac OS X
> > 12-Oct-2023 14:47:18.678 INFO [main]
> > org.apache.catalina.startup.VersionLoggerListener.log OS Version: 14.0
> > 12-Oct-2023 14:47:18.678 INFO [main]
> > org.apache.catalina.startup.VersionLoggerListener.log Architecture:
> aarch64
> > 12-Oct-2023 14:47:18.678 INFO [main]
> > org.apache.catalina.startup.VersionLoggerListener.log Java Home:
> > /Library/Java/JavaVirtualMachines/zulu-11.jdk/Contents/Home
> > 12-Oct-2023 14:47:18.678 INFO [main]
> > org.apache.catalina.startup.VersionLoggerListener.log JVM Version:
> > 11.0.19+7-LTS
> > 12-Oct-2023 14:47:18.678 INFO [main]
> > org.apache.catalina.startup.VersionLoggerListener.log JVM Vendor: Azul
> > Systems, Inc.
> > 12-Oct-2023 14:47:18.678 INFO [main]
> > org.apache.catalina.startup.VersionLoggerListener.log CATALINA_BASE:
> > /Users/brianbraun/BB/ACME/Programacion-Mac-Silicon/EclipseTomcat9.0.71
> > 12-Oct-2023 14:47:18.678 INFO [main]
> > org.apache.catalina.startup.VersionLoggerListener.log CATALINA_HOME:
> > /Users/brianbraun/BB/ACME/Programacion-Mac-Silicon/EclipseTomcat9.0.71
> > 12-Oct-2023 14:47:18.719 INFO [main]
> > org.apache.catalina.startup.VersionLoggerListener.log Command line
&

Re: JSF errors when upgrading Tomcat and Eclipse: com.sun.faces.config.JavaClassScanningAnnotationScanner$ConstantPoolInfo.containsAnnotation Unknow type constant pool XX at position XX

[Brian Braun]

Hi Chris,

Its JSF version 2.2.1
What is a bytecode scanner? I will google that, I don't have any idea.
And why did I start getting this problem a few days ago? The only thing
that changed is Eclipse (I upgraded it to the latest) and the Tomcat that
Eclipse uses to run the website everytime I run it when I'm developing.

I could upgrade JSF to some other version, but would that solve the issue?
I don't know. And what if the few pages that I created using JSF will not
work anymore because of the upgrade? I really totally forgot about how to
use JSF, so I would not like having to learn it again now just because of
this obstacle!

Who is doing the class scanning? Is it JSF? Is it Tomcat? I have no clue
right now. The interesting thing is that in my production server i didn't
change anything in the software stack, but the WAR that now arrives there
causes this problems. It is like if Eclipse is creating a new type of
class/JAR files with some new characteristic, in my opinion.

Thanks for your help!!!


On Thu, Oct 12, 2023 at 4:35 PM Christopher Schultz <
ch...@christopherschultz.net> wrote:

> Brian,
>
> On 10/12/23 16:55, Brian Braun wrote:
> > Hello,
> >
> > First of all, I apologize if maybe my issue is not exclusively related to
> > Tomcat, but I think it is.
> >
> > I started my website many years ago, using Struts 1.2.4 and since then I
> > have been using it. Some years after that I had the intention to migrate
> to
> > JSF (version 2.2.X) and combine both frameworks for a while until I
> > migrated everything to JSF and Struts was gone. I started learning it,
> > created a few pages on my site but then I realized that it was not the
> > ideal framework for me, so I stopped creating more pages with JSF and
> > continued developing my site with Struts, letting those few JSF pages
> that
> > work coexist with the rest of the site running using Struts. Since then,
> I
> > haven't touched JSF. I haven't created even one page with it, never
> > upgraded its version but the JSF JAR and pages are still there. Years
> > passed and nothing made me think about JSF.
> >
> > Now I'm using:
> > - Mac with the M2 chip
> > - Eclipse (ARM version)
> > - Tomcat, when developing with Eclipse
> > - Tomcat 9.0.58 at my production server (which runs Ubuntu 22.04, x86/64)
> > - Azul's Java 11.0.19+7-LTS aarch64, when developing with Eclipse
> > - Java 11.0.20.1+1-post-Ubuntu-0ubuntu122.04, at the production server
> >
> > Well, a few days ago I upgraded Eclipse to Version: 2023-09 (4.29.0) and
> at
> > the same time upgraded to Azul's Java 11.0.19+7-LTS aarch64 and to Tomcat
> > 9.0.71 when developing. And since then, I get these "SEVERE" JSF error
> > messages (many of them) when I start Tomcat:
> >
> > SEVERE [main]
> >
> com.sun.faces.config.JavaClassScanningAnnotationScanner$ConstantPoolInfo.containsAnnotation
> > Unknow type constant pool NN at position XX
> >
> > Why is that? Could someone please give me a clue? I just upgraded Eclipse
> > and Tomcat, didn't do anything else relevant and now I get these
> messages.
> > And when I create the WAR file and deploy it on my production server, I
> get
> > the same error messages as well over there. It seems like the class files
> > that gets generated are now different, since I didn't upgrade anything on
> > my production server, so it is the WAR file that gets generated with
> > something problematic now.
> >
> > Thanks in advance!
> >
> > Here is the complete stuff that Tomcat shows, as a reference:
> >
> > 12-Oct-2023 14:47:18.676 INFO [main]
> > org.apache.catalina.startup.VersionLoggerListener.log Server version
> name:
> > Apache Tomcat/9.0.71
> > 12-Oct-2023 14:47:18.678 INFO [main]
> > org.apache.catalina.startup.VersionLoggerListener.log Server built: Jan 9
> > 2023 22:33:01 UTC
> > 12-Oct-2023 14:47:18.678 INFO [main]
> > org.apache.catalina.startup.VersionLoggerListener.log Server version
> > number: 9.0.71.0
> > 12-Oct-2023 14:47:18.678 INFO [main]
> > org.apache.catalina.startup.VersionLoggerListener.log OS Name: Mac OS X
> > 12-Oct-2023 14:47:18.678 INFO [main]
> > org.apache.catalina.startup.VersionLoggerListener.log OS Version: 14.0
> > 12-Oct-2023 14:47:18.678 INFO [main]
> > org.apache.catalina.startup.VersionLoggerListener.log Architecture:
> aarch64
> > 12-Oct-2023 14:47:18.678 INFO [main]
> > org.apache.catalina.startup.VersionLoggerListener.log Java Home:
> > /Library/Java/JavaVirtualMachines/zulu-11.jdk/Contents/Home
> > 12-Oct-2023 14:47:18.678 INFO [main]
> >

Re: JSF errors when upgrading Tomcat and Eclipse: com.sun.faces.config.JavaClassScanningAnnotationScanner$ConstantPoolInfo.containsAnnotation Unknow type constant pool XX at position XX

[Christopher Schultz]

Brian,

On 10/12/23 16:55, Brian Braun wrote:

Hello,

First of all, I apologize if maybe my issue is not exclusively related to
Tomcat, but I think it is.

I started my website many years ago, using Struts 1.2.4 and since then I
have been using it. Some years after that I had the intention to migrate to
JSF (version 2.2.X) and combine both frameworks for a while until I
migrated everything to JSF and Struts was gone. I started learning it,
created a few pages on my site but then I realized that it was not the
ideal framework for me, so I stopped creating more pages with JSF and
continued developing my site with Struts, letting those few JSF pages that
work coexist with the rest of the site running using Struts. Since then, I
haven't touched JSF. I haven't created even one page with it, never
upgraded its version but the JSF JAR and pages are still there. Years
passed and nothing made me think about JSF.

Now I'm using:
- Mac with the M2 chip
- Eclipse (ARM version)
- Tomcat, when developing with Eclipse
- Tomcat 9.0.58 at my production server (which runs Ubuntu 22.04, x86/64)
- Azul's Java 11.0.19+7-LTS aarch64, when developing with Eclipse
- Java 11.0.20.1+1-post-Ubuntu-0ubuntu122.04, at the production server

Well, a few days ago I upgraded Eclipse to Version: 2023-09 (4.29.0) and at
the same time upgraded to Azul's Java 11.0.19+7-LTS aarch64 and to Tomcat
9.0.71 when developing. And since then, I get these "SEVERE" JSF error
messages (many of them) when I start Tomcat:

SEVERE [main]
com.sun.faces.config.JavaClassScanningAnnotationScanner$ConstantPoolInfo.containsAnnotation
Unknow type constant pool NN at position XX

Why is that? Could someone please give me a clue? I just upgraded Eclipse
and Tomcat, didn't do anything else relevant and now I get these messages.
And when I create the WAR file and deploy it on my production server, I get
the same error messages as well over there. It seems like the class files
that gets generated are now different, since I didn't upgrade anything on
my production server, so it is the WAR file that gets generated with
something problematic now.

Thanks in advance!

Here is the complete stuff that Tomcat shows, as a reference:

12-Oct-2023 14:47:18.676 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Server version name:
Apache Tomcat/9.0.71
12-Oct-2023 14:47:18.678 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Server built: Jan 9
2023 22:33:01 UTC
12-Oct-2023 14:47:18.678 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Server version
number: 9.0.71.0
12-Oct-2023 14:47:18.678 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log OS Name: Mac OS X
12-Oct-2023 14:47:18.678 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log OS Version: 14.0
12-Oct-2023 14:47:18.678 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Architecture: aarch64
12-Oct-2023 14:47:18.678 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Java Home:
/Library/Java/JavaVirtualMachines/zulu-11.jdk/Contents/Home
12-Oct-2023 14:47:18.678 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log JVM Version:
11.0.19+7-LTS
12-Oct-2023 14:47:18.678 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log JVM Vendor: Azul
Systems, Inc.
12-Oct-2023 14:47:18.678 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log CATALINA_BASE:
/Users/brianbraun/BB/ACME/Programacion-Mac-Silicon/EclipseTomcat9.0.71
12-Oct-2023 14:47:18.678 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log CATALINA_HOME:
/Users/brianbraun/BB/ACME/Programacion-Mac-Silicon/EclipseTomcat9.0.71
12-Oct-2023 14:47:18.719 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Command line
argument:
-Dcatalina.base=/Users/brianbraun/BB/ACME/Programacion-Mac-Silicon/EclipseTomcat9.0.71
12-Oct-2023 14:47:18.719 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Command line
argument:
-Dcatalina.home=/Users/brianbraun/BB/ACME/Programacion-Mac-Silicon/EclipseTomcat9.0.71
12-Oct-2023 14:47:18.719 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Command line
argument:
-Dwtp.deploy=/Users/brianbraun/BB/ACME/Programacion-Mac-Silicon/EclipseTomcat9.0.71/webapps
12-Oct-2023 14:47:18.719 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Command line
argument:
-Djava.util.logging.config.file=/Users/brianbraun/BB/ACME/Programacion-Mac-Silicon/EclipseTomcat9.0.71/conf/logging.properties
12-Oct-2023 14:47:18.720 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Command line
argument: -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
12-Oct-2023 14:47:18.720 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Command line
argument: --add-opens=java.base/java.lang=ALL-UNNAMED
12-Oct-2023 14:47:18.720 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Command line
argument: --add-opens

JSF errors when upgrading Tomcat and Eclipse: com.sun.faces.config.JavaClassScanningAnnotationScanner$ConstantPoolInfo.containsAnnotation Unknow type constant pool XX at position XX

[Brian Braun]

Hello,

First of all, I apologize if maybe my issue is not exclusively related to
Tomcat, but I think it is.

I started my website many years ago, using Struts 1.2.4 and since then I
have been using it. Some years after that I had the intention to migrate to
JSF (version 2.2.X) and combine both frameworks for a while until I
migrated everything to JSF and Struts was gone. I started learning it,
created a few pages on my site but then I realized that it was not the
ideal framework for me, so I stopped creating more pages with JSF and
continued developing my site with Struts, letting those few JSF pages that
work coexist with the rest of the site running using Struts. Since then, I
haven't touched JSF. I haven't created even one page with it, never
upgraded its version but the JSF JAR and pages are still there. Years
passed and nothing made me think about JSF.

Now I'm using:
- Mac with the M2 chip
- Eclipse (ARM version)
- Tomcat, when developing with Eclipse
- Tomcat 9.0.58 at my production server (which runs Ubuntu 22.04, x86/64)
- Azul's Java 11.0.19+7-LTS aarch64, when developing with Eclipse
- Java 11.0.20.1+1-post-Ubuntu-0ubuntu122.04, at the production server

Well, a few days ago I upgraded Eclipse to Version: 2023-09 (4.29.0) and at
the same time upgraded to Azul's Java 11.0.19+7-LTS aarch64 and to Tomcat
9.0.71 when developing. And since then, I get these "SEVERE" JSF error
messages (many of them) when I start Tomcat:

SEVERE [main]
com.sun.faces.config.JavaClassScanningAnnotationScanner$ConstantPoolInfo.containsAnnotation
Unknow type constant pool NN at position XX

Why is that? Could someone please give me a clue? I just upgraded Eclipse
and Tomcat, didn't do anything else relevant and now I get these messages.
And when I create the WAR file and deploy it on my production server, I get
the same error messages as well over there. It seems like the class files
that gets generated are now different, since I didn't upgrade anything on
my production server, so it is the WAR file that gets generated with
something problematic now.

Thanks in advance!

Here is the complete stuff that Tomcat shows, as a reference:

12-Oct-2023 14:47:18.676 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Server version name:
Apache Tomcat/9.0.71
12-Oct-2023 14:47:18.678 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Server built: Jan 9
2023 22:33:01 UTC
12-Oct-2023 14:47:18.678 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Server version
number: 9.0.71.0
12-Oct-2023 14:47:18.678 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log OS Name: Mac OS X
12-Oct-2023 14:47:18.678 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log OS Version: 14.0
12-Oct-2023 14:47:18.678 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Architecture: aarch64
12-Oct-2023 14:47:18.678 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Java Home:
/Library/Java/JavaVirtualMachines/zulu-11.jdk/Contents/Home
12-Oct-2023 14:47:18.678 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log JVM Version:
11.0.19+7-LTS
12-Oct-2023 14:47:18.678 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log JVM Vendor: Azul
Systems, Inc.
12-Oct-2023 14:47:18.678 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log CATALINA_BASE:
/Users/brianbraun/BB/ACME/Programacion-Mac-Silicon/EclipseTomcat9.0.71
12-Oct-2023 14:47:18.678 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log CATALINA_HOME:
/Users/brianbraun/BB/ACME/Programacion-Mac-Silicon/EclipseTomcat9.0.71
12-Oct-2023 14:47:18.719 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Command line
argument:
-Dcatalina.base=/Users/brianbraun/BB/ACME/Programacion-Mac-Silicon/EclipseTomcat9.0.71
12-Oct-2023 14:47:18.719 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Command line
argument:
-Dcatalina.home=/Users/brianbraun/BB/ACME/Programacion-Mac-Silicon/EclipseTomcat9.0.71
12-Oct-2023 14:47:18.719 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Command line
argument:
-Dwtp.deploy=/Users/brianbraun/BB/ACME/Programacion-Mac-Silicon/EclipseTomcat9.0.71/webapps
12-Oct-2023 14:47:18.719 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Command line
argument:
-Djava.util.logging.config.file=/Users/brianbraun/BB/ACME/Programacion-Mac-Silicon/EclipseTomcat9.0.71/conf/logging.properties
12-Oct-2023 14:47:18.720 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Command line
argument: -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
12-Oct-2023 14:47:18.720 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Command line
argument: --add-opens=java.base/java.lang=ALL-UNNAMED
12-Oct-2023 14:47:18.720 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Command line
argument: --add-opens=java.base/java.io=ALL-UNNAMED
12-Oct-2023 14

Re: Tomcat 8.5.xx EOL

[Mark Thomas]

On 13/11/2019 15:05, RICT (Ricco Truelsen) wrote:
> Hi
> 
> Any official EOL on Tomcat 8.5.x yet?
> I can find official info on the Tomcat 8.0.x EOL, but not on the Tomcat 8.5.x?

No.

https://markmail.org/message/6wycxatwzwycmf43

Mark

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Tomcat 8.5.xx EOL

[RICT (Ricco Truelsen)]

Hi

Any official EOL on Tomcat 8.5.x yet?
I can find official info on the Tomcat 8.0.x EOL, but not on the Tomcat 8.5.x?

Best regards,
Ricco

Re: Tomcat 7.0.xx under Java 7?

[Mark Thomas]

On 08/02/17 00:57, James H. H. Lampert wrote:

Ladies and Gentlemen of the Tomcat List:

To date, the overwhelming bulk of our own Tomcat experience has been
under Java 6 JVMs. And we have a customer who will likely be losing that
JVM soon.

Are there any "gotchas" running 7.0.47 or later under Java 7?


No specific issues I am aware of.

General things to look out for:

- GC settings 'optimized' for an older JVM that don't make sense for the 
newer JVM. Best to remove them all and start from a clean slate.


- Web applications including libraries that are now part of the newer 
JVM and causing conflicts.


Mark


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Tomcat 7.0.xx under Java 7?

[James H. H. Lampert]

Ladies and Gentlemen of the Tomcat List:

To date, the overwhelming bulk of our own Tomcat experience has been 
under Java 6 JVMs. And we have a customer who will likely be losing that 
JVM soon.


Are there any "gotchas" running 7.0.47 or later under Java 7?

--
James H. H. Lampert
Touchtone Corporation

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Tomcat 5.0.xx migration

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Uzair,

On 2/9/16 1:11 PM, uzair rashid wrote:
> Most of our business is running Tomcat 7.x.xx or later. But, we
> have a business function of ours that is using Tomcat 5.0.xx.
> Unfortunately, this is causing a lot of issues in terms of
> vulnerability remediation.

You should definitely upgrade anything running Tomcat 5.x to something
later. If possible, Tomcat 8.x would be preferable.

> Apache Tomcat Servlet Host Manager Servlet Cross-Site Scripting 
> Vulnerability

Don't deploy the host manager: no vulnerability at any Tomcat level.

> Apache Tomcat Information Disclosure Vulnerability
> 
> Apache Tomcat Accept-Language Cross-Site Scripting Vulnerability

Though unspecified, these will have no workaround I know of.

> Apache Tomcat JavaDoc Spoofing Vulnerability

This is not a vulnerability in Tomcat itself, but the (Javadoc)
documentation. Nobody should really have to worry about this, unless
you host a copy of the javadoc somewhere in your own environment.

> Apache Tomcat 4, 5 and 6 Examples Web Application Multiple
> Cross-Site Scripting Vulnerabilities
> 
> Apache Tomcat 4 and 5 Cross-Site Scripting Vulnerability in
> Calender Application in JSP Examples
> 
> Apache Tomcat 5 Cross-Site Scripting in implicit-objects.jsp of
> "Examples" Application

Don't deploy the examples: no vulnerability at any Tomcat level.

> Apache Tomcat Multiple Content Length Headers Information
> Disclosure Vulnerability

Not sure.

> Apache Tomcat Multiple Cross-Site Scripting Vulnerabilities in
> Manager and Host Manager Web Applications

Don't deploy the host manager. If you need to deploy the manager
application, make sure you secure it and make sure your web-based
users know not to click on emailed links that take them directly into
the manager application.

> Apache Tomcat 4 and 5 Multiple Cross-Site Scripting
> Vulnerabilities

These are usually issues with an application (e.g. Examples) and not
the server.

> The above is what were are experiencing and we are running Crystal
> Report as well.

What does Crystal Reports have to do with anything?

> Could someone please guide me in the most efficient way to
> upgrade?

http://tomcat.apache.org/migration.html

There are no migration guides from 5.0 -> 8.0, but if you read them
all, you'll know what issues you might face.

> My thought process is 5.0.xx to 5.5 then migration to 6 or 7?

There is no particular reason to upgrade each release one at a time.
You can go from 5.x to 8.x all at once.

> We are running windows 2003. I’m not even sure if it will support
> it?

If Java runs on it, Tomcat will run on it (assuming you have enough
memory to run your own application).

> I am unable to find any process documents or guidance on how to go 
> about the upgrade process and which version could help us in 
> vulnerability remediation. Could someone please help me? This is 
> extremely time sensitive to our business needs.

See the migration guide(s) above.

- -chris
-BEGIN PGP SIGNATURE-
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAla6MuMACgkQ9CaO5/Lv0PDjNACfXUgItmPkp4yjaC1R1sZB53c3
ONIAoIOIs9ETF5f6R5WXLdwtefPdVrIO
=61j9
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Tomcat 5.0.xx migration

[uzair rashid]

Hello Experts:



Most of our business is running Tomcat 7.x.xx or later. But, we have a
business function of ours that is using Tomcat 5.0.xx. Unfortunately, this
is causing a lot of issues in terms of vulnerability remediation.



Apache Tomcat Servlet Host Manager Servlet Cross-Site Scripting
Vulnerability

Apache Tomcat Information Disclosure Vulnerability

Apache Tomcat Accept-Language Cross-Site Scripting Vulnerability

Apache Tomcat JavaDoc Spoofing Vulnerability

Apache Tomcat 4, 5 and 6 Examples Web Application Multiple Cross-Site
Scripting Vulnerabilities

Apache Tomcat 4 and 5 Cross-Site Scripting Vulnerability in Calender
Application in JSP Examples

Apache Tomcat 5 Cross-Site Scripting in implicit-objects.jsp of "Examples"
Application

Apache Tomcat Multiple Content Length Headers Information Disclosure
Vulnerability

Apache Tomcat Multiple Cross-Site Scripting Vulnerabilities in Manager and
Host Manager Web Applications

Apache Tomcat 4 and 5 Multiple Cross-Site Scripting Vulnerabilities





The above is what were are experiencing and we are running Crystal Report
as well.



Could someone please guide me in the most efficient way to upgrade?



My thought process is 5.0.xx to 5.5 then migration to 6 or 7? We are
running windows 2003. I’m not even sure if it will support it? I am unable
to find any process documents or guidance on how to go about the upgrade
process and which version could help us in vulnerability remediation. Could
someone please help me? This is extremely time sensitive to our business
needs.



Cheers!

RE: Protect JSP from Direct Access in Tomcat 7.0.xx

[Sharon Prober (sprober)]

You could always position your jsp's inside the WEB-INF dir
This will enable you to access them only through server redirects rather
than absolute url's

Sharon

-Original Message-
From: Kiran Badi [mailto:ki...@poonam.org] 
Sent: Tuesday, June 19, 2012 3:10 AM
To: Tomcat Users List
Subject: Protect JSP from Direct Access in Tomcat 7.0.xx

Hi All,

I need your guidance again.I have bunch of JSP's close to 100+ which I
need to protect it from direct access.

I have this mapping in web xml and this is not working,It seems that
probably i need to define a role first and then use below settings.But
unfortunately my app is open internet application which does not use
realm at all.

security-constraint
display-nameDenyAccesstoDirectJSP/display-name
web-resource-collection
web-resource-namesample.jsp/web-resource-name
descriptionSample confirmation JSP/description
url-pattern*.jsp/url-pattern http-methodGET/http-method
http-methodPOST/http-method /web-resource-collection
/security-constraint

All my jsp's are residing in the webpages folder of project directory.I
know this is incorrect and probably gives direct access to jsp's.

So I have some clarification to ask,

1. is their a way to tell tomcat to not to serve direct jsp's probably
via web xml

2. Is their any extra setting that is required if I move my JSP's inside
web-inf.I created a folder under web-inf and create sample hello
world.jsp and then tried to invoke that jsp but got 404 message.

- Kiran

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Protect JSP from Direct Access in Tomcat 7.0.xx

[Kiran Badi]

Yup done this Sharon.Thanks
On 6/19/2012 2:03 PM, Sharon Prober (sprober) wrote:

You could always position your jsp's inside the WEB-INF dir
This will enable you to access them only through server redirects rather
than absolute url's

Sharon

-Original Message-
From: Kiran Badi [mailto:ki...@poonam.org]
Sent: Tuesday, June 19, 2012 3:10 AM
To: Tomcat Users List
Subject: Protect JSP from Direct Access in Tomcat 7.0.xx

Hi All,

I need your guidance again.I have bunch of JSP's close to 100+ which I
need to protect it from direct access.

I have this mapping in web xml and this is not working,It seems that
probably i need to define a role first and then use below settings.But
unfortunately my app is open internet application which does not use
realm at all.

security-constraint
display-nameDenyAccesstoDirectJSP/display-name
web-resource-collection
web-resource-namesample.jsp/web-resource-name
descriptionSample confirmation JSP/description
url-pattern*.jsp/url-pattern  http-methodGET/http-method
http-methodPOST/http-method  /web-resource-collection
/security-constraint

All my jsp's are residing in the webpages folder of project directory.I
know this is incorrect and probably gives direct access to jsp's.

So I have some clarification to ask,

1. is their a way to tell tomcat to not to serve direct jsp's probably
via web xml

2. Is their any extra setting that is required if I move my JSP's inside
web-inf.I created a folder under web-inf and create sample hello
world.jsp and then tried to invoke that jsp but got 404 message.

- Kiran

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org





-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Protect JSP from Direct Access in Tomcat 7.0.xx

[Kiran Badi]

Hi All,

I need your guidance again.I have bunch of JSP's close to 100+ which I 
need to protect it from direct access.


I have this mapping in web xml and this is not working,It seems that 
probably i need to define a role first and then use below settings.But 
unfortunately my app is open internet application which does not use 
realm at all.


security-constraint
display-nameDenyAccesstoDirectJSP/display-name
web-resource-collection
web-resource-namesample.jsp/web-resource-name
descriptionSample confirmation JSP/description
url-pattern*.jsp/url-pattern
http-methodGET/http-method
http-methodPOST/http-method
/web-resource-collection
/security-constraint

All my jsp's are residing in the webpages folder of project directory.I 
know this is incorrect and probably gives direct access to jsp's.


So I have some clarification to ask,

1. is their a way to tell tomcat to not to serve direct jsp's probably 
via web xml


2. Is their any extra setting that is required if I move my JSP's inside 
web-inf.I created a folder under web-inf and create sample hello 
world.jsp and then tried to invoke that jsp but got 404 message.


- Kiran

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Protect JSP from Direct Access in Tomcat 7.0.xx

[Tim Watts]

Hi Kiran,

On Tue, 2012-06-19 at 05:40 +0530, Kiran Badi wrote:
 Hi All,
 
 I need your guidance again.I have bunch of JSP's close to 100+ which I 
 need to protect it from direct access.
 
By direct access do you mean that http://host/myapp/sample.jsp is
returning the JSP source code rather than executing it?  Or do you mean
that you don't want any .jsp URLs to be accessible to users?

 I have this mapping in web xml and this is not working,It seems that 
 probably i need to define a role first and then use below settings.But 
 unfortunately my app is open internet application which does not use 
 realm at all.
 
 security-constraint
 display-nameDenyAccesstoDirectJSP/display-name
 web-resource-collection
 web-resource-namesample.jsp/web-resource-name
 descriptionSample confirmation JSP/description
 url-pattern*.jsp/url-pattern
 http-methodGET/http-method
 http-methodPOST/http-method
 /web-resource-collection
 /security-constraint
 
This isn't going to help you. Dump it.

 All my jsp's are residing in the webpages folder of project directory.I 
 know this is incorrect and probably gives direct access to jsp's.
 
 So I have some clarification to ask,
 
 1. is their a way to tell tomcat to not to serve direct jsp's probably 
 via web xml
 
If by serve direct jsp's you mean don't return source code then,
yes.  Put them under your web app's directory.  For example, if your web
app's context is 'myapp' then in tomcat it will be deployed under
TC_BASE/webapps/myapp.  You could put them directly in this directory
or group them under a separate directory; 'jsps' for instance.  Then
sample.jsp would be addressed as http://host/myapp/sample.jsp (or
http://host/myapp/jsps/sample.jsp )

 2. Is their any extra setting that is required if I move my JSP's inside 
 web-inf.I created a folder under web-inf and create sample hello 
 world.jsp and then tried to invoke that jsp but got 404 message.
 
First of all, it's WEB-INF. Case matters.  

No, there's no special setting that will directly expose anything
under WEB-INF via a URL.  That's the part of the Servlet Spec.  It's a
Good Thing®.  However, if you're trying to make your JSPs inaccessible
via URLs, then you can move them there and have them indirectly accessed
using a servlet which forwards the request to them.  See
ServletContext.getRequestDispatcher() and RequestDispatcher.forward().  

Hopefully, you're trying to use or move toward the MVC (Model, View,
Controller) pattern.  If not, you should.  Google MVC design pattern.
There are many, many frameworks that will make this easier for you (once
you learn them): Struts, Spring MVC...

If you're well into your project and don't want to add a framework to it
you could write a simple servlet that uses an algorithm to map URI paths
to JSPs then forwards to the JSP using a dispatcher.  For instance, you
could put your JSPs in myapp/WEB-INF/jsps.  Then have the servlet map a
URI such as /sample to /WEB-INF/jsps/sample.jsp (all relative
to /myapp). 

This isn't a great approach because you really aren't separating the
model from the view (all the app logic and display logic are housed in
the JSP -- a maintenance nightmare).  But if you don't have time to
re-architect the app now, it will hide the .jsp's from direct access.
And it will put you in a slightly better position if/WHEN you do
re-architect it.


 - Kiran
 
 -
 To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
 For additional commands, e-mail: users-h...@tomcat.apache.org
 



signature.asc
Description: This is a digitally signed message part

Re: Protect JSP from Direct Access in Tomcat 7.0.xx

[Kiran Badi]

On 6/19/2012 8:03 AM, Tim Watts wrote:

Hi Kiran,

On Tue, 2012-06-19 at 05:40 +0530, Kiran Badi wrote:

Hi All,

I need your guidance again.I have bunch of JSP's close to 100+ which I
need to protect it from direct access.


By direct access do you mean that http://host/myapp/sample.jsp is
returning the JSP source code rather than executing it?  Or do you mean
that you don't want any .jsp URLs to be accessible to users?
No its not returning source code.I have couple of jsps where in I use EL 
in those to access session objects and directly accessing those jsps is 
not something I want.



I have this mapping in web xml and this is not working,It seems that
probably i need to define a role first and then use below settings.But
unfortunately my app is open internet application which does not use
realm at all.

security-constraint
display-nameDenyAccesstoDirectJSP/display-name
web-resource-collection
web-resource-namesample.jsp/web-resource-name
descriptionSample confirmation JSP/description
url-pattern*.jsp/url-pattern
http-methodGET/http-method
http-methodPOST/http-method
/web-resource-collection
/security-constraint


This isn't going to help you. Dump it.

Yup its not helping.



All my jsp's are residing in the webpages folder of project directory.I
know this is incorrect and probably gives direct access to jsp's.

So I have some clarification to ask,

1. is their a way to tell tomcat to not to serve direct jsp's probably
via web xml


If by serve direct jsp's you mean don't return source code then,
yes.  Put them under your web app's directory.  For example, if your web
app's context is 'myapp' then in tomcat it will be deployed under
TC_BASE/webapps/myapp.  You could put them directly in this directory
or group them under a separate directory; 'jsps' for instance.  Then
sample.jsp would be addressed as http://host/myapp/sample.jsp (or
http://host/myapp/jsps/sample.jsp )

Yup I have same setup.Still its not working.my bad.



2. Is their any extra setting that is required if I move my JSP's inside
web-inf.I created a folder under web-inf and create sample hello
world.jsp and then tried to invoke that jsp but got 404 message.


First of all, it's WEB-INF. Case matters.

Ok got it.



No, there's no special setting that will directly expose anything
under WEB-INF via a URL.  That's the part of the Servlet Spec.  It's a
Good Thing®.  However, if you're trying to make your JSPs inaccessible
via URLs, then you can move them there and have them indirectly accessed
using a servlet which forwards the request to them.  See
ServletContext.getRequestDispatcher() and RequestDispatcher.forward().
Yup I have lot many of request dispatchers in servlets.Almost all my 
JSP's are using data which is forwarded by servlets.I pull data from db 
via servlet, store it in session scope,forward it to jsp and in jsp 
access it via el.On logoff I remove attributes from the session.



Hopefully, you're trying to use or move toward the MVC (Model, View,
Controller) pattern.  If not, you should.  Google MVC design pattern.
There are many, many frameworks that will make this easier for you (once
you learn them): Struts, Spring MVC...

If you're well into your project and don't want to add a framework to it
you could write a simple servlet that uses an algorithm to map URI paths
to JSPs then forwards to the JSP using a dispatcher.  For instance, you
could put your JSPs in myapp/WEB-INF/jsps.  Then have the servlet map a
URI such as /sample to /WEB-INF/jsps/sample.jsp (all relative
to /myapp).

http://localhost:8080/mysite/WEB-INF/jsp/newjsp.jsp

I just created folder jsp under WEB-INF and then added newjsp.jsp(this 
is hello world jsp) and then ran the file.I get 404 error. I am trying 
all this with netbeans.

This isn't a great approach because you really aren't separating the
model from the view (all the app logic and display logic are housed in
the JSP -- a maintenance nightmare).  But if you don't have time to
re-architect the app now, it will hide the .jsp's from direct access.
And it will put you in a slightly better position if/WHEN you do
re-architect it.
I think I am using kind of MVC pattern of course the one used around 6 
to 8 years back.I am using jsp as view, servlet as kind controller and 
then some beans/jstl and el to make my life easy somewhat. I would love 
to work with frameworks like spring or struts someday.


Ok  let me explain as what I need again,

I have form A with say about 10 fields, lets call this as jsp A. So in 
browser bar it looks like http://localhost:8080/mysite/A.jsp


User fills this A.jsp and then clicks Submit button. It posts the form 
to Servlet B which does insert in the database and then forwards the 
request via request dispatcher to  C.jsp which has some confirmation 
details in it.(Unique reference ids pulled out from DB).


Now with my existing setup if I directly give url like

http://localhost:8080/mysite/C.jsp   I go directly to C Jsp which I 
should not because its not suppose 

Re: Protect JSP from Direct Access in Tomcat 7.0.xx

[Tim Watts]

On Tue, 2012-06-19 at 08:48 +0530, Kiran Badi wrote:
 No its not returning source code.I have couple of jsps where in I use EL 
 in those to access session objects and directly accessing those jsps is 
 not something I want.

Good move.

SNIP

  2. Is their any extra setting that is required if I move my JSP's inside
  web-inf.I created a folder under web-inf and create sample hello
  world.jsp and then tried to invoke that jsp but got 404 message.
 
  First of all, it's WEB-INF. Case matters.
 Ok got it.
 
 
  No, there's no special setting that will directly expose anything
  under WEB-INF via a URL.  That's the part of the Servlet Spec.  It's a
  Good Thing®.  However, if you're trying to make your JSPs inaccessible
  via URLs, then you can move them there and have them indirectly accessed
  using a servlet which forwards the request to them.  See
  ServletContext.getRequestDispatcher() and RequestDispatcher.forward().

 Yup I have lot many of request dispatchers in servlets.Almost all my 
 JSP's are using data which is forwarded by servlets.I pull data from db 
 via servlet, store it in session scope,forward it to jsp and in jsp 
 access it via el.On logoff I remove attributes from the session.
 

So then those JSPs which are forwarded to by servlets (typical
controllers in MVC) could be moved to WEB-INF/whatever and then the
servlets would use a dispatcher to forward to
/WEB-INF/whatever/sample.jsp instead of /webpages/sample.jsp or
whatever they're using now.  You'd need to physically move those JSPs
then update the servlets to use the JSPs' new location.

 
  Hopefully, you're trying to use or move toward the MVC (Model, View,
  Controller) pattern.  If not, you should.  Google MVC design pattern.
  There are many, many frameworks that will make this easier for you (once
  you learn them): Struts, Spring MVC...
 
  If you're well into your project and don't want to add a framework to it
  you could write a simple servlet that uses an algorithm to map URI paths
  to JSPs then forwards to the JSP using a dispatcher.  For instance, you
  could put your JSPs in myapp/WEB-INF/jsps.  Then have the servlet map a
  URI such as /sample to /WEB-INF/jsps/sample.jsp (all relative
  to /myapp).
 http://localhost:8080/mysite/WEB-INF/jsp/newjsp.jsp
 
 I just created folder jsp under WEB-INF and then added newjsp.jsp(this 
 is hello world jsp) and then ran the file.I get 404 error. I am trying 
 all this with netbeans.

Well I hope by now you understand why or we're just going in circles.
Of course, that URL gives a 404: it's trying to access WEB-INF which is
never accessible via HTTP.  But it is accessible via
RequestDispatcher.forward() -- e.g.:


servletCtx.getRequestDispatcher(/WEB-INF/jsp/newjsp.jsp).forward(request, 
response);

This is kind of like what you said earlier that your servlets are
essentially doing, right?


  This isn't a great approach because you really aren't separating the
  model from the view (all the app logic and display logic are housed in
  the JSP -- a maintenance nightmare).  But if you don't have time to
  re-architect the app now, it will hide the .jsp's from direct access.
  And it will put you in a slightly better position if/WHEN you do
  re-architect it.
 I think I am using kind of MVC pattern of course the one used around 6 
 to 8 years back.I am using jsp as view, servlet as kind controller and 
 then some beans/jstl and el to make my life easy somewhat. I would love 
 to work with frameworks like spring or struts someday.
 
They're free you know. :-)  But of course, free software doesn't add
hours to the day.  You're basically rolling your own MVC and that will
probably help you understand better what these frameworks do.  But move
away from this as soon as you can.  They've solved a lot of problems you
probably haven't even considered and they can make your applications
much less brittle if you take the time to learn them well.

 Ok  let me explain as what I need again,
 
 I have form A with say about 10 fields, lets call this as jsp A. So in 
 browser bar it looks like http://localhost:8080/mysite/A.jsp
 
Ah, so you do want SOME of your JSPs to be URL accessible!  Well, if
A.jsp doesn't and never ever will have any dependencies on the
application's state then fine.  Maybe it's true today but I doubt it
will stay that way.  So it's probably better to be consistent and hide
this as well.

 User fills this A.jsp and then clicks Submit button. It posts the form 
 to Servlet B which does insert in the database and then forwards the 
 request via request dispatcher to  C.jsp which has some confirmation 
 details in it.(Unique reference ids pulled out from DB).
 
So on submit, an HTTP POST is sent to http://localhost:8080/mysite/B.
Then servlet B does its work and essentially invokes:

ctx.getRequestDispatcher(/C.jsp).forward(request, response);

then C.jsp sends back the response using data from the session.

Is this right?

(btw, you know your app'ss 

Re: Protect JSP from Direct Access in Tomcat 7.0.xx

[Kiran Badi]

On 6/19/2012 10:22 AM, Tim Watts wrote:

Hopefully, you're trying to use or move toward the MVC (Model, View,
Controller) pattern.  If not, you should.  Google MVC design pattern.
There are many, many frameworks that will make this easier for you (once
you learn them): Struts, Spring MVC...

If you're well into your project and don't want to add a framework to it
you could write a simple servlet that uses an algorithm to map URI paths
to JSPs then forwards to the JSP using a dispatcher.  For instance, you
could put your JSPs in myapp/WEB-INF/jsps.  Then have the servlet map a
URI such as /sample to /WEB-INF/jsps/sample.jsp (all relative
to /myapp).

http://localhost:8080/mysite/WEB-INF/jsp/newjsp.jsp

I just created folder jsp under WEB-INF and then added newjsp.jsp(this
is hello world jsp) and then ran the file.I get 404 error. I am trying
all this with netbeans.

Well I hope by now you understand why or we're just going in circles.
Of course, that URL gives a 404: it's trying to access WEB-INF which is
never accessible via HTTP.  But it is accessible via
RequestDispatcher.forward() -- e.g.:


servletCtx.getRequestDispatcher(/WEB-INF/jsp/newjsp.jsp).forward(request, 
response);

This is kind of like what you said earlier that your servlets are
essentially doing, right?
No I did not do the way you mentioned.I just created a jsp under WEB-INF 
and invoked it directly and got 404.I think I now see what you are 
mentioning.

and its wonderful idea.Makes perfect sense now.Thanks Tim.



This isn't a great approach because you really aren't separating the
model from the view (all the app logic and display logic are housed in
the JSP -- a maintenance nightmare).  But if you don't have time to
re-architect the app now, it will hide the .jsp's from direct access.
And it will put you in a slightly better position if/WHEN you do
re-architect it.

I think I am using kind of MVC pattern of course the one used around 6
to 8 years back.I am using jsp as view, servlet as kind controller and
then some beans/jstl and el to make my life easy somewhat. I would love
to work with frameworks like spring or struts someday.


They're free you know. :-)  But of course, free software doesn't add
hours to the day.  You're basically rolling your own MVC and that will
probably help you understand better what these frameworks do.  But move
away from this as soon as you can.  They've solved a lot of problems you
probably haven't even considered and they can make your applications
much less brittle if you take the time to learn them well.
Yup I have another project in mind which I plan to roll out soon 
probably either with spring or JSF.Maybe in a month or 2.I am fast 
learner and risk taker.





Ok  let me explain as what I need again,

I have form A with say about 10 fields, lets call this as jsp A. So in
browser bar it looks like http://localhost:8080/mysite/A.jsp


Ah, so you do want SOME of your JSPs to be URL accessible!  Well, if
A.jsp doesn't and never ever will have any dependencies on the
application's state then fine.  Maybe it's true today but I doubt it
will stay that way.  So it's probably better to be consistent and hide
this as well.


User fills this A.jsp and then clicks Submit button. It posts the form
to Servlet B which does insert in the database and then forwards the
request via request dispatcher to  C.jsp which has some confirmation
details in it.(Unique reference ids pulled out from DB).


So on submit, an HTTP POST is sent to http://localhost:8080/mysite/B.
Then servlet B does its work and essentially invokes:

ctx.getRequestDispatcher(/C.jsp).forward(request, response);

then C.jsp sends back the response using data from the session.

Is this right?

(btw, you know your app'ss requirements better than I, but storing all
data in the session isn't the only scope available.  It's likely that a
lot of response data needn't survive past the current request.  In that
case, setting request attributes would be better -- less memory needed,
less likely to pick up data that's inappropriate for the current
request).
Yup thats correct.I will explore this option of moving attributes to 
request.Thanks.

Now with my existing setup if I directly give url like

http://localhost:8080/mysite/C.jsp   I go directly to C Jsp which I
should not because its not suppose to be accessed directly.


Right.  Put C.jsp in WEB-INF, get a request dispatcher for
/WEB-INF/C.jsp, forward to that and go home.

Yup got it.I think this should resolve my issue.


-

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Tomcat 6.xx SSL supports

[sanjivacharyya]

Hi,

I have the below requirements for SSL certificates.
Please do let me know is tomcat 6.xx  supports below requirements :-
1) 128 bit data encryption will be employed. 
2) 1024 bit server certificate keys will be used. 
3) 2048 bit VeriSign Intermediate and Root CA Certificate keys will be used. 

Thanks in advance.
Regards,
Sanjiv
-- 
View this message in context: 
http://old.nabble.com/Tomcat-6.xx-SSL-supports-tp32356619p32356619.html
Sent from the Tomcat - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Tomcat 6.xx SSL supports

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Sanjiv,

On 8/29/2011 8:53 AM, sanjivacharyya wrote:
 I have the below requirements for SSL certificates. Please do let
 me know is tomcat 6.xx  supports below requirements :- 1) 128 bit
 data encryption will be employed. 2) 1024 bit server certificate
 keys will be used. 3) 2048 bit VeriSign Intermediate and Root CA
 Certificate keys will be used.

These will either be supported by the JVM or by OpenSSL depending on
how you have your server configured. I believe there are no problems
with the above requirements under either configuration.

- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk5buJMACgkQ9CaO5/Lv0PCvbwCeIabFZssIybm94LdSGRrD2lhu
sv0An145oLGfsZ4a5llW4apXLkmXrRIZ
=h3KX
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

FW: Accessing Properties file located in Conf Directory of Tomcat 5.XX

[Kaverappa.Prabhakar]

_
From: Prabhakar, Kaverappa
Sent: Thursday, August 20, 2009 10:20 AM
To: 'users@tomcat.apache.org'
Subject: Accessing Properties file located in Conf Directory of Tomcat 5.XX


We have to place, as per rules set by the department, the properties file in 
the Conf directory of Tomcat AS. The TOMCAT does not find the properties file 
placed in CONF directory but it does find when placed in Common or Shared 
directory of TOMCAT.

I tried placing the directory path in the java code of Jdeveloper (see below 
for variation of codes used) and created WAR file using Jdeveloper to deploy it 
on TOMCAT. But still it does not find it.

I tried placing the directory path in the java code of Jdeveloper (see below 
for variation of codes used) and created WAR file using Jdeveloper to deploy it 
on TOMCAT. But still it does not find it.

prop.load(loader.getResourceAsStream(genPricing.properties));
prop.load(loader.getResourceAsStream(/genPricing.properties));
prop.load(loader.getResourceAsStream(/conf/genPricing.properties));
prop.load(loader.getResourceAsStream(conf/genPricing.properties));
prop.load(loader.getResourceAsStream($tomcat_home\\conf\\genPricing.properties));
prop.load(loader.getResourceAsStream(${tomcat_home}/conf/genPricing.properties));

Any suggestion as to how to read the properties file located in CONF directory.

Quick response would be greatly appreciated.

Prabhakar

Accessing Properties file located in Conf Directory of Tomcat 5.XX

[Kaverappa.Prabhakar]

We have to place, as per rules set by the department, the properties file in 
the Conf directory of Tomcat AS. The TOMCAT does not find the properties file 
placed in CONF directory but it does find when placed in Common or Shared 
directory of TOMCAT.

I tried placing the directory path in the java code of Jdeveloper (see below 
for variation of codes used) and created WAR file using Jdeveloper to deploy it 
on TOMCAT. But still it does not find it.

I tried placing the directory path in the java code of Jdeveloper (see below 
for variation of codes used) and created WAR file using Jdeveloper to deploy it 
on TOMCAT. But still it does not find it.

prop.load(loader.getResourceAsStream(genPricing.properties));
prop.load(loader.getResourceAsStream(/genPricing.properties));
prop.load(loader.getResourceAsStream(/conf/genPricing.properties));
prop.load(loader.getResourceAsStream(conf/genPricing.properties));
prop.load(loader.getResourceAsStream($tomcat_home\\conf\\genPricing.properties));
prop.load(loader.getResourceAsStream(${tomcat_home}/conf/genPricing.properties));

Any suggestion as to how to read the properties file located in CONF directory.

Quick response would be greatly appreciated.

Prabhakar

RE: Accessing Properties file located in Conf Directory of Tomcat 5.XX

[Martin Gainty]

there are at least 100 people on this list that can accomplish this requirement

you will need to handle this requirement by posting a statement of work 
details on how to write a statement of work referenced here
http://www.usability.gov/plan/sow.html

1 or more engineers will respond with a RFQ with a proposal and cost estimate. 
You can then select the most qualified help... 

let us know when you have posted your SOW

__ 
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
 
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger 
sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung 
oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem 
Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. 
Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung 
fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le 
destinataire prévu, nous te demandons avec bonté que pour satisfaire informez 
l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est 
interdite. Ce message sert à l'information seulement et n'aura pas n'importe 
quel effet légalement obligatoire. Étant donné que les email peuvent facilement 
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité 
pour le contenu fourni.




 From: kaverappa.prabha...@do.treas.gov
 To: users@tomcat.apache.org
 Date: Thu, 20 Aug 2009 10:52:30 -0400
 Subject: FW: Accessing Properties file located in Conf Directory of Tomcat 
 5.XX
 
 
 
 _
 From: Prabhakar, Kaverappa
 Sent: Thursday, August 20, 2009 10:20 AM
 To: 'users@tomcat.apache.org'
 Subject: Accessing Properties file located in Conf Directory of Tomcat 5.XX
 
 
 We have to place, as per rules set by the department, the properties file in 
 the Conf directory of Tomcat AS. The TOMCAT does not find the properties file 
 placed in CONF directory but it does find when placed in Common or Shared 
 directory of TOMCAT.
 
 I tried placing the directory path in the java code of Jdeveloper (see below 
 for variation of codes used) and created WAR file using Jdeveloper to deploy 
 it on TOMCAT. But still it does not find it.
 
 I tried placing the directory path in the java code of Jdeveloper (see below 
 for variation of codes used) and created WAR file using Jdeveloper to deploy 
 it on TOMCAT. But still it does not find it.
 
 prop.load(loader.getResourceAsStream(genPricing.properties));
 prop.load(loader.getResourceAsStream(/genPricing.properties));
 prop.load(loader.getResourceAsStream(/conf/genPricing.properties));
 prop.load(loader.getResourceAsStream(conf/genPricing.properties));
 prop.load(loader.getResourceAsStream($tomcat_home\\conf\\genPricing.properties));
 prop.load(loader.getResourceAsStream(${tomcat_home}/conf/genPricing.properties));
 
 Any suggestion as to how to read the properties file located in CONF 
 directory.
 
 Quick response would be greatly appreciated.
 
 Prabhakar
 
 
 

_
With Windows Live, you can organize, edit, and share your photos.
http://www.windowslive.com/Desktop/PhotoGallery

Re: Accessing Properties file located in Conf Directory of Tomcat 5.XX

[Tim Funk]

I am assuming loader is an instance of a classloader. The classloader 
doesn't see the conf directory. (But as your  noticed - it does see the 
common directory)


Your easiest (but tomcat specific) solution is to do something like this:
File confDir = new File(System.properties(catalina.home), conf);
File propFile = new File(confDir , genPricing.properties);
Properties p = new Properties();
p.load(new FileInputStream(propFile));


-Tim


kaverappa.prabha...@do.treas.gov wrote:

We have to place, as per rules set by the department, the properties file in 
the Conf directory of Tomcat AS. The TOMCAT does not find the properties file 
placed in CONF directory but it does find when placed in Common or Shared 
directory of TOMCAT.

I tried placing the directory path in the java code of Jdeveloper (see below 
for variation of codes used) and created WAR file using Jdeveloper to deploy it 
on TOMCAT. But still it does not find it.

I tried placing the directory path in the java code of Jdeveloper (see below 
for variation of codes used) and created WAR file using Jdeveloper to deploy it 
on TOMCAT. But still it does not find it.

prop.load(loader.getResourceAsStream(genPricing.properties));
prop.load(loader.getResourceAsStream(/genPricing.properties));
prop.load(loader.getResourceAsStream(/conf/genPricing.properties));
prop.load(loader.getResourceAsStream(conf/genPricing.properties));
prop.load(loader.getResourceAsStream($tomcat_home\\conf\\genPricing.properties));
prop.load(loader.getResourceAsStream(${tomcat_home}/conf/genPricing.properties));

Any suggestion as to how to read the properties file located in CONF directory.

Quick response would be greatly appreciated.

Prabhakar







-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Accessing Properties file located in Conf Directory of Tomcat 5.XX

[Pid]

On 20/08/2009 16:24, Martin Gainty wrote:


there are at least 100 people on this list that can accomplish this requirement


*Can* yes. *Will*, no.


you will need to handle this requirement by posting a statement of work
details on how to write a statement of work referenced here
http://www.usability.gov/plan/sow.html


What in the world are you talking about?/rhetorical


1 or more engineers will respond with a RFQ with a proposal and cost estimate.
You can then select the most qualified help...


@Kaverappa: No, they *absolutely will not*.


let us know when you have posted your SOW


No, just ignore this nonsense.

@Martin, if you're pitching for work, can you do it somewhere else please?


p



__
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité

Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger 
sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung 
oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem 
Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. 
Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung 
fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le 
destinataire prévu, nous te demandons avec bonté que pour satisfaire informez 
l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est 
interdite. Ce message sert à l'information seulement et n'aura pas n'importe 
quel effet légalement obligatoire. Étant donné que les email peuvent facilement 
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité 
pour le contenu fourni.





From: kaverappa.prabha...@do.treas.gov
To: users@tomcat.apache.org
Date: Thu, 20 Aug 2009 10:52:30 -0400
Subject: FW: Accessing Properties file located in Conf Directory of Tomcat 5.XX



_
From: Prabhakar, Kaverappa
Sent: Thursday, August 20, 2009 10:20 AM
To: 'users@tomcat.apache.org'
Subject: Accessing Properties file located in Conf Directory of Tomcat 5.XX


We have to place, as per rules set by the department, the properties file in 
the Conf directory of Tomcat AS. The TOMCAT does not find the properties file 
placed in CONF directory but it does find when placed in Common or Shared 
directory of TOMCAT.

I tried placing the directory path in the java code of Jdeveloper (see below 
for variation of codes used) and created WAR file using Jdeveloper to deploy it 
on TOMCAT. But still it does not find it.

I tried placing the directory path in the java code of Jdeveloper (see below 
for variation of codes used) and created WAR file using Jdeveloper to deploy it 
on TOMCAT. But still it does not find it.

prop.load(loader.getResourceAsStream(genPricing.properties));
prop.load(loader.getResourceAsStream(/genPricing.properties));
prop.load(loader.getResourceAsStream(/conf/genPricing.properties));
prop.load(loader.getResourceAsStream(conf/genPricing.properties));
prop.load(loader.getResourceAsStream($tomcat_home\\conf\\genPricing.properties));
prop.load(loader.getResourceAsStream(${tomcat_home}/conf/genPricing.properties));

Any suggestion as to how to read the properties file located in CONF directory.

Quick response would be greatly appreciated.

Prabhakar





_
With Windows Live, you can organize, edit, and share your photos.
http://www.windowslive.com/Desktop/PhotoGallery



-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Tomcat 5.5, Apache 2.0.XX and mod_proxy

[mip]

I'm trying to proxy my Tomcat web application through Apache 2.0 using
mod_proxy.

I have uncommented the following in my server.xml:

!-- Define a Proxied HTTP/1.1 Connector on port 8082 --
!-- See proxy documentation for more information about using this. --
Connector port=8082
   maxThreads=150 minSpareThreads=25 maxSpareThreads=75
   enableLookups=false
   acceptCount=100 debug=0 connectionTimeout=2
   proxyPort=80 disableUploadTimeout=true /

and I've added the following to my httpd.conf:

  VirtualHost *:80
  ServerName foo.bar.com
  ProxyPass  /  http://foobar.com:8082/app/
  ProxyPassReverse  /  http://foobar.com:8082/app/
  /VirtualHost

The pages are being passed without any problems but the sessions are being
lost as cookies are not being passed. I'm guessing I need to add something
to the above stanza which rewrite the cookies. But what?
-- 
View this message in context: 
http://www.nabble.com/Tomcat-5.5%2C-Apache-2.0.XX-and-mod_proxy-tf4881521.html#a13970134
Sent from the Tomcat - User mailing list archive at Nabble.com.


-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Tomcat 5.5, Apache 2.0.XX and mod_proxy

[Peter Stavrinides]

Thats because your configuration is incomplete, in order for Apache to 
pass the cookie to the correct context you need to do some additional 
configuration (or alternatively use a connector like mod_jk)


You may need to configure the jvmRoute parameter in server.xml, this 
allows Apache to map to the correct Tomcat context, otherwise deploy 
your web app in the Tomcat root context.


Connector port=8082
  maxThreads=150 minSpareThreads=25 maxSpareThreads=75
  enableLookups=false
  acceptCount=100 debug=0 connectionTimeout=2
  proxyPort=80 disableUploadTimeout=true 
	   jvmRoute=T1/



You also need to add a server mapping in Apache, one way to do this 
easily is with a RewriteMap. (If you use Apache 2.2 then you could use 
the in-built mod_proxy_balancer module). I also use Apache 2.0 so I just 
make a static mapping, which looks something like this:



RewriteMap SERVERS rnd:/etc/apache2/servers.conf

--
servers.conf
--
T1  tomcat.server.com:8081
ALL   tomcat.server.com:8081 



#configure more instances for load balancing if you wish

Peter



mip wrote:

I'm trying to proxy my Tomcat web application through Apache 2.0 using
mod_proxy.

I have uncommented the following in my server.xml:

!-- Define a Proxied HTTP/1.1 Connector on port 8082 --
!-- See proxy documentation for more information about using this. --
Connector port=8082
   maxThreads=150 minSpareThreads=25 maxSpareThreads=75
   enableLookups=false
   acceptCount=100 debug=0 connectionTimeout=2
   proxyPort=80 disableUploadTimeout=true /

and I've added the following to my httpd.conf:

  VirtualHost *:80
  ServerName foo.bar.com
  ProxyPass  /  http://foobar.com:8082/app/
  ProxyPassReverse  /  http://foobar.com:8082/app/
  /VirtualHost

The pages are being passed without any problems but the sessions are being
lost as cookies are not being passed. I'm guessing I need to add something
to the above stanza which rewrite the cookies. But what?
  

Re: Tomcat 5.5, Apache 2.0.XX and mod_proxy

[Peter Stavrinides]

It is just the port your Tomcat is running on, which could be any port, 
so if you are using 8082 that will be your port... it's better though 
not to be on port 80.



mip wrote:

Thanks Peter.

Should that be:

--
servers.conf
--
T1  tomcat.server.com:8082
ALL   tomcat.server.com:8082

?

If not what is port 8081 being used for?



Peter Stavrinides wrote:
  
Thats because your configuration is incomplete, in order for Apache to 
pass the cookie to the correct context you need to do some additional 
configuration (or alternatively use a connector like mod_jk)


You may need to configure the jvmRoute parameter in server.xml, this 
allows Apache to map to the correct Tomcat context, otherwise deploy 
your web app in the Tomcat root context.


Connector port=8082
   maxThreads=150 minSpareThreads=25 maxSpareThreads=75
   enableLookups=false
   acceptCount=100 debug=0 connectionTimeout=2
   proxyPort=80 disableUploadTimeout=true 
	   jvmRoute=T1/



You also need to add a server mapping in Apache, one way to do this 
easily is with a RewriteMap. (If you use Apache 2.2 then you could use 
the in-built mod_proxy_balancer module). I also use Apache 2.0 so I just 
make a static mapping, which looks something like this:



RewriteMap SERVERS rnd:/etc/apache2/servers.conf

--
servers.conf
--
T1  tomcat.server.com:8081
ALL   tomcat.server.com:8081 



#configure more instances for load balancing if you wish

Peter



mip wrote:


I'm trying to proxy my Tomcat web application through Apache 2.0 using
mod_proxy.

I have uncommented the following in my server.xml:

!-- Define a Proxied HTTP/1.1 Connector on port 8082 --
!-- See proxy documentation for more information about using this.
--
Connector port=8082
   maxThreads=150 minSpareThreads=25 maxSpareThreads=75
   enableLookups=false
   acceptCount=100 debug=0 connectionTimeout=2
   proxyPort=80 disableUploadTimeout=true /

and I've added the following to my httpd.conf:

  VirtualHost *:80
  ServerName foo.bar.com
  ProxyPass  /  http://foobar.com:8082/app/
  ProxyPassReverse  /  http://foobar.com:8082/app/
  /VirtualHost

The pages are being passed without any problems but the sessions are
being
lost as cookies are not being passed. I'm guessing I need to add
something
to the above stanza which rewrite the cookies. But what?
  
  





  



-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Tomcat 5.5, Apache 2.0.XX and mod_proxy

[mip]

Thanks Peter.

Should that be:

--
servers.conf
--
T1  tomcat.server.com:8082
ALL   tomcat.server.com:8082

?

If not what is port 8081 being used for?



Peter Stavrinides wrote:
 
 Thats because your configuration is incomplete, in order for Apache to 
 pass the cookie to the correct context you need to do some additional 
 configuration (or alternatively use a connector like mod_jk)
 
 You may need to configure the jvmRoute parameter in server.xml, this 
 allows Apache to map to the correct Tomcat context, otherwise deploy 
 your web app in the Tomcat root context.
 
 Connector port=8082
maxThreads=150 minSpareThreads=25 maxSpareThreads=75
enableLookups=false
acceptCount=100 debug=0 connectionTimeout=2
proxyPort=80 disableUploadTimeout=true 
  jvmRoute=T1/
 
 
 You also need to add a server mapping in Apache, one way to do this 
 easily is with a RewriteMap. (If you use Apache 2.2 then you could use 
 the in-built mod_proxy_balancer module). I also use Apache 2.0 so I just 
 make a static mapping, which looks something like this:
 
 
 RewriteMap SERVERS rnd:/etc/apache2/servers.conf
 
 --
 servers.conf
 --
 T1  tomcat.server.com:8081
 ALL   tomcat.server.com:8081 
 
 
 #configure more instances for load balancing if you wish
 
 Peter
 
 
 
 mip wrote:
 I'm trying to proxy my Tomcat web application through Apache 2.0 using
 mod_proxy.

 I have uncommented the following in my server.xml:

 !-- Define a Proxied HTTP/1.1 Connector on port 8082 --
 !-- See proxy documentation for more information about using this.
 --
 Connector port=8082
maxThreads=150 minSpareThreads=25 maxSpareThreads=75
enableLookups=false
acceptCount=100 debug=0 connectionTimeout=2
proxyPort=80 disableUploadTimeout=true /

 and I've added the following to my httpd.conf:

   VirtualHost *:80
   ServerName foo.bar.com
   ProxyPass  /  http://foobar.com:8082/app/
   ProxyPassReverse  /  http://foobar.com:8082/app/
   /VirtualHost

 The pages are being passed without any problems but the sessions are
 being
 lost as cookies are not being passed. I'm guessing I need to add
 something
 to the above stanza which rewrite the cookies. But what?
   
 
 
 

-- 
View this message in context: 
http://www.nabble.com/Tomcat-5.5%2C-Apache-2.0.XX-and-mod_proxy-tf4881521.html#a13971776
Sent from the Tomcat - User mailing list archive at Nabble.com.


-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Tomcat 5.5, Apache 2.0.XX and mod_proxy

[mip]

 --
 T1  tomcat.server.com:8081
 ALL   tomcat.server.com:8081 


 #configure more instances for load balancing if you wish

 Peter



 mip wrote:
 
 I'm trying to proxy my Tomcat web application through Apache 2.0 using
 mod_proxy.

 I have uncommented the following in my server.xml:

 !-- Define a Proxied HTTP/1.1 Connector on port 8082 --
 !-- See proxy documentation for more information about using this.
 --
 Connector port=8082
maxThreads=150 minSpareThreads=25
 maxSpareThreads=75
enableLookups=false
acceptCount=100 debug=0 connectionTimeout=2
proxyPort=80 disableUploadTimeout=true /

 and I've added the following to my httpd.conf:

   VirtualHost *:80
   ServerName foo.bar.com
   ProxyPass  /  http://foobar.com:8082/app/
   ProxyPassReverse  /  http://foobar.com:8082/app/
   /VirtualHost

 The pages are being passed without any problems but the sessions are
 being
 lost as cookies are not being passed. I'm guessing I need to add
 something
 to the above stanza which rewrite the cookies. But what?
   
   

 

   
 
 
 -
 To start a new topic, e-mail: users@tomcat.apache.org
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 

-- 
View this message in context: 
http://www.nabble.com/Tomcat-5.5%2C-Apache-2.0.XX-and-mod_proxy-tf4881521.html#a13972723
Sent from the Tomcat - User mailing list archive at Nabble.com.


-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

xx

[rahul]

rahul
--
1. e4 _

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Problem with Tomcat 6.0.xx and JAAS and userContextClassLoader

[A Sunley]

Hello all,

We're using Tomcat 6.0.14 and we need to use JAAS for our webapp. We have a
custom login module and it's desirable for us to have the custom LoginModule
.jar inside the WEB-INF\lib directory of our webapp.

However with Tomcat 6 it appears we can only place the jar in the lib folder
of Tomcat, otherwise we get a 'SEVERE: Class com.devtest.auth.UserPrincipal
not found! Class not added' on startup. I can't find much information on
this issue, but the issue is perhaps better described here:
http://support.liferay.com/browse/LEP-2995;jsessionid=C72F970D8B99F4BD60185FB0A1567A8F?page=history

According to the link it is because Tomcat 6 performs a Class.forName()
lookup. 

Is there anyway around this?

Thanks,
Alan.
-- 
View this message in context: 
http://www.nabble.com/Problem-with-Tomcat-6.0.xx-and-JAAS-and-userContextClassLoader-tf4394188.html#a12529648
Sent from the Tomcat - User mailing list archive at Nabble.com.


-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Problem with Tomcat 6.0.xx and JAAS and userContextClassLoader

[Mark Thomas]

A Sunley wrote:
 Is there anyway around this?

No.

Mark


-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Problem with Tomcat 6.0.xx and JAAS and userContextClassLoader

[Mark Thomas]

A Sunley wrote:
 Is this bug with Tomcat 6, or is it intentional? The version 6 documentation
 mentions that setting useContextClassLoader switches between context and
 container class loading, but obviously that isn't the case anymore...

Ignore my previous post. It is indeed a bug in TC6.

Mark

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Problem with Tomcat 6.0.xx and JAAS and userContextClassLoader

[A Sunley]

Is this bug with Tomcat 6, or is it intentional? The version 6 documentation
mentions that setting useContextClassLoader switches between context and
container class loading, but obviously that isn't the case anymore...

http://tomcat.apache.org/tomcat-6.0-doc/realm-howto.html#JAASRealm



markt-2 wrote:
 
 A Sunley wrote:
 Is there anyway around this?
 
 No.
 
 Mark
 
 
 -
 To start a new topic, e-mail: users@tomcat.apache.org
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 

-- 
View this message in context: 
http://www.nabble.com/Problem-with-Tomcat-6.0.xx-and-JAAS-and-userContextClassLoader-tf4394188.html#a12534233
Sent from the Tomcat - User mailing list archive at Nabble.com.


-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

-XX:+HeapDumpOnOutOfMemoryError

[[EMAIL PROTECTED]]

I specified that parameter in JAVA_OPTS variable, but after the first 
java.lang.OutOfMemoryError: Java heap space error, no dump file was created. 
Where should that file be created by default? any clue?
Thanks


--
Leggi GRATIS le tue mail con il telefonino i-mode™ di Wind
http://i-mode.wind.it/



-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: -XX:+HeapDumpOnOutOfMemoryError

[Rainer Jung]

In the working directory of the process. Of course you need enough free
disk space.

There is also

-XX:HeapDumpPath=DIRECTORY_OR_FILE

(Caution: I don't know, if all JVM versions that implement
-XX:+HeapDumpOnOutOfMemoryError, implement this one too).

You should check in the process table (if it's a unix like system) if
your switches are picked up appropriately.

Also you can check their function by wrinting a simple java app, that
has an unterminated loop allocating objects and setting the heap size to
a small value, which should prodice an OurOfmemoryError and a heap dump.

Regards,

Rainer

[EMAIL PROTECTED] schrieb:
 I specified that parameter in JAVA_OPTS variable, but after the first 
 java.lang.OutOfMemoryError: Java heap space error, no dump file was 
 created. Where should that file be created by default? any clue?
 Thanks

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: -XX:+HeapDumpOnOutOfMemoryError

[[EMAIL PROTECTED]]

 In the working directory of the process. Of course you need enough free
 disk space.



working directory means something like:
/TomcatServer/work/Catalina/localhost/webapp_name/ ?
because there is nothing there :( and there is enough free space.


 There is also

 -XX:HeapDumpPath=DIRECTORY_OR_FILE

 (Caution: I don't know, if all JVM versions that implement
 -XX:+HeapDumpOnOutOfMemoryError, implement this one too).

 You should check in the process table (if it's a unix like system) if
 your switches are picked up appropriately.

/usr/local/jdk/bin/java -server -Xms512m -Xmx1024m 
-XX:+HeapDumpOnOutOfMemoryError 
-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager 
-Djava.endorsed.dirs=/usr/local/jakarta/jakarta-tomcat-5.5.9/common/endorsed 
-classpath 
:/usr/local/jakarta/jakarta-tomcat-5.5.9/bin/bootstrap.jar:/usr/local/jakarta/jakarta-tomcat-5.5.9/bin/commons-logging-api.jar
 -Dcatalina.base=/usr/local/jakarta/jakarta-tomcat-5.5.9 
-Dcatalina.home=/usr/local/jakarta/jakarta-tomcat-5.5.9 
-Djava.io.tmpdir=/usr/local/jakarta/jakarta-tomcat-5.5.9/temp 
org.apache.catalina.startup.Bootstrap start

is the process info. Any clue why it didn't get generated?


 Also you can check their function by wrinting a simple java app, that
 has an unterminated loop allocating objects and setting the heap size to
 a small value, which should prodice an OurOfmemoryError and a heap dump.

 Regards,

 Rainer

 [EMAIL PROTECTED] schrieb:
  I specified that parameter in JAVA_OPTS variable, but after the first 
  java.lang.OutOfMemoryError: Java heap space error, no dump file was 
  created. Where should that file be created by default? any clue?
  Thanks

 -
 To start a new topic, e-mail: users@tomcat.apache.org
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]

 


--
Leggi GRATIS le tue mail con il telefonino i-mode™ di Wind
http://i-mode.wind.it/



-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: -XX:+HeapDumpOnOutOfMemoryError

[[EMAIL PROTECTED]]

  In the working directory of the process. Of course you need enough free
  disk space.
 


 working directory means something like:
 /TomcatServer/work/Catalina/localhost/webapp_name/ ?
 because there is nothing there :( and there is enough free space.


  There is also
 
  -XX:HeapDumpPath=DIRECTORY_OR_FILE
 
  (Caution: I don't know, if all JVM versions that implement
  -XX:+HeapDumpOnOutOfMemoryError, implement this one too).
 
  You should check in the process table (if it's a unix like system) if
  your switches are picked up appropriately.

 /usr/local/jdk/bin/java -server -Xms512m -Xmx1024m 
 -XX:+HeapDumpOnOutOfMemoryError 
 -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager 
 -Djava.endorsed.dirs=/usr/local/jakarta/jakarta-tomcat-5.5.9/common/endorsed 
 -classpath 
 :/usr/local/jakarta/jakarta-tomcat-5.5.9/bin/bootstrap.jar:/usr/local/jakarta/jakarta-tomcat-5.5.9/bin/commons-logging-api.jar
  -Dcatalina.base=/usr/local/jakarta/jakarta-tomcat-5.5.9 
 -Dcatalina.home=/usr/local/jakarta/jakarta-tomcat-5.5.9 
 -Djava.io.tmpdir=/usr/local/jakarta/jakarta-tomcat-5.5.9/temp 
 org.apache.catalina.startup.Bootstrap start

 is the process info. Any clue why it didn't get generated?


With that process line, is it normal that the 
Runtime().getRuntime().totalMemory() command gives me 43425792?


  Also you can check their function by wrinting a simple java app, that
  has an unterminated loop allocating objects and setting the heap size to
  a small value, which should prodice an OurOfmemoryError and a heap dump.
 
  Regards,
 
  Rainer
 
  [EMAIL PROTECTED] schrieb:
   I specified that parameter in JAVA_OPTS variable, but after the first 
   java.lang.OutOfMemoryError: Java heap space error, no dump file was 
   created. Where should that file be created by default? any clue?
   Thanks
 
  -
  To start a new topic, e-mail: users@tomcat.apache.org
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 


 --
 Leggi GRATIS le tue mail con il telefonino i-mode™ di Wind
 http://i-mode.wind.it/



 -
 To start a new topic, e-mail: users@tomcat.apache.org
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]

 


--
Leggi GRATIS le tue mail con il telefonino i-mode™ di Wind
http://i-mode.wind.it/



-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: -XX:+HeapDumpOnOutOfMemoryError

[Filip Hanik - Dev Lists]

working directory is the bin directory

Filip

[EMAIL PROTECTED] wrote:

In the working directory of the process. Of course you need enough free
disk space.





working directory means something like:
/TomcatServer/work/Catalina/localhost/webapp_name/ ?
because there is nothing there :( and there is enough free space.


  

There is also

-XX:HeapDumpPath=DIRECTORY_OR_FILE

(Caution: I don't know, if all JVM versions that implement
-XX:+HeapDumpOnOutOfMemoryError, implement this one too).

You should check in the process table (if it's a unix like system) if
your switches are picked up appropriately.



/usr/local/jdk/bin/java -server -Xms512m -Xmx1024m 
-XX:+HeapDumpOnOutOfMemoryError 
-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager 
-Djava.endorsed.dirs=/usr/local/jakarta/jakarta-tomcat-5.5.9/common/endorsed 
-classpath 
:/usr/local/jakarta/jakarta-tomcat-5.5.9/bin/bootstrap.jar:/usr/local/jakarta/jakarta-tomcat-5.5.9/bin/commons-logging-api.jar
 -Dcatalina.base=/usr/local/jakarta/jakarta-tomcat-5.5.9 
-Dcatalina.home=/usr/local/jakarta/jakarta-tomcat-5.5.9 
-Djava.io.tmpdir=/usr/local/jakarta/jakarta-tomcat-5.5.9/temp 
org.apache.catalina.startup.Bootstrap start

is the process info. Any clue why it didn't get generated?

 
  

Also you can check their function by wrinting a simple java app, that
has an unterminated loop allocating objects and setting the heap size to
a small value, which should prodice an OurOfmemoryError and a heap dump.

Regards,

Rainer

[EMAIL PROTECTED] schrieb:


I specified that parameter in JAVA_OPTS variable, but after the first 
java.lang.OutOfMemoryError: Java heap space error, no dump file was created. 
Where should that file be created by default? any clue?
Thanks
  

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]






--
Leggi GRATIS le tue mail con il telefonino i-mode™ di Wind
http://i-mode.wind.it/



-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



  



-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Starting Tomcat 5.5.23 gives error in localhost.xxxx-xx-xx.log

[Gupta, Medhavi \(GE Healthcare\)]

 Hi,
 
 I have tomcat 5.5.23 binary distribution Windows executable.
 Environmental variable  JAVA_HOME is set to C:\Program
 Files\Java\jre1.5.0_06. When I try to start the Tomcat Service, I see
 the below error in localhost.-xx-xx.log file. I am not able to
 understand what can be the reason for this? Am I missing something. In
 Apache tomcat properties under Java , Java Virtual Machine is set to
 C:\Program Files\Java\jre1.5.0_06\bin\client\jvm.dll.
 
 Apr 20, 2007 2:43:54 PM org.apache.catalina.core.ApplicationContext
 log
 INFO: org.apache.webapp.balancer.BalancerFilter: init(): ruleChain:
 [org.apache.webapp.balancer.RuleChain:
 [org.apache.webapp.balancer.rules.URLStringMatchRule: Target string:
 News / Redirect URL: http://www.cnn.com],
 [org.apache.webapp.balancer.rules.RequestParameterRule: Target param
 name: paramName / Target param value: paramValue / Redirect URL:
 http://www.yahoo.com],
 [org.apache.webapp.balancer.rules.AcceptEverythingRule: Redirect URL:
 http://jakarta.apache.org]]
 Apr 20, 2007 2:43:54 PM org.apache.catalina.core.StandardContext
 listenerStart
 SEVERE: Error configuring application listener of class
 listeners.ContextListener
 java.lang.ClassFormatError: Extra bytes at the end of class file
 listeners/ContextListener
   at java.lang.ClassLoader.defineClass1(Native Method)
   at java.lang.ClassLoader.defineClass(Unknown Source)
   at java.security.SecureClassLoader.defineClass(Unknown Source)
   at
 org.apache.catalina.loader.WebappClassLoader.findClassInternal(WebappC
 lassLoader.java:1812)
   at
 org.apache.catalina.loader.WebappClassLoader.findClass(WebappClassLoad
 er.java:866)
   at
 org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoad
 er.java:1319)
   at
 org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoad
 er.java:1198)
   at
 org.apache.catalina.core.StandardContext.listenerStart(StandardContext
 .java:3677)
   at
 org.apache.catalina.core.StandardContext.start(StandardContext.java:41
 83)
   at
 org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.
 java:759)
   at
 org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739
 )
   at
 org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524)
   at
 org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java
 :904)
   at
 org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.ja
 va:867)
   at
 org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:474)
   at
 org.apache.catalina.startup.HostConfig.start(HostConfig.java:1112)
   at
 org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:
 310)
   at
 org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(Lifecycle
 Support.java:119)
   at
 org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1021)
   at
 org.apache.catalina.core.StandardHost.start(StandardHost.java:718)
   at
 org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1013)
   at
 org.apache.catalina.core.StandardEngine.start(StandardEngine.java:442)
   at
 org.apache.catalina.core.StandardService.start(StandardService.java:45
 0)
   at
 org.apache.catalina.core.StandardServer.start(StandardServer.java:709)
   at org.apache.catalina.startup.Catalina.start(Catalina.java:551)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
 Source)
   at java.lang.reflect.Method.invoke(Unknown Source)
   at
 org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:275)
   at
 org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
 Apr 20, 2007 2:43:54 PM org.apache.catalina.core.StandardContext
 listenerStart
 SEVERE: Error configuring application listener of class
 listeners.SessionListener
 java.lang.ClassFormatError: Extra bytes at the end of class file
 listeners/SessionListener
   at java.lang.ClassLoader.defineClass1(Native Method)
   at java.lang.ClassLoader.defineClass(Unknown Source)
   at java.security.SecureClassLoader.defineClass(Unknown Source)
   at
 org.apache.catalina.loader.WebappClassLoader.findClassInternal(WebappC
 lassLoader.java:1812)
   at
 org.apache.catalina.loader.WebappClassLoader.findClass(WebappClassLoad
 er.java:866)
   at
 org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoad
 er.java:1319)
   at
 org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoad
 er.java:1198)
   at
 org.apache.catalina.core.StandardContext.listenerStart(StandardContext
 .java:3677)
   at
 org.apache.catalina.core.StandardContext.start(StandardContext.java:41
 83)
   at
 org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.
 java:759)
   at
 org.apache.catalina.core.ContainerBase.addChild

RE: Starting Tomcat 5.5.23 gives error in localhost.xxxx-xx-xx.log

[Caldarale, Charles R]

 From: Gupta, Medhavi (GE Healthcare) 
 [mailto:[EMAIL PROTECTED] 
 Subject: Starting Tomcat 5.5.23 gives error in 
 localhost.-xx-xx.log
 
  I have tomcat 5.5.23 binary distribution Windows executable.
 
  java.lang.ClassFormatError: Extra bytes at the end of class file
  listeners/ContextListener

The usual cause of the above is corrupted jar files, often due to using
a Windows FTP client in ASCII (rather than binary) mode to move them.
The Windows FTP client likes to convert any 0x0A bytes (line feed) into
0x0A 0x0D pairs (line feed, carriage return).  Try reinstalling Tomcat
without doing any FTP transfers.

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you
received this in error, please contact the sender and delete the e-mail
and its attachments from all computers.

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: RE : Problems configuring a Context path=xx using Apache/Tomcat

[René Schade]

Thanks, that really helped.

It works fine if I place the file Servlets#application.xml
In the CATALINA_HOME/conf/Catalina/localhost/ folder.

I would prefer to place it in the /META-INF/ folder in the application, but 
Tomcat seems to ignore files not named context.xml in this folder.

Any suggestions?

René
 

 -Original Message-
 From: LASSIEGE Hugo [mailto:[EMAIL PROTECTED]
 Sent: 24. oktober 2006 10:22
 To: Tomcat Users List
 Subject: RE : Problems configuring a Context path=xx using
 Apache/Tomcat
 
 In tomcat 5.5.17, you can't use path in context (See bug
 http://issues.apache.org/bugzilla/show_bug.cgi?id=39120)
 But you can modify the name of your context file :
 servlets#application.xml, it should work.
 
 hugo
 
 -Message d'origine-
 De : René Schade [mailto:[EMAIL PROTECTED]
 Envoyé : mardi 24 octobre 2006 10:18
 À : users@tomcat.apache.org
 Objet : Problems configuring a Context path=xx using Apache/Tomcat
 
 Hi List,
 
 
 
 I'm running Apache 2.0, Tomcat 5.5.17, jdk 1.5
 
 
 
 I'm upgrading from Apache 1.3 Tomcat 3.* jdk 1.4
 
 
 
 In my Apache log file I have the following:
 
 
 
 JkMount /manager* foo
 
 JkMount /servlets/* foo
 
 
 
 The manager application works fine, when typing the URL
 
 
 
 http://website/manager/html
 
 
 
 Everything is ok, the manager application is launched.
 
 
 
 Now I'm trying to install an application on the path
 /servlets/myapplication. The Context file looks like this:
 
 
 
 Context  reloadable=true path=/servlets/myapplication/
 docBase=${catalina.home}/home/schade/myapplication/ debug=5
 allowoverride=true
 
   Valve
 className=org.apache.catalina.valves.AccessLogValve
 
 prefix=kvisremote_by_schade. suffix=.txt
 
  pattern=common/
 
 /Context
 
 
 
 Typing a URL like http://website/servlets/myapplication/testfile.html does
 not trigger this context. I've made a similar Valve for the manager-
 application, and here every request to the manager Context is logged.
 Logging the host verifies that requests sent to
 http://website/servlets/kvisremote are sent to the host, but it does not
 seam to know which context to forward the request to.
 
 
 
 I guess it has something to do with the path-attribute. A similar solution
 worked fine on the old server...
 
 
 
 I've been struggling with this for a while now, so any kinds of
 suggestions are appreciated.
 
 
 
 Regards,
 René
 
 
 
 
 CONFIDENTIALITY:   This email (including any attachments) may contain
 confidential, proprietary and privileged information, and unauthorized
 disclosure or use is prohibited.  If you received this email in error,
 please notify the sender and delete this email from your system.  Thank
 you
 
 
 CONFIDENTIALITÉ: Ce courrier électronique (pièces jointes incluses) peut
 contenir des informations confidentielles, propriétaires et privilégiées,
 dont la divulgation ou l'utilisation non-autorisée est interdite.
 Si vous avez reçu ce courrier électronique par erreur, nous vous
 remercions de bien vouloir avertir l'expéditeur et détruire ce courrier
 électronique
 de votre système.
 Merci.
 
 
 
 -
 To start a new topic, e-mail: users@tomcat.apache.org
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]


-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Problems configuring a Context path=xx using Apache/Tomcat

[Michael Courcy]

Hi
Can you explain where you define context.xml ?
Here is a fragment of
http://tomcat.apache.org/tomcat-5.5-doc/config/context.html
path : [...] The value of this field must not be set except when 
statically defining a Context in server.xml, as it will be infered from 
the filenames used for either the .xml context file or the docBase.


Mic


René Schade a écrit :

Hi List,

 


I'm running Apache 2.0, Tomcat 5.5.17, jdk 1.5

 


I'm upgrading from Apache 1.3 Tomcat 3.* jdk 1.4

 


In my Apache log file I have the following:

 


JkMount /manager* foo

JkMount /servlets/* foo

 


The manager application works fine, when typing the URL

 

http://website/manager/html 

 


Everything is ok, the manager application is launched.

 


Now I'm trying to install an application on the path /servlets/myapplication. 
The Context file looks like this:

 


Context  reloadable=true path=/servlets/myapplication/ 
docBase=${catalina.home}/home/schade/myapplication/ debug=5 allowoverride=true

  Valve className=org.apache.catalina.valves.AccessLogValve

prefix=kvisremote_by_schade. suffix=.txt

 pattern=common/

/Context

 


Typing a URL like http://website/servlets/myapplication/testfile.html does not 
trigger this context. I've made a similar Valve for the manager-application, and here 
every request to the manager Context is logged. Logging the host verifies 
that requests sent to http://website/servlets/kvisremote are sent to the host, but it 
does not seam to know which context to forward the request to.

 


I guess it has something to do with the path-attribute. A similar solution 
worked fine on the old server...

 

I've been struggling with this for a while now, so any kinds of suggestions are appreciated. 

 


Regards,
René


  



-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Problems configuring a Context path=xx using Apache/Tomcat

[Michael Courcy]

Have a look there as well

http://issues.apache.org/bugzilla/show_bug.cgi?id=39120

René Schade a écrit :

Hi List,

 


I'm running Apache 2.0, Tomcat 5.5.17, jdk 1.5

 


I'm upgrading from Apache 1.3 Tomcat 3.* jdk 1.4

 


In my Apache log file I have the following:

 


JkMount /manager* foo

JkMount /servlets/* foo

 


The manager application works fine, when typing the URL

 

http://website/manager/html 

 


Everything is ok, the manager application is launched.

 


Now I'm trying to install an application on the path /servlets/myapplication. 
The Context file looks like this:

 


Context  reloadable=true path=/servlets/myapplication/ 
docBase=${catalina.home}/home/schade/myapplication/ debug=5 allowoverride=true

  Valve className=org.apache.catalina.valves.AccessLogValve

prefix=kvisremote_by_schade. suffix=.txt

 pattern=common/

/Context

 


Typing a URL like http://website/servlets/myapplication/testfile.html does not 
trigger this context. I've made a similar Valve for the manager-application, and here 
every request to the manager Context is logged. Logging the host verifies 
that requests sent to http://website/servlets/kvisremote are sent to the host, but it 
does not seam to know which context to forward the request to.

 


I guess it has something to do with the path-attribute. A similar solution 
worked fine on the old server...

 

I've been struggling with this for a while now, so any kinds of suggestions are appreciated. 

 


Regards,
René


  



-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Problems configuring a Context path=xx using Apache/Tomcat

[René Schade]

Hi List,

 

I'm running Apache 2.0, Tomcat 5.5.17, jdk 1.5

 

I'm upgrading from Apache 1.3 Tomcat 3.* jdk 1.4

 

In my Apache log file I have the following:

 

JkMount /manager* foo

JkMount /servlets/* foo

 

The manager application works fine, when typing the URL

 

http://website/manager/html 

 

Everything is ok, the manager application is launched.

 

Now I'm trying to install an application on the path /servlets/myapplication. 
The Context file looks like this:

 

Context  reloadable=true path=/servlets/myapplication/ 
docBase=${catalina.home}/home/schade/myapplication/ debug=5 
allowoverride=true

  Valve className=org.apache.catalina.valves.AccessLogValve

prefix=kvisremote_by_schade. suffix=.txt

 pattern=common/

/Context

 

Typing a URL like http://website/servlets/myapplication/testfile.html does not 
trigger this context. I've made a similar Valve for the manager-application, 
and here every request to the manager Context is logged. Logging the host 
verifies that requests sent to http://website/servlets/kvisremote are sent to 
the host, but it does not seam to know which context to forward the request to.

 

I guess it has something to do with the path-attribute. A similar solution 
worked fine on the old server...

 

I've been struggling with this for a while now, so any kinds of suggestions are 
appreciated. 

 

Regards,
René

RE : Problems configuring a Context path=xx using Apache/Tomcat

[LASSIEGE Hugo]

In tomcat 5.5.17, you can't use path in context (See bug 
http://issues.apache.org/bugzilla/show_bug.cgi?id=39120)
But you can modify the name of your context file : servlets#application.xml, it 
should work.

hugo

-Message d'origine-
De : René Schade [mailto:[EMAIL PROTECTED] 
Envoyé : mardi 24 octobre 2006 10:18
À : users@tomcat.apache.org
Objet : Problems configuring a Context path=xx using Apache/Tomcat

Hi List,

 

I'm running Apache 2.0, Tomcat 5.5.17, jdk 1.5

 

I'm upgrading from Apache 1.3 Tomcat 3.* jdk 1.4

 

In my Apache log file I have the following:

 

JkMount /manager* foo

JkMount /servlets/* foo

 

The manager application works fine, when typing the URL

 

http://website/manager/html 

 

Everything is ok, the manager application is launched.

 

Now I'm trying to install an application on the path /servlets/myapplication. 
The Context file looks like this:

 

Context  reloadable=true path=/servlets/myapplication/ 
docBase=${catalina.home}/home/schade/myapplication/ debug=5 
allowoverride=true

  Valve className=org.apache.catalina.valves.AccessLogValve

prefix=kvisremote_by_schade. suffix=.txt

 pattern=common/

/Context

 

Typing a URL like http://website/servlets/myapplication/testfile.html does not 
trigger this context. I've made a similar Valve for the manager-application, 
and here every request to the manager Context is logged. Logging the host 
verifies that requests sent to http://website/servlets/kvisremote are sent to 
the host, but it does not seam to know which context to forward the request to.

 

I guess it has something to do with the path-attribute. A similar solution 
worked fine on the old server...

 

I've been struggling with this for a while now, so any kinds of suggestions are 
appreciated. 

 

Regards,
René




CONFIDENTIALITY:   This email (including any attachments) may contain
confidential, proprietary and privileged information, and unauthorized
disclosure or use is prohibited.  If you received this email in error,
please notify the sender and delete this email from your system.  Thank you


CONFIDENTIALITÉ: Ce courrier électronique (pièces jointes incluses) peut 
contenir des informations confidentielles, propriétaires et privilégiées,
dont la divulgation ou l'utilisation non-autorisée est interdite.
Si vous avez reçu ce courrier électronique par erreur, nous vous remercions de 
bien vouloir avertir l'expéditeur et détruire ce courrier électronique
de votre système.
Merci.



-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]