Bonita 6.3.8 Subscription edition server Installation : Connection is broken: "java.net.ConnectException: Connection refused: connect: localhost:9091"

Submitted by anirudh on Fri, 11/21/2014 - 18:44
1
0
-1

I am trying to install subscription edition 6.3.8 on our dev server(Apache Tomcat 7 , Windows Server , Postgres 9.3 database). I have followed the steps here : http://documentation.bonitasoft.com/tomcat-bundle-0

We have a subscription edition, but unfortunately the Agreement doesn't help during server setup or debugging while installing it. We had a consultant come to our office and even he couldn't resolve this issue. Also the tech support weren't able to help with my ticket.

Is anybody facing similar issues ? Any pointers would be helpful.

Here is the stack trace:

2014-11-21 09:31:13 bitronix.tm.recovery.Recoverer WARNING: error running recovery on resource 'jdbc/BusinessDataDSXA', resource marked as failed (background recoverer will retry recovery) bitronix.tm.recovery.RecoveryException: cannot start recovery on a PoolingDataSource containing an XAPool of resource jdbc/BusinessDataDSXA with 0 connection(s) (0 still available) -failed- at bitronix.tm.resource.jdbc.PoolingDataSource.startRecovery(PoolingDataSource.java:288) at bitronix.tm.recovery.Recoverer.recover(Recoverer.java:258) at bitronix.tm.recovery.Recoverer.recoverAllResources(Recoverer.java:226) at bitronix.tm.recovery.Recoverer.run(Recoverer.java:142) at java.lang.Thread.run(Thread.java:745) Caused by: bitronix.tm.internal.BitronixRuntimeException: incremental recovery failed when trying to acquire a connection from failed resource 'jdbc/BusinessDataDSXA' at bitronix.tm.resource.common.XAPool.getConnectionHandle(XAPool.java:103) at bitronix.tm.resource.jdbc.PoolingDataSource.startRecovery(PoolingDataSource.java:284) ... 4 more Caused by: bitronix.tm.recovery.RecoveryException: cannot start recovery on a PoolingDataSource containing an XAPool of resource jdbc/BusinessDataDSXA with 0 connection(s) (0 still available) at bitronix.tm.resource.jdbc.PoolingDataSource.startRecovery(PoolingDataSource.java:288) at bitronix.tm.recovery.IncrementalRecoverer.recover(IncrementalRecoverer.java:61) at bitronix.tm.resource.common.XAPool.getConnectionHandle(XAPool.java:100) ... 5 more Caused by: org.h2.jdbc.JdbcSQLException: Connection is broken: "java.net.ConnectException: Connection refused: connect: localhost:9091" [90067-170] at org.h2.message.DbException.getJdbcSQLException(DbException.java:329) at org.h2.message.DbException.get(DbException.java:158) at org.h2.engine.SessionRemote.connectServer(SessionRemote.java:399) at org.h2.engine.SessionRemote.connectEmbeddedOrServer(SessionRemote.java:287) at org.h2.jdbc.JdbcConnection.(JdbcConnection.java:109) at org.h2.jdbc.JdbcConnection.(JdbcConnection.java:93) at org.h2.Driver.connect(Driver.java:72) at org.h2.jdbcx.JdbcDataSource.getJdbcConnection(JdbcDataSource.java:181) at org.h2.jdbcx.JdbcDataSource.getXAConnection(JdbcDataSource.java:315) at bitronix.tm.resource.jdbc.PoolingDataSource.createPooledConnection(PoolingDataSource.java:341) at bitronix.tm.resource.common.XAPool.createPooledObject(XAPool.java:283) at bitronix.tm.resource.common.XAPool.grow(XAPool.java:391) at bitronix.tm.resource.common.XAPool.getInPool(XAPool.java:371) at bitronix.tm.resource.common.XAPool.getConnectionHandle(XAPool.java:123) at bitronix.tm.resource.jdbc.PoolingDataSource.startRecovery(PoolingDataSource.java:284) ... 7 more Caused by: java.net.ConnectException: Connection refused: connect at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method) at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:85) at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339) at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200) at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) at java.net.Socket.connect(Socket.java:579) at org.h2.util.NetUtils.createSocket(NetUtils.java:119) at org.h2.util.NetUtils.createSocket(NetUtils.java:100) at org.h2.engine.SessionRemote.initTransfer(SessionRemote.java:93) at org.h2.engine.SessionRemote.connectServer(SessionRemote.java:395) ... 19 more

