Hi Sebastian,
Sorry I'm slow to respond, I just noticed this message.
First, is your multicast network setup properly? From shell can you ping
228.0.0.4 and receive replies from from both hosts? If not, check the
routes you setup for multicasting.
It's weird, but on RHEL 4, I had to comment out the "mcast-bind-addr"
setting so it binds to all addresses, or it wouldn't work. I originally
tried binding only to my internal VPN address like in your config, but it
would work for some reason.
Another thing to check for is if access to port 45564 is enabled. You can
try telnetting to that port from one server to the other and see if it
connects. Might have to adjust iptables or whatever firewall service you
have running.
Not sure what version of OFBiz you're using. My version was a checkout from
a year ago, so I had to manually update to Tomcat 5.5.20.
Did you get Lambda Probe up and running? Is the multicasting showing up?
Keep us posted.
-sterling
On 3/14/07, Sebastian Schirmer <[EMAIL PROTECTED]> wrote:
Hello Sterling,
I am interesting on a ofbiz cluster setup with session replication between
two hosts. I have investigated some time on the setup. The log shows
also
cluster.mcast messages but it seems that the broadcast messages are not
receive packets from an other host node. I have also added your catalina
patch from jira. Do you have a configuration example for a two node
cluster?
here is my setup the node 1 has 192.168.51.54 the second is configured on
node one:
<container name="catalina-container"
class="org.ofbiz.catalina.container.CatalinaContainer">
<!-- static configuration for tomcat -->
<property name="delegator-name" value="default"/>
<property name="use-naming" value="false"/>
<property name="debug" value="0"/>
<property name="apps-context-reloadable" value="false"/>
<property name="apps-cross-context" value="false"/>
<property name="apps-distributable" value="true"/>
<!-- one or more tomcat engines (servers); map to this + host -->
<property name="default-server" value="engine">
<property name="default-host" value="192.168.51.54"/>
<property name="jvm-route" value="appl01"/>
<property name="access-log-pattern">
<property-value>%h %l %u %t "%r" %s %b "%{Referer}i"
"%{User-Agent}i"</property-value>
</property>
<property name="access-log-resolve" value="true"/>
<property name="access-log-rotate" value="true"/>
<property name="access-log-prefix" value="access_log."/>
<property name="access-log-dir" value="framework/logs"/>
<property name="enable-request-dump" value="false"/>
<property name="default-server-cluster" value="cluster">
<property name="rep-valve-filter">
<property-value>.*\.gif;.*\.js;.*\.jpg;.*\.htm;.*\.html;.*\.txt;</property-value>
</property>
<property name="manager-class"
value="org.apache.catalina.cluster.session.DeltaManager"/>
<property name="debug" value="5"/>
<property name="replication-mode" value="pooled"/>
<property name="tcp-listen-host" value="192.168.51.54"/>
<property name="tcp-listen-port" value="4000"/>
<property name="tcp-sector-timeout" value="100"/>
<property name="tcp-thread-count" value="6"/>
<property name="mcast-bind-addr" value="192.168.51.54"/>
<property name="mcast-addr" value="228.0.0.4"/>
<property name="mcast-port" value="45564"/>
<property name="mcast-freq" value="500"/>
<property name="mcast-drop-time" value="3000"/>
</property>
node two:
<container name="catalina-container"
class="org.ofbiz.catalina.container.CatalinaContainer">
<!-- static configuration for tomcat -->
<property name="delegator-name" value="default"/>
<property name="use-naming" value="false"/>
<property name="debug" value="0"/>
<property name="apps-context-reloadable" value="false"/>
<property name="apps-cross-context" value="false"/>
<property name="apps-distributable" value="true"/>
<!-- one or more tomcat engines (servers); map to this + host -->
<property name="default-server" value="engine">
<property name="default-host" value="192.168.51.55"/>
<property name="jvm-route" value="appl02"/>
<property name="access-log-pattern">
<property-value>%h %l %u %t "%r" %s %b "%{Referer}i"
"%{User-Agent}i"</property-value>
</property>
<property name="access-log-resolve" value="true"/>
<property name="access-log-rotate" value="true"/>
<property name="access-log-prefix" value="access_log."/>
<property name="access-log-dir" value="framework/logs"/>
<property name="enable-request-dump" value="false"/>
<property name="default-server-cluster" value="cluster">
<property name="rep-valve-filter">
<property-value>.*\.gif;.*\.js;.*\.jpg;.*\.htm;.*\.html;.*\.txt;</property-value>
</property>
<property name="manager-class"
value="org.apache.catalina.cluster.session.DeltaManager"/>
<property name="debug" value="5"/>
<property name="replication-mode" value="pooled"/>
<property name="tcp-listen-host" value="192.168.51.55"/>
<property name="tcp-listen-port" value="4000"/>
<property name="tcp-sector-timeout" value="100"/>
<property name="tcp-thread-count" value="6"/>
<property name="mcast-bind-addr" value="192.168.51.55"/>
<property name="mcast-addr" value="228.0.0.4"/>
<property name="mcast-port" value="45564"/>
<property name="mcast-freq" value="500"/>
<property name="mcast-drop-time" value="3000"/>
</property>
Kind regards
sebastian
--On Mittwoch, 21. Februar 2007 03:27 -0700 Sterling Okura
<[EMAIL PROTECTED]> wrote:
> Hi everyone. I want to share a helpful tool for those who haven't used
it
> yet. Lambda Probe (www.lambdaprobe.org) is an administration &
monitoring
> tool for Tomcat. It shows detailed session, system, memory, cluster,
and
> other info. It has nice real-time stat updates via ajax. I finally got
> clustering and session replication working with OFBiz and Lambda was
> critical in troubleshooting and debugging the setup.
>
> I wrote up a howto for running it in OFBiz hot-deploy at
> http://www.bizlift.com/ofbiz/lambda_probe_for_ofbiz.html. The document
is
> continuing to be refined and updated, and will eventually be added to
> wiki/doc section. Will also write howto on clustering since there seem
to
> be several requests throughout the history of the list but no definitive
> instructions.
>
> aloha,
> sterling
--
Sebastian Schirmer
ZYRES digital media systems GmbH
Eschersheimer Landstr. 5-7 60322 Frankfurt am Main
Phone +49 (0)69 98 55 99 - 0
Fax +49 (0)69 98 55 99 - 11
Firmensitz: Eschersheimer Landstr. 5-7 60322 Frankfurt am Main
Registergericht: Amtsgericht Frankfurt am Main, HRB 76374
Geschäftsführer: Sebastian Schirmer
http://www.zyres.com/
-- RFC|1855|2.1.1
