[JBoss JIRA] Created: (JBTM-847) Look into how AssumedComplete works for ArjunaJTA (and jtax)
by Mark Little (JIRA)
Look into how AssumedComplete works for ArjunaJTA (and jtax)
------------------------------------------------------------
Key: JBTM-847
URL: https://issues.jboss.org/browse/JBTM-847
Project: JBoss Transaction Manager
Issue Type: Task
Security Level: Public (Everyone can see)
Components: JTA
Reporter: Mark Little
Assignee: Tom Jenkinson
When a transaction cannot be completed over a long period of time, a scanner is supposed to kick in and move the log elsewhere. Those scanners exist in ArjunaCore and ArjunaJTS, but do not appear to be there in ArjunaJTA. It should be straightforward to add them by using the base class in ArjunaCore, but investigate whether they are present already and just not obvious.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 6 months
[JBoss JIRA] (JBTM-1124) jbosstm/jboss-as merge failed from the upstream
by Amos Feng (JIRA)
Amos Feng created JBTM-1124:
-------------------------------
Summary: jbosstm/jboss-as merge failed from the upstream
Key: JBTM-1124
URL: https://issues.jboss.org/browse/JBTM-1124
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Build System
Reporter: Amos Feng
Assignee: Tom Jenkinson
Fix For: 5.0.0.M2
the following error when doing 'git pull --rebase upstream master' on jbosstm/jboss-as(BRANCH_5).
...
Auto-merging pom.xml
Auto-merging jacorb/pom.xml
CONFLICT (content): Merge conflict in jacorb/pom.xml
Auto-merging build/pom.xml
Auto-merging build/build.xml
Failed to merge in the changes.
Patch failed at 0001 5.0.0.M2-SNAPSHOT version of TS
...
jacorb/pom.xm
...
<dependency>
<<<<<<< HEAD
<groupId>org.jboss.as</groupId>
<artifactId>jboss-as-network</artifactId>
</dependency>
<dependency>
<groupId>org.jboss.jbossts</groupId>
<artifactId>jbossjts</artifactId>
=======
<groupId>org.jboss.narayana.jts</groupId>
<artifactId>narayana-jts</artifactId>
>>>>>>> 5.0.0.M2-SNAPSHOT version of TS
</dependency>
see https://github.com/jbossas/jboss-as/commit/d3fb1ce3f1688a654e19c0e56b7f98...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 6 months
[JBoss JIRA] (JBTM-1113) artifacts id different between narayana and jbossts when building jboss-as
by Amos Feng (JIRA)
Amos Feng created JBTM-1113:
-------------------------------
Summary: artifacts id different between narayana and jbossts when building jboss-as
Key: JBTM-1113
URL: https://issues.jboss.org/browse/JBTM-1113
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Amos Feng
Assignee: Tom Jenkinson
checkout 5_BRANCH on jboss-as and build fail.
It looks like we should change groupId from "org.jboss.jbossts" to "org.jboss.narayana" and different artifact id between them:
1. <dependency>
<groupId>org.jboss.jbossts</groupId>
<artifactId>jbossjts</artifactId>
</dependency>
2. <dependency>
<groupId>org.jboss.jbossts</groupId>
<artifactId>jbossxts</artifactId>
</dependency>
3. <dependency>
<groupId>org.jboss.jbossts</groupId>
<artifactId>jbossxts-api</artifactId>
</dependency>
4. <dependency>
<groupId>org.jboss.jbossts</groupId>
<artifactId>jbosstxbridge</artifactId>
</dependency>
5. <dependency>
<groupId>org.jboss.jbossts</groupId>
<artifactId>jbossjts-integration</artifactId>
</dependency>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 6 months