September 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-1209) Automate Workload's Istio Config tab

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1209?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan commented on SWSQE-1209: --------------------------------------- https://github.com/Kiali-QE/kiali-qe-python/pull/325 > Automate Workload's Istio Config tab > ------------------------------------ > > Key: SWSQE-1209 > URL: https://issues.redhat.com/browse/SWSQE-1209 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > > https://github.com/kiali/kiali-ui/pull/1901 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-1209) Automate Workload's Istio Config tab

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1209?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan resolved SWSQE-1209. ----------------------------------- Resolution: Done > Automate Workload's Istio Config tab > ------------------------------------ > > Key: SWSQE-1209 > URL: https://issues.redhat.com/browse/SWSQE-1209 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > > https://github.com/kiali/kiali-ui/pull/1901 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (WFLY-13283) WFLYTX0001: Unable to roll back active transaction exception thrown from RTS inbound bridge

by Ondrej Chaloupka (Jira)

[ https://issues.redhat.com/browse/WFLY-13283?page=com.atlassian.jira.plugi... ] Ondrej Chaloupka updated WFLY-13283: ------------------------------------ Git Pull Request: (was: https://github.com/wildfly/wildfly/pull/13140) > WFLYTX0001: Unable to roll back active transaction exception thrown from RTS inbound bridge > ------------------------------------------------------------------------------------------- > > Key: WFLY-13283 > URL: https://issues.redhat.com/browse/WFLY-13283 > Project: WildFly > Issue Type: Bug > Components: Transactions > Affects Versions: 19.0.0.Final > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Major > > This is an integration problem of REST-AT transaction inbound bridge with WFTC client. > It's in the same way as there was for XTS txnbridge https://issues.redhat.com/browse/WFLY-9455 > The trouble is that REST-AT bridge implementation works with Narayana transaction manager. All the calls which go to the {{javax.transaction.TransactionManager}} is integrated to Narayana transaction manager backed by {{AtomicActions}} etc. > But WildFly is fully integrated with WFTC TransactionManager as a wrapper over the Narayana one. > The inbound bridge manages merging the REST-AT context with JTA context. On incoming REST call the InboundBridge is started and resume a transaction: > https://github.com/jbosstm/narayana/blob/5.10.4.Final/rts/at/bridge/src/m... > It's implemented by `ContainerRequestFilter` which is invoked on incoming call before the method is executed: > https://github.com/jbosstm/narayana/blob/5.10.4.Final/rts/at/bridge/src/m... > After execution is needed the transaction would be suspended again. In current time it happens for Narayana transaction but not for the WFTC transaction > Narayana `ContainerResponseFilter` handling: > * https://github.com/jbosstm/narayana/blob/5.10.4.Final/rts/at/bridge/src/m... > * https://github.com/jbosstm/narayana/blob/5.10.4.Final/rts/at/bridge/src/m... > (btw. the same is about handling of JAX-WS XTS txnbridge: https://github.com/jbosstm/narayana/blob/5.10.4.Final/txbridge/src/main/j...) > Now the issue is that WFLY WFTC Transaction is not suspended on the outbound. It means the EJB still think there is an active transaction. But it's only the WFTC wrapper which wraps an empty Narayana transaction. All the real business work was done, the real transaction was suspended. > When the call leaves the EJB there is a action which ensures no transaction leaves the EJB method (https://github.com/wildfly/wildfly/blob/19.0.0.Final/transactions/src/mai...). When there is some active context it's rolled-back. So WFTC Transaction rollback is called but as the WFTC holds an empty wrapper the rollback finishes with exception server log message[1]. > [1] > {quote} > ERROR [org.jboss.as.txn] (default task-1) WFLYTX0003: APPLICATION ERROR: transaction still active in request with status 0 > ERROR [org.jboss.as.txn] (default task-1) 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:105) > 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:1543) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1541) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1541) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1541) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1541) > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:249) > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:78) > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:99) > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:376) > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:830) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377) > at java.lang.Thread.run(Thread.java:748) > {quote} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (WFLY-13740) Upgrade Narayana to 5.10.6.Final

by Ondrej Chaloupka (Jira)

[ https://issues.redhat.com/browse/WFLY-13740?page=com.atlassian.jira.plugi... ] Ondrej Chaloupka edited comment on WFLY-13740 at 9/7/20 3:12 AM: ----------------------------------------------------------------- Release notes for Narayana 5.10.6.Final are available at: https://issues.redhat.com/secure/ReleaseNote.jspa?projectId=12310200&vers... was (Author: ochaloup): Release notes for Narayana 5.10.6.Final is available at: https://issues.redhat.com/secure/ReleaseNote.jspa?projectId=12310200&vers... > Upgrade Narayana to 5.10.6.Final > -------------------------------- > > Key: WFLY-13740 > URL: https://issues.redhat.com/browse/WFLY-13740 > Project: WildFly > Issue Type: Component Upgrade > Components: Transactions > Reporter: Bartosz Spyrko-Smietanko > Assignee: Ondrej Chaloupka > Priority: Major > Labels: downstream_dependency > Fix For: 21.0.0.Beta1 > > > Component upgrade of Narayana to version 5.10.6.Final. > This is to track fix for JBTM-3337 in Wildfly required by downstream -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (WFLY-13740) Upgrade Narayana to 5.10.6.Final

by Ondrej Chaloupka (Jira)

[ https://issues.redhat.com/browse/WFLY-13740?page=com.atlassian.jira.plugi... ] Ondrej Chaloupka commented on WFLY-13740: ----------------------------------------- Release notes for Narayana 5.10.6.Final is available at: https://issues.redhat.com/secure/ReleaseNote.jspa?projectId=12310200&vers... > Upgrade Narayana to 5.10.6.Final > -------------------------------- > > Key: WFLY-13740 > URL: https://issues.redhat.com/browse/WFLY-13740 > Project: WildFly > Issue Type: Component Upgrade > Components: Transactions > Reporter: Bartosz Spyrko-Smietanko > Assignee: Ondrej Chaloupka > Priority: Major > Labels: downstream_dependency > Fix For: 21.0.0.Beta1 > > > Component upgrade of Narayana to version 5.10.6.Final. > This is to track fix for JBTM-3337 in Wildfly required by downstream -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (WFLY-13824) Use TimeUtil timeout adjustments in cases of timeout defined on JMS receive

by Ondrej Chaloupka (Jira)

[ https://issues.redhat.com/browse/WFLY-13824?page=com.atlassian.jira.plugi... ] Ondrej Chaloupka updated WFLY-13824: ------------------------------------ Git Pull Request: https://github.com/wildfly/wildfly/pull/13537 > Use TimeUtil timeout adjustments in cases of timeout defined on JMS receive > --------------------------------------------------------------------------- > > Key: WFLY-13824 > URL: https://issues.redhat.com/browse/WFLY-13824 > Project: WildFly > Issue Type: Enhancement > Components: Test Suite > Affects Versions: 20.0.1.Final > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Minor > > There are several places in testsuite where is omitted usage of {{TimeoutUtil}} to allow adjustment of timeouts. When user defines the property {{-Dtimeout.factor}} when he runs the testsuite the waiting timeout for the JMS receival should be adjusted as well. > This issue comes from issues hit on Narayana CI. The machine is slow and running the WildFly testsuite with the Narayana SNAPSHOTs is unstable because of timeouts are not configurable at many places. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-5092) Windows Service cannot be stopped when using custom JAVA_HOME path

by Lukas Vydra (Jira)

[ https://issues.redhat.com/browse/WFCORE-5092?page=com.atlassian.jira.plug... ] Lukas Vydra commented on WFCORE-5092: ------------------------------------- Hi [~wraaflaub], I suppose that passing JAVA_HOME variable via /environment parameter is a supported solution. In the case of NO_PAUSE env variable, I don't think that calling jboss-cli.bat from service.bat with pausing makes any sense. So I have added NOPAUSE=Y to StopParams in PR. > Windows Service cannot be stopped when using custom JAVA_HOME path > ------------------------------------------------------------------ > > Key: WFCORE-5092 > URL: https://issues.redhat.com/browse/WFCORE-5092 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Affects Versions: 11.0.0.Final > Reporter: Walter Raaflaub > Assignee: Lukas Vydra > Priority: Major > > I am running keycloak in a Wildfly container as a Windows service on Windows Server 2019. The service starts up and works correctly; but it hangs when I try to stop it. > There is no global JAVA_HOME environment variable defined on the server; I'm using a custom JAVA_HOME path that I have configured in standalone.conf.bat. > While stopping, the service issues the following warning in stdout.log: > {noformat} > JAVA_HOME is not set. Unexpected results may occur. > Set JAVA_HOME to the directory of your local JDK to avoid this message. > Drcken Sie eine beliebige Taste . . . > {noformat} > (Drücken Sie eine beliebige Taste . . . = German vor "Press any key ...") > It seems that when stopping the service, the JAVA_HOME setting is not correctly passed to the jboss-cli.bat script. The script seems to be waiting for user input, which is akward in a Windows service. That means that also the NOPAUSE setting is not passed correctly to the jboss-cli.bat script. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-5111) Upgrade JBoss MSC from 1.4.11 to 1.4.12

by Richard Opalka (Jira)

[ https://issues.redhat.com/browse/WFCORE-5111?page=com.atlassian.jira.plug... ] Richard Opalka updated WFCORE-5111: ----------------------------------- Release Notes Text: (was: https://github.com/jboss/xerces/compare/jboss-2.12.0.SP02...jboss-2.12.0.SP3) > Upgrade JBoss MSC from 1.4.11 to 1.4.12 > --------------------------------------- > > Key: WFCORE-5111 > URL: https://issues.redhat.com/browse/WFCORE-5111 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Server > Reporter: Richard Opalka > Assignee: Richard Opalka > Priority: Major > Fix For: 13.0.0.Beta6 > > > Brings in: > Fixes: > MSC-252 Removing double word of service in the thrown exception ServiceNotFoundException > Enhancements: > MSC-255 Deprecating StabilityMonitor & StabilityStatistics -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-5111) Upgrade JBoss MSC from 1.4.11 to 1.4.12

by Richard Opalka (Jira)

[ https://issues.redhat.com/browse/WFCORE-5111?page=com.atlassian.jira.plug... ] Richard Opalka updated WFCORE-5111: ----------------------------------- Release Notes Text: https://github.com/jboss/xerces/compare/jboss-2.12.0.SP02...jboss-2.12.0.SP3 > Upgrade JBoss MSC from 1.4.11 to 1.4.12 > --------------------------------------- > > Key: WFCORE-5111 > URL: https://issues.redhat.com/browse/WFCORE-5111 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Server > Reporter: Richard Opalka > Assignee: Richard Opalka > Priority: Major > Fix For: 13.0.0.Beta6 > > > Brings in: > Fixes: > MSC-252 Removing double word of service in the thrown exception ServiceNotFoundException > Enhancements: > MSC-255 Deprecating StabilityMonitor & StabilityStatistics -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (WFLY-13633) Undeployed CMR resource JNDI names are not deregisted as needing to be treated as CMR

by Lin Gao (Jira)

[ https://issues.redhat.com/browse/WFLY-13633?page=com.atlassian.jira.plugi... ] Lin Gao updated WFLY-13633: --------------------------- Labels: downstream_dependency (was: ) > Undeployed CMR resource JNDI names are not deregisted as needing to be treated as CMR > ------------------------------------------------------------------------------------- > > Key: WFLY-13633 > URL: https://issues.redhat.com/browse/WFLY-13633 > Project: WildFly > Issue Type: Bug > Components: Transactions > Reporter: Thomas Jenkinson > Assignee: Michael Musgrove > Priority: Blocker > Labels: downstream_dependency > > https://github.com/wildfly/wildfly/blob/master/transactions/src/main/java... does not remove the JNDI name from the list of names that Narayana will treat as CMR resources as it is removed from a copy of the map: https://github.com/jbosstm/narayana/blob/48818111d12d2e51b52082a00bcb6060... > This means that if Narayana encounters another resource at a later time with the same JNDI name it will consider it is a CMR resource. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

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 September 2020