2014-11-21 09:32:14 bitronix.tm.recovery.Recoverer WARNING: error running recovery on resource 'jdbc/BusinessDataDSXA', resource marked as failed (background recoverer will retry recovery) bitronix.tm.recovery.RecoveryException: cannot start recovery on a PoolingDataSource containing an XAPool of resource jdbc/BusinessDataDSXA with 0 connection(s) (0 still available) -failed- at bitronix.tm.resource.jdbc.PoolingDataSource.startRecovery(PoolingDataSource.java:288) at bitronix.tm.recovery.Recoverer.recover(Recoverer.java:258) at bitronix.tm.recovery.Recoverer.recoverAllResources(Recoverer.java:226) at bitronix.tm.recovery.Recoverer.run(Recoverer.java:142) at java.lang.Thread.run(Thread.java:745) Caused by: bitronix.tm.internal.BitronixRuntimeException: incremental recovery failed when trying to acquire a connection from failed resource 'jdbc/BusinessDataDSXA' at bitronix.tm.resource.common.XAPool.getConnectionHandle(XAPool.java:103) at bitronix.tm.resource.jdbc.PoolingDataSource.startRecovery(PoolingDataSource.java:284) ... 4 more Caused by: bitronix.tm.recovery.RecoveryException: cannot start recovery on a PoolingDataSource containing an XAPool of resource jdbc/BusinessDataDSXA with 0 connection(s) (0 still available) at bitronix.tm.resource.jdbc.PoolingDataSource.startRecovery(PoolingDataSource.java:288) at bitronix.tm.recovery.IncrementalRecoverer.recover(IncrementalRecoverer.java:61) at bitronix.tm.resource.common.XAPool.getConnectionHandle(XAPool.java:100) ... 5 more Caused by: org.h2.jdbc.JdbcSQLException: Connection is broken: "java.net.ConnectException: Connection refused: connect: localhost:9091" [90067-170] at org.h2.message.DbException.getJdbcSQLException(DbException.java:329) at org.h2.message.DbException.get(DbException.java:158) at org.h2.engine.SessionRemote.connectServer(SessionRemote.java:399) at org.h2.engine.SessionRemote.connectEmbeddedOrServer(SessionRemote.java:287) at org.h2.jdbc.JdbcConnection.(JdbcConnection.java:109) at org.h2.jdbc.JdbcConnection.(JdbcConnection.java:93) at org.h2.Driver.connect(Driver.java:72) at org.h2.jdbcx.JdbcDataSource.getJdbcConnection(JdbcDataSource.java:181) at org.h2.jdbcx.JdbcDataSource.getXAConnection(JdbcDataSource.java:315) at bitronix.tm.resource.jdbc.PoolingDataSource.createPooledConnection(PoolingDataSource.java:341) at bitronix.tm.resource.common.XAPool.createPooledObject(XAPool.java:283) at bitronix.tm.resource.common.XAPool.grow(XAPool.java:391) at bitronix.tm.resource.common.XAPool.getInPool(XAPool.java:371) at bitronix.tm.resource.common.XAPool.getConnectionHandle(XAPool.java:123) at bitronix.tm.resource.jdbc.PoolingDataSource.startRecovery(PoolingDataSource.java:284) ... 7 more Caused by: java.net.ConnectException: Connection refused: connect at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method) at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:85) at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339) at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200) at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) at java.net.Socket.connect(Socket.java:579) at org.h2.util.NetUtils.createSocket(NetUtils.java:119) at org.h2.util.NetUtils.createSocket(NetUtils.java:100) at org.h2.engine.SessionRemote.initTransfer(SessionRemote.java:93) at org.h2.engine.SessionRemote.connectServer(SessionRemote.java:395) ... 19 more

