June 2015 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2434) @Transactional annotation on stereotype leads to error "ARJUNA016107: Expected an @Transactional annotation at class and/or method level"

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2434?page=com.atlassian.jira.plugin.... ] Gytis Trikleris moved WFLY-4784 to JBTM-2434: --------------------------------------------- Project: JBoss Transaction Manager (was: WildFly) Key: JBTM-2434 (was: WFLY-4784) Affects Version/s: (was: 8.2.0.Final) (was: 9.0.0.CR1) Component/s: JTA (was: CDI / Weld) (was: Transactions) > @Transactional annotation on stereotype leads to error "ARJUNA016107: Expected an @Transactional annotation at class and/or method level" > ----------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2434 > URL: https://issues.jboss.org/browse/JBTM-2434 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Environment: JDK 1.7u72 x64, Windows 8.1 Professional > Reporter: Alexander Morozov > Assignee: Gytis Trikleris > Priority: Critical > Attachments: wildfly-jta-cdi.zip > > > It is seems that CDI Transactional extesion doesn't support well @Transactional annotation on CDI stereotypes. JTA transaction is created by library interceptor, but in case of exception on component's side, _com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorBase.getTransactional(...)_ method failed to locate @Transactional annotation on target component. It leads to exception like that > {code} > java.lang.RuntimeException: ARJUNA016107: Expected an @Transactional annotation at class and/or method level > at com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorBase.getTransactional(TransactionalInterceptorBase.java:83) > at com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorBase.handleException(TransactionalInterceptorBase.java:118) > at com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorBase.invokeInCallerTx(TransactionalInterceptorBase.java:106) > at com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorMandatory.intercept(TransactionalInterceptorMandatory.java:58) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.weld.interceptor.reader.SimpleInterceptorInvocation$SimpleMethodInvocation.invoke(SimpleInterceptorInvocation.java:74) > at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.executeAroundInvoke(InterceptorMethodHandler.java:84) > at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.executeInterception(InterceptorMethodHandler.java:72) > at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.invoke(InterceptorMethodHandler.java:56) > at org.jboss.weld.bean.proxy.CombinedInterceptorAndDecoratorStackMethodHandler.invoke(CombinedInterceptorAndDecoratorStackMethodHandler.java:79) > at org.jboss.weld.bean.proxy.CombinedInterceptorAndDecoratorStackMethodHandler.invoke(CombinedInterceptorAndDecoratorStackMethodHandler.java:68) > at com.mycompany.wildfly.jta.cdi.UserEventDispatcher$Proxy$_$$_WeldSubclass.dispatch(Unknown Source) > at com.mycompany.wildfly.jta.cdi.UserEventDispatcher$Proxy$_$$_WeldClientProxy.dispatch(Unknown Source) > at com.mycompany.wildfly.jta.cdi.UserApplicationService.addUser(UserApplicationService.java:18) > at com.mycompany.wildfly.jta.cdi.UserApplicationService$Proxy$_$$_WeldSubclass.addUser$$super(Unknown Source) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.weld.interceptor.proxy.TerminalAroundInvokeInvocationContext.proceedInternal(TerminalAroundInvokeInvocationContext.java:49) > at org.jboss.weld.interceptor.proxy.AroundInvokeInvocationContext.proceed(AroundInvokeInvocationContext.java:77) > at com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorBase.invokeInOurTx(TransactionalInterceptorBase.java:92) > at com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorRequired.intercept(TransactionalInterceptorRequired.java:52) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.weld.interceptor.reader.SimpleInterceptorInvocation$SimpleMethodInvocation.invoke(SimpleInterceptorInvocation.java:74) > at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.executeAroundInvoke(InterceptorMethodHandler.java:84) > at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.executeInterception(InterceptorMethodHandler.java:72) > at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.invoke(InterceptorMethodHandler.java:56) > at org.jboss.weld.bean.proxy.CombinedInterceptorAndDecoratorStackMethodHandler.invoke(CombinedInterceptorAndDecoratorStackMethodHandler.java:79) > at org.jboss.weld.bean.proxy.CombinedInterceptorAndDecoratorStackMethodHandler.invoke(CombinedInterceptorAndDecoratorStackMethodHandler.java:68) > at com.mycompany.wildfly.jta.cdi.UserApplicationService$Proxy$_$$_WeldSubclass.addUser(Unknown Source) > at com.mycompany.wildfly.jta.cdi.UserApplicationService$Proxy$_$$_WeldClientProxy.addUser(Unknown Source) > at com.mycompany.wildfly.jta.cdi.BootstrapExtension.start(BootstrapExtension.java:20) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > ......... > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2432) Cannot test IBM J9 VM on linux

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2432?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2432: ------------------------------------- I think what is happening is (I agree confusing) but you are using download director to download the package. Download director needs the Java plugin installing and Chrome (which you are using) doesn't like plugins anymore so the page doesn't think its installed and redirects you to Oracle to update your version of Java so you can then use the download manager (as I say, confusing and unclear) Two options: 1. Use a different browser to download it 2. There is an option to switch to direct download a. http://www.ibm.com/developerworks/java/jdk/linux/download.html b. click "Java SE Version 8 (last updated: 01 May 2015)" c. choose "64-bit AMD/Opteron/EM64T" d. "Download Now" e. enter data f. Toggle table to "Download using http" <--- THIS IS THE KEY BIT > Cannot test IBM J9 VM on linux > ------------------------------- > > Key: JBTM-2432 > URL: https://issues.jboss.org/browse/JBTM-2432 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Reporter: Michael Musgrove > Assignee: Tom Jenkinson > Fix For: 5.next > > > We currently have provisional support for the IBM® J9 virtual machine for Java 7 but building narayana master now requires Java 8 (which we inherited from WildFly master which enforces Java 8). > Now it appears that the J9 virtual machine for Java 8 is not available on linux. When you go to the download page the linux download button redirects to the Oracle Hot Spot VM. We either need to abandon support for J9 or we add a CI machine running z/OS -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2433) TransactionRolledBackException in MultiCloseTest

