2 Replies Latest reply on Aug 26, 2002 4:05 AM by Peter Willsund

    Problem with connection pool in JBoss 2.4.8

    Peter Willsund Newbie

      Hi!
      I tried to start JBoss 2.4.8 with the same jboss.jcml file as I have used in 2.4.7 but I get the following error:

      [INFO,cs_pool] Starting
      [INFO,XAPoolDataSource] Creating XA Pool
      [INFO,cs_pool] XA Connection pool cs_pool bound to java:/cs_pool
      [ERROR,cs_pool] Stopped
      java.lang.RuntimeException: No ManagedConnections Available!
      at org.jboss.pool.ObjectPool.getObject(ObjectPool.java:687)
      at org.jboss.pool.jdbc.xa.XAPoolDataSource.getConnection(XAPoolDataSource.java:227)
      at org.jboss.jdbc.XADataSourceLoader.startService(XADataSourceLoader.java:415)
      at org.jboss.util.ServiceMBeanSupport.start(ServiceMBeanSupport.java:103)
      at java.lang.reflect.Method.invoke(Native Method)
      at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628)
      at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
      at org.jboss.configuration.ConfigurationService$ServiceProxy.invoke(ConfigurationService.java:967)
      at $Proxy0.start(Unknown Source)
      at org.jboss.util.ServiceControl.start(ServiceControl.java:79)
      at java.lang.reflect.Method.invoke(Native Method)
      at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628)
      at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
      at org.jboss.Main.(Main.java:209)
      at org.jboss.Main$1.run(Main.java:110)
      at java.security.AccessController.doPrivileged(Native Method)
      at org.jboss.Main.main(Main.java:106)
      [ERROR,ConfigurationService] Unexpected error
      java.lang.RuntimeException: No ManagedConnections Available!
      at org.jboss.pool.ObjectPool.getObject(ObjectPool.java:687)
      at org.jboss.pool.jdbc.xa.XAPoolDataSource.getConnection(XAPoolDataSource.java:227)
      at org.jboss.jdbc.XADataSourceLoader.startService(XADataSourceLoader.java:415)
      at org.jboss.util.ServiceMBeanSupport.start(ServiceMBeanSupport.java:103)
      at java.lang.reflect.Method.invoke(Native Method)
      at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628)
      at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
      at org.jboss.configuration.ConfigurationService$ServiceProxy.invoke(ConfigurationService.java:967)
      at $Proxy0.start(Unknown Source)
      at org.jboss.util.ServiceControl.start(ServiceControl.java:79)
      at java.lang.reflect.Method.invoke(Native Method)
      at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628)
      at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
      at org.jboss.Main.(Main.java:209)
      at org.jboss.Main$1.run(Main.java:110)
      at java.security.AccessController.doPrivileged(Native Method)
      at org.jboss.Main.main(Main.java:106)


      If I use the old lib/ext/jbosspool.jar from 2.4.7 my 2.4.8 starts up OK.

      Part of my jboss.jcml:

      com.merant.datadirect.jdbc.sqlserver.SQLServerDriver



      org.jboss.pool.jdbc.xa.wrapper.XADataSourceImpl
      cs_pool
      jdbc:sqlserver://db:1433;DatabaseName=user_db;SelectMethod=Cursor
      user
      password


      Does anybody know why the 2.4.8 jbosspool complains?