[JBoss JIRA] (JBTM-882) org.jboss.jbossts:jbossjts:jar have to use PROVIDED scope dependency on org.jboss.logging:jboss-logging-generator:jar
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-882?page=com.atlassian.jira.plugin.s... ]
Tom Jenkinson closed JBTM-882.
------------------------------
> org.jboss.jbossts:jbossjts:jar have to use PROVIDED scope dependency on org.jboss.logging:jboss-logging-generator:jar
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: JBTM-882
> URL: https://issues.jboss.org/browse/JBTM-882
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.15.3
> Reporter: Richard Opalka
> Assignee: Tom Jenkinson
> Fix For: 4.16.0.Beta1
>
>
> The org.jboss.jbossts:jbossjts:jar
> in AS7 trunk brings in the compile dependency on
> org.jboss.logging:jboss-logging-generator
> The identified dependency tree is:
> {code}
> [INFO] | | | +- org.jboss.jbossts:jbossjts:jar:4.15.3.Final:compile
> [INFO] | | | | +- commons-httpclient:commons-httpclient:jar:3.1-jbossorg-1:compile
> [INFO] | | | | +- emma:emma:jar:2.0.5312:compile
> [INFO] | | | | +- emma:emma_ant:jar:2.0.5312:compile
> [INFO] | | | | | \- ant:ant:jar:1.6.3:compile
> [INFO] | | | | +- org.hornetq:hornetq-core:jar:2.2.6.Final:compile
> [INFO] | | | | +- tanukisoft:wrapper:jar:3.2.3:compile
> [INFO] | | | | +- jacorb:jacorb:jar:2.3.1jboss.patch01-brew:compile
> [INFO] | | | | +- jacorb:idl:jar:2.3.1jboss.patch01-brew:compile
> [INFO] | | | | +- org.jboss.integration:jboss-corba-ots-spi:jar:6.0.0.CR1:compile
> [INFO] | | | | | \- org.jboss.javaee:jboss-transaction-api:jar:1.0.1.GA:compile
> [INFO] | | | | +- org.jboss.jbossas:jboss-server-manager:jar:1.0.4.Final:compile
> [INFO] | | | | | \- org.picketbox:jboss-security-spi:jar:3.0.0.CR2:runtime
> [INFO] | | | | +- org.jboss.remoting:jboss-remoting:jar:2.5.3:compile
> [INFO] | | | | +- dom4j:dom4j:jar:1.6.1:compile
> [INFO] | | | | +- org.jboss.logging:jboss-logging-generator:jar:1.0.0.Beta6:compile <<<< wrong dependency scope here
> [INFO] | | | | \- org.hibernate.javax.persistence:hibernate-jpa-2.0-api:jar:1.0.1.Final:compile
> [INFO] | | | +- org.jboss.jbossts:jbossjts-integration:jar:4.15.3.Final:compile
> {code}
--
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
11 years, 2 months
[JBoss JIRA] (JBTM-932) Recover inflight subordinate transactions
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-932?page=com.atlassian.jira.plugin.s... ]
Tom Jenkinson closed JBTM-932.
------------------------------
> Recover inflight subordinate transactions
> -----------------------------------------
>
> Key: JBTM-932
> URL: https://issues.jboss.org/browse/JBTM-932
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Tom Jenkinson
> Assignee: Tom Jenkinson
> Fix For: 4.16.0.Final
>
>
> The call to XATerminator::recover() only returns transactions that are in the RecoveryStore.
> What if?
> 1. EIS propagates transaction "XYZ"
> 2. EIS crashes
> 3. We are not notified of this
> 4. EIS recovers
> 5. EIS calls XATerminator::recover
> 6. The inflight "XYZ" is not returned as it was not prepared and is therefore not in the RecoveryStore
--
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
11 years, 2 months
[JBoss JIRA] (JBTM-930) Run of ATSubordinateCrashDuringPrepare.MultiParticipantPrepareAndCommitTest is missing expected output
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-930?page=com.atlassian.jira.plugin.s... ]
Tom Jenkinson closed JBTM-930.
------------------------------
> Run of ATSubordinateCrashDuringPrepare.MultiParticipantPrepareAndCommitTest is missing expected output
> ------------------------------------------------------------------------------------------------------
>
> Key: JBTM-930
> URL: https://issues.jboss.org/browse/JBTM-930
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: XTS
> Affects Versions: 4.6.1.CP12
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Fix For: 4.6.1.CP13
>
> Attachments: ATSubordinateCrashDuringPrepare.MultiParticipantPrepareAndCommitTest
>
>
> I ran script:
> https://svn.jboss.org/repos/labs/labs/jbosstm/branches/JBOSSTS_4_6_1_GA_C...
> with test:
> org.jboss.jbossts.xts.servicetests.test.at.subordinate.MultiParticipantPrepareAndCommitTest
> And the following expected output is missing from the trace log:
> {code}
> # rollback called for pseudo participant XXXXXX
> # rollback called for subordinate transaction XXX
> # rollback sent for Participant XXXXXX
> # rollback received for Participant XXXXXX
> # aborted sent for Participant XXXXXX
> # aborted received for Participant XXXXXX
> # rollback sent for Participant XXXXXX
> # rollback received for Participant XXXXXX
> # aborted sent for Participant XXXXXX
> # aborted received for Participant XXXXXX
> # rollback returned for subordinate transaction XXX
> # rollback completed for pseudo participant XXXXXX
> {code}
> I think the expected output shuld actually be:
> {code}
> # rollback called for pseudo-participant XXXXXX
> # rollback called for subordinate coordinator XXX
> # rollback sent for Coordinator engine XXXXXX
> # rollback received for Participant XXXXXX
> # aborted sent for Participant XXXXXX
> # aborted received for Coordinator engine XXXXXX
> # rollback sent for Coordinator engine XXXXXX
> # rollback received for Participant XXXXXX
> # aborted sent for Participant XXXXXX
> # aborted received for Coordinator engine XXXXXX
> # rollback returned for subordinate coordinator XXX
> # rollback completed for pseudo-participant XXXXXX
> {code}
> Either way, these lines are missing from the output. Is this still a valid run, or do we have a failure?
> See attached log.
--
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
11 years, 2 months