[ 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 class HALocalManagedConnectionFactory it's very simple (even not thread-safe yet) - ra.xml for this connection factory is added in resources/ha-local-rar - it's packaged into jboss-ha-local-jdbc.rar - the datasource is deployed in -ds.xml with ha-local-tx-datasource which has a new element url-delimeter It worked for a simple testcase that I will add to the testsuite. Any remarks so far? This is in HEAD only for now. Thanks. > Add support for datasource failover > ----------------------------------- > > Key: JBAS-1391 > URL: http://jira.jboss.com/jira/browse/JBAS-1391 > Project: JBoss Application Server > Type: Feature Request > Components: JCA service > Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final > Reporter: Scott M Stark > Assignee: Luc Texier > Fix For: JBossAS-4.0.2 Final > > > The change to > org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory > is easier than org.jboss.resource.adapter.jdbc.xa.XAManagedConnectionFactory > In LocalManagedConnectionFactory add a property "delimiter" > which when present will parse the connectionURL into multiple urls. > In XAManagedConnectionFactory you will also need a property to identify which > of the xaProps needs to be parsed for mulitple urls. > i.e. you need to identify which property contains the server to contact. > In both cases, if createManagedConnection fails for the first url, replace it > with the second url, and try again until all urls are exhausted. > Of course, you can get clever and remember which urls are currently failing > and try the non failing urls first, And also if the db is replicating, you > might want it to "load balance" > connections across the urls? > Also, this design does not allow for using different properties with > different db servers, e.g. user and password might change across the servers. > It also doesn't enforce that only connections from one connectionURL (db > server) are in the pool at the same time in the event the db is not > replicating. > If you are going to do this, I would suggest you subclass/replicate the > managed connection factories and create separate rars so we can mark them as > experimental. > xxxxxxxxxxxxxxxxxxxxxxxx > Adrian Brock > Director of Support > Back Office > JBoss Inc. > xxxxxxxxxxxxxxxxxxxxxxxx -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
