September 2016 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2739) Add a CI job for testing jboss-transaction-spi

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2739?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2739: -------------------------------- Fix Version/s: 5.next (was: 5.3.5.Final) > Add a CI job for testing jboss-transaction-spi > ---------------------------------------------- > > Key: JBTM-2739 > URL: https://issues.jboss.org/browse/JBTM-2739 > Project: JBoss Transaction Manager > Issue Type: Task > Components: SPI > Affects Versions: 5.3.4.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > We need a CI job to test that narayana works with the latest jboss-transaction-spi and this should include PRs as well as master. > In addition, the two projects duplicate tests so the the duplicates need removing from narayana (but only after we have added this CI testing). > Note that jboss-transaction-spi has a test dependency on the last released stable version of narayana so that dependency would need to changed to the version of our current SNAPSHOT for these new proposed CI jobs to be useful. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2713) Investigate why a null FileLock is declared but not used

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2713?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2713: -------------------------------- Fix Version/s: 5.next (was: 5.3.5.Final) > Investigate why a null FileLock is declared but not used > -------------------------------------------------------- > > Key: JBTM-2713 > URL: https://issues.jboss.org/browse/JBTM-2713 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.next > > > It is not assigned but later on it is checked for null and if not then released: > https://github.com/jbosstm/narayana/blob/29270942f17cc553ad1497a41f60fce1... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2728) Add a forget operation to the tooling

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2728?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2728: -------------------------------- Fix Version/s: 5.next (was: 5.3.5.Final) > Add a forget operation to the tooling > ------------------------------------- > > Key: JBTM-2728 > URL: https://issues.jboss.org/browse/JBTM-2728 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Tooling > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > The tooling provides two features for dealing with heuristic participants: > * a recover command that will move it back into the prepared state if the admin thinks a second prepare attempt is likely to succeed; > * a delete operation if the admin thinks it safe to do so; > > In the case of XA resources we also need a forget operation which will trigger the resource adaptor to clean up its end instead of relying on the admin to use tooling provided by the RA to clean up. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2705) Investigate alternatives to encoding recovery data in RecoveryCoordinator IORs

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2705?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2705: -------------------------------- Fix Version/s: 5.next (was: 5.3.5.Final) > Investigate alternatives to encoding recovery data in RecoveryCoordinator IORs > ------------------------------------------------------------------------------ > > Key: JBTM-2705 > URL: https://issues.jboss.org/browse/JBTM-2705 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: JTS > Affects Versions: 5.3.3.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > During JTS resource enlistment we create a RecoveryCoordinator IOR and embed recovery information in the ObjectKey part. This is not a portable solution since we need to use ORB vendor specific APIs to modify the ObjectKey. It would be preferable if we could use something that is in the CORBA specs that will work for all ORBs such as Portable Intercpeors (http://www.omg.org/cgi-bin/doc?ptc/2001-03-04). > Note that there is no current solution for IBM orb. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

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

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2688?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2688: -------------------------------- Fix Version/s: 5.next (was: 5.3.5.Final) > 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2685) Check that narayana builds and runs using the Java SE 9 compiler

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2685?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2685: -------------------------------- Fix Version/s: 5.next (was: 5.3.5.Final) > Check that narayana builds and runs using the Java SE 9 compiler > ---------------------------------------------------------------- > > Key: JBTM-2685 > URL: https://issues.jboss.org/browse/JBTM-2685 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Affects Versions: 5.3.3.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Critical > Fix For: 5.next > > > Get the latest build from https://jdk9.java.net/download/ and check for any issues. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2678) @TxLogged annotation does not work

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2678?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2678: -------------------------------- Fix Version/s: 5.next (was: 5.3.5.Final) > @TxLogged annotation does not work > ---------------------------------- > > Key: JBTM-2678 > URL: https://issues.jboss.org/browse/JBTM-2678 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Compensations > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > @TxLogged annotation does not work in Compensations framework. All it's assertions were removed from the tests with this commit: https://github.com/jbosstm/narayana/commit/efd15eeb080c6b6338f3658c4aa581... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2673) ThreadUtil getThreadId(Thread) ignores argument

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2673?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2673: -------------------------------- Fix Version/s: 5.next (was: 5.3.5.Final) > ThreadUtil getThreadId(Thread) ignores argument > ----------------------------------------------- > > Key: JBTM-2673 > URL: https://issues.jboss.org/browse/JBTM-2673 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > During investigation of https://developer.jboss.org/thread/269784?start=15&tstart=0 it was observed that the ThreadUtil implementation does not use the Thread argument and simply uses a ThreadLocal: > https://github.com/jbosstm/narayana/blob/master/ArjunaCore/arjuna/classes... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2662) Export org.jboss.tm, has 1, private references [org.jboss.logging]

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2662?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2662: -------------------------------- Fix Version/s: 5.next (was: 5.3.5.Final) > Export org.jboss.tm, has 1, private references [org.jboss.logging] > -------------------------------------------------------------------- > > Key: JBTM-2662 > URL: https://issues.jboss.org/browse/JBTM-2662 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2661) Unknown directive cardinality: in Require-Capability

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2661?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2661: -------------------------------- Fix Version/s: 5.next (was: 5.3.5.Final) > Unknown directive cardinality: in Require-Capability > ---------------------------------------------------- > > Key: JBTM-2661 > URL: https://issues.jboss.org/browse/JBTM-2661 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > [WARNING] Bundle org.jboss.narayana.osgi:narayana-osgi-jta:bundle:5.3.3.Final-SNAPSHOT : Unknown directive cardinality: in Require-Capability, allowed directives are effective:,resolution:,filter:, and 'x-*'. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 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 September 2016