A cluster question
Hello,
I have a session bean that changes its state as pages call methods on that bean. I
want this bean to be replictated to other cluster members but it seems like it gets
replicated only once, straight after it is created.
Is there any other way to force replication apart from calling
session.setAttribute(name, bean) ? I have tried useDirtyFlag true and false - no luck.
The application is distributed and all other things do get replicated.
Regards,
Vlad
This is a little test case for my problem:
test.jsp:
-
jsp:useBean id=mybean class=TestBean scope=session /
%
out.print(mybean.a());
%
TestBean.java
-
import org.apache.log4j.Logger;
import java.io.Serializable;
import java.io.IOException;
import java.util.Random;
public class TestBean implements Serializable{
private static Logger logger = Logger.getLogger(TestBean.class);
private long m_a = 0;
private Random rnd = new Random(System.currentTimeMillis());
public long a() {
m_a = rnd.nextLong();
return m_a;
}
private void writeObject(java.io.ObjectOutputStream out) throws IOException {
//logger.debug(Serialized);
System.out.println(Serialized);
out.defaultWriteObject();
}
private void readObject(java.io.ObjectInputStream in) throws IOException,
ClassNotFoundException {
in.defaultReadObject();
//logger.debug(Deserialized);
System.out.println(Deserialized);
}
}
The information contained in this email message may be confidential. If you are not
the intended recipient, any use, interference with, disclosure or copying of this
material is unauthorised and prohibited. Although this message and any attachments are
believed to be free of viruses, no responsibility is accepted by Informa for any loss
or damage arising in any way from receipt or use thereof. Messages to and from the
company are monitored for operational reasons and in accordance with lawful business
practices.
If you have received this message in error, please notify us by return and delete the
message and any attachments. Further enquiries/returns can be sent to [EMAIL
PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: A cluster question
Thanks a lot Filip, SimpleTcpReplicationManager does indeed work the way i need it!
Vlad
-Original Message-
From: Filip Hanik (lists) [mailto:[EMAIL PROTECTED]
Sent: Wed 5/26/2004 6:43 PM
To: Tomcat Users List
Cc:
Subject:RE: A cluster question
Is there any other way to force replication apart from calling
session.setAttribute(name, bean)
yes, there is, but not using the DeltaManager,
instead use SimpleTcpReplicationMananger and set useDirtyFlag=false
the useDirtyFlag is ignored on the delta manager, since the delta manager
only replicates deltas.
filip
-Original Message-
From: Ilyschenko, Vlad [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 26, 2004 9:32 AM
To: Tomcat Users List
Subject: A cluster question
Hello,
I have a session bean that changes its state as pages call methods on that
bean. I want this bean to be replictated to other cluster members but it
seems like it gets replicated only once, straight after it is created.
Is there any other way to force replication apart from calling
session.setAttribute(name, bean) ? I have tried useDirtyFlag true and
false - no luck.
The application is distributed and all other things do get replicated.
Regards,
Vlad
This is a little test case for my problem:
test.jsp:
-
jsp:useBean id=mybean class=TestBean scope=session /
%
out.print(mybean.a());
%
TestBean.java
-
import org.apache.log4j.Logger;
import java.io.Serializable;
import java.io.IOException;
import java.util.Random;
public class TestBean implements Serializable{
private static Logger logger = Logger.getLogger(TestBean.class);
private long m_a = 0;
private Random rnd = new Random(System.currentTimeMillis());
public long a() {
m_a = rnd.nextLong();
return m_a;
}
private void writeObject(java.io.ObjectOutputStream out) throws
IOException {
//logger.debug(Serialized);
System.out.println(Serialized);
out.defaultWriteObject();
}
private void readObject(java.io.ObjectInputStream in) throws
IOException, ClassNotFoundException {
in.defaultReadObject();
//logger.debug(Deserialized);
System.out.println(Deserialized);
}
}
The information contained in this email message may be confidential. If you
are not the intended recipient, any use, interference with, disclosure or
copying of this material is unauthorised and prohibited. Although this
message and any attachments are believed to be free of viruses, no
responsibility is accepted by Informa for any loss or damage arising in any
way from receipt or use thereof. Messages to and from the company are
monitored for operational reasons and in accordance with lawful business
practices.
If you have received this message in error, please notify us by return and
delete the message and any attachments. Further enquiries/returns can be
sent to [EMAIL PROTECTED]
---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.676 / Virus Database: 438 - Release Date: 5/3/2004
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.676 / Virus Database: 438 - Release Date: 5/3/2004
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: A cluster question
hi Filip,
sorry to say but i've encountered another problem. Although
SimpleTcpReplicationManager does replicate my bean ok it doesnt seem to maintain the
session correctly.
To test the cluster im using round-robin DNS record. Whenever the client browser is
forced to switch from one tomcat instance to another a new session is getting created
and the old session is lost. I must say that the browser does maintain cookies ok but
amazingly JSESSIONID cookie value does not match session id of the newly created
session.
This only happens to SimpleTcpReplicationManager, DelataManager maintains sessions ok.
The version of tomcat i'm testing on is 5.0.19
Regards,
Vlad
-Original Message-
From: Filip Hanik (lists) [mailto:[EMAIL PROTECTED]
Sent: Wed 26/05/2004 22:12
To: Tomcat Users List
Cc:
Subject: RE: A cluster question
anytime, glad I could help!
Filip
-Original Message-
From: Ilyschenko, Vlad [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 26, 2004 2:56 PM
To: Tomcat Users List
Subject: RE: A cluster question
Thanks a lot Filip, SimpleTcpReplicationManager does indeed work the way i
need it!
Vlad
-Original Message-
From: Filip Hanik (lists) [mailto:[EMAIL PROTECTED]
Sent: Wed 5/26/2004 6:43 PM
To: Tomcat Users List
Cc:
Subject:RE: A cluster question
Is there any other way to force replication apart from calling
session.setAttribute(name, bean)
yes, there is, but not using the DeltaManager,
instead use SimpleTcpReplicationMananger and set useDirtyFlag=false
the useDirtyFlag is ignored on the delta manager, since the delta manager
only replicates deltas.
filip
-Original Message-
From: Ilyschenko, Vlad [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 26, 2004 9:32 AM
To: Tomcat Users List
Subject: A cluster question
Hello,
I have a session bean that changes its state as pages call methods on that
bean. I want this bean to be replictated to other cluster members but it
seems like it gets replicated only once, straight after it is created.
Is there any other way to force replication apart from calling
session.setAttribute(name, bean) ? I have tried useDirtyFlag true and
false - no luck.
The application is distributed and all other things do get replicated.
Regards,
Vlad
This is a little test case for my problem:
test.jsp:
-
jsp:useBean id=mybean class=TestBean scope=session /
%
out.print(mybean.a());
%
TestBean.java
-
import org.apache.log4j.Logger;
import java.io.Serializable;
import java.io.IOException;
import java.util.Random;
public class TestBean implements Serializable{
private static Logger logger = Logger.getLogger(TestBean.class);
private long m_a = 0;
private Random rnd = new Random(System.currentTimeMillis());
public long a() {
m_a = rnd.nextLong();
return m_a;
}
private void writeObject(java.io.ObjectOutputStream out) throws
IOException {
//logger.debug(Serialized);
System.out.println(Serialized);
out.defaultWriteObject();
}
private void readObject(java.io.ObjectInputStream in) throws
IOException, ClassNotFoundException {
in.defaultReadObject();
//logger.debug(Deserialized);
System.out.println(Deserialized);
}
}
The information contained in this email message may be confidential. If you
are not the intended recipient, any use, interference with, disclosure or
copying of this material is unauthorised and prohibited. Although this
message and any attachments are believed to be free of viruses, no
responsibility is accepted by Informa for any loss or damage arising in any
way from receipt or use thereof. Messages to and from the company are
monitored for operational reasons and in accordance with lawful business
practices.
If you have received this message in error, please notify us by return
RE: Filter causing memory on TC-5.0.18 and 5.0.19
Hi, We also are experiencing memory leaks in tomcat since we upgraded from 5.0.16 to 5.0.19. In particular I found out that web app sessions will not timeout with session-timeout=1 (or rather it will, but not after 1 minute): session-config session-timeout1/session-timeout /session-config using StandardManager. Does 5.0.19 honor session-timeout parameter at all? The output of /manager/sessions?path=/testcontext is: - OK - Session information for application at context path /testcontext Default maximum session inactive interval 1 minutes 60 - 70 minutes:2 sessions - Regards, Vlad Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: Monday, March 08, 2004 1:53 PM To: Tomcat Users List Subject: RE: Filter causing memory on TC-5.0.18 and 5.0.19 Hi, We search hard in the archive and found many, many questions in regards of this. Can you please point out specific messages or threads in the archives that ask about a filter causing a tomcat memory leak? Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] The information contained in this email message may be confidential. If you are not the intended recipient, any use, interference with, disclosure or copying of this material is unauthorised and prohibited. Although this message and any attachments are believed to be free of viruses, no responsibility is accepted by Informa for any loss or damage arising in any way from receipt or use thereof. Messages to and from the company are monitored for operational reasons and in accordance with lawful business practices. If you have received this message in error, please notify us by return and delete the message and any attachments. Further enquiries/returns can be sent to [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Filter causing memory on TC-5.0.18 and 5.0.19
Sorry about that. I was thinking that those issues are related. -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: Monday, March 08, 2004 3:54 PM To: Tomcat Users List Subject: RE: Filter causing memory on TC-5.0.18 and 5.0.19 Hi, We also are experiencing memory leaks in tomcat since we upgraded from 5.0.16 to 5.0.19. In particular I found out that web app sessions will not timeout with session-timeout=1 (or rather it will, but not after 1 minute): What is it recently with people hijacking threads? Please use a separate thread for the session timeout question, this one is about filters. Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] The information contained in this email message may be confidential. If you are not the intended recipient, any use, interference with, disclosure or copying of this material is unauthorised and prohibited. Although this message and any attachments are believed to be free of viruses, no responsibility is accepted by Informa for any loss or damage arising in any way from receipt or use thereof. Messages to and from the company are monitored for operational reasons and in accordance with lawful business practices. If you have received this message in error, please notify us by return and delete the message and any attachments. Further enquiries/returns can be sent to [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Problem: Apache 2.0.48 + mod_jk 1.2.6 + tomcat 5.0.19
Hi, I'm running Solaris 9, Apache 2.0.48, mod_jk 1.2.6 and tomcat 5.0.19 and I'm getting these messages in apache error log: (128)Network is unreachable: connect to listener Those aren't too frequent though but seem to present problems: We have a monitoring tool that uses commons-httpclient to poll tomcat every so often and that tool seem to be getting this exception: 27 Feb 2004 10:21:06 ERROR local_services_monitor2-wrk2 - I/O failure reading response body java.net.SocketTimeoutException: Read timed out at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:129) at java.net.SocketInputStream.read(SocketInputStream.java:182) at java.io.FilterInputStream.read(FilterInputStream.java:66) at java.io.PushbackInputStream.read(PushbackInputStream.java:120) at org.apache.commons.httpclient.ChunkedInputStream.getChunkSizeFromInputSt ream(ChunkedInputStream.java:264) at org.apache.commons.httpclient.ChunkedInputStream.nextChunk(ChunkedInputS tream.java:237) at org.apache.commons.httpclient.ChunkedInputStream.read(ChunkedInputStream .java:192) at java.io.FilterInputStream.read(FilterInputStream.java:111) at org.apache.commons.httpclient.AutoCloseInputStream.read(AutoCloseInputSt ream.java:142) at java.io.FilterInputStream.read(FilterInputStream.java:90) at org.apache.commons.httpclient.AutoCloseInputStream.read(AutoCloseInputSt ream.java:161) at org.apache.commons.httpclient.HttpMethodBase.getResponseBody(HttpMethodB ase.java:717) at org.apache.commons.httpclient.HttpMethodBase.getResponseBodyAsString(Htt pMethodBase.java:764) at com.informa.jwatch.jobs.HttpMonitor.start(Unknown Source) at com.informa.jwatch.jobs.HttpXmlMonitor.start(Unknown Source) at com.informa.jwatch.BasicJobContext.executeJob(BasicJobContext.java:32) at com.informa.jwatch.AbstractJobContext.execute(AbstractJobContext.java:90 ) at com.informa.jwatch.BatchJobContext.executeJob(BatchJobContext.java:30) at com.informa.jwatch.AbstractJobContext.execute(AbstractJobContext.java:90 ) at com.informa.jwatch.exec.ExecutionGroup$WorkerThread.run(ExecutionGroup.j ava:176) The weird thing is that httpclient always receives http headers and occasionally fails on the content body. Basically every time I see that exception in the monitoring log it coincides with network unreachable message in apache error log. Any ideas on this matter would be greatly appreciated! Thanks, Vlad The information contained in this email message may be confidential. If you are not the intended recipient, any use, interference with, disclosure or copying of this material is unauthorised and prohibited. Although this message and any attachments are believed to be free of viruses, no responsibility is accepted by Informa for any loss or damage arising in any way from receipt or use thereof. Messages to and from the company are monitored for operational reasons and in accordance with lawful business practices. If you have received this message in error, please notify us by return and delete the message and any attachments. Further enquiries/returns can be sent to [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Problem: Apache 2.0.48 + mod_jk 1.2.6 + tomcat 5.0.19
Update. This is what happens when the load on tomcat is high: all requests are executed but for some of those tomcat is unable to send the response back (browser stalls and will eventually time out after the timeout set in httpd.conf has expired). As the load goes down tomcat is able to send content back with no problems. What configuration settings can affect this behavior? Vlad -Original Message- From: Ilyschenko, Vlad Sent: Monday, March 01, 2004 9:46 AM To: Tomcat Users List Subject: Problem: Apache 2.0.48 + mod_jk 1.2.6 + tomcat 5.0.19 Hi, I'm running Solaris 9, Apache 2.0.48, mod_jk 1.2.6 and tomcat 5.0.19 and I'm getting these messages in apache error log: (128)Network is unreachable: connect to listener Those aren't too frequent though but seem to present problems: We have a monitoring tool that uses commons-httpclient to poll tomcat every so often and that tool seem to be getting this exception: 27 Feb 2004 10:21:06 ERROR local_services_monitor2-wrk2 - I/O failure reading response body java.net.SocketTimeoutException: Read timed out at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:129) at java.net.SocketInputStream.read(SocketInputStream.java:182) at java.io.FilterInputStream.read(FilterInputStream.java:66) at java.io.PushbackInputStream.read(PushbackInputStream.java:120) at org.apache.commons.httpclient.ChunkedInputStream.getChunkSizeFromInputSt ream(ChunkedInputStream.java:264) at org.apache.commons.httpclient.ChunkedInputStream.nextChunk(ChunkedInputS tream.java:237) at org.apache.commons.httpclient.ChunkedInputStream.read(ChunkedInputStream .java:192) at java.io.FilterInputStream.read(FilterInputStream.java:111) at org.apache.commons.httpclient.AutoCloseInputStream.read(AutoCloseInputSt ream.java:142) at java.io.FilterInputStream.read(FilterInputStream.java:90) at org.apache.commons.httpclient.AutoCloseInputStream.read(AutoCloseInputSt ream.java:161) at org.apache.commons.httpclient.HttpMethodBase.getResponseBody(HttpMethodB ase.java:717) at org.apache.commons.httpclient.HttpMethodBase.getResponseBodyAsString(Htt pMethodBase.java:764) at com.informa.jwatch.jobs.HttpMonitor.start(Unknown Source) at com.informa.jwatch.jobs.HttpXmlMonitor.start(Unknown Source) at com.informa.jwatch.BasicJobContext.executeJob(BasicJobContext.java:32) at com.informa.jwatch.AbstractJobContext.execute(AbstractJobContext.java:90 ) at com.informa.jwatch.BatchJobContext.executeJob(BatchJobContext.java:30) at com.informa.jwatch.AbstractJobContext.execute(AbstractJobContext.java:90 ) at com.informa.jwatch.exec.ExecutionGroup$WorkerThread.run(ExecutionGroup.j ava:176) The weird thing is that httpclient always receives http headers and occasionally fails on the content body. Basically every time I see that exception in the monitoring log it coincides with network unreachable message in apache error log. Any ideas on this matter would be greatly appreciated! Thanks, Vlad The information contained in this email message may be confidential. If you are not the intended recipient, any use, interference with, disclosure or copying of this material is unauthorised and prohibited. Although this message and any attachments are believed to be free of viruses, no responsibility is accepted by Informa for any loss or damage arising in any way from receipt or use thereof. Messages to and from the company are monitored for operational reasons and in accordance with lawful business practices. If you have received this message in error, please notify us by return and delete the message and any attachments. Further enquiries/returns can be sent to [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Problem: Apache 2.0.48 + mod_jk 1.2.6 + tomcat 5.0.19
More update. Tomcat response does get through to the client! But browser keeps spinning and then times out. JK bug may be? Any advise guys? This is a production environment so I have to get this sorted. Vlad -Original Message- From: Ilyschenko, Vlad Sent: Monday, March 01, 2004 10:45 AM To: Tomcat Users List Subject: RE: Problem: Apache 2.0.48 + mod_jk 1.2.6 + tomcat 5.0.19 Update. This is what happens when the load on tomcat is high: all requests are executed but for some of those tomcat is unable to send the response back (browser stalls and will eventually time out after the timeout set in httpd.conf has expired). As the load goes down tomcat is able to send content back with no problems. What configuration settings can affect this behavior? Vlad -Original Message- From: Ilyschenko, Vlad Sent: Monday, March 01, 2004 9:46 AM To: Tomcat Users List Subject: Problem: Apache 2.0.48 + mod_jk 1.2.6 + tomcat 5.0.19 Hi, I'm running Solaris 9, Apache 2.0.48, mod_jk 1.2.6 and tomcat 5.0.19 and I'm getting these messages in apache error log: (128)Network is unreachable: connect to listener Those aren't too frequent though but seem to present problems: We have a monitoring tool that uses commons-httpclient to poll tomcat every so often and that tool seem to be getting this exception: 27 Feb 2004 10:21:06 ERROR local_services_monitor2-wrk2 - I/O failure reading response body java.net.SocketTimeoutException: Read timed out at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:129) at java.net.SocketInputStream.read(SocketInputStream.java:182) at java.io.FilterInputStream.read(FilterInputStream.java:66) at java.io.PushbackInputStream.read(PushbackInputStream.java:120) at org.apache.commons.httpclient.ChunkedInputStream.getChunkSizeFromInputSt ream(ChunkedInputStream.java:264) at org.apache.commons.httpclient.ChunkedInputStream.nextChunk(ChunkedInputS tream.java:237) at org.apache.commons.httpclient.ChunkedInputStream.read(ChunkedInputStream .java:192) at java.io.FilterInputStream.read(FilterInputStream.java:111) at org.apache.commons.httpclient.AutoCloseInputStream.read(AutoCloseInputSt ream.java:142) at java.io.FilterInputStream.read(FilterInputStream.java:90) at org.apache.commons.httpclient.AutoCloseInputStream.read(AutoCloseInputSt ream.java:161) at org.apache.commons.httpclient.HttpMethodBase.getResponseBody(HttpMethodB ase.java:717) at org.apache.commons.httpclient.HttpMethodBase.getResponseBodyAsString(Htt pMethodBase.java:764) at com.informa.jwatch.jobs.HttpMonitor.start(Unknown Source) at com.informa.jwatch.jobs.HttpXmlMonitor.start(Unknown Source) at com.informa.jwatch.BasicJobContext.executeJob(BasicJobContext.java:32) at com.informa.jwatch.AbstractJobContext.execute(AbstractJobContext.java:90 ) at com.informa.jwatch.BatchJobContext.executeJob(BatchJobContext.java:30) at com.informa.jwatch.AbstractJobContext.execute(AbstractJobContext.java:90 ) at com.informa.jwatch.exec.ExecutionGroup$WorkerThread.run(ExecutionGroup.j ava:176) The weird thing is that httpclient always receives http headers and occasionally fails on the content body. Basically every time I see that exception in the monitoring log it coincides with network unreachable message in apache error log. Any ideas on this matter would be greatly appreciated! Thanks, Vlad The information contained in this email message may be confidential. If you are not the intended recipient, any use, interference with, disclosure or copying of this material is unauthorised and prohibited. Although this message and any attachments are believed to be free of viruses, no responsibility is accepted by Informa for any loss or damage arising in any way from receipt or use thereof. Messages to and from the company are monitored for operational reasons and in accordance with lawful business practices. If you have received this message in error, please notify us by return and delete the message and any attachments. Further enquiries/returns can be sent to [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Problem: Apache 2.0.48 + mod_jk 1.2.6 + tomcat 5.0.19
More update on that: Tomcat returns a header: Transfer-Encoding: chunked And it doesn't always return \0 (zero) at the end of the content. That is what causes commons-httpclient to throw the exception and browsers to keep spinning after page is displayed. Can something be done about that? Vlad -Original Message- From: Ilyschenko, Vlad Sent: Monday, March 01, 2004 11:05 AM To: Tomcat Users List Subject: RE: Problem: Apache 2.0.48 + mod_jk 1.2.6 + tomcat 5.0.19 More update. Tomcat response does get through to the client! But browser keeps spinning and then times out. JK bug may be? Any advise guys? This is a production environment so I have to get this sorted. Vlad -Original Message- From: Ilyschenko, Vlad Sent: Monday, March 01, 2004 10:45 AM To: Tomcat Users List Subject: RE: Problem: Apache 2.0.48 + mod_jk 1.2.6 + tomcat 5.0.19 Update. This is what happens when the load on tomcat is high: all requests are executed but for some of those tomcat is unable to send the response back (browser stalls and will eventually time out after the timeout set in httpd.conf has expired). As the load goes down tomcat is able to send content back with no problems. What configuration settings can affect this behavior? Vlad -Original Message- From: Ilyschenko, Vlad Sent: Monday, March 01, 2004 9:46 AM To: Tomcat Users List Subject: Problem: Apache 2.0.48 + mod_jk 1.2.6 + tomcat 5.0.19 Hi, I'm running Solaris 9, Apache 2.0.48, mod_jk 1.2.6 and tomcat 5.0.19 and I'm getting these messages in apache error log: (128)Network is unreachable: connect to listener Those aren't too frequent though but seem to present problems: We have a monitoring tool that uses commons-httpclient to poll tomcat every so often and that tool seem to be getting this exception: 27 Feb 2004 10:21:06 ERROR local_services_monitor2-wrk2 - I/O failure reading response body java.net.SocketTimeoutException: Read timed out at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:129) at java.net.SocketInputStream.read(SocketInputStream.java:182) at java.io.FilterInputStream.read(FilterInputStream.java:66) at java.io.PushbackInputStream.read(PushbackInputStream.java:120) at org.apache.commons.httpclient.ChunkedInputStream.getChunkSizeFromInputSt ream(ChunkedInputStream.java:264) at org.apache.commons.httpclient.ChunkedInputStream.nextChunk(ChunkedInputS tream.java:237) at org.apache.commons.httpclient.ChunkedInputStream.read(ChunkedInputStream .java:192) at java.io.FilterInputStream.read(FilterInputStream.java:111) at org.apache.commons.httpclient.AutoCloseInputStream.read(AutoCloseInputSt ream.java:142) at java.io.FilterInputStream.read(FilterInputStream.java:90) at org.apache.commons.httpclient.AutoCloseInputStream.read(AutoCloseInputSt ream.java:161) at org.apache.commons.httpclient.HttpMethodBase.getResponseBody(HttpMethodB ase.java:717) at org.apache.commons.httpclient.HttpMethodBase.getResponseBodyAsString(Htt pMethodBase.java:764) at com.informa.jwatch.jobs.HttpMonitor.start(Unknown Source) at com.informa.jwatch.jobs.HttpXmlMonitor.start(Unknown Source) at com.informa.jwatch.BasicJobContext.executeJob(BasicJobContext.java:32) at com.informa.jwatch.AbstractJobContext.execute(AbstractJobContext.java:90 ) at com.informa.jwatch.BatchJobContext.executeJob(BatchJobContext.java:30) at com.informa.jwatch.AbstractJobContext.execute(AbstractJobContext.java:90 ) at com.informa.jwatch.exec.ExecutionGroup$WorkerThread.run(ExecutionGroup.j ava:176) The weird thing is that httpclient always receives http headers and occasionally fails on the content body. Basically every time I see that exception in the monitoring log it coincides with network unreachable message in apache error log. Any ideas on this matter would be greatly appreciated! Thanks, Vlad The information contained in this email message may be confidential. If you are not the intended recipient, any use, interference with, disclosure or copying of this material is unauthorised and prohibited. Although this message and any attachments are believed to be free of viruses, no responsibility is accepted by Informa for any loss or damage arising in any way from receipt or use thereof. Messages to and from the company are monitored for operational reasons and in accordance with lawful business practices. If you have received this message in error, please notify us by return and delete the message and any attachments. Further enquiries/returns can be sent to [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED
tomcat 5.0.19 cluster problem
Hi, We are running three Solaris9 boxes with tomcat 5.0.19 on them. Cluster configuration is as follows: Cluster className=org.apache.catalina.cluster.tcp.SimpleTcpCluster managerClassName=org.apache.catalina.cluster.session.DeltaManager expireSessionsOnShutdown=false useDirtyFlag=true Membership className=org.apache.catalina.cluster.mcast.McastService mcastAddr=228.0.0.3 mcastPort=45564 mcastFrequency=500 mcastDropTime=3000/ Receiver className=org.apache.catalina.cluster.tcp.ReplicationListener tcpListenAddress=auto tcpListenPort=4001 tcpSelectorTimeout=100 tcpThreadCount=60/ Sender className=org.apache.catalina.cluster.tcp.ReplicationTransmitter replicationMode=pooled/ Valve className=org.apache.catalina.cluster.tcp.ReplicationValve filter=.*\.gif;.*\.js;.*\.jpg;.*\.htm;.*\.html;.*\.txt;/ /Cluster Yesterday tomcat on one of the servers ran out of memory that coincided with a clustered web application hang across all three servers. All tomcat instances started exhibiting cluster problems in one shape or another. I wonder if 5.0.19 cluster has memory leaks. I have not experienced OutOfMemory problems on those boxes running 5.0.16 for over a month. In any case could a cluster node that ran out of memory destroy the entire cluster? You could find the log fragments from those three boxes below: Box #1 (IP: 192.168.64.40) - the one with memory problems: 22 Feb 2004 00:26:43 INFO Cluster-MembershipReceiver - Received member disappeared:org.apache.catalina.cluster.mcast.McastMember[tcp://192.168. 64.36:4001,192.168.64.36,4001, alive=112504278] 22 Feb 2004 00:26:43 INFO Cluster-MembershipReceiver - Replication member added:org.apache.catalina.cluster.mcast.McastMember[tcp://192.168.64.36: 4001,192.168.64.36,4001, alive=112532838] 22 Feb 2004 00:26:53 INFO Cluster-MembershipReceiver - Received member disappeared:org.apache.catalina.cluster.mcast.McastMember[tcp://192.168. 64.36:4001,192.168.64.36,4001, alive=112532838] 22 Feb 2004 00:26:53 INFO Cluster-MembershipReceiver - Replication member added:org.apache.catalina.cluster.mcast.McastMember[tcp://192.168.64.36: 4001,192.168.64.36,4001, alive=112540488] 22 Feb 2004 00:26:58 INFO Cluster-MembershipReceiver - Received member disappeared:org.apache.catalina.cluster.mcast.McastMember[tcp://192.168. 64.36:4001,192.168.64.36,4001, alive=112540488] 22 Feb 2004 00:26:58 INFO Cluster-MembershipReceiver - Replication member added:org.apache.catalina.cluster.mcast.McastMember[tcp://192.168.64.36: 4001,192.168.64.36,4001, alive=112548138] 22 Feb 2004 00:27:04 INFO Cluster-MembershipReceiver - Received member disappeared:org.apache.catalina.cluster.mcast.McastMember[tcp://192.168. 64.41:4001,192.168.64.41,4001, alive=113937290] 22 Feb 2004 00:27:04 INFO Cluster-MembershipReceiver - Replication member added:org.apache.catalina.cluster.mcast.McastMember[tcp://192.168.64.41: 4001,192.168.64.41,4001, alive=113967890] 22 Feb 2004 00:27:09 INFO Cluster-MembershipReceiver - Received member disappeared:org.apache.catalina.cluster.mcast.McastMember[tcp://192.168. 64.36:4001,192.168.64.36,4001, alive=112548138] 22 Feb 2004 00:27:09 INFO Cluster-MembershipReceiver - Replication member added:org.apache.catalina.cluster.mcast.McastMember[tcp://192.168.64.36: 4001,192.168.64.36,4001, alive=112558338] 22 Feb 2004 00:27:19 INFO Cluster-MembershipReceiver - Received member disappeared:org.apache.catalina.cluster.mcast.McastMember[tcp://192.168. 64.41:4001,192.168.64.41,4001, alive=113967890] 22 Feb 2004 00:27:19 INFO Cluster-MembershipReceiver - Replication member added:org.apache.catalina.cluster.mcast.McastMember[tcp://192.168.64.41: 4001,192.168.64.41,4001, alive=113981150] 22 Feb 2004 00:27:27 ERROR TP-Processor16 - An exception or error occurred in the container during the request processing java.lang.OutOfMemoryError 22 Feb 2004 00:27:27 DEBUG Finalizer - result finalized 22 Feb 2004 00:27:27 INFO Cluster-MembershipReceiver - Received member disappeared:org.apache.catalina.cluster.mcast.McastMember[tcp://192.168. 64.36:4001,192.168.64.36,4001, alive=112558338] 22 Feb 2004 00:27:27 INFO Cluster-MembershipReceiver - Replication member added:org.apache.catalina.cluster.mcast.McastMember[tcp://192.168.64.36: 4001,192.168.64.36,4001, alive=112573638] 22 Feb 2004 00:27:27 INFO TP-Processor16 - Unknown message 0 22 Feb 2004 00:27:34 INFO Cluster-MembershipReceiver - Received member disappeared:org.apache.catalina.cluster.mcast.McastMember[tcp://192.168. 64.36:4001,192.168.64.36,4001, alive=112573638] 22 Feb 2004 00:27:34 INFO Cluster-MembershipReceiver - Replication member
