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
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 sy
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
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 wrote:
> This customer has two cluster nodes. This helps the server to be more
> available. They are identical in any way and both
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
On 09.03.2012 18:19, Doron Tsur wrote:
Hi Guys,
A while back I've addressed you guys with the non paged pool issue. Most
people advised upgrading the java/tomcat. We did just that and the issue is
still happening. We are investigating a lot of directions of memory leaks
in the environment with M
NO JDBC driver
On Fri, Mar 9, 2012 at 9:28 PM, Christopher Schultz <
ch...@christopherschultz.net> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Konstantin,
>
> On 3/9/12 2:21 PM, Konstantin Kolinko wrote:
> > 2. There are database drivers. What database drivers are you
> > using?
On Fri, Mar 9, 2012 at 9:16 PM, Christopher Schultz <
ch...@christopherschultz.net> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Doron,
>
> On 3/9/12 12:19 PM, Doron Tsur wrote:
> > Tomcat: 7 latest Java: 1.6.25 OS: Windows Server 2003 R2 SP2
>
> qballer: sorry. Java 1.6.0_25 t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Konstantin,
On 3/9/12 2:21 PM, Konstantin Kolinko wrote:
> 2. There are database drivers. What database drivers are you
> using?
Good thought: there's no reason to assume that the connectors are
leaking this stuff.
Doron, if you are using a JDBC dri
2012/3/9 Doron Tsur :
> Hi Guys,
>
> A while back I've addressed you guys with the non paged pool issue. Most
> people advised upgrading the java/tomcat. We did just that and the issue is
> still happening. We are investigating a lot of directions of memory leaks
> in the environment with Microsoft
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Doron,
On 3/9/12 12:19 PM, Doron Tsur wrote:
> Tomcat: 7 latest Java: 1.6.25 OS: Windows Server 2003 R2 SP2
1. What specific version of Tomcat 7?
2. 1.6.25 is not a version of Java that I know of. Real version number
and vendor, please?
> This i
Hi Guys,
A while back I've addressed you guys with the non paged pool issue. Most
people advised upgrading the java/tomcat. We did just that and the issue is
still happening. We are investigating a lot of directions of memory leaks
in the environment with Microsoft. I wanted to address you guys, t
12 matches
Mail list logo
