December 2015 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2518) Product comparison benchmark CI job fails with OutOfMemoryError

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2518?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2518: -------------------------------- Fix Version/s: (was: 5.next) > Product comparison benchmark CI job fails with OutOfMemoryError > --------------------------------------------------------------- > > Key: JBTM-2518 > URL: https://issues.jboss.org/browse/JBTM-2518 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Performance Testing > Affects Versions: 5.2.2 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > > http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-benchmar... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2518) Product comparison benchmark CI job fails with OutOfMemoryError

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2518?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-2518. ------------------------------- Resolution: Out of Date > Product comparison benchmark CI job fails with OutOfMemoryError > --------------------------------------------------------------- > > Key: JBTM-2518 > URL: https://issues.jboss.org/browse/JBTM-2518 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Performance Testing > Affects Versions: 5.2.2 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > > http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-benchmar... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2567) QA suite failure: CrashRecovery02_2_Test??? (hqstore/JDKORB)

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2567?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2567: -------------------------------- Issue Type: Bug (was: Feature Request) > QA suite failure: CrashRecovery02_2_Test??? (hqstore/JDKORB) > ------------------------------------------------------------ > > Key: JBTM-2567 > URL: https://issues.jboss.org/browse/JBTM-2567 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > http://albany.eng.hst.ams2.redhat.com/job/narayana-hqstore/135/PROFILE=QA... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2305) Incomplete tooling documentation

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2305?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2305: -------------------------------- Issue Type: Task (was: Enhancement) > Incomplete tooling documentation > -------------------------------- > > Key: JBTM-2305 > URL: https://issues.jboss.org/browse/JBTM-2305 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Affects Versions: 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > For tooling the docs defer to the wildfly/EAP cli for "5.1.1. Browse and Manage Transactions Using an Application Server". We had some text in the README explaining how to view the tooling MBeans but the equivalent needs to be added to the development_guide too for use with standalone narayana. > In addition the docs need to explain how to extend the tooling for new abstract records (basically the user needs to create a JMX MBean for the new type and register it with the ObjStoreBrowser). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2497) Update or remove references of HornetQ to Artemis

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2497?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2497: -------------------------------- Issue Type: Task (was: Feature Request) > Update or remove references of HornetQ to Artemis > ------------------------------------------------- > > Key: JBTM-2497 > URL: https://issues.jboss.org/browse/JBTM-2497 > Project: JBoss Transaction Manager > Issue Type: Task > Components: BlackTie, Demonstrator, Documentation > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > There were reports of HornetQ still in at least the fooapp QS. We should try to remove references to the specific implementation unless necessary and in those cases use the correct name which is now Artemis. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2583) Try to contact the transaction status connection manager to determine if a transaction containing XAResources is still in-flight before relying on orphan detection

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2583?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2583: -------------------------------- Fix Version/s: 5.later (was: 5.next) > Try to contact the transaction status connection manager to determine if a transaction containing XAResources is still in-flight before relying on orphan detection > ------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2583 > URL: https://issues.jboss.org/browse/JBTM-2583 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Recovery > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.later > > > Currently we use a timeout based system to determine if prepared Xids that a ResourceManager knows about but where the transaction is not prepared yet are the result of a pre-prepare crash or whether it is just slow progress of the resources/transaction manager. > This issue is to record an enhancement to the recovery manager for XAResources to attempt to contact the transaction manager to determine if an Xid is indoubt before rolling it back. > > There are a couple of advantages to this: > 1. In the common case where the recovery manager and transaction manager are co-located this negates the need for a timeout based process entirely > 2. In the case where the recovery manager and transaction manager are distributed, the current behaviour of orphan detection can be employed (or the timeout interval extended) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2584) Failed commit during one-phase commit optimization only logs warning and lets EJB invocation succeed

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2584?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2584: ------------------------------------- This is the signature of the method we are discussing I assume? https://docs.oracle.com/javaee/6/api/javax/transaction/TransactionManager... Please can you link in a discussion to ascertain the nature of the intended behaviour for others in our community? > Failed commit during one-phase commit optimization only logs warning and lets EJB invocation succeed > ---------------------------------------------------------------------------------------------------- > > Key: JBTM-2584 > URL: https://issues.jboss.org/browse/JBTM-2584 > Project: JBoss Transaction Manager > Issue Type: Bug > Environment: Ubuntu Linux 32Bit, Java 8, WildFly 8.2.1.Final > Reporter: Torsten Roemer > > I have an entity manager (Oracle XA datasource) and a JCA resource adapter supporting LocalTransaction in one transaction. > Following scenario: > - An entity with values equal to those in the database is merged > - The commit() of the local-tx resource fails and throws a ResourceException > All that happens is a warning being logged: > {noformat} > 00:34:47,619 WARN [com.arjuna.ats.jta] (default task-24) ARJUNA016039: onePhaseCommit on < formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffff7f000101:25752588:566c9884:209, node_name=1, branch_uid=0:ffff7f000101:25752588:566c9884:211, subordinatenodename=null, eis_name=java:/FileDataSource > (LocalXAResourceImpl@41ac4d[connectionListener=d5fa3f connectionManager=1e7041 warned=false currentXid=null productName=Generic JCA productVersion=1.0 jndiName=java:/FileDataSource]) failed with exception XAException.XA_RBROLLBACK: org.jboss.jca.core.spi.transaction.local.LocalXAException: IJ001156: Could not commit local transaction > at org.jboss.jca.core.tx.jbossts.LocalXAResourceImpl.commit(LocalXAResourceImpl.java:180) [ironjacamar-core-impl-1.1.9.Final.jar:1.1.9.Final] > at com.arjuna.ats.internal.jta.resources.arjunacore.XAOnePhaseResource.commit(XAOnePhaseResource.java:113) > at com.arjuna.ats.internal.arjuna.abstractrecords.LastResourceRecord.topLevelPrepare(LastResourceRecord.java:152) > at com.arjuna.ats.arjuna.coordinator.AbstractRecord.topLevelOnePhaseCommit(AbstractRecord.java:428) > at com.arjuna.ats.arjuna.coordinator.BasicAction.onePhaseCommit(BasicAction.java:2317) > at com.arjuna.ats.arjuna.coordinator.BasicAction.prepare(BasicAction.java:2110) > at com.arjuna.ats.arjuna.coordinator.BasicAction.End(BasicAction.java:1481) > at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.end(TwoPhaseCoordinator.java:96) > at com.arjuna.ats.arjuna.AtomicAction.commit(AtomicAction.java:162) > at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1166) > at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:126) > at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:93) [wildfly-ejb3-8.2.1.Final.jar:8.2.1.Final] > {noformat} > and the EJB invocation succeeds. > I would expect the EJB to receive a RollbackException since the commit failed with XAException.XA_RBROLLBACK. > Debugging BasicAction.prepare(), I can see that because the outcome of prepare is TwoPhaseOutcome.PREPARE_READONLY, one phase commit optimization is applied and onePhaseCommit() is called where the outcome TwoPhaseOutcome.ONE_PHASE_ERROR isn't considered an error as far as I understand. > Then TwoPhaseOutcome.PREPARE_ONE_PHASE_COMMITTED is returned from BasicAction.prepare(). > I would never expect the EJB invocation to succeed if any participant in the transaction fails to commit. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2585) Configure CMR test programatically

