You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Doron Tsur <qb...@gmail.com> on 2012/04/10 14:11:04 UTC
Re: Non page pool issue will not go away, please help.
Switching to Blocking IO from Non Blocking IO seems to have solved the
issue. I don't know why, does anybody have ideas?
On Sat, Mar 10, 2012 at 2:57 AM, Doron Tsur <qb...@gmail.com> wrote:
> This customer has two cluster nodes. This helps the server to be more
> available. They are identical in any way and both have this issue. The
> server is a simple HTTP put get server. It uses some SSL and zipping but
> nothing fancy. Since the configuration are always the same nothing is
> special in the TCP layer. regarding TCP connection state I wouldn't know, I
> let tomcat do most of the job. I kick in to action when objects are formed,
> way after TCP.
>
> No direct memory either.
> No native code.
> It's java, tomcat and HTTP mostly.
>
>
> Anything strange in the output of "netstat -an"?
>> To many connections of some kind? Unusual TCP connection states?
>>
>> Regards,
>>
>> Rainer
>>
>
>
Re: Non page pool issue will not go away, please help.
Posted by Pid <pi...@pidster.com>.
On 10/04/2012 23:21, Doron Tsur wrote:
> Another conclusion to share here is that when running on windows 2003
> enterprise R2 (the one we tested, but could be other windows OS) killing
> tomcat will not return the non page pool back to the OS. Even on systems
> that it isn't leaking. Usually there is no need for so much memory
> including our system, but this should be checked.
You should use a tool like VisualVM or JConsole to inspect the running
JVM and try to identify if one of the memory areas of the JVM increases
in parallel with the leak you're seeing from the OS view.
p
> PID- thanks for the tip.
>
>
> On Tue, Apr 10, 2012 at 5:31 PM, Pid <pi...@pidster.com> wrote:
>
>> On 10/04/2012 13:11, Doron Tsur wrote:
>>> Switching to Blocking IO from Non Blocking IO seems to have solved the
>>> issue. I don't know why, does anybody have ideas?
>>
>> Try the latest version of Tomcat. There were patches to the Connector
>> code in versions subsequent to 7.0.23.
>>
>>
>> p
>>
>>
>> --
>>
>> [key:62590808]
>>
>>
>
--
[key:62590808]
Re: Non page pool issue will not go away, please help.
Posted by Doron Tsur <qb...@gmail.com>.
Another conclusion to share here is that when running on windows 2003
enterprise R2 (the one we tested, but could be other windows OS) killing
tomcat will not return the non page pool back to the OS. Even on systems
that it isn't leaking. Usually there is no need for so much memory
including our system, but this should be checked.
PID- thanks for the tip.
On Tue, Apr 10, 2012 at 5:31 PM, Pid <pi...@pidster.com> wrote:
> On 10/04/2012 13:11, Doron Tsur wrote:
> > Switching to Blocking IO from Non Blocking IO seems to have solved the
> > issue. I don't know why, does anybody have ideas?
>
> Try the latest version of Tomcat. There were patches to the Connector
> code in versions subsequent to 7.0.23.
>
>
> p
>
>
> --
>
> [key:62590808]
>
>
Re: Non page pool issue will not go away, please help.
Posted by Pid <pi...@pidster.com>.
On 10/04/2012 13:11, Doron Tsur wrote:
> Switching to Blocking IO from Non Blocking IO seems to have solved the
> issue. I don't know why, does anybody have ideas?
Try the latest version of Tomcat. There were patches to the Connector
code in versions subsequent to 7.0.23.
p
--
[key:62590808]