0 Replies Latest reply on Apr 15, 2010 8:15 AM by ravendra kumar

    null connection error:  FailOver, High Availability DataSource configuration on Jboss esb4.2.1GA

    ravendra kumar Newbie

      Hi,

       

      I am trying to configure high Availability datasource  on jbossesb-server-4.2.1GA for Failover functionality,

       

      Esb server is throwing following error  while testing Failover "Throwable while attempting to get a new connection"

       

      while same configuration setuup  is working fine on Jboss AS 4.0.5 server (please see attached  SpiderHA-ds.xml file).

       

      I am not able to guess where the problem is actually,

       

       

      Any help will be Highly appriciated.

       

      note: I already have Installed Jboss-ha-local-jdbc.rar library on both servers and normal datasource on esbserver working fime

       

      Thanks,

      Ravi

       

      The error from esb server is following.

       

      17:16:24,204 WARN  [JBossManagedConnectionPool] Throwable while attempting to get a new connection: null
      java.lang.NullPointerException
              at org.jboss.resource.adapter.jdbc.local.HALocalManagedConnectionFactory.doCreateManagedConnection(HALocalManagedConnectionFactory.java:84)
              at org.jboss.resource.adapter.jdbc.local.HALocalManagedConnectionFactory.createManagedConnection(HALocalManagedConnectionFactory.java:77)
              at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.createConnectionEventListener(InternalManagedConnectionPool.java:577)
              at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPool.java:262)
              at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManagedConnectionPool.java:501)
              at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:341)
              at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedConnection(TxConnectionManager.java:315)
              at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:399)
              at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:842)
              at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:88)
              at com.test.mbean.HADatasourceTest.startService(HADatasourceTest.java:31)
              at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
              at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
              at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
              at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
              at java.lang.reflect.Method.invoke(Method.java:597)
              at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
              at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
              at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
              at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
              at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
              at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)