October 2016 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2776) Investigate the arquillian tests failure with the JDK 9

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-2776?page=com.atlassian.jira.plugin.... ] Amos Feng updated JBTM-2776: ---------------------------- Summary: Investigate the arquillian tests failure with the JDK 9 (was: Investigate the arquillian issue with the JDK 9) > Investigate the arquillian tests failure with the JDK 9 > ------------------------------------------------------- > > Key: JBTM-2776 > URL: https://issues.jboss.org/browse/JBTM-2776 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Build System > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.next > > > the arquillian can not create the container -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2776) Investigate the arquillian issue with the JDK 9

by Amos Feng (JIRA)

Amos Feng created JBTM-2776: ------------------------------- Summary: Investigate the arquillian issue with the JDK 9 Key: JBTM-2776 URL: https://issues.jboss.org/browse/JBTM-2776 Project: JBoss Transaction Manager Issue Type: Sub-task Reporter: Amos Feng Assignee: Amos Feng the arquillian can not create the container -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2775) Upgrade byteman to 4.0.0-BETA0 to support the JDK 9

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-2775?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Amos Feng created pull request #1081 in GitHub ---------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Upgrade byteman to 4.0.0-BETA0 to support the JDK 9 > --------------------------------------------------- > > Key: JBTM-2775 > URL: https://issues.jboss.org/browse/JBTM-2775 > Project: JBoss Transaction Manager > Issue Type: Task > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.next > > > This is a preview release allowing Byteman to be used with a JDK9 that includes the Java Platform Module System. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

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

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-2685?page=com.atlassian.jira.plugin.... ] Amos Feng commented on JBTM-2685: --------------------------------- It needs to upgrade the byteman to 4.0.0-BETA0 and the ArjunaJTA/jta tests with the byteman rules should work. I had test them with the jdk9-ea+140 although the byteman throws the Exception {code} AccessManager:init unexpected error initialising JigsawAccessManager java.lang.reflect.InvocationTargetException at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(java.base@9-ea/Native Method) at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(java.base@9-ea/NativeMethodAccessorImpl.java:62) at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(java.base@9-ea/DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(java.base@9-ea/Method.java:535) at org.jboss.byteman.agent.AccessManager.init(AccessManager.java:80) at org.jboss.byteman.agent.Transformer.<init>(Transformer.java:98) at org.jboss.byteman.agent.Retransformer.<init>(Retransformer.java:60) at jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(java.base@9-ea/Native Method) at jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(java.base@9-ea/NativeConstructorAccessorImpl.java:62) at jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(java.base@9-ea/DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(java.base@9-ea/Constructor.java:455) at org.jboss.byteman.agent.Main.premain(Main.java:269) at org.jboss.byteman.agent.Main.agentmain(Main.java:307) at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(java.base@9-ea/Native Method) at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(java.base@9-ea/NativeMethodAccessorImpl.java:62) at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(java.base@9-ea/DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(java.base@9-ea/Method.java:535) at sun.instrument.InstrumentationImpl.loadClassAndStartAgent(java.instrument@9-ea/InstrumentationImpl.java:396) at sun.instrument.InstrumentationImpl.loadClassAndCallAgentmain(java.instrument@9-ea/InstrumentationImpl.java:418) Caused by: java.lang.NoSuchMethodError: java.lang.module.ModuleDescriptor.module(Ljava/lang/String;)Ljava/lang/module/ModuleDescriptor$Builder; at org.jboss.byteman.layer.LayerModuleFinder.<init>(LayerModuleFinder.java:82) at org.jboss.byteman.layer.LayerFactory.installModule(LayerFactory.java:63) at org.jboss.byteman.agent.JigsawAccessManager.init(JigsawAccessManager.java:63) ... 19 more {code} > 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2775) Upgrade byteman to 4.0.0-BETA0 to support the JDK 9

by Amos Feng (JIRA)

Amos Feng created JBTM-2775: ------------------------------- Summary: Upgrade byteman to 4.0.0-BETA0 to support the JDK 9 Key: JBTM-2775 URL: https://issues.jboss.org/browse/JBTM-2775 Project: JBoss Transaction Manager Issue Type: Task Reporter: Amos Feng Assignee: Amos Feng Fix For: 5.next This is a preview release allowing Byteman to be used with a JDK9 that includes the Java Platform Module System. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2774) Leak when imported subordinate transactions are rolled back by reaper before remote reaper

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2774?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTM-2774: ----------------------------------------------- Fedor Gavrilov <fgavrilo(a)redhat.com> changed the Status of [bug 1387316|https://bugzilla.redhat.com/show_bug.cgi?id=1387316] from NEW to ASSIGNED > Leak when imported subordinate transactions are rolled back by reaper before remote reaper > ------------------------------------------------------------------------------------------ > > Key: JBTM-2774 > URL: https://issues.jboss.org/browse/JBTM-2774 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Application Server Integration > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Critical > Fix For: 4.17.38, 5.2.20.Final, 5.next > > > When using the EJB remoting transport that layers over the top of JCA it is possible for a race condition between the two reapers. > Normally you have server 1 and server 2. Each of these insert the TwoPhaseCoordinator in their TransactionReaper. If the TransactionReaper in server 2 fires first then it will rollback the TPC. > When server 1 Reaper EJB remoting transport fires it will try to rollback at server 2 also and it is this that should be safe to remove the transactionImple reference. > At the time of reporting the reference is not removed though and so the reference to the TransactionImple is not removed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2774) Leak when imported subordinate transactions are rolled back by reaper before remote reaper

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2774?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2774: -------------------------------- Fix Version/s: 5.2.20.Final > Leak when imported subordinate transactions are rolled back by reaper before remote reaper > ------------------------------------------------------------------------------------------ > > Key: JBTM-2774 > URL: https://issues.jboss.org/browse/JBTM-2774 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Application Server Integration > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Critical > Fix For: 4.17.38, 5.2.20.Final, 5.next > > > When using the EJB remoting transport that layers over the top of JCA it is possible for a race condition between the two reapers. > Normally you have server 1 and server 2. Each of these insert the TwoPhaseCoordinator in their TransactionReaper. If the TransactionReaper in server 2 fires first then it will rollback the TPC. > When server 1 Reaper EJB remoting transport fires it will try to rollback at server 2 also and it is this that should be safe to remove the transactionImple reference. > At the time of reporting the reference is not removed though and so the reference to the TransactionImple is not removed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2774) Leak when imported subordinate transactions are rolled back by reaper before remote reaper

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2774?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2774: -------------------------------- Priority: Critical (was: Major) > Leak when imported subordinate transactions are rolled back by reaper before remote reaper > ------------------------------------------------------------------------------------------ > > Key: JBTM-2774 > URL: https://issues.jboss.org/browse/JBTM-2774 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Application Server Integration > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Critical > Fix For: 4.17.38, 5.next > > > When using the EJB remoting transport that layers over the top of JCA it is possible for a race condition between the two reapers. > Normally you have server 1 and server 2. Each of these insert the TwoPhaseCoordinator in their TransactionReaper. If the TransactionReaper in server 2 fires first then it will rollback the TPC. > When server 1 Reaper EJB remoting transport fires it will try to rollback at server 2 also and it is this that should be safe to remove the transactionImple reference. > At the time of reporting the reference is not removed though and so the reference to the TransactionImple is not removed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2774) Leak when imported subordinate transactions are rolled back by reaper before remote reaper

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2774?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2774: -------------------------------- Fix Version/s: 4.17.38 5.2.20.Final 5.next > Leak when imported subordinate transactions are rolled back by reaper before remote reaper > ------------------------------------------------------------------------------------------ > > Key: JBTM-2774 > URL: https://issues.jboss.org/browse/JBTM-2774 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Application Server Integration > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 4.17.38, 5.next > > > When using the EJB remoting transport that layers over the top of JCA it is possible for a race condition between the two reapers. > Normally you have server 1 and server 2. Each of these insert the TwoPhaseCoordinator in their TransactionReaper. If the TransactionReaper in server 2 fires first then it will rollback the TPC. > When server 1 Reaper EJB remoting transport fires it will try to rollback at server 2 also and it is this that should be safe to remove the transactionImple reference. > At the time of reporting the reference is not removed though and so the reference to the TransactionImple is not removed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2774) Leak when imported subordinate transactions are rolled back by reaper before remote reaper

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2774?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2774: -------------------------------- Fix Version/s: (was: 5.2.20.Final) > Leak when imported subordinate transactions are rolled back by reaper before remote reaper > ------------------------------------------------------------------------------------------ > > Key: JBTM-2774 > URL: https://issues.jboss.org/browse/JBTM-2774 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Application Server Integration > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 4.17.38, 5.next > > > When using the EJB remoting transport that layers over the top of JCA it is possible for a race condition between the two reapers. > Normally you have server 1 and server 2. Each of these insert the TwoPhaseCoordinator in their TransactionReaper. If the TransactionReaper in server 2 fires first then it will rollback the TPC. > When server 1 Reaper EJB remoting transport fires it will try to rollback at server 2 also and it is this that should be safe to remove the transactionImple reference. > At the time of reporting the reference is not removed though and so the reference to the TransactionImple is not removed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 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 October 2016