[JBoss JIRA] (JBTM-1406) Database shutdown warning on Raspberry Pi
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1406?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-1406:
--------------------------------
Fix Version/s: 5.0.0.M2
> Database shutdown warning on Raspberry Pi
> -----------------------------------------
>
> Key: JBTM-1406
> URL: https://issues.jboss.org/browse/JBTM-1406
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Transaction Core
> Affects Versions: 4.17.3
> Environment: Raspberry Pi with latest distro installed and openjdk 6.
> Reporter: Mark Little
> Priority: Optional
> Fix For: 5.0.0.M2
>
>
> Exception in thread "Thread-6" java.lang.RuntimeException: org.h2.jdbc.JdbcSQLException: Database is already closed (to disable automatic closing at VM shutdown, add ";DB_CLOSE_ON_EXIT=FALSE" to the db URL) [90121-168]
> at com.arjuna.ats.internal.arjuna.objectstore.jdbc.JDBCImple_driver$1.initialValue(JDBCImple_driver.java:552)
> at com.arjuna.ats.internal.arjuna.objectstore.jdbc.JDBCImple_driver$1.initialValue(JDBCImple_driver.java:545)
> at java.lang.ThreadLocal.setInitialValue(ThreadLocal.java:160)
> at java.lang.ThreadLocal.get(ThreadLocal.java:150)
> at com.arjuna.ats.internal.arjuna.objectstore.jdbc.JDBCImple_driver.remove_state(JDBCImple_driver.java:384)
> at com.arjuna.ats.internal.arjuna.objectstore.jdbc.JDBCStore.remove_committed(JDBCStore.java:155)
> at com.arjuna.ats.internal.arjuna.recovery.TransactionStatusManagerItem.removeThis(TransactionStatusManagerItem.java:166)
> at com.arjuna.ats.arjuna.recovery.TransactionStatusManager.shutdown(TransactionStatusManager.java:152)
> at com.arjuna.ats.arjuna.coordinator.TxControl$Shutdown.run(TxControl.java:63)
> Caused by: org.h2.jdbc.JdbcSQLException: Database is already closed (to disable automatic closing at VM shutdown, add ";DB_CLOSE_ON_EXIT=FALSE" to the db URL) [90121-168]
> at org.h2.message.DbException.getJdbcSQLException(DbException.java:329)
> at org.h2.message.DbException.get(DbException.java:169)
> at org.h2.message.DbException.get(DbException.java:146)
> at org.h2.message.DbException.get(DbException.java:135)
> at org.h2.jdbc.JdbcConnection.checkClosed(JdbcConnection.java:1384)
> at org.h2.jdbc.JdbcConnection.checkClosed(JdbcConnection.java:1359)
> at org.h2.jdbc.JdbcConnection.setAutoCommit(JdbcConnection.java:403)
> at com.arjuna.ats.internal.arjuna.objectstore.jdbc.accessors.DynamicDataSourceJDBCAccess.getConnection(DynamicDataSourceJDBCAccess.java:53)
> at com.arjuna.ats.internal.arjuna.objectstore.jdbc.JDBCImple_driver$1.initialValue(JDBCImple_driver.java:550)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (JBTM-1420) org.apache.commons.io.output.DeferredFileOutputStream class not found
by Gytis Trikleris (JIRA)
[ https://issues.jboss.org/browse/JBTM-1420?page=com.atlassian.jira.plugin.... ]
Gytis Trikleris commented on JBTM-1420:
---------------------------------------
http://172.17.131.2/job/narayana/140
> org.apache.commons.io.output.DeferredFileOutputStream class not found
> ---------------------------------------------------------------------
>
> Key: JBTM-1420
> URL: https://issues.jboss.org/browse/JBTM-1420
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Testing, TXFramework
> Reporter: Gytis Trikleris
> Assignee: Paul Robinson
> Priority: Minor
> Fix For: 5.0.0.M2
>
>
> See: http://172.17.131.2/job/narayana/139
> {noformat}
> Tests in error:
> clientDrivenCommitTest(org.jboss.narayana.txframework.functional.rest.at.simpleEJB.ClientTXInterceptorTest): java.lang.NoClassDefFoundError: org/apache/commons/io/output/DeferredFileOutputStream
> multipleInvokeTest(org.jboss.narayana.txframework.functional.rest.at.simpleEJB.IndirectTXManagementTest): org/apache/commons/io/output/DeferredFileOutputStream
> clientDrivenRollbackTest(org.jboss.narayana.txframework.functional.rest.at.simpleEJB.IndirectTXManagementTest): org/apache/commons/io/output/DeferredFileOutputStream
> participantDrivenRollbackTest(org.jboss.narayana.txframework.functional.rest.at.simpleEJB.IndirectTXManagementTest): org/apache/commons/io/output/DeferredFileOutputStream
> clientDrivenCommitTest(org.jboss.narayana.txframework.functional.rest.at.simpleEJB.IndirectTXManagementTest): org/apache/commons/io/output/DeferredFileOutputStream
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (JBTM-1356) Parallel prepare implementation does not handle LRCO correctly
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1356?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-1356:
--------------------------------
Fix Version/s: 5.0.0.M2
(was: 5.0.0.M3)
> Parallel prepare implementation does not handle LRCO correctly
> --------------------------------------------------------------
>
> Key: JBTM-1356
> URL: https://issues.jboss.org/browse/JBTM-1356
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Transaction Core
> Affects Versions: 5.0.0.M1
> Reporter: Michael Musgrove
> Assignee: Gytis Trikleris
> Priority: Optional
> Fix For: 5.0.0.M2
>
>
> We implement LRCO by putting the 1PC aware resources at the end of the prepared list. Prepare is implemented by preparing each record in the prepared list and then stopping if any prepare fails. This means that if any 2PC aware resource fails then the 1PC resources are not get asked to prepare/commit.
> The parallel prepare implementation prepares all participants in separate threads which is wrong - it should prepare 2PC aware participants first and if they vote commit should the 1PC resources be asked to commit.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months