2014-11-21 09:33:13 bitronix.tm.recovery.Recoverer WARNING: error running recovery on resource 'jdbc/BusinessDataDSXA', resource marked as failed (background recoverer will retry recovery) bitronix.tm.recovery.RecoveryException: cannot start recovery on a PoolingDataSource containing an XAPool of resource jdbc/BusinessDataDSXA with 0 connection(s) (0 still available) -failed- at bitronix.tm.resource.jdbc.PoolingDataSource.startRecovery(PoolingDataSource.java:288) at bitronix.tm.recovery.Recoverer.recover(Recoverer.java:258) at bitronix.tm.recovery.Recoverer.recoverAllResources(Recoverer.java:226) at bitronix.tm.recovery.Recoverer.run(Recoverer.java:142) at java.lang.Thread.run(Thread.java:745) Caused by: bitronix.tm.internal.BitronixRuntimeException: incremental recovery failed when trying to acquire a connection from failed resource 'jdbc/BusinessDataDSXA' at bitronix.tm.resource.common.XAPool.getConnectionHandle(XAPool.java:103) at bitronix.tm.resource.jdbc.PoolingDataSource.startRecovery(PoolingDataSource.java:284) ... 4 more Caused by: bitronix.tm.recovery.RecoveryException: cannot start recovery on a PoolingDataSource containing an XAPool of resource jdbc/BusinessDataDSXA with 0 connection(s) (0 still available) at bitronix.tm.resource.jdbc.PoolingDataSource.startRecovery(PoolingDataSource.java:288) at bitronix.tm.recovery.IncrementalRecoverer.recover(IncrementalRecoverer.java:61) at bitronix.tm.resource.common.XAPool.getConnectionHandle(XAPool.java:100) ... 5 more Caused by: org.h2.jdbc.JdbcSQLException: Connection is broken: "java.net.ConnectException: Connection refused: connect: localhost:9091" [90067-170] at org.h2.message.DbException.getJdbcSQLException(DbException.java:329) at org.h2.message.DbException.get(DbException.java:158) at org.h2.engine.SessionRemote.connectServer(SessionRemote.java:399) at org.h2.engine.SessionRemote.connectEmbeddedOrServer(SessionRemote.java:287) at org.h2.jdbc.JdbcConnection.(JdbcConnection.java:109) at org.h2.jdbc.JdbcConnection.(JdbcConnection.java:93) at org.h2.Driver.connect(Driver.java:72) at org.h2.jdbcx.JdbcDataSource.getJdbcConnection(JdbcDataSource.java:181) at org.h2.jdbcx.JdbcDataSource.getXAConnection(JdbcDataSource.java:315) at bitronix.tm.resource.jdbc.PoolingDataSource.createPooledConnection(PoolingDataSource.java:341) at bitronix.tm.resource.common.XAPool.createPooledObject(XAPool.java:283) at bitronix.tm.resource.common.XAPool.grow(XAPool.java:391) at bitronix.tm.resource.common.XAPool.getInPool(XAPool.java:371) at bitronix.tm.resource.common.XAPool.getConnectionHandle(XAPool.java:123) at bitronix.tm.resource.jdbc.PoolingDataSource.startRecovery(PoolingDataSource.java:284) ... 7 more Caused by: java.net.ConnectException: Connection refused: connect at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method) at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:85) at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339) at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200) at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) at java.net.Socket.connect(Socket.java:579) at org.h2.util.NetUtils.createSocket(NetUtils.java:119) at org.h2.util.NetUtils.createSocket(NetUtils.java:100) at org.h2.engine.SessionRemote.initTransfer(SessionRemote.java:93) at org.h2.engine.SessionRemote.connectServer(SessionRemote.java:395) ... 19 more

