[JBoss JIRA] (JBTM-2285) Missing specs upload to the web page
by Gytis Trikleris (JIRA)
[ https://issues.jboss.org/browse/JBTM-2285?page=com.atlassian.jira.plugin.... ]
Gytis Trikleris updated JBTM-2285:
----------------------------------
Attachment: REST-Atomic_v2_draft_8_comments_sept_4.pdf
RESTAT-v2-latest.pdf
> Missing specs upload to the web page
> ------------------------------------
>
> Key: JBTM-2285
> URL: https://issues.jboss.org/browse/JBTM-2285
> Project: JBoss Transaction Manager
> Issue Type: Task
> Components: Documentation
> Reporter: Gytis Trikleris
> Assignee: Gytis Trikleris
> Fix For: 5.0.4
>
> Attachments: IntegrationGuide.odt, IntegrationGuide.pdf, REST-Atomic_v2_draft_8_comments_sept_4.pdf, RESTAT-v2-latest.pdf
>
>
> Upload the attached files somewhere, so that they could be accesses from our web page
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 1 month
[JBoss JIRA] (JBTM-2285) Missing specs upload to the web page
by Gytis Trikleris (JIRA)
Gytis Trikleris created JBTM-2285:
-------------------------------------
Summary: Missing specs upload to the web page
Key: JBTM-2285
URL: https://issues.jboss.org/browse/JBTM-2285
Project: JBoss Transaction Manager
Issue Type: Task
Components: Documentation
Reporter: Gytis Trikleris
Assignee: Gytis Trikleris
Fix For: 5.0.4
Attachments: IntegrationGuide.odt, IntegrationGuide.pdf
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 1 month
[JBoss JIRA] (JBTM-2278) Allow the transaction manager suspend operation to succeed for JTS mode
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2278?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-2278:
--------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Allow the transaction manager suspend operation to succeed for JTS mode
> -----------------------------------------------------------------------
>
> Key: JBTM-2278
> URL: https://issues.jboss.org/browse/JBTM-2278
> Project: JBoss Transaction Manager
> Issue Type: Enhancement
> Components: JTS
> Reporter: Tom Jenkinson
> Assignee: Tom Jenkinson
> Fix For: 5.0.4
>
>
> It is not possible to perform TransactionManager::suspend operation during an afterCompletion call when the server is configured for JTS and has JacORB configured with interposition interceptors. This is because the transaction has not been used on the thread yet and when OTSManager.current() operation finds the PropagationContext in PICurrent to tries to recreate the hierarchy and ArjunaTransactionImple register_resource detects the transaction is no longer active so throws an Inactive exception causing suspend to fail.
> SystemException is a valid response code from suspend but it would be desirable to try to avoid this when the transaction is local to the Synchronization.
> Allowing suspend means this code would work:
> public afterCompletion(status) {
> tm.suspend()
> tm.begin()
> tm.commit()
> }
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 1 month
[JBoss JIRA] (JBTM-2264) Error enlisting second xa resource on the same oracle instance but other schema
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2264?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-2264:
--------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
I have merged this into master now. Thanks for the report!
> Error enlisting second xa resource on the same oracle instance but other schema
> -------------------------------------------------------------------------------
>
> Key: JBTM-2264
> URL: https://issues.jboss.org/browse/JBTM-2264
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Components: JTA
> Affects Versions: 5.0.3
> Reporter: Evgeniy Smelik
> Assignee: Tom Jenkinson
> Fix For: 5.0.4
>
> Attachments: sscce.zip, sscce.zip, test.log
>
>
> I've got an exception {{java.sql.SQLException: ConnectionImple.registerDatabase - ARJUNA017017: enlist of resource failed}} while preparing statement in the second connection within the same oracle instance but other schema.
> Whole stack trace:
> {noformat}
> oracle.jdbc.xa.OracleXAException
> at oracle.jdbc.xa.OracleXAResource.checkError(OracleXAResource.java:1110)
> at oracle.jdbc.xa.client.OracleXAResource.start(OracleXAResource.java:240)
> at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.enlistResource(TransactionImple.java:741)
> at com.arjuna.ats.internal.jdbc.ConnectionImple.registerDatabase(ConnectionImple.java:983)
> at com.arjuna.ats.internal.jdbc.ConnectionImple.prepareStatement(ConnectionImple.java:179)
> at SimpleJdbcTest.insert(SimpleJdbcTest.java:46)
> at SimpleJdbcTest.main(SimpleJdbcTest.java:36)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at com.intellij.rt.execution.application.AppMain.main(AppMain.java:134)
> java.sql.SQLException: ConnectionImple.registerDatabase - ARJUNA017017: enlist of resource failed
> at com.arjuna.ats.internal.jdbc.ConnectionImple.registerDatabase(ConnectionImple.java:1003)
> at com.arjuna.ats.internal.jdbc.ConnectionImple.prepareStatement(ConnectionImple.java:179)
> at SimpleJdbcTest.insert(SimpleJdbcTest.java:46)
> at SimpleJdbcTest.main(SimpleJdbcTest.java:36)
> {noformat}
> (Detail log and SSCCE are attached).
> I use jboss transaction manager in standaloine application just to test jboss JTA implementation. The same code works well if one and second data sources use own (different) database instances.
> I note that atomikos and bitronix JTA implementation works correctly in the same environment irrespectively single oracle instance is used or not.
> I found similar problem [here|http://stackoverflow.com/questions/23617179/jboss-6-1-unable-to-get-...].
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 1 month
[JBoss JIRA] (JBTM-2284) XID.toString broken: indexing mistake in array
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2284?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson resolved JBTM-2284.
---------------------------------
Resolution: Done
> XID.toString broken: indexing mistake in array
> ----------------------------------------------
>
> Key: JBTM-2284
> URL: https://issues.jboss.org/browse/JBTM-2284
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Affects Versions: 4.17.15
> Environment: EAP 6.2.4 with JBoss JTS module in version 4.17.15
> Reporter: Christian von Kutzleben
> Assignee: Tom Jenkinson
> Fix For: 4.17.24
>
>
> com.arjuna.ats.internal.jta.xa.XID
>
> public String toString ()
> {
> //...
> stringBuilder.append(", ");
> for (int i = 0; i < bqual_length; i++) {
> stringBuilder.append(gtrid_length+data[i]);
> }
> //...
> }
>
> correct: stringBuilder.append(data[i+gtrid_length]);
> The result is, that the Xid instances logged in log files are corrupted and multiple different Xid share the same String representation, which makes the logging information unusable
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 1 month