Re: [Resin-interest] How do I configure clustering so that it actually works with 4.0.15/4.0.18/4.0.19?
On 07/08/2011 12:12 PM, Eric Kreiser wrote:
see attached zip
both servers logs as I make several requests
--
I know this is a bit of a rhetorical question... but it seems like it
shouldn't be possible to be this difficult to get working... doesn't
it boil down to only a few configs?
Thanks. That should be enough (though may take some time).
I haven't figured out why you're not seeing the data. The updates are
being sent, and that configuration is identical to one here.)
-- Scott
On 07/08/2011 12:35 PM, Scott Ferguson wrote:
On 07/07/2011 06:18 PM, Eric Kreiser wrote:
I've attached a few logs
(I am running with 2 servers (server 'a' and 'b')... I have my
logging configured a little differently - so not everything from
resin go to my jvm log )
server-changing-session-attri_jvm.log === is from server a, when the
request hit server a and server a changed a session attribute (so
the session should have gotten pushed to server b but didn't)
server-changing-session-attri_stdout.log === is from server a, when
the request hit server a and server a changed a session attribute
(so the session should have gotten pushed to server b but didn't)
when-other-server-changes-session-attri.log === is from server a,
when the request hit server b and server b changed a session
attribute (so the session should have gotten pushed to server a but
didn't)
You didn't include the request log from the second request.
-- Scott
thanks
Eric
On 07/07/2011 07:29 PM, Scott Ferguson wrote:
Can you create a log which include a servlet access that should
replicate session data (at "finer" level) and mail me the jvm-xxx.log?
-- Scott
On 07/07/2011 04:17 PM, Eric Kreiser wrote:
On 07/07/2011 07:02 PM, Scott Ferguson wrote:
On 07/07/2011 03:51 PM, Eric Kreiser wrote:
I am having trouble getting resin-admin running inside my servers... is
there another way I can verify that the servers can see each other?
JMX or something?
The resin-admin is the easiest.
If you look at the logs (at the "finer" level), you should see something
like:
[11-07-07 15:30:14.378] {main} JvmDeadlockHealthCheck[OK:OK]
[11-07-07 15:30:14.381] {main} MemoryTenuredHealthCheck[OK:87.63%
free (627.312M free, 715.850M max, 88.538M used)]
...
[11-07-07 15:30:14.383] {main} HeartbeatHealthCheck[OK:OK]
You can look at JMX under the ClusterServer bean and look for the
isHeartbeatActive() and LastHeartbeatTime().
-- Scott
using JMX to look at both servers... the HeartbeatActive=true and
the LastHeartbeatTime is getting updated as well
On 07/07/2011 05:01 PM, Scott Ferguson wrote:
On 07/07/2011 01:37 PM, Eric Kreiser wrote:
I have my resin conf all setup... my servers starting/running, but if I
load balance... and don't use stickiness to servers... the session is
not kept in sync between the servers. I am trying to test this all...
so I am only running 2 servers - but both servers are configured as
triads so that they should know about each other. They are running on
the same machine(just with different ip/ports) - so I am not having
network issues or anything.
snippet below from my config
false
6701
10.10.1.145
false
6701
10.10.1.141
200
before-headers
false
java
true
what am I missing?
That looks fine. In the /resin-admin, do you see the servers able to
connect to each other?
(The health tab will show connection failures in the Resin|Heartbeat
check and also the Heartbeat tab.)
-- Scott
thanks
Eric
___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest
___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest
___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest
___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest
--
*Eric S. Kreiser* *
* Senior Software Architect
*M**z**inga**
* 5095 Ritter Road • Mechanicsburg, PA 17055
---
*Call me:* 717.458.9804
*Fax me:* 717.790.0401
*Email me:* ekrei...@mzinga.com
*Learn more:* http://mzinga.com/v/ekreiser/
*Follow Mzinga:* http://twitter.com/mzinga
*Our Customer Experience Community:*
http://community.omnisocial.mzinga.com/app/signon/
___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] How do I configure clustering so that it actually works with 4.0.15/4.0.18/4.0.19?
On 07/07/2011 06:18 PM, Eric Kreiser wrote:
I've attached a few logs
(I am running with 2 servers (server 'a' and 'b')... I have my logging
configured a little differently - so not everything from resin go to
my jvm log )
server-changing-session-attri_jvm.log === is from server a, when the
request hit server a and server a changed a session attribute (so the
session should have gotten pushed to server b but didn't)
server-changing-session-attri_stdout.log === is from server a, when
the request hit server a and server a changed a session attribute (so
the session should have gotten pushed to server b but didn't)
when-other-server-changes-session-attri.log === is from server a, when
the request hit server b and server b changed a session attribute (so
the session should have gotten pushed to server a but didn't)
You didn't include the request log from the second request.
-- Scott
thanks
Eric
On 07/07/2011 07:29 PM, Scott Ferguson wrote:
Can you create a log which include a servlet access that should
replicate session data (at "finer" level) and mail me the jvm-xxx.log?
-- Scott
On 07/07/2011 04:17 PM, Eric Kreiser wrote:
On 07/07/2011 07:02 PM, Scott Ferguson wrote:
On 07/07/2011 03:51 PM, Eric Kreiser wrote:
I am having trouble getting resin-admin running inside my servers... is
there another way I can verify that the servers can see each other?
JMX or something?
The resin-admin is the easiest.
If you look at the logs (at the "finer" level), you should see something
like:
[11-07-07 15:30:14.378] {main} JvmDeadlockHealthCheck[OK:OK]
[11-07-07 15:30:14.381] {main} MemoryTenuredHealthCheck[OK:87.63%
free (627.312M free, 715.850M max, 88.538M used)]
...
[11-07-07 15:30:14.383] {main} HeartbeatHealthCheck[OK:OK]
You can look at JMX under the ClusterServer bean and look for the
isHeartbeatActive() and LastHeartbeatTime().
-- Scott
using JMX to look at both servers... the HeartbeatActive=true and
the LastHeartbeatTime is getting updated as well
On 07/07/2011 05:01 PM, Scott Ferguson wrote:
On 07/07/2011 01:37 PM, Eric Kreiser wrote:
I have my resin conf all setup... my servers starting/running, but if I
load balance... and don't use stickiness to servers... the session is
not kept in sync between the servers. I am trying to test this all...
so I am only running 2 servers - but both servers are configured as
triads so that they should know about each other. They are running on
the same machine(just with different ip/ports) - so I am not having
network issues or anything.
snippet below from my config
false
6701
10.10.1.145
false
6701
10.10.1.141
200
before-headers
false
java
true
what am I missing?
That looks fine. In the /resin-admin, do you see the servers able to
connect to each other?
(The health tab will show connection failures in the Resin|Heartbeat
check and also the Heartbeat tab.)
-- Scott
thanks
Eric
___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest
___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest
___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest
___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest
___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] How do I configure clustering so that it actually works with 4.0.15/4.0.18/4.0.19?
I've attached a few logs
(I am running with 2 servers (server 'a' and 'b')... I have my logging
configured a little differently - so not everything from resin go to my
jvm log )
server-changing-session-attri_jvm.log === is from server a, when the
request hit server a and server a changed a session attribute (so the
session should have gotten pushed to server b but didn't)
server-changing-session-attri_stdout.log === is from server a, when the
request hit server a and server a changed a session attribute (so the
session should have gotten pushed to server b but didn't)
when-other-server-changes-session-attri.log === is from server a, when
the request hit server b and server b changed a session attribute (so
the session should have gotten pushed to server a but didn't)
thanks
Eric
I've also attached a "diff" file of the 2 servers resin config files---
most of the differences are jvm-arg differences
On 07/07/2011 07:29 PM, Scott Ferguson wrote:
Can you create a log which include a servlet access that should
replicate session data (at "finer" level) and mail me the jvm-xxx.log?
-- Scott
On 07/07/2011 04:17 PM, Eric Kreiser wrote:
On 07/07/2011 07:02 PM, Scott Ferguson wrote:
On 07/07/2011 03:51 PM, Eric Kreiser wrote:
I am having trouble getting resin-admin running inside my servers... is
there another way I can verify that the servers can see each other?
JMX or something?
The resin-admin is the easiest.
If you look at the logs (at the "finer" level), you should see something
like:
[11-07-07 15:30:14.378] {main} JvmDeadlockHealthCheck[OK:OK]
[11-07-07 15:30:14.381] {main} MemoryTenuredHealthCheck[OK:87.63%
free (627.312M free, 715.850M max, 88.538M used)]
...
[11-07-07 15:30:14.383] {main} HeartbeatHealthCheck[OK:OK]
You can look at JMX under the ClusterServer bean and look for the
isHeartbeatActive() and LastHeartbeatTime().
-- Scott
using JMX to look at both servers... the HeartbeatActive=true and the
LastHeartbeatTime is getting updated as well
On 07/07/2011 05:01 PM, Scott Ferguson wrote:
On 07/07/2011 01:37 PM, Eric Kreiser wrote:
I have my resin conf all setup... my servers starting/running, but if I
load balance... and don't use stickiness to servers... the session is
not kept in sync between the servers. I am trying to test this all...
so I am only running 2 servers - but both servers are configured as
triads so that they should know about each other. They are running on
the same machine(just with different ip/ports) - so I am not having
network issues or anything.
snippet below from my config
false
6701
10.10.1.145
false
6701
10.10.1.141
200
before-headers
false
java
true
what am I missing?
That looks fine. In the /resin-admin, do you see the servers able to
connect to each other?
(The health tab will show connection failures in the Resin|Heartbeat
check and also the Heartbeat tab.)
-- Scott
thanks
Eric
___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest
___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest
___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest
___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest
07-07 21:06:15.549 closing pool item from idle
timeout:ManagedPoolItem[jdbc/devdb,5,ManagedConnectionImpl]
07-07 21:06:15.549 connection pool destroy ManagedPoolItem[jdbc/devdb,5,null]
07-07 21:06:15.549 destroy ManagedConnectionImpl[jdbc/devdb.d0.2]
07-07 21:06:15.771 closing pool item from idle
timeout:ManagedPoolItem[jdbc/master,92,ManagedConnectionImpl]
07-07 21:06:15.771 connection pool destroy ManagedPoolItem[jdbc/master,92,null]
07-07 21:06:15.771 destroy ManagedConnectionImpl[jdbc/master.d0.29]
07-07 21:06:44.062 RMI Scheduler(0): wake up
07-07 21:06:44.062 RMI Scheduler(0): connection timeout expired
07-07 21:06:44.062 RMI Scheduler(0): close connection
07-07 21:06:44.071 RMI Scheduler(0): wake up
07-07 21:06:22.274 TcpSocketLink[id=15,a] starting connection
TcpSocketLink[id=server://10.10.1.145:6803-15,server://10.10.1.145:6803,ACCEPT],
total=6
07-07 21:06:22.274
TcpSocketLink[id=server://10.10.1.145:6803-15,server://10.10.1.145:6803,ACCEPT]
accept from 10.10.1.145:51212
07-07 21:06:22.274 Hmux[a:15] start request
07-07 21:06:22.274 Hmux[a:15] U:uri /app/test.jsp
07-07 21:06:22.274
TcpSocketLink[id=server://10.10.1.145:6803-17,server://10.10.1.145:6803,INIT]
starting listen thread
07-07 21:06:22.274 Hmux[a:15] m:method GET
07-07 21:06:22.274
TcpSocketLink[id=server://10.10.1.145:6803-17,server://10.10.1.145:6803,INIT]
start thread server://10.10.1.145:6