by Gytis Trikleris (JIRA)

Gytis Trikleris created JBTM-2585: ------------------------------------- Summary: Configure CMR test programatically Key: JBTM-2585 URL: https://issues.jboss.org/browse/JBTM-2585 Project: JBoss Transaction Manager Issue Type: Task Components: JTA, Testing Reporter: Gytis Trikleris Priority: Minor I think we should add CMR configuration to standalon-full.xml programatically rather than copying standalone-cmr.xml manually in order to run CMRIntegrationTest. It needs to be kept up to date all the time. Also, it's a bit misleading when running the test for the first time. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2585) Configure CMR test programatically

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2585?page=com.atlassian.jira.plugin.... ] Gytis Trikleris reassigned JBTM-2585: ------------------------------------- Assignee: Gytis Trikleris > Configure CMR test programatically > ---------------------------------- > > Key: JBTM-2585 > URL: https://issues.jboss.org/browse/JBTM-2585 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTA, Testing > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > > I think we should add CMR configuration to standalon-full.xml programatically rather than copying standalone-cmr.xml manually in order to run CMRIntegrationTest. It needs to be kept up to date all the time. Also, it's a bit misleading when running the test for the first time. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2570) Remove unused private methods and fields in XTS

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2570?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-2570: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Remove unused private methods and fields in XTS > ----------------------------------------------- > > Key: JBTM-2570 > URL: https://issues.jboss.org/browse/JBTM-2570 > Project: JBoss Transaction Manager > Issue Type: Task > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues December 2015