<Quote>
So, if a statement execution results in SQLExceptions from every non-local
database - but success in every local database, AND the jgroups group size is
1 (i.e. !StateManager.isMembershipEmpty() = true), then the database cluster
is stopped (i.e. will no longer process requests, until manually started) and
an error is logged.
</Quote>
I am trying to reproduce this. Does HA-JDBC shutdown the application servers
(Tomcat), or just become unresponsive? I see my applications continueing with
oppose states, and servicing SQL locally.
What am I missing? Here is my config for one of my nodes. The other
application server has a config with the other database marked as local. Is
something misconfigured here? Why am I not seeing the specified behaviour?
According to this FAQ, HA-JDBC should shutdown automatically in this scenario?
https://sourceforge.net/apps/mediawiki/ha-
jdbc/index.php?title=FAQ
<Quote>
So, if a statement execution results in SQLExceptions from every non-local
database - but success in every local database, AND the jgroups group size is
1 (i.e. !StateManager.isMembershipEmpty() = true), then the database cluster
is stopped (i.e. will no longer process requests, until manually started) and
an error is logged.
</Quote>
I am trying to reproduce this. Does HA-JDBC shutdown the application servers
(Tomcat), or just become unresponsive? I see my applications continueing with
oppose states, and servicing SQL locally.
What am I missing? Here is my config for one of my nodes. The other
application server has a config with the other database marked as local. Is
something misconfigured here? Why am I not seeing the specified behaviour?
<ha-jdbc>
<distributable<br>config="stacks.xml"
stack="tcp-sync"
timeout="6000"
/>
<sync
id="diffsync"
class="net.sf.hajdbc.sync.FullSynchronizationStrategy"