October 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9455) WFLYTX0001: Unable to roll back active transaction thrown for EJB bridge transactions

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/WFLY-9455?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka updated WFLY-9455: ---------------------------------- Steps to Reproduce: Could be reproduced with jbosstm quickstart at https://github.com/jbosstm/quickstart {code} export JBOSS_HOME=... cp $JBOSS_HOME/docs/examples/config/standalone-xts.xml $JBOSS_HOME/standalone/configuration mvn clean; mvn install -pl XTS/wsat-jta-multi_service -am -Parq -Dtest=BridgeFromJTATest#testCommit {code} was: Could be reproduced with jbosstm quickstart at https://github.com/jbosstm/quickstart {code} export JBOSS_HOME=... cp $JBOSS_HOME/docs/example/config/standalone-xts.xml standalone/configuration mvn clean; mvn install -pl XTS/wsat-jta-multi_service -am -Parq -Dtest=BridgeFromJTATest#testCommit {code} > WFLYTX0001: Unable to roll back active transaction thrown for EJB bridge transactions > ------------------------------------------------------------------------------------- > > Key: WFLY-9455 > URL: https://issues.jboss.org/browse/WFLY-9455 > Project: WildFly > Issue Type: Bug > Components: XTS > Affects Versions: 11.0.0.CR1 > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > > It happens to get exception > {code} > ERROR [org.jboss.as.txn] (default task-12) WFLYTX0003: APPLICATION ERROR: transaction still active in request with status 0 > ERROR [org.jboss.as.txn] (default task-12) WFLYTX0001: Unable to roll back active transaction: javax.transaction.SystemException: WFTXN0032: Rollback not allowed on imported transaction > at org.wildfly.transaction.client.LocalTransaction.rollbackAndDissociate(LocalTransaction.java:100) > at org.wildfly.transaction.client.ContextTransactionManager.rollback(ContextTransactionManager.java:83) > at org.jboss.as.txn.deployment.TransactionRollbackSetupAction.checkTransactionStatus(TransactionRollbackSetupAction.java:137) > at org.jboss.as.txn.deployment.TransactionRollbackSetupAction.teardown(TransactionRollbackSetupAction.java:67) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1510) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508) > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:272) > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81) > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:104) > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:326) > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:812) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > {code} > when using XTS transactions bridged to JTA for EJB handling. This happens on change of integration layer for WFTC in WFLY11. > The integration issues were already discussed as part of the JBTM-2853. > Here I hit a trouble of having log filled with the exception mentioned above. This does not cause a functionality trouble but the log is ugly filled with ERRORs. > The trouble seems to be caused by the fact that transaction is imported on ivocation of WS > https://github.com/wildfly/wildfly/blob/master/webservices/server-integra... > but as it was suspended in the integration code before > https://github.com/jbosstm/narayana/blob/master/txbridge/src/main/java/or... > now the WFTC holds the notion about the transaction even on call of > https://github.com/wildfly/wildfly/blob/master/transactions/src/main/java... > and such transaction is tried to be rollback which is forbidden on WFTC for imported ones and thus at least ERROR msg is written to the log. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1779) JDK 9 build drools: upgrade plugins (enforcer, revapi, javadoc, ...) to be JDK 9 compatible

by Petr Široký (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1779?page=com.atlassian.jira.plugi... ] Petr Široký updated DROOLS-1779: -------------------------------- Fix Version/s: 7.5.0.Final > JDK 9 build drools: upgrade plugins (enforcer, revapi, javadoc, ...) to be JDK 9 compatible > ------------------------------------------------------------------------------------------- > > Key: DROOLS-1779 > URL: https://issues.jboss.org/browse/DROOLS-1779 > Project: Drools > Issue Type: Task > Reporter: Geoffrey De Smet > Assignee: Petr Široký > Priority: Critical > Fix For: 7.5.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-9502) javax.naming.InvalidNameException: WFNAM00007: Invalid URL scheme name "null" when jms bridge is trying to do remote lookup on EAP6/HornetQ

