jbossts-issues January 2016

jbossts-issues@lists.jboss.org

1 participants
225 discussions

[JBoss JIRA] (JBTM-2598) Merge in BlackTie Javadocs to main Narayana javadocs

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-2598: ----------------------------------- Summary: Merge in BlackTie Javadocs to main Narayana javadocs Key: JBTM-2598 URL: https://issues.jboss.org/browse/JBTM-2598 Project: JBoss Transaction Manager Issue Type: Task Components: Build System, Documentation Reporter: Tom Jenkinson Assignee: Tom Jenkinson Priority: Minor Fix For: 5.next The BlackTie javadocs are still separate http://narayana.io/documentation/index.html - it would be useful to ensure that they are in the same place as the rest of the Narayana javadocs. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2594) Link some doc chapters at higher levels on the project site

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2594?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2594: ------------------------------------- I don't think we link to the specific blacktie docs, just its javadocs - and that is only because they aren't integrated into the main build. I will create a new issue to merge the BlackTie javadocs into the main Narayana ones. I agree that linking to specific sections of the docs would still be useful from the site. One thing we would need to consider is how to make sure docbook generates links that don't look random (#d0e16062 in your example). > Link some doc chapters at higher levels on the project site > ----------------------------------------------------------- > > Key: JBTM-2594 > URL: https://issues.jboss.org/browse/JBTM-2594 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Documentation > Affects Versions: 5.2.11.Final > Reporter: Mark Little > > On the main Narayana site (http://narayana.io) we call out the higher level components such as JTA, STM, Orb Portability etc. However, on the docs page (http://narayana.io/documentation/index.html), apart from Blacktie the reader needs to load and read through the entire doc (or manually search) for the relevant sections. Maybe link the relevant chapters (such as http://narayana.io/docs/project/index.html#d0e16062) in the docs pages and/or the top level of the site, so someone looking for the JTS or STM docs can click there immediately. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2593) Suggest making this read_state INFO not WARN

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2593?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2593: ------------------------------------- It was added for JBTM-2168 within commit https://github.com/jbosstm/narayana/commit/e0cd8687ad9763c511a7878a2faddc... > Suggest making this read_state INFO not WARN > -------------------------------------------- > > Key: JBTM-2593 > URL: https://issues.jboss.org/browse/JBTM-2593 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Transaction Core > Affects Versions: 5.2.11.Final > Reporter: Mark Little > Assignee: Mark Little > Priority: Minor > > I'm not sure why it was added or why it's a warning. Maybe should be info or debug? > read_state operation, ShadowingStore_6 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2592) Incorrect warning messaging in ShadowingStore

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2592?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2592: ------------------------------------- Hi Mark, it was added here: https://github.com/jbosstm/narayana/commit/e0cd8687ad9763c511a7878a2faddc... > Incorrect warning messaging in ShadowingStore > --------------------------------------------- > > Key: JBTM-2592 > URL: https://issues.jboss.org/browse/JBTM-2592 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transaction Core > Affects Versions: 5.2.11.Final > Reporter: Mark Little > Assignee: Mark Little > Priority: Minor > > warn_objectstore_ShadowingStore_6 currently says ... > "ShadowingStore::read_state() - no type name given for object state" > ... when in fact the else clause is triggered when the state isn't committed or uncommitted (typically when it's unknown and the state doesn't exist). > I'm not sure when this warning message was added because it wasn't there in JBossTS 4.8 or 4.15.3. > I'm going to fix this issue (the text). I'll create a separate issue because I think this should be info not warning. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

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

by Ondřej Chaloupka (JIRA)

Ondřej Chaloupka created JBTM-2597: -------------------------------------- Summary: Failed commit during one-phase commit optimization only logs warning and lets EJB invocation succeed Key: JBTM-2597 URL: https://issues.jboss.org/browse/JBTM-2597 Project: JBoss Transaction Manager Issue Type: Bug Environment: Ubuntu Linux 32Bit, Java 8, WildFly 8.2.1.Final Reporter: Ondřej Chaloupka Assignee: Michael Musgrove Fix For: 5.2.10.Final 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, 11 months

1
0
0 / 0

← Newer
1
...
20
21
22
23
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues January 2016