I have Tomcat 7.0.26 running on Window7 Pro. I also have Tomcat 7.0.40
running on a Windows 7 Home Premium. Both have the same website.
(Obviously, I'm doing some testing.)
In the website, a user logs on and the user ID is kept in the session.
In one of the JSP pages I have some JavaScrip
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jane,
On 6/13/13 6:44 PM, Jane Muse wrote:
> I'm using the standard implementation of Realm. Here's the code
>
> //Validate passwords try { if (oldTomcatPassword != null &&
> !"".equals(oldTomcatPassword.trim())) { TomcatConfig tconf =
> TomcatConf
Hello,
I do not think destination NAT is good solution because it works on TCP
layer and knows nothing about domain names and URLs (both are application
level (http) knowledge). So you would need to use separate IP/port for
that and in case you have it you can bind tomcat there directly) So
appl
I'm using the standard implementation of Realm. Here's the code
//Validate passwords
try {
if (oldTomcatPassword != null &&
!"".equals(oldTomcatPassword.trim()))
{
TomcatConfig tconf = TomcatConfig.get
Hello,
What is "request for application"? How would any software know this request
is for abc app?
You should use different URLs (servlet contexts) or different domain names.
Then you may install nginx or apache or squid or something else that would
forward your requests to the following tomcats.
you can swap out one jar for another
Ant has no idea which container it is communicating with unless you tell it
catalina.jar is tied to the Servlet Spec so
you cannot change catalina unless you change the accompanying Servlet Spec
so you've already done that why not write a Quick and Dirty ant
for IP Redirecting and or automatic Network Address Translations (e.g. Port 80
redirects to Port 81)
you will need a proxy server
please contact supp...@cisco.com
for product and service options
Viel Gluck
Martin
__
Verzicht und Vertraulichke
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Steve,
On 6/13/13 5:27 PM, Steve Nickels wrote:
>>> I figured out the problem. The error was due to my system
>>> rebasing the libeay32.dll library from its desired base address
>>> of 0xFB0. According to OpenSSL documents, this is supposed
>>>
> > I figured out the problem. The error was due to my system rebasing the
> > libeay32.dll library from its desired base address of 0xFB0.
> > According to OpenSSL documents, this is supposed to generate a
> > specific error message of
> > FIPS_R_FINGERPRINT_DOES_NOT_MATCH_NONPIC_RELATED, but
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chuck,
On 6/13/13 4:40 PM, Caldarale, Charles R wrote:
>> From: Jane Muse [mailto:jm...@rocketsoftware.com] Subject: RE:
>> Class cast exception when starting tomcat 7.0.1
>
>> I had catalina.jar in WEB-INF/lib.
>
> Very, very bad move.
>
>> It's
> From: Jane Muse [mailto:jm...@rocketsoftware.com]
> Subject: RE: Class cast exception when starting tomcat 7.0.1
> I had catalina.jar in WEB-INF/lib.
Very, very bad move.
> It's needed because we have an implementation of Realm to store an
> encrypted tomcat password users enter in the webap
I had catalina.jar in WEB-INF/lib. It's needed because we have an
implementation of Realm to store an encrypted tomcat password users enter in
the webapp. If I remove it and add the catalina.jar from tomcat_home/lib to
the classpath, I have to change the signature from
org.apache.catalina.real
> From: Christopher Schultz [mailto:ch...@christopherschultz.net]
> Subject: Re: forward request by changing the port in request url
> > Once you have a ROOT webapp, you can deploy the standard URL
> > rewrite filter therein to send the request anywhere you want:
> > http://tuckey.org/urlrewrite/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chuck,
On 6/13/13 2:23 PM, Caldarale, Charles R wrote:
>> From: Anil Goyal -X (anigoyal - Aricent Technologies at Cisco)
>> [mailto:anigo...@cisco.com] Subject: forward request by changing
>> the port in request url
>
>> i have application abc.war
> From: Anil Goyal -X (anigoyal - Aricent Technologies at Cisco)
> [mailto:anigo...@cisco.com]
> Subject: forward request by changing the port in request url
> i have application abc.war deployed in webapps_new service which is running
> on port 8081. This application is not there in webapps.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Anil,
On 6/13/13 2:00 PM, Anil Goyal -X (anigoyal - Aricent Technologies at
Cisco) wrote:
> i have two service running under tomcat. One service is default
> i.e. catalina on port 8080 and 8443 second service is catalina_new
> on port 8081 and 8444.
> From: Christopher Schultz [mailto:ch...@christopherschultz.net]
> Subject: Re: Class cast exception when starting tomcat 7.0.1
> I'll admit it's not clear from the version number which versions are
> beta, released, etc. You have to look at the ChangeLog:
It's easier to look in the archives if
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Steve,
On 6/13/13 1:57 PM, Steve Nickels wrote:
> I figured out the problem. The error was due to my system rebasing
> the libeay32.dll library from its desired base address of
> 0xFB0. According to OpenSSL documents, this is supposed to
> gene
> From: Jane Muse [mailto:jm...@rocketsoftware.com]
> Subject: RE: Class cast exception when starting tomcat 7.0.1
> In the archives I thought the only unreleased versions would be specified
> "beta". Please let me know if this is not the case.
No, the description of alpha, beta, and stable as
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jane,
On 6/13/13 12:38 PM, Jane Muse wrote:
> In the archives I thought the only unreleased versions would be
> specified "beta". Please let me know if this is not the case.
I'll admit it's not clear from the version number which versions are
beta,
i have two service running under tomcat. One service is default i.e. catalina
on port 8080 and 8443
second service is catalina_new on port 8081 and 8444.
i have application abc.war deployed in webapps_new service which is running on
port 8081. This application is not there in webapps.
i want if
I figured out the problem. The error was due to my system rebasing the
libeay32.dll library from its desired base address of 0xFB0. According to
OpenSSL documents, this is supposed to generate a specific error message of
FIPS_R_FINGERPRINT_DOES_NOT_MATCH_NONPIC_RELATED, but because I wasn't
In the archives I thought the only unreleased versions would be specified
"beta". Please let me know if this is not the case.
Thanks.
-Original Message-
From: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com]
Sent: Thursday, June 13, 2013 9:25 AM
To: Tomcat Users List
Subject: RE
> From: Jane Muse [mailto:jm...@rocketsoftware.com]
> Subject: RE: Class cast exception when starting tomcat 7.0.1
> Just saying, I wasn't using a 3 year unreleased version. Maybe a 3 year
> version, yes. Here's my original email:
> "I'm getting a class cast exception when starting up tomcat 7.
Just saying, I wasn't using a 3 year unreleased version. Maybe a 3 year
version, yes. Here's my original email:
"I'm getting a class cast exception when starting up tomcat 7.0.1. I've
migrated from 6.0.18 to 7.0.1. I got the same error when migrating directly to
7.0.4. The error is:"
-Orig
> From: Jane Muse [mailto:jm...@rocketsoftware.com]
> Subject: RE: Class cast exception when starting tomcat 7.0.1
> Who says I was using a 3 year old unreleased level?
Your subject line.
> I tried an easier migration - Tomcat 6.0.18 to 7.0.10.
The "logic" of that completely escapes me.
- Ch
> Who says I was using a 3 year old unreleased level?
You did when you set the subject line to "Class cast exception when
starting tomcat 7.0.1" Charles was hinting that 7.0.1 wasn't released
Chris
-
To unsubscribe, e-mail: user
Who says I was using a 3 year old unreleased level? I had started out with
Tomcat 7.0.41 and when I got the class cast exception, I tried an easier
migration - Tomcat 6.0.18 to 7.0.10. I downloaded 7.0.10 from the archives. As
I said, the problem was due to using catalina.jar in my WEB-INF lib,
> >> I notice that Tomcat distributes openssl.exe and not openssl.dll (or
> >> similar). Are you building openssl.exe or openssl.dll when you build
> >> OpenSSL?
> >
> > Building OpenSSL on Windows results in three distributable files:
> > libeay32.dll, ssleay32.dll, and openssl.exe. I copy the fir
Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chirag,
On 6/13/13 12:59 AM, Chirag Dewan wrote:
A little more digging in and I found out that only with SSL,tomcat
is creating a large number of sessions. I can see in the logs for
HTTP:
INFO: SessionListener:
sessio
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chirag,
On 6/13/13 12:59 AM, Chirag Dewan wrote:
> A little more digging in and I found out that only with SSL,tomcat
> is creating a large number of sessions. I can see in the logs for
> HTTP:
>
> INFO: SessionListener:
> sessionDestroyed('2E8DE0
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Steve,
On 6/12/13 6:54 PM, Steve Nickels wrote:
>>> I'm fairly confident that the OpenSSL library I'm using is
>>> valid and uncorrupted (I've used a couple different copies: an
>>> existing set of binaries being used successfully in another
>>> pro
Christopher
Thx for response, I will inform guys from business about what You have
written, and let them consider it
Regards
Jakub
On Wed, Jun 12, 2013 at 4:10 PM, Christopher Schultz <
ch...@christopherschultz.net> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Jakob,
>
> On 6/
33 matches
Mail list logo
