[JBoss JIRA] (JBTM-1398) Review subsystem usage across Narayana
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1398?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1398:
--------------------------------
Description:
h1. Components and their subsystem requirements:
h2. Transactions
XTS
Bootstrap coordinator
Setup WS endpoints for coordinator
Setup WS endpoints for the participants
Respond to configuration from standalone-xts.xml
REST-TX
Boostrap the coordinator
Setup a REST endpoint for the coordinator
Setup a REST endpoint for the participants
Blacktie
Register MDB
Register MBean
STM?
TXFramework
Modify the WS handler chain on application deployment
Registers a CDI extension
> Review subsystem usage across Narayana
> --------------------------------------
>
> Key: JBTM-1398
> URL: https://issues.jboss.org/browse/JBTM-1398
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: TXFramework
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Fix For: 5.0.0.M2
>
> Original Estimate: 2 days
> Time Spent: 6 hours
> Remaining Estimate: 1 day, 2 hours
>
> h1. Components and their subsystem requirements:
> h2. Transactions
>
> XTS
> Bootstrap coordinator
> Setup WS endpoints for coordinator
> Setup WS endpoints for the participants
> Respond to configuration from standalone-xts.xml
> REST-TX
> Boostrap the coordinator
> Setup a REST endpoint for the coordinator
> Setup a REST endpoint for the participants
> Blacktie
> Register MDB
> Register MBean
> STM?
> TXFramework
> Modify the WS handler chain on application deployment
> Registers a CDI extension
--
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-1398) Review TXFramework's subsystem usage (and change if required)
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1398?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1398:
--------------------------------
Description: (was: We need to review the various options for including TXFramework subsytem code in AS7.
1. Create a new Subsytem
2. Leave it in the XTS one
Also do we want all the subsytem code to live in the narayana codebase, rather than the AS7 one?
Pros: don't need to rebuild AS7 when changing it. Don't need to raise a pull req on AS7 when we want to change it.
Cons: We have to maintain it. In the past AS7 developers have made changes as the internals of AS7 change. We don't want to have to do this ourselves.
I suggest we look at how other projects are doing this before committing to a particular method.)
> Review TXFramework's subsystem usage (and change if required)
> -------------------------------------------------------------
>
> Key: JBTM-1398
> URL: https://issues.jboss.org/browse/JBTM-1398
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: TXFramework
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Fix For: 5.0.0.M2
>
> Original Estimate: 2 days
> Time Spent: 6 hours
> Remaining Estimate: 1 day, 2 hours
>
--
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-1419) exceptions in jta spec artifact inconsistent with Oracle doc
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1419?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson resolved JBTM-1419.
---------------------------------
Resolution: Rejected
Hi,
This issue would be better raised in the AS7 forum I think as that API is not controlled by the JBTM project. That said IllegalState is a Runtime exception, hence does not need to be declared in the throws clause so I wouldn't really say its a bug. If you want to re-open this, please do be sure to move it to the AS7 project.
Thanks,
Tom
> exceptions in jta spec artifact inconsistent with Oracle doc
> ------------------------------------------------------------
>
> Key: JBTM-1419
> URL: https://issues.jboss.org/browse/JBTM-1419
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JTA
> Reporter: Radim Kolář
> Assignee: Tom Jenkinson
>
> exceptions listed in this artifact:
> <groupId>org.jboss.spec.javax.transaction</groupId>
> <artifactId>jboss-transaction-api_1.1_spec</artifactId>
> <version>1.0.1.Final</version>
> are sometimes not consistent with official JTA 1.1 documentation - http://download.oracle.com/otn-pub/jcp/jta-1.1-spec-oth-JSpec
> For example JTA documentation for Transaction.commit() lists throws IllegalStateException (spec page 34) while this exception is omitted from your spec JAR.
> There are more cases like that. I recommend you to recheck api spec against PDF documentation from Oracle.
--
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-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:
--------------------------------
Assignee: Tom Jenkinson
> 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
> Assignee: Tom Jenkinson
> 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-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:
--------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/jbosstm/narayana/pull/194
> 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
>
> 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