March 2016 - jbossts-issues - Jboss List Archives

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

by Jive JIRA Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2624?page=com.atlassian.jira.plugin.... ] Jive JIRA Integration updated JBTM-2624: ---------------------------------------- Forum Reference: https://developer.jboss.org/message/953631#953631 > 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-223) Check WL-to-JBossTS interoperability (via JTS).

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-223?page=com.atlassian.jira.plugin.s... ] Issue was automatically transitioned when Michael Musgrove created pull request #992 in GitHub ---------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Coding In Progress) > Check WL-to-JBossTS interoperability (via JTS). > ----------------------------------------------- > > Key: JBTM-223 > URL: https://issues.jboss.org/browse/JBTM-223 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTS > Reporter: Mark Little > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > Extensible header structure corba call > key value slot ids > slot for transaction context is not in the well known slot > tx context was not defined so we used the market leader at the time -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2643) "number-of-application-rollbacks" statistic counted multiple times during single rollback

by Anonymous (JIRA)

[ https://issues.jboss.org/browse/JBTM-2643?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when TomasHofman created pull request #991 in GitHub ----------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Coding In Progress) > "number-of-application-rollbacks" statistic counted multiple times during single rollback > ----------------------------------------------------------------------------------------- > > Key: JBTM-2643 > URL: https://issues.jboss.org/browse/JBTM-2643 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transaction Core > Reporter: Tomas Hofman > Assignee: Tomas Hofman > > During transaction timeout, "number-of-application-rollbacks" stat is incremented twice. As a result, "number-of-application-rollbacks" can be higher then "number-of-aborted-transactions". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2643) "number-of-application-rollbacks" statistic counted multiple times during single rollback

by Tomas Hofman (JIRA)

[ https://issues.jboss.org/browse/JBTM-2643?page=com.atlassian.jira.plugin.... ] Tomas Hofman updated JBTM-2643: ------------------------------- Status: Pull Request Sent (was: Pull Request Sent) Git Pull Request: https://github.com/jbosstm/narayana/pull/991 > "number-of-application-rollbacks" statistic counted multiple times during single rollback > ----------------------------------------------------------------------------------------- > > Key: JBTM-2643 > URL: https://issues.jboss.org/browse/JBTM-2643 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transaction Core > Reporter: Tomas Hofman > Assignee: Tomas Hofman > > During transaction timeout, "number-of-application-rollbacks" stat is incremented twice. As a result, "number-of-application-rollbacks" can be higher then "number-of-aborted-transactions". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2465) PR job is missing perf regression output

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2465?page=com.atlassian.jira.plugin.... ] Michael Musgrove closed JBTM-2465. ---------------------------------- Resolution: Out of Date > PR job is missing perf regression output > ---------------------------------------- > > Key: JBTM-2465 > URL: https://issues.jboss.org/browse/JBTM-2465 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.2.0 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.later > > > The PERF axis of the CI job https://github.com/jbosstm/narayana/pull/889 did not produce any output because of the following error: > {code} > Error: Unable to access jarfile /home/hudson/workspace/btny-pulls-narayana-jdk8/PROFILE/PERF/jdk/jdk8.latest/label/linux/tmp/performance/narayana/ArjunaCore/arjuna/target/benchmarks.jar > cp: cannot stat `/home/hudson/workspace/btny-pulls-narayana-jdk8/PROFILE/PERF/jdk/jdk8.latest/label/linux/tmp/performance/narayana/ArjunaCore/arjuna/target/jmh/com.hp.mwtests.ts.arjuna.performance.Performance1-master.csv': No such file or directory > Error: Unable to access jarfile /home/hudson/workspace/btny-pulls-narayana-jdk8/PROFILE/PERF/jdk/jdk8.latest/label/linux/tmp/performance/narayana/ArjunaCore/arjuna/target/benchmarks.jar > cp: cannot stat `/home/hudson/workspace/btny-pulls-narayana-jdk8/PROFILE/PERF/jdk/jdk8.latest/label/linux/tmp/performance/narayana/ArjunaCore/arjuna/target/jmh/com.hp.mwtests.ts.arjuna.atomicaction.CheckedActionTest-master.csv': No such file or directory > Error: Unable to access jarfile /home/hudson/workspace/btny-pulls-narayana-jdk8/PROFILE/PERF/jdk/jdk8.latest/label/linux/tmp/performance/narayana/ArjunaJTA/jta/target/benchmarks.jar > cp: cannot stat `/home/hudson/workspace/btny-pulls-narayana-jdk8/PROFILE/PERF/jdk/jdk8.latest/label/linux/tmp/performance/narayana/ArjunaJTA/jta/target/jmh/com.arjuna.ats.jta.xa.performance.JTAStoreTests-master.csv': No such file or directory > no benchmarks to compare > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2643) "number-of-application-rollbacks" statistic counted multiple times during single rollback

by Tomas Hofman (JIRA)

[ https://issues.jboss.org/browse/JBTM-2643?page=com.atlassian.jira.plugin.... ] Tomas Hofman commented on JBTM-2643: ------------------------------------ Two stacktraces where the value is incremented: {code} "Transaction Reaper Worker 1@13945" daemon prio=5 tid=0x21b nid=NA runnable java.lang.Thread.State: RUNNABLE at com.arjuna.ats.arjuna.coordinator.TxStats.incrementApplicationRollbacks(TxStats.java:263) at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.cancel(TwoPhaseCoordinator.java:120) at com.arjuna.ats.arjuna.AtomicAction.cancel(AtomicAction.java:215) at com.arjuna.ats.arjuna.coordinator.TransactionReaper.doCancellations(TransactionReaper.java:381) at com.arjuna.ats.internal.arjuna.coordinator.ReaperWorkerThread.run(ReaperWorkerThread.java:78) "default task-54@13969" prio=5 tid=0x21f nid=NA runnable java.lang.Thread.State: RUNNABLE at com.arjuna.ats.arjuna.coordinator.TxStats.incrementApplicationRollbacks(TxStats.java:263) at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.cancel(TwoPhaseCoordinator.java:120) at com.arjuna.ats.arjuna.AtomicAction.abort(AtomicAction.java:186) at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.rollbackAndDisassociate(TransactionImple.java:1282) at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.rollback(BaseTransaction.java:143) at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.rollback(BaseTransactionManagerDelegate.java:134) at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:93) at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:279) at org.jboss.as.ejb3.tx.CMTTxInterceptor.requiresNew(CMTTxInterceptor.java:349) at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:241) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:43) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:100) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:66) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:54) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356) at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:636) at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:61) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356) at org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:195) at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:185) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:73) at org.jboss.as.quickstarts.ear.client.GreeterEJBLocal$$$view7.sayHello(Unknown Source:-1) at org.jboss.as.quickstarts.ear.controller.GreeterBean.sayHello(GreeterBean.java:84) at sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java:-1) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.sun.el.util.ReflectionUtil.invokeMethod(ReflectionUtil.java:181) at com.sun.el.parser.AstValue.invoke(AstValue.java:289) at com.sun.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:304) at org.jboss.weld.util.el.ForwardingMethodExpression.invoke(ForwardingMethodExpression.java:40) at org.jboss.weld.el.WeldMethodExpression.invoke(WeldMethodExpression.java:50) at org.jboss.weld.util.el.ForwardingMethodExpression.invoke(ForwardingMethodExpression.java:40) at org.jboss.weld.el.WeldMethodExpression.invoke(WeldMethodExpression.java:50) at com.sun.faces.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:105) at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:87) at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:102) at javax.faces.component.UICommand.broadcast(UICommand.java:315) at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:790) at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:1282) at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:81) at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:198) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:658) at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85) at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62) at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131) at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60) at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77) at io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50) at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:284) at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:263) at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81) at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:174) at io.undertow.server.Connectors.executeRootHandler(Connectors.java:202) at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:793) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) {code} > "number-of-application-rollbacks" statistic counted multiple times during single rollback > ----------------------------------------------------------------------------------------- > > Key: JBTM-2643 > URL: https://issues.jboss.org/browse/JBTM-2643 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transaction Core > Reporter: Tomas Hofman > Assignee: Tomas Hofman > > During transaction timeout, "number-of-application-rollbacks" stat is incremented twice. As a result, "number-of-application-rollbacks" can be higher then "number-of-aborted-transactions". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2643) "number-of-application-rollbacks" statistic counted multiple times during single rollback

by Tomas Hofman (JIRA)

[ https://issues.jboss.org/browse/JBTM-2643?page=com.atlassian.jira.plugin.... ] Work on JBTM-2643 started by Tomas Hofman. ------------------------------------------ > "number-of-application-rollbacks" statistic counted multiple times during single rollback > ----------------------------------------------------------------------------------------- > > Key: JBTM-2643 > URL: https://issues.jboss.org/browse/JBTM-2643 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transaction Core > Reporter: Tomas Hofman > Assignee: Tomas Hofman > > During transaction timeout, "number-of-application-rollbacks" stat is incremented twice. As a result, "number-of-application-rollbacks" can be higher then "number-of-aborted-transactions". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2643) "number-of-application-rollbacks" statistic counted multiple times during single rollback

by Tomas Hofman (JIRA)

Tomas Hofman created JBTM-2643: ---------------------------------- Summary: "number-of-application-rollbacks" statistic counted multiple times during single rollback Key: JBTM-2643 URL: https://issues.jboss.org/browse/JBTM-2643 Project: JBoss Transaction Manager Issue Type: Bug Components: Transaction Core Reporter: Tomas Hofman Assignee: Tomas Hofman During transaction timeout, "number-of-application-rollbacks" stat is incremented twice. As a result, "number-of-application-rollbacks" can be higher then "number-of-aborted-transactions". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2606) Create Spring Boot starter for Narayana

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2606?page=com.atlassian.jira.plugin.... ] Work on JBTM-2606 stopped by Gytis Trikleris. --------------------------------------------- > Create Spring Boot starter for Narayana > --------------------------------------- > > Key: JBTM-2606 > URL: https://issues.jboss.org/browse/JBTM-2606 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: JTA > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > Spring provides a bunch of Spring Boot starter artefacts in order to make integration of certain projects easier. We should investigate having one for Narayana. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2642) Interoperability issues with ArjunaJTS CosTransactions idl

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2642?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2642: ----------------------------------- Summary: Interoperability issues with ArjunaJTS CosTransactions idl (was: ArjunaJTS CosTransactions idl is not spec compliant) > Interoperability issues with ArjunaJTS CosTransactions idl > ---------------------------------------------------------- > > Key: JBTM-2642 > URL: https://issues.jboss.org/browse/JBTM-2642 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Reporter: Michael Musgrove > Assignee: Michael Musgrove > > The copy of CosTransactions.idl in our source tree does not match any of the OTS spec versions, in partciular the enum ordering of Status values is different so we get the wrong status when asking foreign application servers for the status of a transaction. > I checked versions 1.0 and 1.1 (http://www.omg.org/spec/OTS/) and versions 1.3 and 1.4 (http://www.omg.org/spec/TRANS/), I could not locate version 1.2. The idl used by other application servers seems to match versions 1.3 and 1.4: > {code} > enum Status { > StatusActive, > StatusMarkedRollback, > StatusPrepared, > StatusCommitted, > StatusRolledBack, > StatusUnknown, > StatusNoTransaction, > StatusPreparing, > StatusCommitting, > StatusRollingBack > }; > {code} > whereas we are using > {code} > enum Status { StatusActive, StatusMarkedRollback, StatusPrepared, > StatusCommitted, StatusRolledBack, StatusUnknown, > StatusPreparing, StatusCommitting, StatusRollingBack, > StatusNoTransaction }; > {code} > Notice that the enum position of StatusNoTransaction is different. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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