2014-11-21 09:34:14 bitronix.tm.recovery.Recoverer WARNING: error running recovery on resource 'jdbc/BusinessDataDSXA', resource marked as failed (background recoverer will retry recovery) bitronix.tm.recovery.RecoveryException: cannot start recovery on a PoolingDataSource containing an XAPool of resource jdbc/BusinessDataDSXA with 0 connection(s) (0 still available) -failed- at bitronix.tm.resource.jdbc.PoolingDataSource.startRecovery(PoolingDataSource.java:288) at bitronix.tm.recovery.Recoverer.recover(Recoverer.java:258) at bitronix.tm.recovery.Recoverer.recoverAllResources(Recoverer.java:226) at bitronix.tm.recovery.Recoverer.run(Recoverer.java:142) at java.lang.Thread.run(Thread.java:745) Caused by: bitronix.tm.internal.BitronixRuntimeException: incremental recovery failed when trying to acquire a connection from failed resource 'jdbc/BusinessDataDSXA' at bitronix.tm.resource.common.XAPool.getConnectionHandle(XAPool.java:103) at bitronix.tm.resource.jdbc.PoolingDataSource.startRecovery(PoolingDataSource.java:284) ... 4 more Caused by: bitronix.tm.recovery.RecoveryException: cannot start recovery on a PoolingDataSource containing an XAPool of resource jdbc/BusinessDataDSXA with 0 connection(s) (0 still available) at bitronix.tm.resource.jdbc.PoolingDataSource.startRecovery(PoolingDataSource.java:288) at bitronix.tm.recovery.IncrementalRecoverer.recover(IncrementalRecoverer.java:61) at bitronix.tm.resource.common.XAPool.getConnectionHandle(XAPool.java:100) ... 5 more Caused by: org.h2.jdbc.JdbcSQLException: Connection is broken: "java.net.ConnectException: Connection refused: connect: localhost:9091" [90067-170] at org.h2.message.DbException.getJdbcSQLException(DbException.java:329) at org.h2.message.DbException.get(DbException.java:158) at org.h2.engine.SessionRemote.connectServer(SessionRemote.java:399) at org.h2.engine.SessionRemote.connectEmbeddedOrServer(SessionRemote.java:287) at org.h2.jdbc.JdbcConnection.(JdbcConnection.java:109) at org.h2.jdbc.JdbcConnection.(JdbcConnection.java:93) at org.h2.Driver.connect(Driver.java:72) at org.h2.jdbcx.JdbcDataSource.getJdbcConnection(JdbcDataSource.java:181) at org.h2.jdbcx.JdbcDataSource.getXAConnection(JdbcDataSource.java:315) at bitronix.tm.resource.jdbc.PoolingDataSource.createPooledConnection(PoolingDataSource.java:341) at bitronix.tm.resource.common.XAPool.createPooledObject(XAPool.java:283) at bitronix.tm.resource.common.XAPool.grow(XAPool.java:391) at bitronix.tm.resource.common.XAPool.getInPool(XAPool.java:371) at bitronix.tm.resource.common.XAPool.getConnectionHandle(XAPool.java:123) at bitronix.tm.resource.jdbc.PoolingDataSource.startRecovery(PoolingDataSource.java:284) ... 7 more Caused by: java.net.ConnectException: Connection refused: connect at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method) at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:85) at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339) at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200) at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) at java.net.Socket.connect(Socket.java:579) at org.h2.util.NetUtils.createSocket(NetUtils.java:119) at org.h2.util.NetUtils.createSocket(NetUtils.java:100) at org.h2.engine.SessionRemote.initTransfer(SessionRemote.java:93) at org.h2.engine.SessionRemote.connectServer(SessionRemote.java:395) ... 19 more

Bonita 6.3.8
BusinessDataDSXA

Comments

Submitted by haris.subasic on Mon, 11/24/2014 - 10:13

Hello, you mention using Postgresql, but then we see in the log tha tyou are still using H2. Could you verify that Postgresql is correctly configured, as described here ?

Permalink
Submitted by anirudh on Mon, 11/24/2014 - 10:19

Here Postgres is for Process Data. H2 is being used for Business Data. I had to dump this installation and start afresh. I took professional help to set it up as I was told my installation is corrupted and cannot be fixed.

Permalink
Submitted by haris.subasic on Mon, 11/24/2014 - 10:38

OK, I understand now. Make sure that localhost is recognized on your server (loopback). You can try maybe with the server name or ip in the url for your business data datasource.

Permalink
1 answer

Submitted by Philippe L on Mon, 11/24/2014 - 11:32
1
0
-1
This one is the BEST answer!

Hi Anirudh

I'm sorry you have the feeling to be abandoned on this problem. I think there is a misunderstanding on both sides of the role and responsibilities of our teams. We can clarify that with you. feel free to contact your Account Manager or Customer Success team for more information.

We have engaged our teams to help you on your installation. I encourage you to continue the investigation with our support team regarding this problem. Even if it requires some help from our consultants, Support team will gather the elements to start investigation and state if it is recommended to be helped by our Consultants.

Best regards Philippe

Notifications