June 2016 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2676) Allow TransactionalDriver connection.close() in afterCompletion

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2676?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2676: ------------------------------------- Please can you add a test case? I wonder if my patch would help here: https://github.com/jbosstm/narayana/pull/1022 > Allow TransactionalDriver connection.close() in afterCompletion > --------------------------------------------------------------- > > Key: JBTM-2676 > URL: https://issues.jboss.org/browse/JBTM-2676 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transactional Driver > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > Hibernate closes connections in afterCompletion. However, TransactionalDriver requires transaction to be in an active state in order to delist resource. > See new JTA and Hibernate standalone quickstart for reproduction. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2583) Use the local ActionStatusService to determine if a transaction containing XAResources is still in-flight before relying on orphan detection

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2583?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTM-2583: ----------------------------------------------- Vladimir Dosoudil <dosoudil(a)redhat.com> changed the Status of [bug 1310603|https://bugzilla.redhat.com/show_bug.cgi?id=1310603] from MODIFIED to ON_QA > Use the local ActionStatusService 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: Enhancement > Components: Recovery > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 4.17.34, 5.2.17.Final, 5.3.0.Final > > > 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. > > * In the case where the recovery manager and transaction manager are co-located this negates the need for a timeout based process entirely > * In the case where the recovery manager and transaction manager are not in the same JVM process, the current behaviour of timeout based orphan detection MUST still be employed -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2579) Throw XAException in XATerminator::commit if a wrapped resource fails transiently

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2579?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTM-2579: ----------------------------------------------- Vladimir Dosoudil <dosoudil(a)redhat.com> changed the Status of [bug 1329142|https://bugzilla.redhat.com/show_bug.cgi?id=1329142] from MODIFIED to ON_QA > Throw XAException in XATerminator::commit if a wrapped resource fails transiently > --------------------------------------------------------------------------------- > > Key: JBTM-2579 > URL: https://issues.jboss.org/browse/JBTM-2579 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Critical > Fix For: 4.17.31, 5.2.9.Final > > > It is possible for a resource that we are wrapping to return say XA_RETRY or XA_RMFAIL and therefore end up in the BasicAction failed list. However there is no error returned from commit in this circumstance as the recovery manager should ensure a consistent outcome. > The reason this becomes a problem for JTA and XATerminator in particular is that as no error is returned a parent coordinator will assume the branch completed successfully. In the future when it calls XATerminator::recover though this branch will be returned and detected as an orphan. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2550) If a class cannot be deserialized safely, try to fallback and use the XARecoveryModule to locate an appropriate XAResource

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2550?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTM-2550: ----------------------------------------------- Vladimir Dosoudil <dosoudil(a)redhat.com> changed the Status of [bug 1333245|https://bugzilla.redhat.com/show_bug.cgi?id=1333245] from MODIFIED to ON_QA > If a class cannot be deserialized safely, try to fallback and use the XARecoveryModule to locate an appropriate XAResource > -------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2550 > URL: https://issues.jboss.org/browse/JBTM-2550 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Recovery > Affects Versions: 5.2.8.Final > Reporter: Amos Feng > Assignee: Tom Jenkinson > Priority: Blocker > Fix For: 4.17.33, 5.2.10.Final > > > This exception happens with using the IBM MQ rar in the wildfly. > com.ibm.mq.connector.xa.XARWrapper is the serialize object. when the RecoveryManager tries to restore_state from the object record, it will load the class and threw CNFE as it can not access the XARWrapper classe in the RAR > We can catch this exception and try to get from the helpers. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2690) Update "wiki-example" to use WildFly

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2690?page=com.atlassian.jira.plugin.... ] Michael Musgrove commented on JBTM-2690: ---------------------------------------- We already have a distributed JTS quickstart for wildfly/EAP (https://github.com/wildfly/quickstart/tree/10.x/jts‌ / https://github.com/jboss-eap/quickstart/tree/master-eap6/jts > Update "wiki-example" to use WildFly > ------------------------------------ > > Key: JBTM-2690 > URL: https://issues.jboss.org/browse/JBTM-2690 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Reporter: Tom Jenkinson > Priority: Minor > > It is using AS6 so should be updated to use WildFly -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2690) Update "wiki-example" to use WildFly

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-2690: ----------------------------------- Summary: Update "wiki-example" to use WildFly Key: JBTM-2690 URL: https://issues.jboss.org/browse/JBTM-2690 Project: JBoss Transaction Manager Issue Type: Task Components: Demonstrator Reporter: Tom Jenkinson Priority: Minor It is using AS6 so should be updated to use WildFly -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2686) Introduce a Heuristic example in the karaf osgi-jta quickstart

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2686?page=com.atlassian.jira.plugin.... ] Michael Musgrove commented on JBTM-2686: ---------------------------------------- Where is the link to the PR? > Introduce a Heuristic example in the karaf osgi-jta quickstart > -------------------------------------------------------------- > > Key: JBTM-2686 > URL: https://issues.jboss.org/browse/JBTM-2686 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Demonstrator > Reporter: Amos Feng > Assignee: Amos Feng > > This example could be used to show how to mange the transaction object stores with the karaf cli commands. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2624) Introduce the administrator tool in the Narayana JTA OSGi integrated with the Karaf

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-2624?page=com.atlassian.jira.plugin.... ] Amos Feng updated JBTM-2624: ---------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Introduce the administrator tool in the Narayana JTA OSGi integrated with the Karaf > ----------------------------------------------------------------------------------- > > Key: JBTM-2624 > URL: https://issues.jboss.org/browse/JBTM-2624 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > {quote} > We have several management ways in Karaf : > * mbeans (no need to rewrap them) > * shell commands > * a servlet for the felix web console (used by the community) > * a hawtio plugin (used by fuse) > The first two are the most important imho. > {quote} > the manual interventions that may be needed if the heuristic fails to rollback / commit the transactions. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2689) narayana-osgi-jta integration test does not work with the karaf 4.x

by Amos Feng (JIRA)

Amos Feng created JBTM-2689: ------------------------------- Summary: narayana-osgi-jta integration test does not work with the karaf 4.x Key: JBTM-2689 URL: https://issues.jboss.org/browse/JBTM-2689 Project: JBoss Transaction Manager Issue Type: Bug Reporter: Amos Feng Assignee: Amos Feng The aquillian-container-karaf-embedded only support the karaf 2.3.3 and we are using the shell command with 4.x Now we just disable the integration test temperately. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2688) Message was not delivered to the queue in Spring Boot QS

by Gytis Trikleris (JIRA)

Gytis Trikleris created JBTM-2688: ------------------------------------- Summary: Message was not delivered to the queue in Spring Boot QS Key: JBTM-2688 URL: https://issues.jboss.org/browse/JBTM-2688 Project: JBoss Transaction Manager Issue Type: Bug Components: Demonstrator Reporter: Gytis Trikleris Assignee: Gytis Trikleris Priority: Minor Fix For: 5.next {code} ------------------------------------------------------------------------------- Test set: org.jboss.narayana.quickstart.spring.QuickstartApplicationTests ------------------------------------------------------------------------------- Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 11.443 sec <<< FAILURE! testCommit(org.jboss.narayana.quickstart.spring.QuickstartApplicationTests) Time elapsed: 2.43 sec <<< FAILURE! java.lang.AssertionError: Expected: a string containing "Message received: Created entry 'Test Value'" but: was " . ____ _ __ _ _ /\\ / ___'_ __ _ _(_)_ __ __ _ \ \ \ \ ( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \ \\/ ___)| |_)| | | | | || (_| | ) ) ) ) ' |____| .__|_| |_|_| |_\__, | / / / / =========|_|==============|___/=/_/_/_/ :: Spring Boot :: (v1.4.0.M3) 2016-06-14 14:34:55.166 INFO 5790 --- [ main] o.j.n.q.spring.QuickstartApplication : Starting QuickstartApplication on jaime.eng.hst.ams2.redhat.com with PID 5790 (/home/hudson/workspace/btny-pulls-narayana-quickstart/spring/narayana-spring-boot/target/classes started by hudson in /home/hudson/workspace/btny-pulls-narayana-quickstart/spring/narayana-spring-boot) 2016-06-14 14:34:55.167 INFO 5790 --- [ main] o.j.n.q.spring.QuickstartApplication : No active profile set, falling back to default profiles: default 2016-06-14 14:34:55.170 INFO 5790 --- [ main] s.c.a.AnnotationConfigApplicationContext : Refreshing org.springframework.context.annotation.AnnotationConfigApplicationContext@1d0cdb6: startup date [Tue Jun 14 14:34:55 BST 2016]; root of context hierarchy 2016-06-14 14:34:55.655 INFO 5790 --- [ main] f.a.AutowiredAnnotationBeanPostProcessor : JSR-330 'javax.inject.Inject' annotation found and supported for autowiring 2016-06-14 14:34:55.787 INFO 5790 --- [ main] com.arjuna.ats.jbossatx : ARJUNA032010: JBossTS Recovery Service (tag: unknown) - JBoss Inc. 2016-06-14 14:34:55.787 INFO 5790 --- [ main] com.arjuna.ats.jbossatx : ARJUNA032013: Starting transaction recovery manager 2016-06-14 14:34:55.870 INFO 5790 --- [ main] o.s.t.jta.JtaTransactionManager : Using JTA UserTransaction: Transaction: unknown 2016-06-14 14:34:55.870 INFO 5790 --- [ main] o.s.t.jta.JtaTransactionManager : Using JTA TransactionManager: Transaction: unknown 2016-06-14 14:34:55.980 INFO 5790 --- [ main] j.LocalContainerEntityManagerFactoryBean : Building JPA container EntityManagerFactory for persistence unit 'default' 2016-06-14 14:34:55.981 INFO 5790 --- [ main] o.hibernate.jpa.internal.util.LogHelper : HHH000204: Processing PersistenceUnitInfo [ name: default ...] 2016-06-14 14:34:55.995 INFO 5790 --- [ main] org.hibernate.dialect.Dialect : HHH000400: Using dialect: org.hibernate.dialect.H2Dialect 2016-06-14 14:34:56.040 INFO 5790 --- [ main] o.h.t.schema.internal.SchemaCreatorImpl : HHH000476: Executing import script 'org.hibernate.tool.schema.internal.exec.ScriptSourceInputNonExistentImpl@637cff' 2016-06-14 14:34:56.045 INFO 5790 --- [ main] j.LocalContainerEntityManagerFactoryBean : Initialized JPA EntityManagerFactory for persistence unit 'default' 2016-06-14 14:34:56.191 INFO 5790 --- [ main] org.apache.activemq.artemis.core.server : AMQ221000: live Message Broker is starting with configuration Broker Configuration (clustered=false,journalDirectory=/tmp/artemis-data/journal,bindingsDirectory=data/bindings,largeMessagesDirectory=data/largemessages,pagingDirectory=data/paging) 2016-06-14 14:34:56.192 INFO 5790 --- [ main] org.apache.activemq.artemis.core.server : AMQ221045: libaio is not available, switching the configuration into NIO 2016-06-14 14:34:56.193 INFO 5790 --- [ main] org.apache.activemq.artemis.core.server : AMQ221043: Protocol module found: [artemis-server]. Adding protocol support for: CORE 2016-06-14 14:34:56.220 INFO 5790 --- [ main] org.apache.activemq.artemis.core.server : AMQ221003: Trying to deploy queue jms.queue.quickstart-messages 2016-06-14 14:34:56.231 INFO 5790 --- [ main] org.apache.activemq.artemis.core.server : AMQ221007: Server is now live 2016-06-14 14:34:56.231 INFO 5790 --- [ main] org.apache.activemq.artemis.core.server : AMQ221001: Apache ActiveMQ Artemis Message Broker version 1.2.0 [localhost, nodeID=c852656c-3234-11e6-94cb-52540027ba72] 2016-06-14 14:34:56.496 INFO 5790 --- [ main] o.s.j.e.a.AnnotationMBeanExporter : Registering beans for JMX exposure on startup 2016-06-14 14:34:56.503 INFO 5790 --- [ main] o.s.c.support.DefaultLifecycleProcessor : Starting beans in phase 2147483647 2016-06-14 14:34:56.509 INFO 5790 --- [ main] o.j.n.q.spring.QuickstartApplication : Started QuickstartApplication in 1.418 seconds (JVM running for 10.75) 2016-06-14 14:34:56.520 INFO 5790 --- [ main] o.h.h.i.QueryTranslatorFactoryInitiator : HHH000397: Using ASTQueryTranslatorFactory Entries at the start: [] Creating entry 'Test Value' Entries at the end: [Entry{id=1, value='Test Value'}] 2016-06-14 14:34:57.444 INFO 5790 --- [ main] s.c.a.AnnotationConfigApplicationContext : Closing org.springframework.context.annotation.AnnotationConfigApplicationContext@1d0cdb6: startup date [Tue Jun 14 14:34:55 BST 2016]; root of context hierarchy 2016-06-14 14:34:57.446 INFO 5790 --- [ main] o.s.c.support.DefaultLifecycleProcessor : Stopping beans in phase 2147483647 2016-06-14 14:34:57.447 WARN 5790 --- [enerContainer-1] o.s.j.l.DefaultMessageListenerContainer : Rejecting received message because of the listener container having been stopped in the meantime: ActiveMQMessage[ID:c88ada9c-3234-11e6-94cb-52540027ba72]:PERSISTENT/ClientMessage[messageID=7, durable=true, address=jms.queue.quickstart-messages,userID=c88ada9c-3234-11e6-94cb-52540027ba72,properties=TypedProperties[__AMQ_CID=c8897b08-3234-11e6-94cb-52540027ba72]] 2016-06-14 14:34:57.456 INFO 5790 --- [ main] o.s.j.e.a.AnnotationMBeanExporter : Unregistering JMX-exposed beans on shutdown 2016-06-14 14:34:57.466 INFO 5790 --- [ main] org.apache.activemq.artemis.core.server : AMQ221002: Apache ActiveMQ Artemis Message Broker version 1.2.0 [c852656c-3234-11e6-94cb-52540027ba72] stopped, uptime 1.275 seconds 2016-06-14 14:34:57.469 INFO 5790 --- [ main] j.LocalContainerEntityManagerFactoryBean : Closing JPA EntityManagerFactory for persistence unit 'default' 2016-06-14 14:34:57.470 INFO 5790 --- [ main] .SchemaDropperImpl$DelayedDropActionImpl : HHH000477: Starting delayed drop of schema as part of SessionFactory shut-down' 2016-06-14 14:34:57.488 INFO 5790 --- [ main] com.arjuna.ats.jbossatx : ARJUNA032014: Stopping transaction recovery manager " at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20) at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:8) at org.jboss.narayana.quickstart.spring.QuickstartApplicationTests.testCommit(QuickstartApplicationTests.java:41) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) at org.springframework.boot.test.rule.OutputCapture$1.evaluate(OutputCapture.java:61) at org.junit.rules.RunRules.evaluate(RunRules.java:20) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164) at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110) at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175) at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcessWhenForked(SurefireStarter.java:107) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:68) {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues June 2016