[JBoss JIRA] (JBTM-2533) Possibility to run "scripts/hudson/narayana.sh" on different platforms.
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2533?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-2533:
--------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Possibility to run "scripts/hudson/narayana.sh" on different platforms.
> -----------------------------------------------------------------------
>
> Key: JBTM-2533
> URL: https://issues.jboss.org/browse/JBTM-2533
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Components: Testing
> Affects Versions: 5.2.5.Final
> Reporter: Hayk Hovsepyan
> Assignee: Hayk Hovsepyan
> Priority: Blocker
> Fix For: 5.next
>
>
> Currently "scripts/hudson/narayana.sh" uses "sed" command with "-i" option, so it looks like:
> "sed -i file -e expression".
> "-i" option is not supported on some platforms (HP-UX).
> We need to apply workaround here and modify "sed" commands to be in this format:
> "sed -e expression file > file.tmp && mv file.tmp file"
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months
[JBoss JIRA] (JBTM-2434) @Transactional annotation on stereotype leads to error "ARJUNA016107: Expected an @Transactional annotation at class and/or method level"
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2434?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson commented on JBTM-2434:
-------------------------------------
You could try doing your own custom build of WildFly with version 5.2.0 of Narayana in it or upgrade to WFLY 10?
> @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
> Fix For: 5.2.0
>
> 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.4.11#64026)
8 years, 7 months
[JBoss JIRA] (JBTM-2434) @Transactional annotation on stereotype leads to error "ARJUNA016107: Expected an @Transactional annotation at class and/or method level"
by Alexander Morozov (JIRA)
[ https://issues.jboss.org/browse/JBTM-2434?page=com.atlassian.jira.plugin.... ]
Alexander Morozov commented on JBTM-2434:
-----------------------------------------
Several days ago I've faced with the same issue, but on Wildfly 9.0.2 :(
> @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
> Fix For: 5.2.0
>
> 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.4.11#64026)
8 years, 7 months
[JBoss JIRA] (JBTM-2533) Possibility to run "scripts/hudson/narayana.sh" on different platforms.
by Hayk Hovsepyan (JIRA)
[ https://issues.jboss.org/browse/JBTM-2533?page=com.atlassian.jira.plugin.... ]
Work on JBTM-2533 started by Hayk Hovsepyan.
--------------------------------------------
> Possibility to run "scripts/hudson/narayana.sh" on different platforms.
> -----------------------------------------------------------------------
>
> Key: JBTM-2533
> URL: https://issues.jboss.org/browse/JBTM-2533
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Components: Testing
> Affects Versions: 5.2.5.Final
> Reporter: Hayk Hovsepyan
> Assignee: Hayk Hovsepyan
> Priority: Blocker
> Fix For: 5.next
>
>
> Currently "scripts/hudson/narayana.sh" uses "sed" command with "-i" option, so it looks like:
> "sed -i file -e expression".
> "-i" option is not supported on some platforms (HP-UX).
> We need to apply workaround here and modify "sed" commands to be in this format:
> "sed -e expression file > file.tmp && mv file.tmp file"
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months
[JBoss JIRA] (JBTM-2533) Possibility to run "scripts/hudson/narayana.sh" on different platforms.
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2533?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson commented on JBTM-2533:
-------------------------------------
Hi Hayk,
There isn't an "SLA" (read versioned API) on the script but if you are happy with that caveat, I am happy to review any PR for this.
Thanks,
Tom
> Possibility to run "scripts/hudson/narayana.sh" on different platforms.
> -----------------------------------------------------------------------
>
> Key: JBTM-2533
> URL: https://issues.jboss.org/browse/JBTM-2533
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Components: Testing
> Affects Versions: 5.2.5.Final
> Reporter: Hayk Hovsepyan
> Assignee: Hayk Hovsepyan
> Priority: Blocker
> Fix For: 5.next
>
>
> Currently "scripts/hudson/narayana.sh" uses "sed" command with "-i" option, so it looks like:
> "sed -i file -e expression".
> "-i" option is not supported on some platforms (HP-UX).
> We need to apply workaround here and modify "sed" commands to be in this format:
> "sed -e expression file > file.tmp && mv file.tmp file"
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months
[JBoss JIRA] (JBTM-2533) Possibility to run "scripts/hudson/narayana.sh" on different platforms.
by Hayk Hovsepyan (JIRA)
Hayk Hovsepyan created JBTM-2533:
------------------------------------
Summary: Possibility to run "scripts/hudson/narayana.sh" on different platforms.
Key: JBTM-2533
URL: https://issues.jboss.org/browse/JBTM-2533
Project: JBoss Transaction Manager
Issue Type: Feature Request
Components: Testing
Affects Versions: 5.2.5.Final
Reporter: Hayk Hovsepyan
Assignee: Hayk Hovsepyan
Priority: Blocker
Fix For: 5.next
Currently "scripts/hudson/narayana.sh" uses "sed" command with "-i" option, so it looks like:
"sed -i file -e expression".
"-i" option is not supported on some platforms (HP-UX).
We need to apply workaround here and modify "sed" commands to be in this format:
"sed -e expression file > file.tmp && mv file.tmp file"
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months
[JBoss JIRA] (JBTM-1340) BeanPopulator overhead needs looking into
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1340?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-1340:
--------------------------------
Attachment: SpeedTest.java
Hot_Spots.html
Call_Tree.html
> BeanPopulator overhead needs looking into
> -----------------------------------------
>
> Key: JBTM-1340
> URL: https://issues.jboss.org/browse/JBTM-1340
> Project: JBoss Transaction Manager
> Issue Type: Enhancement
> Components: Common
> Affects Versions: 4.17.2
> Environment: Mac OS 10.7
> Reporter: Mark Little
> Assignee: Tom Jenkinson
> Fix For: 5.next
>
> Attachments: Call_Tree.html, Hot_Spots.html, SpeedTest.java
>
>
> During profiling, BeanPopulator can represent a 7% overhead. It may not seem like a lot, but for something as relatively simple as what BeanPopulator should be doing, it seems to be quite a bit.
> 6.9% - 4,477 ms - 10,000 inv. com.arjuna.ats.arjuna.coordinator.TxStats.enabled
> 6.9% - 4,477 ms - 10,000 inv. com.arjuna.ats.arjuna.common.arjPropertyManager.getCoordinatorEnvironmentBean
> 6.9% - 4,476 ms - 10,000 inv. com.arjuna.common.internal.util.propertyservice.BeanPopulator.getDefaultInstance
> 6.9% - 4,476 ms - 10,000 inv. com.arjuna.common.internal.util.propertyservice.BeanPopulator.getNamedInstance
> 2.5% - 1,587 ms - 10,000 inv. java.lang.StringBuilder.<init>
> 2.3% - 1,507 ms - 10,000 inv. java.lang.StringBuilder.toString
> 0.0% - 320 µs - 10,000 inv. java.util.concurrent.ConcurrentMap.containsKey
> 0.0% - 61 µs - 10,000 inv. java.lang.Class.getName
> 0.0% - 25 µs - 10,000 inv. java.util.concurrent.ConcurrentMap.get
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months