[
http://jira.jboss.com/jira/browse/JBAS-1391?page=comments#action_12316308 ]
Adrian Brock commented on JBAS-1391:
I don't like the idea of it always starting from the first url.
Once it has failed over, it should remain sticky on that url until it
[
http://jira.jboss.com/jira/browse/JBAS-1391?page=comments#action_12316249 ]
Alexey Loubyansky commented on JBAS-1391:
-
First step is done.
- local managed connection factory is added in
package org.jboss.resource.adapter.jdbc.local;
public
[
http://jira.jboss.com/jira/browse/JBAS-1391?page=comments#action_12316221 ]
Alexey Loubyansky commented on JBAS-1391:
-
I was asked to look into this. Wouldn't it be easier to have a logical
DataSource that would maintain a list of target
[
http://jira.jboss.com/jira/browse/JBAS-1391?page=comments#action_12316223 ]
Adrian Brock commented on JBAS-1391:
First, it is better to discuss the design in the dev forums.
To answer your question Alex, it can be done both ways.
The DataSource
[
http://jira.jboss.com/jira/browse/JBAS-1391?page=comments#action_12316225 ]
Adrian Brock commented on JBAS-1391:
Sean's comment is entirely unrelated to the problem.
He is talking about *restarting* JBossMQ with a new DataSource/ConnectionURL
[
http://jira.jboss.com/jira/browse/JBAS-1391?page=comments#action_12316228 ]
Alexey Loubyansky commented on JBAS-1391:
-
You are right, Adrian. I'll look at your first suggestion. Thanks.
Add support for datasource failover
[
http://jira.jboss.com/jira/browse/JBAS-1391?page=comments#action_12316230 ]
Adrian Brock commented on JBAS-1391:
There is an even more important problem with the DataSource of DataSources
approach.
Any failover will bypass the transaction
[
http://jira.jboss.com/jira/browse/JBAS-1391?page=comments#action_12315880 ]
Sean Boltman commented on JBAS-1391:
In general there appears to be no database failover capability, but in our
case, our application handles database failover. There
