Correct, I had to add a parameter in the connection url, I set the
socketTimeout in 5000 milliseconds in this way:
connection-urljdbc:mysql://192.168.10.210:3306/POK2?socketTimeout=5000|jdbc:mysql://192.168.10.219:3306/POK2?socketTimeout=5000/connection-url
For anyone looking at mysql failover,
I have a problem using datasource failover with MySQL. My setup is JBoss at
host A, and mysql in host B, replicated in host A. I have followed the
instructions in JBossJCADatabaseFailover.
When I stop mysql at machine B with /etc/init.d/mysql stopfailover works
flawlessly, but if I disconnect
Excellent, I deleted the jms configuration, and copied the one in default,
made the necesary changes, and it worked. The problem with PokQueryDs was that
in the AS, the pool was named PokQueryDS (that makes me feel like dumb). Thanks
for all.
View the original post :
Well, in the default config it seems that JMS uses the hypersonic db, and I
read everywhere that this is a bad idea in a production environment (I couldn't
find why), so I changed the DefaultDS to use mysql locally, and then I changed
the DataSourceBinding at mysql-jdbc2-service.xml to use it,
Hi, I'm having a very strange behavior with a cluster. The main problem is that
I have diferent datasources, that they appear to start correctly, when I try to
use them I get a NullPointerException. There are some other strange things that
occur:
The first node starts without problem, no
Yes, I get the same Incomplete Deployment listing on all servers, except the
first I start, no matter which of all is. I don't want JMS being clustered, I
want it standalone for each server. The DefaultDS uses a local mysql in each
server. I have two more datasources which they point to two