by Martin Švehla (JIRA)

[ https://issues.jboss.org/browse/WFLY-9502?page=com.atlassian.jira.plugin.... ] Martin Švehla moved JBEAP-13668 to WFLY-9502: --------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-9502 (was: JBEAP-13668) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: JMS Naming (was: ActiveMQ) (was: Naming) Affects Version/s: 11.0.0.Final (was: 7.1.0.CR3) > javax.naming.InvalidNameException: WFNAM00007: Invalid URL scheme name "null" when jms bridge is trying to do remote lookup on EAP6/HornetQ > ------------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-9502 > URL: https://issues.jboss.org/browse/WFLY-9502 > Project: WildFly > Issue Type: Bug > Components: JMS, Naming > Affects Versions: 11.0.0.Final > Reporter: Martin Švehla > Assignee: Martyn Taylor > Priority: Critical > > When I create jms bridge on EAP7 that tries to connect to EAP6, it throws following issue when trying to do remote lookup for connection factory or destination on EAP6. > {code} > 2017-10-31 09:44:18,769 WARN [org.apache.activemq.artemis.jms.bridge] (Thread-102) AMQ342010: Failed to connect JMS Bridge N/A: javax.naming.InvalidNameException: WFNAM00007: Invalid URL scheme name "null" > at org.wildfly.naming.client.WildFlyRootContext.getProviderContext(WildFlyRootContext.java:808) > at org.wildfly.naming.client.WildFlyRootContext.lookup(WildFlyRootContext.java:140) > at javax.naming.InitialContext.lookup(InitialContext.java:417) > at javax.naming.InitialContext.lookup(InitialContext.java:417) > at org.apache.activemq.artemis.jms.bridge.impl.JNDIFactorySupport.createObject(JNDIFactorySupport.java:46) > at org.apache.activemq.artemis.jms.bridge.impl.JNDIDestinationFactory.createDestination(JNDIDestinationFactory.java:32) > at org.apache.activemq.artemis.jms.bridge.impl.JMSBridgeImpl.setupJMSObjects(JMSBridgeImpl.java:1072) > at org.apache.activemq.artemis.jms.bridge.impl.JMSBridgeImpl.setupJMSObjectsWithRetry(JMSBridgeImpl.java:1247) > at org.apache.activemq.artemis.jms.bridge.impl.JMSBridgeImpl.access$2600(JMSBridgeImpl.java:75) > at org.apache.activemq.artemis.jms.bridge.impl.JMSBridgeImpl$FailureHandler.run(JMSBridgeImpl.java:1747) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > {\code} > When debugging I noticed that WildFlyRootContext.getProviderContext there's no NamingProviderFactory available to resolve the name, so I think the error message is just a consequence of that. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2082) Prepare drools-wb-verifier module for static code analysis

by Jozef Marko (JIRA)

Jozef Marko created DROOLS-2082: ----------------------------------- Summary: Prepare drools-wb-verifier module for static code analysis Key: DROOLS-2082 URL: https://issues.jboss.org/browse/DROOLS-2082 Project: Drools Issue Type: Sub-task Reporter: Jozef Marko Assignee: Jozef Marko -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1801) [Guided Decision Table] Work Item Parameter values are not initialized properly

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1801?page=com.atlassian.jira.plugi... ] Jozef Marko closed DROOLS-1801. ------------------------------- Release Notes Text: No more reproducible due to GUVNOR-3143 Fix Version/s: 7.5.0.Final Resolution: Cannot Reproduce Bug > [Guided Decision Table] Work Item Parameter values are not initialized properly > ------------------------------------------------------------------------------- > > Key: DROOLS-1801 > URL: https://issues.jboss.org/browse/DROOLS-1801 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Affects Versions: 7.1.0.Beta2 > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Minor > Labels: reported-by-qe > Fix For: 7.5.0.Final > > > Is user wants to execute the same Work Item multiple times, he must always clear the parameter values from previous time. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1788) [Guided Decision Table] "Entry point" and "Binding" cannot be updated

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1788?page=com.atlassian.jira.plugi... ] Jozef Marko resolved DROOLS-1788. --------------------------------- Fix Version/s: 7.5.0.Final Resolution: Done > [Guided Decision Table] "Entry point" and "Binding" cannot be updated > --------------------------------------------------------------------- > > Key: DROOLS-1788 > URL: https://issues.jboss.org/browse/DROOLS-1788 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Reporter: Guilherme Carreiro > Assignee: Guilherme Carreiro > Fix For: 7.5.0.Final > > Attachments: bug-1.gif > > > It's impossible to update the "Entry point" and "Binding" fields in a "Condition Column". See: > !bug-1.gif|thumbnail! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2000) Test Scenario: Not possible to use a global

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2000?page=com.atlassian.jira.plugi... ] Jozef Marko reassigned DROOLS-2000: ----------------------------------- Assignee: Jozef Marko > Test Scenario: Not possible to use a global > ------------------------------------------- > > Key: DROOLS-2000 > URL: https://issues.jboss.org/browse/DROOLS-2000 > Project: Drools > Issue Type: Bug > Components: Test Scenarios Editor > Reporter: Toni Rikkola > Assignee: Jozef Marko > Priority: Blocker > > Tried with two globals. One added into a DRL file and another added with menu New->Global Variable(s). > Neither of these two show up in the Test Scenario popup. Tried a full build, reopening the test scenario and even restarting the workbench. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1993) Test Scenarios: Boolean dropdown does not set the default value, even when it is shown for the user

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1993?page=com.atlassian.jira.plugi... ] Jozef Marko closed DROOLS-1993. ------------------------------- Resolution: Cannot Reproduce Bug > Test Scenarios: Boolean dropdown does not set the default value, even when it is shown for the user > --------------------------------------------------------------------------------------------------- > > Key: DROOLS-1993 > URL: https://issues.jboss.org/browse/DROOLS-1993 > Project: Drools > Issue Type: Bug > Components: Test Scenarios Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Critical > Fix For: 7.5.0.Final > > > # Open "Are they old enough" > # Add new expect for 'application'. "true" is selected in the dropdown > # Run the scenario. Log shows that "" was compared instead of "true" -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1993) Test Scenarios: Boolean dropdown does not set the default value, even when it is shown for the user

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1993?page=com.atlassian.jira.plugi... ] Jozef Marko closed DROOLS-1993. ------------------------------- Release Notes Text: Seems to be no more reproducible. Resolution: Cannot Reproduce Bug > Test Scenarios: Boolean dropdown does not set the default value, even when it is shown for the user > --------------------------------------------------------------------------------------------------- > > Key: DROOLS-1993 > URL: https://issues.jboss.org/browse/DROOLS-1993 > Project: Drools > Issue Type: Bug > Components: Test Scenarios Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Critical > > # Open "Are they old enough" > # Add new expect for 'application'. "true" is selected in the dropdown > # Run the scenario. Log shows that "" was compared instead of "true" -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1993) Test Scenarios: Boolean dropdown does not set the default value, even when it is shown for the user

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1993?page=com.atlassian.jira.plugi... ] Jozef Marko reopened DROOLS-1993: --------------------------------- > Test Scenarios: Boolean dropdown does not set the default value, even when it is shown for the user > --------------------------------------------------------------------------------------------------- > > Key: DROOLS-1993 > URL: https://issues.jboss.org/browse/DROOLS-1993 > Project: Drools > Issue Type: Bug > Components: Test Scenarios Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Critical > Fix For: 7.5.0.Final > > > # Open "Are they old enough" > # Add new expect for 'application'. "true" is selected in the dropdown > # Run the scenario. Log shows that "" was compared instead of "true" -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2017