On 10/05/2012 13:55, Miguel Gonzalez wrote:
> I usually prefer to have software packaged because I can get software
> security updates
I'm not sure that this is a good strategy for Tomcat installations.
Some distro's are very slow about updating their packages.
p
--
[key:62590808]
signat
> From: Miguel Gonzalez [mailto:miguel_3_gonza...@yahoo.es]
> Subject: Re: tomcat pausing and process killed
> Do you suggest using a rpm (I'm running Centos 5.2)
Definitely not. If you use a 3rd-party repackaged version of Tomcat, you'll
need to get support from that 3r
Asunto: Re: tomcat pausing and process killed
Miguel,
just a couple of general remarks.
Tomcat is an open-source project, developed and supported by volunteers.
These volunteers do not have all the time in the world, so they tend to focus
first on the current Tomcat version (7.x), a bit less on th
Miguel,
just a couple of general remarks.
Tomcat is an open-source project, developed and supported by volunteers.
These volunteers do not have all the time in the world, so they tend to focus first on the
current Tomcat version (7.x), a bit less on the previous version (6.x), and much less on
2012/5/9 Miguel Gonzalez :
>
> I have tomcat 5.5.27 and jdk 1.5.0_17
> (..)
>
> May 8, 2012 12:03:48 PM org.apache.tomcat.util.http.Parameters
> processParameters
> WARNING: Parameters: Character decoding failed. Parameter skipped.
>
>(...)
>
> I will check it, however I don't see in the access
On 09/05/2012 21:47, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Miguel,
On 5/9/12 11:29 AM, Miguel Gonzalez wrote:
I will check it, however I don't see in the access logs something
relevant. Any string I can check
Anything with %-codes that are invalid. You'll ha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Miguel,
On 5/9/12 11:29 AM, Miguel Gonzalez wrote:
> I will check it, however I don't see in the access logs something
> relevant. Any string I can check
Anything with %-codes that are invalid. You'll have to write your own
regular parser or regex t
>Maybe
an attacker is trying a series of URLs in a row, and finally they
manage one that finds a weakness in your very very old Tomcat.
>> I really don't know what to enable to get to know what is causing Tomcat to
>> crash
>>
>Enabling the AccessLog Valve may enable you to see the bad reque
Hi.
Miguel Gonzalez wrote:
Dear all,
I have tomcat 5.5.27 and jdk 1.5.0_17
That's all quite old,and you should probably upgrade.
As someone suggested to the list I enabled HeapDumpOnOutOfMemoryError. I have
javamelody running to monitor tomcat. The only thing that I see is that memory
