On Mon Mar 31 21:13:25 CEST 2008 Tomcat Users List
wrote:
On Mon, Mar 31, 2008 at 3:38 AM, Ronald Klop <[EMAIL PROTECTED]> wrote:
>
> See my previous mail about send/receive buffers filling because Ack wasn't
> read by FastAsyncSender.
> The option waitForAck="true" did the trick for me. But fo
David Rees wrote:
On Mon, Mar 31, 2008 at 4:48 PM, Filip Hanik - Dev Lists
<[EMAIL PROTECTED]> wrote:
David Rees wrote:
> One problem I've intermittently had with clustering is that after a
> Tomcat restart (we shut down one node and it immediately restarts,
> generally within 30 seconds),
On Mon, Mar 31, 2008 at 5:06 PM, Filip Hanik - Dev Lists
<[EMAIL PROTECTED]> wrote:
> David Rees wrote:
> > I've got a cluster in my test lab with the following configuration on
> 5.5.26:
> >
> >
> >
> > Looking at /manager/jmxproxy?qry=*:* I see the same thing on both
> > nodes (extra info
David Rees wrote:
On Mon, Mar 31, 2008 at 12:52 PM, Rainer Jung <[EMAIL PROTECTED]> wrote:
Ronald Klop schrieb:
See my previous mail about send/receive buffers filling because Ack
> wasn't read by FastAsyncSender.
> The option waitForAck="true" did the trick for me. But for
>
On Mon, Mar 31, 2008 at 4:48 PM, Filip Hanik - Dev Lists
<[EMAIL PROTECTED]> wrote:
> David Rees wrote:
> > One problem I've intermittently had with clustering is that after a
> > Tomcat restart (we shut down one node and it immediately restarts,
> > generally within 30 seconds), they two nodes
On Mon, Mar 31, 2008 at 12:52 PM, Rainer Jung <[EMAIL PROTECTED]> wrote:
> Ronald Klop schrieb:
> > See my previous mail about send/receive buffers filling because Ack
> > wasn't read by FastAsyncSender.
> > The option waitForAck="true" did the trick for me. But for
> > FastAsyncSender you shoul
David Rees wrote:
On Mon, Mar 31, 2008 at 12:49 PM, Rainer Jung <[EMAIL PROTECTED]> wrote:
First to make sure: counting objects in general only makes sense after a
full GC. Otherwise the heap dump will contain garbage too.
Yes, I made sure the objects I was looking at had a valid GC
On Mon, Mar 31, 2008 at 12:49 PM, Rainer Jung <[EMAIL PROTECTED]> wrote:
> First to make sure: counting objects in general only makes sense after a
> full GC. Otherwise the heap dump will contain garbage too.
Yes, I made sure the objects I was looking at had a valid GC
reference. They really wer
David Rees wrote:
On Mon, Mar 31, 2008 at 3:38 AM, Ronald Klop <[EMAIL PROTECTED]> wrote:
See my previous mail about send/receive buffers filling because Ack wasn't
read by FastAsyncSender.
The option waitForAck="true" did the trick for me. But for FastAsyncSender
you should set sendAck="fal
David Rees schrieb:
On Mon, Mar 31, 2008 at 3:38 AM, Ronald Klop <[EMAIL PROTECTED]> wrote:
See my previous mail about send/receive buffers filling because Ack wasn't
read by FastAsyncSender.
The option waitForAck="true" did the trick for me. But for FastAsyncSender
you should set sendAck="fals
Ronald Klop schrieb:
See my previous mail about send/receive buffers filling because Ack
wasn't read by FastAsyncSender.
The option waitForAck="true" did the trick for me. But for
FastAsyncSender you should set sendAck="false" on the receiving side.
Ronald.
Hi Ronald,
I saw your previous cl
David Rees schrieb:
On Sun, Mar 30, 2008 at 2:14 AM, David Rees <[EMAIL PROTECTED]> wrote:
From my understanding of the clustering software, it appears that
Tomcat is trying to send messages to the other Tomcat but it isn't
receiving them? Shouldn't it drop membership and give up? I suspect
On Mon, Mar 31, 2008 at 3:38 AM, Ronald Klop <[EMAIL PROTECTED]> wrote:
>
> See my previous mail about send/receive buffers filling because Ack wasn't
> read by FastAsyncSender.
> The option waitForAck="true" did the trick for me. But for FastAsyncSender
> you should set sendAck="false" on the rec
See my previous mail about send/receive buffers filling because Ack wasn't read
by FastAsyncSender.
The option waitForAck="true" did the trick for me. But for FastAsyncSender you should set
sendAck="false" on the receiving side.
Ronald.
On Mon Mar 31 02:07:51 CEST 2008 Tomcat Users List
wrot
I've had a problem with send/receive buffers filling up because
FastAsyncSocketSender doesn't read the Ack from the other cluster node.
Does netstat -n give you full buffers on the cluster tcp connections (port 8015
I think)?
This might cause Tomcat to stack up a lot of session data in its inter
On Sun, Mar 30, 2008 at 2:14 AM, David Rees <[EMAIL PROTECTED]> wrote:
> From my understanding of the clustering software, it appears that
> Tomcat is trying to send messages to the other Tomcat but it isn't
> receiving them? Shouldn't it drop membership and give up? I suspect
> that some recon
On Sun, Mar 30, 2008 at 1:49 AM, David Rees <[EMAIL PROTECTED]> wrote:
> I have a 2-Tomcat 5.5.26 cluster running 64bit Java which leaks
> ClusterData and LinkObject objects.
>
> I have a hprof dump which shows over 600k of each of those classes.
> Analyzing them with a profiler reveals an endle
I have a 2-Tomcat 5.5.26 cluster running 64bit Java which leaks
ClusterData and LinkObject objects.
I have a hprof dump which shows over 600k of each of those classes.
Analyzing them with a profiler reveals an endless loop of
LinkObject.next references through all 600k of them. There were about
60
18 matches
Mail list logo
