> From: charlesk40 [mailto:charles...@yahoo.com]
> Subject: Tomcat 7 sometime returns wrong IP address with
> request.getRemoteAddr()
> box1 makes a request to Tomcat7 server but the request.getRemoteAddr()
> returns the IP address of box2 (or box n). This problem doesn't happen
> all the time
Hi,
We have just upgraded the Tomcat from 6 to 7.
After the upgrade, we have noticed some IP address returned from
request.getRemoteAddr() is not the as expected.
In more detail, we have list of client boxes making a request.
Lets say, box1, box2,.. box n.
box1 makes a request to Tomcat7 server
You are right. I meant to say Tomcat 7
On Wed, Sep 21, 2011 at 2:18 PM, Caldarale, Charles R <
chuck.caldar...@unisys.com> wrote:
> > From: Narahari 'n' Savitha [mailto:savith...@gmail.com]
> > Subject: Re: websphere 7.0 JAXWS webservice deployed in tomcat 6.0.32 not
> working
>
> > Tomcat7 can
2011/9/21 BARRON, HAROLD H CTR DISA EE :
>
> Apache Tomcat AJP Protocol Security Bypass and Information Disclosure
> Vulnerability - (CVE-2011-3190):
>
1. Mitigation options are listed here:
http://tomcat.apache.org/security-5.html
http://tomcat.apache.org/security-6.html
Both 5.5 and 6.0 have a
On 21/09/2011 16:15, Wilde, Bruce R. wrote:
> When is Tomcat version 6.0.34 expected to be released?
There are no fixed release dates, but Tomcat 6 releases about 4 times
per year.
p
signature.asc
Description: OpenPGP digital signature
On 21/09/2011 15:54, Michael-O wrote:
> Christopher,
>
> Christopher Schultz schrieb:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Mike,
>>
>> On 9/21/2011 3:52 AM, 1983-01...@gmx.net wrote:
>>> I have removed the MemoryRealm from my server.xml in Tomcat 6.0.33
>>> and noticed that th
Classification: UNCLASSIFIED
Caveats: NONE
Team,
Since Tomcat 5.5.34 has not been made available for the current
Apache Tomcat Injection Vulnerability=20
(IAVA 2011-B-0114), is there a workaround for this problem until the
patch is out. This software is being used on a Windows 2003 Se
On 21/09/2011 19:18, Caldarale, Charles R wrote:
>> From: Narahari 'n' Savitha [mailto:savith...@gmail.com]
>> Subject: Re: websphere 7.0 JAXWS webservice deployed in tomcat 6.0.32 not
>> working
>
>> Tomcat7 can handle Servlet3 based classes.
>
> But Tomcat 6 can't, so perhaps you should retry
> From: Narahari 'n' Savitha [mailto:savith...@gmail.com]
> Subject: Re: websphere 7.0 JAXWS webservice deployed in tomcat 6.0.32 not
> working
> Tomcat7 can handle Servlet3 based classes.
But Tomcat 6 can't, so perhaps you should retry using Tomcat 7.
- Chuck
THIS COMMUNICATION MAY CONTAIN
Thank You Chris for your time and help.
I understand that I need WebServices Engine like AXIS2 or METRO or Apache
CXF.
Here is the deal.
Websphere7 uses AXIS2 as the WebServices engine.
I have my Webservices class with Annotation of @WebService. This is then
compiled to WEB-INF\classes folder
When is Tomcat version 6.0.34 expected to be released?
Bruce
Christopher,
Christopher Schultz schrieb:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mike,
On 9/21/2011 3:52 AM, 1983-01...@gmx.net wrote:
I have removed the MemoryRealm from my server.xml in Tomcat 6.0.33
and noticed that the StandardEngine creates a JAASRealm [1]:
21.09.2011 09:14:58 or
Chris,
I do have one other webapp deployed alongside, but neither of them ever gets
reloaded. We always do a full stop/start of tomcat to roll out new builds
(which is about the only time we ever stop these apps).
There's absolutely no performance penalty that I'm aware of. It was just
the yet-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
André,
On 9/20/2011 4:45 PM, André Warnier wrote:
> Christopher Schultz wrote:
>> You can't do this unless all your JSPs are at the same directory
>> level, say, in "myapp".
>
> Why not ? Suppose all stylesheets are in
> (tomcat_dir)/webapps/myapp/c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Shanti,
On 9/21/2011 1:39 AM, Yajnik, Shanti wrote:
> Thanks Chris. Do you know when 6.0.34 version of Tomcat will be
> available for download?
Note that there is a simple workaround with affected versions: use
mod_jk's "secret" setting on all your w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Shanti,
On 9/21/2011 1:39 AM, Yajnik, Shanti wrote:
> Thanks Chris. Do you know when 6.0.34 version of Tomcat will be
> available for download?
Nope. It will ship whenever the devs decide it's time for another release.
- -chris
-BEGIN PGP SIGNAT
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mike,
On 9/21/2011 3:52 AM, 1983-01...@gmx.net wrote:
> I have removed the MemoryRealm from my server.xml in Tomcat 6.0.33
> and noticed that the StandardEngine creates a JAASRealm [1]:
> 21.09.2011 09:14:58 org.apache.catalina.realm.JAASRealm
> set
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Narahari,
On 9/20/2011 11:15 PM, Narahari 'n' Savitha wrote:
> I have a JAXWS webservice developed in WebSphere 7.0. It is
> working there. The stack in Websphere is Axis2.0
>
> I wrote a POJO Java class, annotated with the @WebService
> annotation
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dan,
On 9/20/2011 4:47 PM, Dan Checkoway wrote:
> Thanks Chris. Those threads are *never* idle in this app. :-)
> They're still getting recycled periodically, it looks like, despite
> lack of idle time.
Hmm, that does sound weird. Do you have other
On 21/09/2011 01:03, Manger, James H wrote:
>> On 20/09/2011 08:31, Manger, James H wrote:
>>> The manager and host-manager apps included with Tomcat 7.0.21 are both:
>>> * configured to use BASIC authentication; and
>>> * configured with a custom error page for 401 (unauthenticated) error codes.
>
Hi folks,
I have removed the MemoryRealm from my server.xml in Tomcat 6.0.33 and noticed
that the StandardEngine creates a JAASRealm [1]:
21.09.2011 09:14:58 org.apache.catalina.realm.JAASRealm setContainer
INFO: Set JAAS app name Catalina
What is the reasoning behind this?
I assume that any app
21 matches
Mail list logo
