You can subscribe to this list here.
2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(3) |
Aug
(1) |
Sep
(9) |
Oct
(3) |
Nov
|
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2005 |
Jan
(1) |
Feb
(4) |
Mar
(1) |
Apr
(23) |
May
(2) |
Jun
(5) |
Jul
|
Aug
(10) |
Sep
(14) |
Oct
|
Nov
(2) |
Dec
(26) |
2006 |
Jan
(34) |
Feb
(21) |
Mar
(32) |
Apr
(11) |
May
(32) |
Jun
(25) |
Jul
(35) |
Aug
(32) |
Sep
(26) |
Oct
(31) |
Nov
(6) |
Dec
(23) |
2007 |
Jan
(5) |
Feb
(20) |
Mar
(13) |
Apr
(31) |
May
(19) |
Jun
(175) |
Jul
(51) |
Aug
(28) |
Sep
(30) |
Oct
(12) |
Nov
(22) |
Dec
(10) |
2008 |
Jan
(13) |
Feb
(11) |
Mar
(19) |
Apr
(45) |
May
(36) |
Jun
(6) |
Jul
(21) |
Aug
(13) |
Sep
(32) |
Oct
(24) |
Nov
(35) |
Dec
(39) |
2009 |
Jan
(9) |
Feb
|
Mar
(7) |
Apr
(2) |
May
(5) |
Jun
(13) |
Jul
(6) |
Aug
(87) |
Sep
(4) |
Oct
|
Nov
(17) |
Dec
|
2010 |
Jan
(3) |
Feb
(14) |
Mar
(6) |
Apr
(2) |
May
(2) |
Jun
|
Jul
|
Aug
(17) |
Sep
|
Oct
|
Nov
|
Dec
|
2011 |
Jan
(13) |
Feb
|
Mar
|
Apr
(79) |
May
(1) |
Jun
|
Jul
(12) |
Aug
(2) |
Sep
|
Oct
|
Nov
(2) |
Dec
(2) |
2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(6) |
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
(2) |
2013 |
Jan
|
Feb
(3) |
Mar
|
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
2014 |
Jan
(4) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Master Of T. <hi....@bt...> - 2016-05-02 16:35:26
|
... looks like i was missing commons-pool ... seems to be working now. On Mon, May 02, 2016 at 08:41:19AM +0100, Master Of The wrote: > Hi, > > I am having this bit of XML in my cluster config: > > <state id="sqlite"> > <property name="locationPattern">/tmp/{0}</property> > </state> > > However, when I start my application it errors out with this on first > attempt of creating HA-JDBC connection to the cluster (this is probably > where cluster gets initialized): > > java.lang.IllegalArgumentException: java.lang.IllegalArgumentException: No net.sf.hajdbc.state.StateManagerFactory found matching sqlite > > I've tried with H2 SQL state manager as well. Same kind of error just > with 'sql' at the end. > > I am passing cluster config xml file programmatically in properties to > my application's connect() function and everything else works as > expected and advertised. > > Am I missing something required for state manager to start/function > correctly? Regards -- Master Of The Universe hi....@bt... |
From: Master Of T. <hi....@bt...> - 2016-05-02 07:41:27
|
Hi, I am having this bit of XML in my cluster config: <state id="sqlite"> <property name="locationPattern">/tmp/{0}</property> </state> However, when I start my application it errors out with this on first attempt of creating HA-JDBC connection to the cluster (this is probably where cluster gets initialized): java.lang.IllegalArgumentException: java.lang.IllegalArgumentException: No net.sf.hajdbc.state.StateManagerFactory found matching sqlite I've tried with H2 SQL state manager as well. Same kind of error just with 'sql' at the end. I am passing cluster config xml file programmatically in properties to my application's connect() function and everything else works as expected and advertised. Am I missing something required for state manager to start/function correctly? Regards -- Master Of The Universe hi....@bt... |
From: Paul F. <pau...@ca...> - 2014-01-29 00:46:58
|
Response inline. On Wed, 2014-01-29 at 00:31 +0100, Ja kub wrote: > for ha-jdbc-2.0.16-rc-1-jdk1.6.jar I recommend using version 3.0.0 instead. This was released a month ago. > in ha-jdbc-cluster-petclinic.xml > <?xml version="1.0"?> > <ha-jdbc> > <sync id="passive" > class="net.sf.hajdbc.sync.PassiveSynchronizationStrategy"/> > <cluster balancer="round-robin" default-sync="passive" > dialect="mysql" meta-data-cache="none" transaction-mode="serial"> > <datasource id="database1"> > <name>java:comp/env/jdbc/petclinic1</name> > </datasource> > <datasource id="database2"> > <name>java:comp/env/jdbc/petclinic2</name> > </datasource> > </cluster> > </ha-jdbc> > > > > in tomcat/context.xml > > <Context> > <WatchedResource>WEB-INF/web.xml</WatchedResource> > > <Resource name="jdbc/petclinic1" auth="Container" > type="javax.sql.DataSource" > maxActive="100" maxIdle="30" maxWait="10000" > username="root" password="x" > driverClassName="com.mysql.jdbc.Driver" > url="jdbc:mysql://localhost:3306/petclinic"/> > > > <Resource name="jdbc/petclinic2" auth="Container" > type="javax.sql.DataSource" > maxActive="100" maxIdle="30" maxWait="10000" > username="root" password="" > driverClassName="com.mysql.jdbc.Driver" > url="jdbc:mysql://localhost:3306/petclinic"/> > > > > <Resource name="jdbc/petclinic" auth="Container" > type="javax.sql.DataSource" > username="root" password="xxx" > driverClassName="net.sf.hajdbc.sql.Driver" > url="jdbc:ha-jdbc:cluster-petclinic"/> > > below works fine > > <Resource name="jdbc/petclinic" > type="net.sf.hajdbc.sql.DataSource" > factory="org.apache.naming.factory.BeanFactory" > closeMethod="stop" > cluster="datasource" > > config="file:///szkolenie/tomcat/lib_hajdbc/ha-jdbc-cluster-petclinic.xml"/> > > but when I replace it with > > <Resource name="jdbc/petclinic" auth="Container" > type="javax.sql.DataSource" > username="root" password="xxx" > driverClassName="net.sf.hajdbc.sql.Driver" > url="jdbc:ha-jdbc:cluster-petclinic"/> > > </Context> Since the configuration above accesses HA-JDBC via its Driver, you must also access the underlying databases via their driver. You need to chose which configuration you want to use without mixing the two. Remember that Tomcat creates a connection pool for each <Resource type="javax.sql.DataSource/>, so using a connection pool for both the individual databases connections *and* HA-JDBC connection proxies does not make sense. > > I get error: > > Caused by: org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot > create PoolableConnectionFactory (null) > at > org.apache.tomcat.dbcp.dbcp.BasicDataSource.createPoolableConnectionFactory(BasicDataSource.java:1549) ~[tomcat-dbcp.jar:7.0.50] > at > org.apache.tomcat.dbcp.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1388) ~[tomcat-dbcp.jar:7.0.50] > at > org.apache.tomcat.dbcp.dbcp.BasicDataSource.getConnection(BasicDataSource.java:1044) ~[tomcat-dbcp.jar:7.0.50] > at > org.springframework.jdbc.datasource.DataSourceUtils.doGetConnection(DataSourceUtils.java:111) ~[spring-jdbc-4.0.0.RELEASE.jar:4.0.0.RELEASE] > at > org.springframework.jdbc.datasource.DataSourceUtils.getConnection(DataSourceUtils.java:77) ~[spring-jdbc-4.0.0.RELEASE.jar:4.0.0.RELEASE] > ... 30 common frames omitted > Caused by: java.sql.SQLException: null > at > net.sf.hajdbc.util.SQLExceptionFactory.createSQLException(SQLExceptionFactory.java:58) ~[ha-jdbc-2.0.16-rc-1-jdk1.6.jar:na] > at > net.sf.hajdbc.DatabaseClusterFactory.getDatabaseCluster(DatabaseClusterFactory.java:125) ~[ha-jdbc-2.0.16-rc-1-jdk1.6.jar:na] > at net.sf.hajdbc.sql.Driver.getDatabaseCluster(Driver.java:180) > ~[ha-jdbc-2.0.16-rc-1-jdk1.6.jar:na] > at net.sf.hajdbc.sql.Driver.connect(Driver.java:84) > ~[ha-jdbc-2.0.16-rc-1-jdk1.6.jar:na] > at > org.apache.tomcat.dbcp.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:38) ~[tomcat-dbcp.jar:7.0.50] > at > org.apache.tomcat.dbcp.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:582) ~[tomcat-dbcp.jar:7.0.50] > at > org.apache.tomcat.dbcp.dbcp.BasicDataSource.validateConnectionFactory(BasicDataSource.java:1556) ~[tomcat-dbcp.jar:7.0.50] > at > org.apache.tomcat.dbcp.dbcp.BasicDataSource.createPoolableConnectionFactory(BasicDataSource.java:1545) ~[tomcat-dbcp.jar:7.0.50] > ... 34 common frames omitted > Caused by: javax.management.MBeanRegistrationException: Exception > thrown in preRegister method > at > com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.preRegisterInvoke(DefaultMBeanServerInterceptor.java:1020) ~[na:1.6.0_37] > at > com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:938) ~[na:1.6.0_37] > at > com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:917) ~[na:1.6.0_37] > at > com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:312) ~[na:1.6.0_37] > at > com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:482) ~[na:1.6.0_37] > at > net.sf.hajdbc.DatabaseClusterFactory.getDatabaseCluster(DatabaseClusterFactory.java:118) ~[ha-jdbc-2.0.16-rc-1-jdk1.6.jar:na] > ... 40 common frames omitted > Caused by: org.jibx.runtime.JiBXException: Expected "cluster" end tag, > found "datasource" start tag (line 5, col 30) > at > org.jibx.runtime.impl.UnmarshallingContext.parsePastCurrentEndTag(UnmarshallingContext.java:736) ~[jibx-run-1.2.1.jar:1.2.1] > at > net.sf.hajdbc.sql.DriverDatabaseCluster.JiBX_binding_driver_unmarshal_2_0(DriverDatabaseCluster.java) ~[ha-jdbc-2.0.16-rc-1-jdk1.6.jar:na] > at > net.sf.hajdbc.sql.JiBX_binding_driverDriverDatabaseCluster_access.unmarshal() ~[ha-jdbc-2.0.16-rc-1-jdk1.6.jar:na] > at > org.jibx.runtime.impl.UnmarshallingContext.unmarshalElement(UnmarshallingContext.java:2762) ~[jibx-run-1.2.1.jar:1.2.1] > at > net.sf.hajdbc.sql.AbstractDatabaseCluster.preRegister(AbstractDatabaseCluster.java:1045) ~[ha-jdbc-2.0.16-rc-1-jdk1.6.jar:na] > at > com.sun.jmx.mbeanserver.MBeanSupport.preRegister(MBeanSupport.java:176) ~[na:1.6.0_37] > at > com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.preRegisterInvoke(DefaultMBeanServerInterceptor.java:1010) ~[na:1.6.0_37] > ... 45 common frames omitted > Jan 29, 2014 12:10:54 AM org.apache.catalina.core.StandardContext > startInternal > SEVERE: Error listenerStart > > > ha-jdbc-cluster-petclinic.xml is the same in both cases, is parsed in > first case, but cannot be parsed in second case > > > Where is the problem ? > > > BR > > J. > > ------------------------------------------------------------------------------ > WatchGuard Dimension instantly turns raw network data into actionable > security intelligence. It gives you real-time visual feedback on key > security issues and trends. Skip the complicated setup - simply import > a virtual appliance and go from zero to informed in seconds. > http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.clktrk > _______________________________________________ > ha-jdbc-user mailing list > ha-...@li... > https://lists.sourceforge.net/lists/listinfo/ha-jdbc-user |
From: Paul F. <pau...@ca...> - 2014-01-29 00:40:07
|
You are attempting to access HA-JDBC by its JDBC Driver. In doing so, you must also access the underlying databases via their drivers. The configuration you pasted below is a DataSource configuration, and therefore must be accessed via the net.sf.hajdbc.sql.DataSource. On Tue, 2014-01-28 at 17:00 +0100, Ja kub wrote: > I get > No registered driver will accept url java:comp/env/jdbc/petclinic1 > > with config: > > <ha-jdbc xmlns="urn:ha-jdbc:cluster:3.0"> > <sync id="passive" ></sync> > <cluster balancer="round-robin" dialect="mysql" > default-sync="passive" > > <database id="database1" > location="java:comp/env/jdbc/petclinic1" weight="1"> > </database> > > <database id="database2" > location="java:comp/env/jdbc/petclinic2" weight="1"> > </database> > > </cluster> > </ha-jdbc> > > datasource tag is no longer valid > <datasource id="database1"> > <name>java:comp/env/jdbc/petclinic1</name> > </datasource> > > > do I do sth wrong ? > > here is full stack trace: > > ERROR ContextLoader - Context initialization failed > org.springframework.beans.factory.BeanCreationException: Error > creating bean with name > 'org.springframework.jdbc.datasource.init.DataSourceInitializer#0': > Invocation of init method failed; nested exception is > org.springframework.dao.DataAccessResourceFailureException: Failed to > execute database script; nested exception is > org.springframework.jdbc.CannotGetJdbcConnectionException: Could not > get JDBC Connection; nested exception is > org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create > PoolableConnectionFactory (No registered driver will accept url > java:comp/env/jdbc/petclinic1) > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1553) ~[spring-beans-4.0.0.RELEASE.jar:4.0.0.RELEASE] > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:539) ~[spring-beans-4.0.0.RELEASE.jar:4.0.0.RELEASE] > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:475) ~[spring-beans-4.0.0.RELEASE.jar:4.0.0.RELEASE] > at org.springframework.beans.factory.support.AbstractBeanFactory > $1.getObject(AbstractBeanFactory.java:304) > ~[spring-beans-4.0.0.RELEASE.jar:4.0.0.RELEASE] > at > org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:228) ~[spring-beans-4.0.0.RELEASE.jar:4.0.0.RELEASE] > at > org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:300) ~[spring-beans-4.0.0.RELEASE.jar:4.0.0.RELEASE] > at > org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:195) ~[spring-beans-4.0.0.RELEASE.jar:4.0.0.RELEASE] > at > org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:700) ~[spring-beans-4.0.0.RELEASE.jar:4.0.0.RELEASE] > at > org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:760) ~[spring-context-4.0.0.RELEASE.jar:4.0.0.RELEASE] > at > org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:482) ~[spring-context-4.0.0.RELEASE.jar:4.0.0.RELEASE] > at > org.springframework.web.context.ContextLoader.configureAndRefreshWebApplicationContext(ContextLoader.java:381) ~[spring-web-4.0.0.RELEASE.jar:4.0.0.RELEASE] > at > org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:293) ~[spring-web-4.0.0.RELEASE.jar:4.0.0.RELEASE] > at > org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:106) [spring-web-4.0.0.RELEASE.jar:4.0.0.RELEASE] > at > org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4961) [catalina.jar:7.0.50] > at > org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5455) [catalina.jar:7.0.50] > at > org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) > [catalina.jar:7.0.50] > at > org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901) [catalina.jar:7.0.50] > at > org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877) [catalina.jar:7.0.50] > at > org.apache.catalina.core.StandardHost.addChild(StandardHost.java:634) > [catalina.jar:7.0.50] > at > org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:1074) > [catalina.jar:7.0.50] > at org.apache.catalina.startup.HostConfig > $DeployWar.run(HostConfig.java:1858) [catalina.jar:7.0.50] > at java.util.concurrent.Executors > $RunnableAdapter.call(Executors.java:471) [na:1.7.0_21] > at java.util.concurrent.FutureTask > $Sync.innerRun(FutureTask.java:334) [na:1.7.0_21] > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > [na:1.7.0_21] > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [na:1.7.0_21] > at java.util.concurrent.ThreadPoolExecutor > $Worker.run(ThreadPoolExecutor.java:615) [na:1.7.0_21] > at java.lang.Thread.run(Thread.java:722) [na:1.7.0_21] > Caused by: org.springframework.dao.DataAccessResourceFailureException: > Failed to execute database script; nested exception is > org.springframework.jdbc.CannotGetJdbcConnectionException: Could not > get JDBC Connection; nested exception is > org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create > PoolableConnectionFactory (No registered driver will accept url > java:comp/env/jdbc/petclinic1) > at > org.springframework.jdbc.datasource.init.DatabasePopulatorUtils.execute(DatabasePopulatorUtils.java:56) ~[spring-jdbc-4.0.0.RELEASE.jar:4.0.0.RELEASE] > at > org.springframework.jdbc.datasource.init.DataSourceInitializer.afterPropertiesSet(DataSourceInitializer.java:84) ~[spring-jdbc-4.0.0.RELEASE.jar:4.0.0.RELEASE] > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1612) ~[spring-beans-4.0.0.RELEASE.jar:4.0.0.RELEASE] > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1549) ~[spring-beans-4.0.0.RELEASE.jar:4.0.0.RELEASE] > ... 26 common frames omitted > Caused by: org.springframework.jdbc.CannotGetJdbcConnectionException: > Could not get JDBC Connection; nested exception is > org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create > PoolableConnectionFactory (No registered driver will accept url > java:comp/env/jdbc/petclinic1) > at > org.springframework.jdbc.datasource.DataSourceUtils.getConnection(DataSourceUtils.java:80) ~[spring-jdbc-4.0.0.RELEASE.jar:4.0.0.RELEASE] > at > org.springframework.jdbc.datasource.init.DatabasePopulatorUtils.execute(DatabasePopulatorUtils.java:45) ~[spring-jdbc-4.0.0.RELEASE.jar:4.0.0.RELEASE] > ... 29 common frames omitted > Caused by: org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot > create PoolableConnectionFactory (No registered driver will accept url > java:comp/env/jdbc/petclinic1) > at > org.apache.tomcat.dbcp.dbcp.BasicDataSource.createPoolableConnectionFactory(BasicDataSource.java:1549) ~[tomcat-dbcp.jar:7.0.50] > at > org.apache.tomcat.dbcp.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1388) ~[tomcat-dbcp.jar:7.0.50] > at > org.apache.tomcat.dbcp.dbcp.BasicDataSource.getConnection(BasicDataSource.java:1044) ~[tomcat-dbcp.jar:7.0.50] > at > org.springframework.jdbc.datasource.DataSourceUtils.doGetConnection(DataSourceUtils.java:111) ~[spring-jdbc-4.0.0.RELEASE.jar:4.0.0.RELEASE] > at > org.springframework.jdbc.datasource.DataSourceUtils.getConnection(DataSourceUtils.java:77) ~[spring-jdbc-4.0.0.RELEASE.jar:4.0.0.RELEASE] > ... 30 common frames omitted > Caused by: java.sql.SQLException: No registered driver will accept url > java:comp/env/jdbc/petclinic1 > at > net.sf.hajdbc.sql.SQLExceptionFactory.createException(SQLExceptionFactory.java:51) ~[ha-jdbc-3.0.0.jar:3.0.0] > at > net.sf.hajdbc.sql.SQLExceptionFactory.createException(SQLExceptionFactory.java:35) ~[ha-jdbc-3.0.0.jar:3.0.0] > at > net.sf.hajdbc.AbstractExceptionFactory.createException(AbstractExceptionFactory.java:62) ~[ha-jdbc-3.0.0.jar:3.0.0] > at > net.sf.hajdbc.util.concurrent.LifecycleRegistry.get(LifecycleRegistry.java:95) ~[ha-jdbc-3.0.0.jar:3.0.0] > at > net.sf.hajdbc.util.concurrent.LifecycleRegistry.get(LifecycleRegistry.java:34) ~[ha-jdbc-3.0.0.jar:3.0.0] > at net.sf.hajdbc.sql.Driver.connect(Driver.java:139) > ~[ha-jdbc-3.0.0.jar:3.0.0] > at > org.apache.tomcat.dbcp.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:38) ~[tomcat-dbcp.jar:7.0.50] > at > org.apache.tomcat.dbcp.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:582) ~[tomcat-dbcp.jar:7.0.50] > at > org.apache.tomcat.dbcp.dbcp.BasicDataSource.validateConnectionFactory(BasicDataSource.java:1556) ~[tomcat-dbcp.jar:7.0.50] > at > org.apache.tomcat.dbcp.dbcp.BasicDataSource.createPoolableConnectionFactory(BasicDataSource.java:1545) ~[tomcat-dbcp.jar:7.0.50] > ... 34 common frames omitted > Caused by: java.lang.IllegalArgumentException: No registered driver > will accept url java:comp/env/jdbc/petclinic1 > at > net.sf.hajdbc.sql.DriverDatabase.getDriver(DriverDatabase.java:110) > ~[ha-jdbc-3.0.0.jar:3.0.0] > at > net.sf.hajdbc.sql.DriverDatabase.createConnectionSource(DriverDatabase.java:93) ~[ha-jdbc-3.0.0.jar:3.0.0] > at > net.sf.hajdbc.sql.DriverDatabase.createConnectionSource(DriverDatabase.java:39) ~[ha-jdbc-3.0.0.jar:3.0.0] > at > net.sf.hajdbc.sql.DatabaseClusterImpl.isAlive(DatabaseClusterImpl.java:834) ~[ha-jdbc-3.0.0.jar:3.0.0] > at > net.sf.hajdbc.sql.DatabaseClusterImpl.start(DatabaseClusterImpl.java:708) ~[ha-jdbc-3.0.0.jar:3.0.0] > at > net.sf.hajdbc.util.concurrent.LifecycleRegistry.get(LifecycleRegistry.java:76) ~[ha-jdbc-3.0.0.jar:3.0.0] > ... 40 common frames omitted > Caused by: java.sql.SQLException: No suitable driver > at java.sql.DriverManager.getDriver(DriverManager.java:289) > ~[na:1.7.0_21] > at > net.sf.hajdbc.sql.DriverDatabase.getDriver(DriverDatabase.java:106) > ~[ha-jdbc-3.0.0.jar:3.0.0] > ... 45 common frames omitted > Jan 28, 2014 4:54:16 PM org.apache.catalina.core.StandardContext > startInternal > SEVERE: Error listenerStart > > > BR > J. > > ------------------------------------------------------------------------------ > WatchGuard Dimension instantly turns raw network data into actionable > security intelligence. It gives you real-time visual feedback on key > security issues and trends. Skip the complicated setup - simply import > a virtual appliance and go from zero to informed in seconds. > http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.clktrk > _______________________________________________ > ha-jdbc-user mailing list > ha-...@li... > https://lists.sourceforge.net/lists/listinfo/ha-jdbc-user |
From: Ja k. <jja...@gm...> - 2014-01-28 23:31:38
|
for ha-jdbc-2.0.16-rc-1-jdk1.6.jar in ha-jdbc-cluster-petclinic.xml <?xml version="1.0"?> <ha-jdbc> <sync id="passive" class="net.sf.hajdbc.sync.PassiveSynchronizationStrategy"/> <cluster balancer="round-robin" default-sync="passive" dialect="mysql" meta-data-cache="none" transaction-mode="serial"> <datasource id="database1"> <name>java:comp/env/jdbc/petclinic1</name> </datasource> <datasource id="database2"> <name>java:comp/env/jdbc/petclinic2</name> </datasource> </cluster> </ha-jdbc> in tomcat/context.xml <Context> <WatchedResource>WEB-INF/web.xml</WatchedResource> <Resource name="jdbc/petclinic1" auth="Container" type="javax.sql.DataSource" maxActive="100" maxIdle="30" maxWait="10000" username="root" password="x" driverClassName="com.mysql.jdbc.Driver" url="jdbc:mysql://localhost:3306/petclinic"/> <Resource name="jdbc/petclinic2" auth="Container" type="javax.sql.DataSource" maxActive="100" maxIdle="30" maxWait="10000" username="root" password="" driverClassName="com.mysql.jdbc.Driver" url="jdbc:mysql://localhost:3306/petclinic"/> <Resource name="jdbc/petclinic" auth="Container" type="javax.sql.DataSource" username="root" password="xxx" driverClassName="net.sf.hajdbc.sql.Driver" url="jdbc:ha-jdbc:cluster-petclinic"/> below works fine <Resource name="jdbc/petclinic" type="net.sf.hajdbc.sql.DataSource" factory="org.apache.naming.factory.BeanFactory" closeMethod="stop" cluster="datasource" config="file:///szkolenie/tomcat/lib_hajdbc/ha-jdbc-cluster-petclinic.xml"/> but when I replace it with <Resource name="jdbc/petclinic" auth="Container" type="javax.sql.DataSource" username="root" password="xxx" driverClassName="net.sf.hajdbc.sql.Driver" url="jdbc:ha-jdbc:cluster-petclinic"/> </Context> I get error: Caused by: org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (null) at org.apache.tomcat.dbcp.dbcp.BasicDataSource.createPoolableConnectionFactory(BasicDataSource.java:1549) ~[tomcat-dbcp.jar:7.0.50] at org.apache.tomcat.dbcp.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1388) ~[tomcat-dbcp.jar:7.0.50] at org.apache.tomcat.dbcp.dbcp.BasicDataSource.getConnection(BasicDataSource.java:1044) ~[tomcat-dbcp.jar:7.0.50] at org.springframework.jdbc.datasource.DataSourceUtils.doGetConnection(DataSourceUtils.java:111) ~[spring-jdbc-4.0.0.RELEASE.jar:4.0.0.RELEASE] at org.springframework.jdbc.datasource.DataSourceUtils.getConnection(DataSourceUtils.java:77) ~[spring-jdbc-4.0.0.RELEASE.jar:4.0.0.RELEASE] ... 30 common frames omitted Caused by: java.sql.SQLException: null at net.sf.hajdbc.util.SQLExceptionFactory.createSQLException(SQLExceptionFactory.java:58) ~[ha-jdbc-2.0.16-rc-1-jdk1.6.jar:na] at net.sf.hajdbc.DatabaseClusterFactory.getDatabaseCluster(DatabaseClusterFactory.java:125) ~[ha-jdbc-2.0.16-rc-1-jdk1.6.jar:na] at net.sf.hajdbc.sql.Driver.getDatabaseCluster(Driver.java:180) ~[ha-jdbc-2.0.16-rc-1-jdk1.6.jar:na] at net.sf.hajdbc.sql.Driver.connect(Driver.java:84) ~[ha-jdbc-2.0.16-rc-1-jdk1.6.jar:na] at org.apache.tomcat.dbcp.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:38) ~[tomcat-dbcp.jar:7.0.50] at org.apache.tomcat.dbcp.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:582) ~[tomcat-dbcp.jar:7.0.50] at org.apache.tomcat.dbcp.dbcp.BasicDataSource.validateConnectionFactory(BasicDataSource.java:1556) ~[tomcat-dbcp.jar:7.0.50] at org.apache.tomcat.dbcp.dbcp.BasicDataSource.createPoolableConnectionFactory(BasicDataSource.java:1545) ~[tomcat-dbcp.jar:7.0.50] ... 34 common frames omitted Caused by: javax.management.MBeanRegistrationException: Exception thrown in preRegister method at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.preRegisterInvoke(DefaultMBeanServerInterceptor.java:1020) ~[na:1.6.0_37] at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:938) ~[na:1.6.0_37] at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:917) ~[na:1.6.0_37] at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:312) ~[na:1.6.0_37] at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:482) ~[na:1.6.0_37] at net.sf.hajdbc.DatabaseClusterFactory.getDatabaseCluster(DatabaseClusterFactory.java:118) ~[ha-jdbc-2.0.16-rc-1-jdk1.6.jar:na] ... 40 common frames omitted Caused by: org.jibx.runtime.JiBXException: Expected "cluster" end tag, found "datasource" start tag (line 5, col 30) at org.jibx.runtime.impl.UnmarshallingContext.parsePastCurrentEndTag(UnmarshallingContext.java:736) ~[jibx-run-1.2.1.jar:1.2.1] at net.sf.hajdbc.sql.DriverDatabaseCluster.JiBX_binding_driver_unmarshal_2_0(DriverDatabaseCluster.java) ~[ha-jdbc-2.0.16-rc-1-jdk1.6.jar:na] at net.sf.hajdbc.sql.JiBX_binding_driverDriverDatabaseCluster_access.unmarshal() ~[ha-jdbc-2.0.16-rc-1-jdk1.6.jar:na] at org.jibx.runtime.impl.UnmarshallingContext.unmarshalElement(UnmarshallingContext.java:2762) ~[jibx-run-1.2.1.jar:1.2.1] at net.sf.hajdbc.sql.AbstractDatabaseCluster.preRegister(AbstractDatabaseCluster.java:1045) ~[ha-jdbc-2.0.16-rc-1-jdk1.6.jar:na] at com.sun.jmx.mbeanserver.MBeanSupport.preRegister(MBeanSupport.java:176) ~[na:1.6.0_37] at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.preRegisterInvoke(DefaultMBeanServerInterceptor.java:1010) ~[na:1.6.0_37] ... 45 common frames omitted Jan 29, 2014 12:10:54 AM org.apache.catalina.core.StandardContext startInternal SEVERE: Error listenerStart ha-jdbc-cluster-petclinic.xml is the same in both cases, is parsed in first case, but cannot be parsed in second case Where is the problem ? BR J. |
From: Ja k. <jja...@gm...> - 2014-01-28 16:00:46
|
I get No registered driver will accept url java:comp/env/jdbc/petclinic1 with config: <ha-jdbc xmlns="urn:ha-jdbc:cluster:3.0"> <sync id="passive" ></sync> <cluster balancer="round-robin" dialect="mysql" default-sync="passive" > <database id="database1" location="java:comp/env/jdbc/petclinic1" weight="1"> </database> <database id="database2" location="java:comp/env/jdbc/petclinic2" weight="1"> </database> </cluster> </ha-jdbc> datasource tag is no longer valid <datasource id="database1"> <name>java:comp/env/jdbc/petclinic1</name> </datasource> do I do sth wrong ? here is full stack trace: ERROR ContextLoader - Context initialization failed org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.springframework.jdbc.datasource.init.DataSourceInitializer#0': Invocation of init method failed; nested exception is org.springframework.dao.DataAccessResourceFailureException: Failed to execute database script; nested exception is org.springframework.jdbc.CannotGetJdbcConnectionException: Could not get JDBC Connection; nested exception is org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (No registered driver will accept url java:comp/env/jdbc/petclinic1) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1553) ~[spring-beans-4.0.0.RELEASE.jar:4.0.0.RELEASE] at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:539) ~[spring-beans-4.0.0.RELEASE.jar:4.0.0.RELEASE] at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:475) ~[spring-beans-4.0.0.RELEASE.jar:4.0.0.RELEASE] at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:304) ~[spring-beans-4.0.0.RELEASE.jar:4.0.0.RELEASE] at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:228) ~[spring-beans-4.0.0.RELEASE.jar:4.0.0.RELEASE] at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:300) ~[spring-beans-4.0.0.RELEASE.jar:4.0.0.RELEASE] at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:195) ~[spring-beans-4.0.0.RELEASE.jar:4.0.0.RELEASE] at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:700) ~[spring-beans-4.0.0.RELEASE.jar:4.0.0.RELEASE] at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:760) ~[spring-context-4.0.0.RELEASE.jar:4.0.0.RELEASE] at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:482) ~[spring-context-4.0.0.RELEASE.jar:4.0.0.RELEASE] at org.springframework.web.context.ContextLoader.configureAndRefreshWebApplicationContext(ContextLoader.java:381) ~[spring-web-4.0.0.RELEASE.jar:4.0.0.RELEASE] at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:293) ~[spring-web-4.0.0.RELEASE.jar:4.0.0.RELEASE] at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:106) [spring-web-4.0.0.RELEASE.jar:4.0.0.RELEASE] at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4961) [catalina.jar:7.0.50] at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5455) [catalina.jar:7.0.50] at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) [catalina.jar:7.0.50] at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901) [catalina.jar:7.0.50] at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877) [catalina.jar:7.0.50] at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:634) [catalina.jar:7.0.50] at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:1074) [catalina.jar:7.0.50] at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1858) [catalina.jar:7.0.50] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [na:1.7.0_21] at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [na:1.7.0_21] at java.util.concurrent.FutureTask.run(FutureTask.java:166) [na:1.7.0_21] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [na:1.7.0_21] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [na:1.7.0_21] at java.lang.Thread.run(Thread.java:722) [na:1.7.0_21] Caused by: org.springframework.dao.DataAccessResourceFailureException: Failed to execute database script; nested exception is org.springframework.jdbc.CannotGetJdbcConnectionException: Could not get JDBC Connection; nested exception is org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (No registered driver will accept url java:comp/env/jdbc/petclinic1) at org.springframework.jdbc.datasource.init.DatabasePopulatorUtils.execute(DatabasePopulatorUtils.java:56) ~[spring-jdbc-4.0.0.RELEASE.jar:4.0.0.RELEASE] at org.springframework.jdbc.datasource.init.DataSourceInitializer.afterPropertiesSet(DataSourceInitializer.java:84) ~[spring-jdbc-4.0.0.RELEASE.jar:4.0.0.RELEASE] at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1612) ~[spring-beans-4.0.0.RELEASE.jar:4.0.0.RELEASE] at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1549) ~[spring-beans-4.0.0.RELEASE.jar:4.0.0.RELEASE] ... 26 common frames omitted Caused by: org.springframework.jdbc.CannotGetJdbcConnectionException: Could not get JDBC Connection; nested exception is org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (No registered driver will accept url java:comp/env/jdbc/petclinic1) at org.springframework.jdbc.datasource.DataSourceUtils.getConnection(DataSourceUtils.java:80) ~[spring-jdbc-4.0.0.RELEASE.jar:4.0.0.RELEASE] at org.springframework.jdbc.datasource.init.DatabasePopulatorUtils.execute(DatabasePopulatorUtils.java:45) ~[spring-jdbc-4.0.0.RELEASE.jar:4.0.0.RELEASE] ... 29 common frames omitted Caused by: org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (No registered driver will accept url java:comp/env/jdbc/petclinic1) at org.apache.tomcat.dbcp.dbcp.BasicDataSource.createPoolableConnectionFactory(BasicDataSource.java:1549) ~[tomcat-dbcp.jar:7.0.50] at org.apache.tomcat.dbcp.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1388) ~[tomcat-dbcp.jar:7.0.50] at org.apache.tomcat.dbcp.dbcp.BasicDataSource.getConnection(BasicDataSource.java:1044) ~[tomcat-dbcp.jar:7.0.50] at org.springframework.jdbc.datasource.DataSourceUtils.doGetConnection(DataSourceUtils.java:111) ~[spring-jdbc-4.0.0.RELEASE.jar:4.0.0.RELEASE] at org.springframework.jdbc.datasource.DataSourceUtils.getConnection(DataSourceUtils.java:77) ~[spring-jdbc-4.0.0.RELEASE.jar:4.0.0.RELEASE] ... 30 common frames omitted Caused by: java.sql.SQLException: No registered driver will accept url java:comp/env/jdbc/petclinic1 at net.sf.hajdbc.sql.SQLExceptionFactory.createException(SQLExceptionFactory.java:51) ~[ha-jdbc-3.0.0.jar:3.0.0] at net.sf.hajdbc.sql.SQLExceptionFactory.createException(SQLExceptionFactory.java:35) ~[ha-jdbc-3.0.0.jar:3.0.0] at net.sf.hajdbc.AbstractExceptionFactory.createException(AbstractExceptionFactory.java:62) ~[ha-jdbc-3.0.0.jar:3.0.0] at net.sf.hajdbc.util.concurrent.LifecycleRegistry.get(LifecycleRegistry.java:95) ~[ha-jdbc-3.0.0.jar:3.0.0] at net.sf.hajdbc.util.concurrent.LifecycleRegistry.get(LifecycleRegistry.java:34) ~[ha-jdbc-3.0.0.jar:3.0.0] at net.sf.hajdbc.sql.Driver.connect(Driver.java:139) ~[ha-jdbc-3.0.0.jar:3.0.0] at org.apache.tomcat.dbcp.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:38) ~[tomcat-dbcp.jar:7.0.50] at org.apache.tomcat.dbcp.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:582) ~[tomcat-dbcp.jar:7.0.50] at org.apache.tomcat.dbcp.dbcp.BasicDataSource.validateConnectionFactory(BasicDataSource.java:1556) ~[tomcat-dbcp.jar:7.0.50] at org.apache.tomcat.dbcp.dbcp.BasicDataSource.createPoolableConnectionFactory(BasicDataSource.java:1545) ~[tomcat-dbcp.jar:7.0.50] ... 34 common frames omitted Caused by: java.lang.IllegalArgumentException: No registered driver will accept url java:comp/env/jdbc/petclinic1 at net.sf.hajdbc.sql.DriverDatabase.getDriver(DriverDatabase.java:110) ~[ha-jdbc-3.0.0.jar:3.0.0] at net.sf.hajdbc.sql.DriverDatabase.createConnectionSource(DriverDatabase.java:93) ~[ha-jdbc-3.0.0.jar:3.0.0] at net.sf.hajdbc.sql.DriverDatabase.createConnectionSource(DriverDatabase.java:39) ~[ha-jdbc-3.0.0.jar:3.0.0] at net.sf.hajdbc.sql.DatabaseClusterImpl.isAlive(DatabaseClusterImpl.java:834) ~[ha-jdbc-3.0.0.jar:3.0.0] at net.sf.hajdbc.sql.DatabaseClusterImpl.start(DatabaseClusterImpl.java:708) ~[ha-jdbc-3.0.0.jar:3.0.0] at net.sf.hajdbc.util.concurrent.LifecycleRegistry.get(LifecycleRegistry.java:76) ~[ha-jdbc-3.0.0.jar:3.0.0] ... 40 common frames omitted Caused by: java.sql.SQLException: No suitable driver at java.sql.DriverManager.getDriver(DriverManager.java:289) ~[na:1.7.0_21] at net.sf.hajdbc.sql.DriverDatabase.getDriver(DriverDatabase.java:106) ~[ha-jdbc-3.0.0.jar:3.0.0] ... 45 common frames omitted Jan 28, 2014 4:54:16 PM org.apache.catalina.core.StandardContext startInternal SEVERE: Error listenerStart BR J. |
From: Paul F. <pau...@ca...> - 2013-08-09 15:08:30
|
I agree - this is a valid use case. I don't foresee this logic causing any issues. We'd still want to set the dirty flag, I think, so that the change can be persisted back to the configuration file. Paul On Thu, Aug 8, 2013 at 3:24 PM, Steve Jones <ste...@eu...>wrote: > > In our usage of HA-JDBC we are using the simple balancer type to direct > requests to the node with the highest weight. > > At runtime nodes can be activated and deactivated and we want to be able > to change the node weights to direct traffic to the "primary" node. > > For example, we may start off with: > > Node A : weight 2 > Node B : weight 1 > > If node A is deactivated, we would want the nodes to be: > > Node B : weight 2 > > so any nodes activated subsequently will have lower weights. At the > moment we would have to deactivate B in order to change the weight. > > >From a very quick review it looks as though it is safe to change the > weight when active so I am wondering if this is a valid use case for > which I could submit a pull request. > > As far as implementation goes I assume that if the weight could be > changed when active then the dirty flag should not be set and the weight > field should be declared volatile. > > Thanks, > Steve > > > > ------------------------------------------------------------------------------ > Get 100% visibility into Java/.NET code with AppDynamics Lite! > It's a free troubleshooting tool designed for production. > Get down to code-level detail for bottlenecks, with <2% overhead. > Download for free and get started troubleshooting in minutes. > http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk > _______________________________________________ > ha-jdbc-user mailing list > ha-...@li... > https://lists.sourceforge.net/lists/listinfo/ha-jdbc-user > |
From: Steve J. <ste...@eu...> - 2013-08-08 19:24:52
|
In our usage of HA-JDBC we are using the simple balancer type to direct requests to the node with the highest weight. At runtime nodes can be activated and deactivated and we want to be able to change the node weights to direct traffic to the "primary" node. For example, we may start off with: Node A : weight 2 Node B : weight 1 If node A is deactivated, we would want the nodes to be: Node B : weight 2 so any nodes activated subsequently will have lower weights. At the moment we would have to deactivate B in order to change the weight. >From a very quick review it looks as though it is safe to change the weight when active so I am wondering if this is a valid use case for which I could submit a pull request. As far as implementation goes I assume that if the weight could be changed when active then the dirty flag should not be set and the weight field should be declared volatile. Thanks, Steve |
From: Paul F. <pau...@ca...> - 2013-07-22 13:28:56
|
This logic hasn't changed between 2.0.x and 2.1.x. HA-JDBC will attempt to call close() on any accessible JDBC objects created on the deactivated database. However, this only occurs if the database was deactivated within the context of application code, since only the application code contains references to the proxy objects it creates. In any other context, these objects will get closed on subsequent use. Also, calling Connection.close() cannot close the physical connection if the Connection itself is a connection pooling proxy. In this case, Connection.close() only returns the connection to the pool but does not close it. For this reason, I typically recommend that users enable testOnBorrow (for example, when using DBCP) when using HA-JDBC in conjunction with a connection pool. On Fri, 2013-07-19 at 10:55 -0700, Steve Jones wrote: > It looks like there is a change in behavior somewhere between the latest > code and 2.0.16-rc-1. I didn't notice any explicit guidelines in the > documentation so am not clear if this is expected behavior. > > When a database is deactivated and removed from a cluster the JDBC > connections to the removed database remain open. In 2.0.16-rc-1 I > believe they were closed when this occurred. In the latest code it looks > like the connections to the removed database are closed on use of the > proxy connection (in AbstractProxyFactory.retain) > > This means it is now necessary to refresh all connections in a pool to > ensure that connections to a removed database are closed. > > If this is a bug, I would be happy to contribute a fix given some > direction. > > Thanks, > Steve > > > ------------------------------------------------------------------------------ > See everything from the browser to the database with AppDynamics > Get end-to-end visibility with application monitoring from AppDynamics > Isolate bottlenecks and diagnose root cause in seconds. > Start your free trial of AppDynamics Pro today! > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > _______________________________________________ > ha-jdbc-user mailing list > ha-...@li... > https://lists.sourceforge.net/lists/listinfo/ha-jdbc-user |
From: Steve J. <ste...@eu...> - 2013-07-19 18:17:52
|
It looks like there is a change in behavior somewhere between the latest code and 2.0.16-rc-1. I didn't notice any explicit guidelines in the documentation so am not clear if this is expected behavior. When a database is deactivated and removed from a cluster the JDBC connections to the removed database remain open. In 2.0.16-rc-1 I believe they were closed when this occurred. In the latest code it looks like the connections to the removed database are closed on use of the proxy connection (in AbstractProxyFactory.retain) This means it is now necessary to refresh all connections in a pool to ensure that connections to a removed database are closed. If this is a bug, I would be happy to contribute a fix given some direction. Thanks, Steve |
From: Paul F. <pau...@ca...> - 2013-02-15 18:24:58
|
My guess is that the Ingres driver does not implement Connection.isValid(...). Can you verify this? If it does not, try creating a custom DialectFactory that returns a class extending net.sf.hajdbc.dialect.ingres.IngresDialect and provide a custom implementation of Dialect.isValid(Connection). Details here: http://ha-jdbc.github.com/doc.html#Customizing_HA-JDBC It seems that many JDBC drivers don't yet implement this JDBC 4.0 method. In the meantime, I'll add an implementation of this method to IngresDialect. HA-JDBC doesn't need to know the driver class because, as of Java 1.6, the DriverManager uses a ServiceLoader to load all driver classes on the classpath. HA-JDBC uses this same mechanism to locate component implementations (which is why you won't need to specify the class name of your custom dialect). Paul On Fri, 2013-02-15 at 18:02 +0100, Nicolas Chapurlat wrote: > Hi everybody, > > > I'm trying to use HA-JDBC. > > > I tried with version 2.0 and it works (except some problem with > auto-activate-schedule and failure-detect-schedule cron exception but > this is not the point). > > > I tried with version 2.1-beta3 but I encountered some problems. > (I'm interested by bug fixes and maven dependency management) > > > I get an error message : "Cannot connect to database myDb" > > > My global requirement is the following : > > > - database : Ingres/Vectorwise > - driver : latest Ingres driver > - connection using driver/url > - application developped using playframework2 (java/scala) > - many connections (~ 500) for a database driven application > - read only access to the database > - several instance of the database > > > I added needed dependencies : > > > - "commons-pool" % "commons-pool" % "1.6" > - "commons-codec" % "commons-codec" % "1.7" > - "commons-logging" % "commons-logging" % "1.1" > - "org.jboss.logging" % "jboss-logging" % "3.1.2.GA" > - "org.jgroups" % "jgroups" % "3.2.4.Final" > - "org.slf4j" % "slf4j-api" % "1.7.2" > - "org.tmatesoft.sqljet" % "sqljet" % "1.1.5" > - "com.sleepycat" % "je" % "5.0.58" > > > > Here is my HA-JDBC Driver configuration : > (syntax is play specific but completly understandable) > > > db.myDb.driver=net.sf.hajdbc.sql.Driver > db.myDb.url="jdbc:ha-jdbc:ingres-cluster-1" > db.myDb.user=ingres > db.myDb.password=ingres > db.myDb.disableJMX=false > db.myDb.autocommit=true > db.myDb.isolation=NONE > db.myDb.partitionCount=1 > db.myDb.maxConnectionsPerPartition=4 > db.myDb.minConnectionsPerPartition=4 > db.myDb.acquireIncrement=10 > db.myDb.acquireRetryAttempts=10 > db.myDb.acquireRetryDelay=10 seconds > db.myDb.idleConnectionTestPeriod=5 minutes > db.myDb.initSQL="SELECT 1" > db.myDb.connectionTimeout=20 seconds > db.myDb.idleMaxAge=60 minutes > db.myDb.maxConnectionAge=60 minutes > db.myDb.logStatements=false > > > Here is my ha-jdbc-ingres-cluster-1.xml : > > > <ha-jdbc xmlns="urn:ha-jdbc:cluster:2.1"> > <sync id="passive" /> > <cluster > dialect="ingres" > default-sync="passive" > balancer="load" > meta-data-cache="lazy" > transaction-mode="parallel" > auto-activate-schedule="* * * ? * *" > failure-detect-schedule="0/5 * * ? * *"> > <database id="vw7" > location="jdbc:ingres://10.0.0.244:VW7/myDb"> > <user>ingres</user> > > <password>ingres</password> > </database> > <database id="vw8" > location="jdbc:ingres://10.0.0.244:VW8/myDb"> > <user>ingres</user> > > <password>ingres</password> > </database> > </cluster> > </ha-jdbc> > > > I get not specific error message but the ha-jdbc does not initialize > the 4 connections needed by the pool. > The only thing I found strange is that I found no place is the xml > file to specify the driver class name. > > > Thanks for your help ! > > > I'm also interested in your comments on my needs ... > > > > -- > nc...@gm... > ------------------------------------------------------------------------------ > Free Next-Gen Firewall Hardware Offer > Buy your Sophos next-gen firewall before the end March 2013 > and get the hardware for free! Learn more. > http://p.sf.net/sfu/sophos-d2d-feb > _______________________________________________ > ha-jdbc-user mailing list > ha-...@li... > https://lists.sourceforge.net/lists/listinfo/ha-jdbc-user |
From: Nicolas C. <nc...@gm...> - 2013-02-15 17:02:53
|
Hi everybody, I'm trying to use HA-JDBC. I tried with version 2.0 and it works (except some problem with auto-activate-schedule and failure-detect-schedule cron exception but this is not the point). I tried with version 2.1-beta3 but I encountered some problems. (I'm interested by bug fixes and maven dependency management) I get an error message : "Cannot connect to database myDb" *My global requirement is the following :* - database : Ingres/Vectorwise - driver : latest Ingres driver - connection using driver/url - application developped using playframework2 (java/scala) - many connections (~ 500) for a database driven application - read only access to the database - several instance of the database *I added needed dependencies :* - "commons-pool" % "commons-pool" % "1.6" - "commons-codec" % "commons-codec" % "1.7" - "commons-logging" % "commons-logging" % "1.1" - "org.jboss.logging" % "jboss-logging" % "3.1.2.GA" - "org.jgroups" % "jgroups" % "3.2.4.Final" - "org.slf4j" % "slf4j-api" % "1.7.2" - "org.tmatesoft.sqljet" % "sqljet" % "1.1.5" - "com.sleepycat" % "je" % "5.0.58" *Here is my HA-JDBC Driver configuration :* (syntax is play specific but completly understandable) db.myDb.driver=net.sf.hajdbc.sql.Driver db.myDb.url="jdbc:ha-jdbc:ingres-cluster-1" db.myDb.user=ingres db.myDb.password=ingres db.myDb.disableJMX=false db.myDb.autocommit=true db.myDb.isolation=NONE db.myDb.partitionCount=1 db.myDb.maxConnectionsPerPartition=4 db.myDb.minConnectionsPerPartition=4 db.myDb.acquireIncrement=10 db.myDb.acquireRetryAttempts=10 db.myDb.acquireRetryDelay=10 seconds db.myDb.idleConnectionTestPeriod=5 minutes db.myDb.initSQL="SELECT 1" db.myDb.connectionTimeout=20 seconds db.myDb.idleMaxAge=60 minutes db.myDb.maxConnectionAge=60 minutes db.myDb.logStatements=false *Here is my ha-jdbc-ingres-cluster-1.xml :* <ha-jdbc xmlns="urn:ha-jdbc:cluster:2.1"> <sync id="passive" /> <cluster dialect="ingres" default-sync="passive" balancer="load" meta-data-cache="lazy" transaction-mode="parallel" auto-activate-schedule="* * * ? * *" failure-detect-schedule="0/5 * * ? * *"> <database id="vw7" location="jdbc:ingres://10.0.0.244:VW7/myDb"> <user>ingres</user> <password>ingres</password> </database> <database id="vw8" location="jdbc:ingres://10.0.0.244:VW8/myDb"> <user>ingres</user> <password>ingres</password> </database> </cluster> </ha-jdbc> I get not specific error message but the ha-jdbc does not initialize the 4 connections needed by the pool. The only thing I found strange is that I found no place is the xml file to specify the driver class name. Thanks for your help ! I'm also interested in your comments on my needs ... -- nc...@gm... |
From: Braine, L. <lin...@em...> - 2013-02-07 16:42:29
|
Dear List. Has anyone used/integrated HA-JDBC into JBoss AS 7 ? To gain the benefits of the HA-JDBC I believe I have to integrate into the JCA architecture - would this be correct ? Basically, direct use of the HA-JDBC driver classes in the JBoss provided Datasource factory will not work - as you must use the HAJDBC connection factory class ? Any help or tips would be very appreciated. L |
From: Freire <fr...@cs...> - 2012-12-26 16:01:17
|
De: Freire [mailto:fr...@cs...] Enviada em: quarta-feira, 26 de dezembro de 2012 13:40 Para: 'ha-...@li...' Assunto: wrong XML ? Hell all, I am new to ha-jdbc, and it seems to be a great tool ! My company provides manufacturing critical mission applications, and I am looking for a database mirroring solution to use with them, so my interest in ha-jdbc. I have started up two hsqldb servers in my desktop, different TCP ports, each of them with its own database file, very same schemas. When running my test application to insert one register into the database, only the database named "db" is updated. If I swap names between the two declared databases into the XML, only the "db" named one is updated !! I am quite sure the problem is in the xml file prepared by me, so could someone give me some clues ? Best regards, Eduardo Freire CSI Engenharia e Sistemas (11) 4072-9999 Visite nosso site em <http://www.csi.ind.br> http://www.csi.ind.br <ha-jdbc> <sync id="full" class="net.sf.hajdbc.sync.FullSynchronizationStrategy"> <property name="fetchSize">1000</property> <property name="maxBatchSize">100</property> </sync> <cluster balancer="simple" default-sync="full" dialect="hsqldb" meta-data-cache="eager" transaction-mode="serial"> <database id="db" weight="1"> <driver>org.hsqldb.jdbcDriver</driver> <url>jdbc:hsqldb:hsql://localhost:9002/csi_database</url> <user>SA</user> </database> <database id="db2" weight="2"> <driver>org.hsqldb.jdbcDriver</driver> <url>jdbc:hsqldb:hsql://localhost:9001/csi_database</url> <user>SA</user> </database> </cluster> </ha-jdbc> |
From: Freire <fr...@cs...> - 2012-12-26 15:58:54
|
Hell all, I am new to ha-jdbc, and it seems to be a great tool ! My company provides manufacturing critical mission applications, and I am looking for a database mirroring solution to use with them, so my interest in ha-jdbc. I have started up two hsqldb servers in my desktop, different TCP ports, each of them with its own database file, very same schemas. When running my test application to insert one register into the database, only the database named "db" is updated. If I swap names between the two declared databases into the XML, only the "db" named one is updated !! I am quite sure the problem is in the xml file prepared by me, so could someone give me some clues ? Best regards, Eduardo Freire CSI Engenharia e Sistemas (11) 4072-9999 Visite nosso site em <http://www.csi.ind.br> http://www.csi.ind.br <ha-jdbc> <sync id="full" class="net.sf.hajdbc.sync.FullSynchronizationStrategy"> <property name="fetchSize">1000</property> <property name="maxBatchSize">100</property> </sync> <cluster balancer="simple" default-sync="full" dialect="hsqldb" meta-data-cache="eager" transaction-mode="serial"> <database id="db" weight="1"> <driver>org.hsqldb.jdbcDriver</driver> <url>jdbc:hsqldb:hsql://localhost:9002/csi_database</url> <user>SA</user> </database> <database id="db2" weight="2"> <driver>org.hsqldb.jdbcDriver</driver> <url>jdbc:hsqldb:hsql://localhost:9001/csi_database</url> <user>SA</user> </database> </cluster> </ha-jdbc> |
From: Paul F. <pm...@co...> - 2012-10-12 01:21:03
|
Hello all, It's been 3 years in the making, but I've finally released the initial beta of HA-JDBC 2.1.0. This release ushers in some significant changes. Most notably, I've migrated much of the project infrastructure from sourceforge to github. This includes: * A new home page: http://ha-jdbc.github.com * Source code migration from subversion on sourceforge to git on github * Build framework migration from Ant to Maven * Project documentation migration form Forrest to Maven Technology-wise, HA-JDBC 2.1 introduces several new features, including: * JDBC 4.1 support * Refactored startup * Programmatic configuration * Primary-copy style failure handling * Configurable durability, to handle JDBC client crashes * Failure detection via SQLException introspection * A new dump/restore sync strategy * New cluster state persistence mechanisms * Config file password obfuscation * Refactored configuration file schema * Extension points for easy extensibility * Improved integration with other logging frameworks * No required dependencies! The full changes report can be found here: http://ha-jdbc.github.com/changes-report.html As always, comments, suggestions, bug fixes, contributions are always welcome. Please use https://github.com/ha-jdbc/ha-jdbc/issues for bugs and the github pull request feature for submitting fixes/enhancements. To those on the ha-jdbc-user mailing list not currently subscribed to the ha-jdbc-announce list, I encourage you to do so. Future release announcements will go to this list only. Enjoy, Paul |
From: Paul F. <pm...@co...> - 2012-07-25 13:49:51
|
I migrated the main subversion repository on sourceforge to github a few months ago. On Wed, 2012-07-25 at 14:05 +0200, Tore Halset wrote: > Thanks. > > Is github the main repo or is it at sf.net? > > Regards, > - Tore. > > On Jul 25, 2012, at 13:23 , Paul Ferraro wrote: > > > Ah - I see. Those are both bugs. I just pushed a fix to master for > > both issues. > > Thanks, > > > > Paul > > > > On Wed, 2012-07-25 at 11:14 +0200, Tore Halset wrote: > >> Hello. > >> > >> If I have jboss-logging in classpath, ha-jdbc works fine. If I skip it I get a NoClassDefFoundError in JbossLoggerProvider#getLogger. > >> > >> The problem seem to be that the JBossLoggingProvider class loads fine, but not the JbossLogger. This does not match with the comment in JBossLoggingProvider stating "If this class could be loaded, so can jboss logging." > >> > >> My first plan was to change the JBossLoggingProvider#enabled method to return true only if it can find the org.jboss.logging.Logger class. However, in LoggerFactory you even use disabled loggers for logging the "logging is not enabled"-message. > >> > >> So what am I doing wrong? > >> > >> Regards, > >> - Tore. > >> > >> On Jul 24, 2012, at 23:16 , Paul Ferraro wrote: > >> > >>> jboss-logging is a required compile-time dependency, but an optional > >>> runtime dependency. > >>> > >>> On Tue, 2012-07-24 at 21:11 +0200, Tore Halset wrote: > >>>> Hello. > >>>> > >>>> Why do ha-jdbc require jboss-logging even when I do not use jboss logging? I am using latest ha-jdbc from github. > >>>> > >>>> Regards, > >>>> Tore Halset. > >> > >> > >> ------------------------------------------------------------------------------ > >> Live Security Virtual Conference > >> Exclusive live event will cover all the ways today's security and > >> threat landscape has changed and how IT managers can respond. Discussions > >> will include endpoint security, mobile security and the latest in malware > >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > >> _______________________________________________ > >> ha-jdbc-user mailing list > >> ha-...@li... > >> https://lists.sourceforge.net/lists/listinfo/ha-jdbc-user > > > > > > > > ------------------------------------------------------------------------------ > > Live Security Virtual Conference > > Exclusive live event will cover all the ways today's security and > > threat landscape has changed and how IT managers can respond. Discussions > > will include endpoint security, mobile security and the latest in malware > > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > > _______________________________________________ > > ha-jdbc-user mailing list > > ha-...@li... > > https://lists.sourceforge.net/lists/listinfo/ha-jdbc-user > > > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > ha-jdbc-user mailing list > ha-...@li... > https://lists.sourceforge.net/lists/listinfo/ha-jdbc-user |
From: Tore H. <ha...@pv...> - 2012-07-25 12:05:53
|
Thanks. Is github the main repo or is it at sf.net? Regards, - Tore. On Jul 25, 2012, at 13:23 , Paul Ferraro wrote: > Ah - I see. Those are both bugs. I just pushed a fix to master for > both issues. > Thanks, > > Paul > > On Wed, 2012-07-25 at 11:14 +0200, Tore Halset wrote: >> Hello. >> >> If I have jboss-logging in classpath, ha-jdbc works fine. If I skip it I get a NoClassDefFoundError in JbossLoggerProvider#getLogger. >> >> The problem seem to be that the JBossLoggingProvider class loads fine, but not the JbossLogger. This does not match with the comment in JBossLoggingProvider stating "If this class could be loaded, so can jboss logging." >> >> My first plan was to change the JBossLoggingProvider#enabled method to return true only if it can find the org.jboss.logging.Logger class. However, in LoggerFactory you even use disabled loggers for logging the "logging is not enabled"-message. >> >> So what am I doing wrong? >> >> Regards, >> - Tore. >> >> On Jul 24, 2012, at 23:16 , Paul Ferraro wrote: >> >>> jboss-logging is a required compile-time dependency, but an optional >>> runtime dependency. >>> >>> On Tue, 2012-07-24 at 21:11 +0200, Tore Halset wrote: >>>> Hello. >>>> >>>> Why do ha-jdbc require jboss-logging even when I do not use jboss logging? I am using latest ha-jdbc from github. >>>> >>>> Regards, >>>> Tore Halset. >> >> >> ------------------------------------------------------------------------------ >> Live Security Virtual Conference >> Exclusive live event will cover all the ways today's security and >> threat landscape has changed and how IT managers can respond. Discussions >> will include endpoint security, mobile security and the latest in malware >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> _______________________________________________ >> ha-jdbc-user mailing list >> ha-...@li... >> https://lists.sourceforge.net/lists/listinfo/ha-jdbc-user > > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > ha-jdbc-user mailing list > ha-...@li... > https://lists.sourceforge.net/lists/listinfo/ha-jdbc-user > |
From: Paul F. <pm...@co...> - 2012-07-25 11:24:06
|
Ah - I see. Those are both bugs. I just pushed a fix to master for both issues. Thanks, Paul On Wed, 2012-07-25 at 11:14 +0200, Tore Halset wrote: > Hello. > > If I have jboss-logging in classpath, ha-jdbc works fine. If I skip it I get a NoClassDefFoundError in JbossLoggerProvider#getLogger. > > The problem seem to be that the JBossLoggingProvider class loads fine, but not the JbossLogger. This does not match with the comment in JBossLoggingProvider stating "If this class could be loaded, so can jboss logging." > > My first plan was to change the JBossLoggingProvider#enabled method to return true only if it can find the org.jboss.logging.Logger class. However, in LoggerFactory you even use disabled loggers for logging the "logging is not enabled"-message. > > So what am I doing wrong? > > Regards, > - Tore. > > On Jul 24, 2012, at 23:16 , Paul Ferraro wrote: > > > jboss-logging is a required compile-time dependency, but an optional > > runtime dependency. > > > > On Tue, 2012-07-24 at 21:11 +0200, Tore Halset wrote: > >> Hello. > >> > >> Why do ha-jdbc require jboss-logging even when I do not use jboss logging? I am using latest ha-jdbc from github. > >> > >> Regards, > >> Tore Halset. > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > ha-jdbc-user mailing list > ha-...@li... > https://lists.sourceforge.net/lists/listinfo/ha-jdbc-user |
From: Tore H. <ha...@pv...> - 2012-07-25 09:14:43
|
Hello. If I have jboss-logging in classpath, ha-jdbc works fine. If I skip it I get a NoClassDefFoundError in JbossLoggerProvider#getLogger. The problem seem to be that the JBossLoggingProvider class loads fine, but not the JbossLogger. This does not match with the comment in JBossLoggingProvider stating "If this class could be loaded, so can jboss logging." My first plan was to change the JBossLoggingProvider#enabled method to return true only if it can find the org.jboss.logging.Logger class. However, in LoggerFactory you even use disabled loggers for logging the "logging is not enabled"-message. So what am I doing wrong? Regards, - Tore. On Jul 24, 2012, at 23:16 , Paul Ferraro wrote: > jboss-logging is a required compile-time dependency, but an optional > runtime dependency. > > On Tue, 2012-07-24 at 21:11 +0200, Tore Halset wrote: >> Hello. >> >> Why do ha-jdbc require jboss-logging even when I do not use jboss logging? I am using latest ha-jdbc from github. >> >> Regards, >> Tore Halset. |
From: Paul F. <pm...@co...> - 2012-07-24 21:16:10
|
jboss-logging is a required compile-time dependency, but an optional runtime dependency. On Tue, 2012-07-24 at 21:11 +0200, Tore Halset wrote: > Hello. > > Why do ha-jdbc require jboss-logging even when I do not use jboss logging? I am using latest ha-jdbc from github. > > Regards, > Tore Halset. > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > ha-jdbc-user mailing list > ha-...@li... > https://lists.sourceforge.net/lists/listinfo/ha-jdbc-user |
From: Tore H. <ha...@pv...> - 2012-07-24 19:52:49
|
Hello. Why do ha-jdbc require jboss-logging even when I do not use jboss logging? I am using latest ha-jdbc from github. Regards, Tore Halset. |
From: Paul F. <pm...@co...> - 2011-12-03 14:26:52
|
On Thu, 2011-11-10 at 16:57 -0500, David R Robison wrote: > How would I set the distributable option for use within JBoss? David As of HA-JDBC 2.0.x, setting up distributable works the same way as any other container, since the ha-jdbc config does not integrate with the AS itself. The code in svn trunk supports programmatic configuration, which enables you to write your own AS integration code, either in the form of microcontainer bean configuration (with AS5 and AS6), or by creating your own MSC service (in AS7). This allows you to inject resources like the jgroups channel used by HA-JDBC. |
From: Paul F. <pm...@co...> - 2011-12-03 14:22:29
|
On Thu, 2011-11-10 at 14:39 -0500, David R Robison wrote: > I am using ha-jdbc within JBoss. What happens when JBoss starts up and > no databases have been activated? Will it activate one, all, or none? David If no databases are active following startup, then your application will be unable to access your data, until, that is, you manually activate a database via the JMX activate operation. HA-JDBC never attempts to automatically activate a database unless their is at least 1 active database with which to sync. Paul |
From: David R R. <drr...@op...> - 2011-11-10 21:57:24
|
How would I set the distributable option for use within JBoss? David -- David R Robison Open Roads Consulting, Inc. 103 Watson Road, Chesapeake, VA 23320 phone: (757) 546-3401 e-mail: drr...@op... web: http://openroadsconsulting.com blog: http://therobe.blogspot.com book: http://www.xulonpress.com/bookstore/bookdetail.php?PB_ISBN=9781597816526 This e-mail communication (including any attachments) may contain confidential and/or privileged material intended solely for the individual or entity to which it is addressed. If you are not the intended recipient, you should immediately stop reading this message and delete it from all computers that it resides on. Any unauthorized reading, distribution, copying or other use of this communication (or its attachments) is strictly prohibited. If you have received this communication in error, please notify us immediately. This e-mail communication (including any attachments) may contain confidential and/or privileged material intended solely for the individual or entity to which it is addressed. |