by Gytis Trikleris (JIRA)

Gytis Trikleris created JBTM-2433: ------------------------------------- Summary: TransactionRolledBackException in MultiCloseTest Key: JBTM-2433 URL: https://issues.jboss.org/browse/JBTM-2433 Project: JBoss Transaction Manager Issue Type: Bug Components: XTS Reporter: Gytis Trikleris Assignee: Gytis Trikleris Priority: Minor Fix For: 5.later Attachments: com.arjuna.wstx.tests.arq.ba.MultiCloseTest-output.txt http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/858/PROFIL... {code} ------------------------------------------------------------------------------- Test set: com.arjuna.wstx.tests.arq.ba.MultiCloseTest ------------------------------------------------------------------------------- Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 5.117 sec <<< FAILURE! testMultiClose(com.arjuna.wstx.tests.arq.ba.MultiCloseTest) Time elapsed: 2.5 sec <<< ERROR! com.arjuna.wst.TransactionRolledBackException: null at com.arjuna.wst11.stub.BusinessActivityTerminatorStub.close(BusinessActivityTerminatorStub.java:95) at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.close(UserBusinessActivityImple.java:157) at com.arjuna.wstx.tests.arq.ba.MultiCloseTest.testMultiClose(MultiCloseTest.java:71) {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2433) TransactionRolledBackException in MultiCloseTest

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2433?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-2433: ---------------------------------- Attachment: com.arjuna.wstx.tests.arq.ba.MultiCloseTest-output.txt > TransactionRolledBackException in MultiCloseTest > ------------------------------------------------ > > Key: JBTM-2433 > URL: https://issues.jboss.org/browse/JBTM-2433 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.later > > Attachments: com.arjuna.wstx.tests.arq.ba.MultiCloseTest-output.txt > > > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/858/PROFIL... > {code} > ------------------------------------------------------------------------------- > Test set: com.arjuna.wstx.tests.arq.ba.MultiCloseTest > ------------------------------------------------------------------------------- > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 5.117 sec <<< FAILURE! > testMultiClose(com.arjuna.wstx.tests.arq.ba.MultiCloseTest) Time elapsed: 2.5 sec <<< ERROR! > com.arjuna.wst.TransactionRolledBackException: null > at com.arjuna.wst11.stub.BusinessActivityTerminatorStub.close(BusinessActivityTerminatorStub.java:95) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.close(UserBusinessActivityImple.java:157) > at com.arjuna.wstx.tests.arq.ba.MultiCloseTest.testMultiClose(MultiCloseTest.java:71) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2398) Support VolatileStore.allObjUids

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2398?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2398: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/870 I have sub-typed VolatileStore and TwoPhaseVolatileStore since adding lookup by type name support has a performance impact: - I need to maintain a mapping from uid -> typeName - I update the mapping on each write_committed call The new store types are TypedVolatileStore and TypedTwoPhaseVolatileStore. > Support VolatileStore.allObjUids > --------------------------------- > > Key: JBTM-2398 > URL: https://issues.jboss.org/browse/JBTM-2398 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Performance Testing > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Fix For: 5.later > > > This method is used by REST-AT and would be a useful addition for baselining the performance of the coordinator for comparison with non transactional and empty transaction requests. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2425) Upgrade to latest wildfly version

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2425?page=com.atlassian.jira.plugin.... ] Michael Musgrove resolved JBTM-2425. ------------------------------------ Resolution: Done > Upgrade to latest wildfly version > --------------------------------- > > Key: JBTM-2425 > URL: https://issues.jboss.org/browse/JBTM-2425 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > Latest is 10.0.0.Alpha3-SNAPSHOT -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2425) Upgrade to latest wildfly version

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2425?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2425: ----------------------------------- Git Pull Request: https://github.com/jbosstm/narayana/pull/869 (was: https://github.com/jbosstm/narayana/pull/857) > Upgrade to latest wildfly version > --------------------------------- > > Key: JBTM-2425 > URL: https://issues.jboss.org/browse/JBTM-2425 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > Latest is 10.0.0.Alpha3-SNAPSHOT -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2425) Upgrade to latest wildfly version

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2425?page=com.atlassian.jira.plugin.... ] Michael Musgrove reopened JBTM-2425: ------------------------------------ Needs an upgrade to 10.0.0.Alpha4-SNAPSHOT > Upgrade to latest wildfly version > --------------------------------- > > Key: JBTM-2425 > URL: https://issues.jboss.org/browse/JBTM-2425 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > Latest is 10.0.0.Alpha3-SNAPSHOT -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1359) HA Recovery Manager

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1359?page=com.atlassian.jira.plugin.... ] Michael Musgrove commented on JBTM-1359: ---------------------------------------- I have a fix for this (see PR) but I have dropped the priority to optional since the original requirement (PRODMGT-405) was rejected. > HA Recovery Manager > ------------------- > > Key: JBTM-1359 > URL: https://issues.jboss.org/browse/JBTM-1359 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTA, JTS, Recovery, XTS > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Priority: Optional > Fix For: 6.later > > Original Estimate: 3 weeks > Remaining Estimate: 3 weeks > > JTA should work, but must consider JTS and XTS too (encoded IP addresses in log records) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1359) HA Recovery Manager

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1359?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-1359: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/668 > HA Recovery Manager > ------------------- > > Key: JBTM-1359 > URL: https://issues.jboss.org/browse/JBTM-1359 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTA, JTS, Recovery, XTS > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Priority: Optional > Fix For: 6.later > > Original Estimate: 3 weeks > Remaining Estimate: 3 weeks > > JTA should work, but must consider JTS and XTS too (encoded IP addresses in log records) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 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 June 2015