On 07/07/2011 04:01 PM, Eric Kreiser wrote:
spoke too soon...

it does show "ERROR" on the heartbeat tab for the "other" server

what is the next step it figure what is causing them to not be able to talk to each other?

There should be an message in the log files.

The main thing, though, is to double check that the resin.xml is identical for both servers and that the server port is accessible from one to the other.

The heartbeat isn't much more than a dedicated TCP connection to keep track of each other, sending small packets every 60s to make sure everything's oka.

-- Scott




On 07/07/2011 06: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?



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

<cluster id="app-tier">
<persistent-store type="cluster"/>
<server id="a" address="10.10.1.145" port="6803">
<bind-ports-after-start>false</bind-ports-after-start>
<watchdog-port>6701</watchdog-port>
<watchdog-address>10.10.1.145</watchdog-address>
</server>
<server id="b" address="10.10.1.141" port="6803">
<bind-ports-after-start>false</bind-ports-after-start>
<watchdog-port>6701</watchdog-port>
<watchdog-address>10.10.1.141</watchdog-address>
</server>
<web-app-default>
<session-config cookie-length="100" use-persistent-store="true">
<session-timeout>200</session-timeout>
<always-load-session/>
<save-mode>before-headers</save-mode>
<reuse-session-id>false</reuse-session-id>
<serialization-type>java</serialization-type>
<always-save-session>true</always-save-session>
</session-config>
</web-app-default>
</cluster>

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


--

*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 <mailto: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

_______________________________________________
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest

Reply via email to