September 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-10986) Concurrent Modification Exception when starting server with external JMS broker

by Martin Styk (JIRA)

Martin Styk created WFLY-10986: ---------------------------------- Summary: Concurrent Modification Exception when starting server with external JMS broker Key: WFLY-10986 URL: https://issues.jboss.org/browse/WFLY-10986 Project: WildFly Issue Type: Bug Components: JMS Affects Versions: 14.0.1.Final Reporter: Martin Styk Assignee: Jeff Mesnil Priority: Blocker Start of a WildFly with resource adapter configured to remote messaging broker sometimes fails with following error. {code} ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.resourceadapters.ra."wmq.jmsra".CF: org.jboss.msc.service.StartException in service jboss.resourceadapters.ra."wmq.jmsra".CF: Failed to start service at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1728) at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1556) at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1364) at java.lang.Thread.run(Thread.java:748) Caused by: java.util.ConcurrentModificationException at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:909) at java.util.ArrayList$Itr.next(ArrayList.java:859) at java.util.Collections$UnmodifiableCollection$1.next(Collections.java:1042) at org.jboss.as.connector.metadata.api.resourceadapter.ActivationSecurityUtil.isLegacySecurityRequired(ActivationSecurityUtil.java:41) at org.jboss.as.connector.subsystems.resourceadapters.ConnectionDefinitionService.start(ConnectionDefinitionService.java:68) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1736) at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1698) ... 6 more {code} This issue was introduced in fix for WFLY-9978 in [this commit |https://github.com/ehsavoie/wildfly/commit/8d35c77130c8ba8c47008e1de1225971fa5d8c2e] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2977) [DMN Designer] Optimize Header Metadata constructor

by Jozef Marko (JIRA)

Jozef Marko created DROOLS-2977: ----------------------------------- Summary: [DMN Designer] Optimize Header Metadata constructor Key: DROOLS-2977 URL: https://issues.jboss.org/browse/DROOLS-2977 Project: Drools Issue Type: Task Components: DMN Editor Reporter: Jozef Marko Assignee: Michael Anstis Priority: Minor The header metadata constructor takes as arguments as {{Expression}} so {{HasExpression}} arguments. After some [investigation|https://github.com/kiegroup/kie-wb-common/pull/2085#discuss...] we found out both arguments should be consolidated to one. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10985) UnsupportedOperationException thrown during start if CredentialReference is used in messaging-activemq subsystem

by Miroslav Novak (JIRA)

[ https://issues.jboss.org/browse/WFLY-10985?page=com.atlassian.jira.plugin... ] Miroslav Novak updated WFLY-10985: ---------------------------------- Attachment: standalone-full-ha.xml > UnsupportedOperationException thrown during start if CredentialReference is used in messaging-activemq subsystem > ---------------------------------------------------------------------------------------------------------------- > > Key: WFLY-10985 > URL: https://issues.jboss.org/browse/WFLY-10985 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 14.0.0.Final > Reporter: Miroslav Novak > Assignee: Jeff Mesnil > Priority: Critical > Attachments: standalone-full-ha.xml > > > If messaging subsystem is referencing elytron's credential store like in: > {code} > <bridge name="myBridge" queue-name="jms.queue.InQueue" forwarding-address="jms.queue.OutQueue" ha="true" reconnect-attempts="-1" use-duplicate-detection="true" user="johnOut" static-connectors="bridge-connector"> > <credential-reference store="bridge-cs001" alias="john_out_alias_wrong"/> > </bridge> > {code} > then during start server throws exception: > {code} > 12:49:04,367 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 66) WFLYCTL0013: Operation ("add") failed - address: ([ > ("subsystem" => "messaging-activemq"), > ("server" => "default") > ]): java.lang.UnsupportedOperationException > at org.jboss.msc.service.ServiceBuilderImpl.addDependency(ServiceBuilderImpl.java:409) > at org.jboss.msc.service.DelegatingServiceBuilder.addDependency(DelegatingServiceBuilder.java:147) > at org.jboss.as.controller.security.CredentialReference.getCredentialSourceSupplier(CredentialReference.java:323) > at org.wildfly.extension.messaging.activemq.ServerAdd.addBridgeCredentialStoreReference(ServerAdd.java:732) > at org.wildfly.extension.messaging.activemq.ServerAdd.access$200(ServerAdd.java:175) > at org.wildfly.extension.messaging.activemq.ServerAdd$2.execute(ServerAdd.java:439) > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:999) > at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:743) > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:467) > at org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:384) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1349) > at java.lang.Thread.run(Thread.java:748) > at org.jboss.threads.JBossThread.run(JBossThread.java:485) > {code} > Attaching standalone-full-ha.xml with which is possible to reproduce the issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10985) UnsupportedOperationException thrown during start if CredentialReference is used in messaging-activemq subsystem

by Miroslav Novak (JIRA)

Miroslav Novak created WFLY-10985: ------------------------------------- Summary: UnsupportedOperationException thrown during start if CredentialReference is used in messaging-activemq subsystem Key: WFLY-10985 URL: https://issues.jboss.org/browse/WFLY-10985 Project: WildFly Issue Type: Bug Components: JMS Affects Versions: 14.0.0.Final Reporter: Miroslav Novak Assignee: Jeff Mesnil Priority: Critical If messaging subsystem is referencing elytron's credential store like in: {code} <bridge name="myBridge" queue-name="jms.queue.InQueue" forwarding-address="jms.queue.OutQueue" ha="true" reconnect-attempts="-1" use-duplicate-detection="true" user="johnOut" static-connectors="bridge-connector"> <credential-reference store="bridge-cs001" alias="john_out_alias_wrong"/> </bridge> {code} then during start server throws exception: {code} 12:49:04,367 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 66) WFLYCTL0013: Operation ("add") failed - address: ([ ("subsystem" => "messaging-activemq"), ("server" => "default") ]): java.lang.UnsupportedOperationException at org.jboss.msc.service.ServiceBuilderImpl.addDependency(ServiceBuilderImpl.java:409) at org.jboss.msc.service.DelegatingServiceBuilder.addDependency(DelegatingServiceBuilder.java:147) at org.jboss.as.controller.security.CredentialReference.getCredentialSourceSupplier(CredentialReference.java:323) at org.wildfly.extension.messaging.activemq.ServerAdd.addBridgeCredentialStoreReference(ServerAdd.java:732) at org.wildfly.extension.messaging.activemq.ServerAdd.access$200(ServerAdd.java:175) at org.wildfly.extension.messaging.activemq.ServerAdd$2.execute(ServerAdd.java:439) at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:999) at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:743) at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:467) at org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:384) at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1349) at java.lang.Thread.run(Thread.java:748) at org.jboss.threads.JBossThread.run(JBossThread.java:485) {code} Attaching standalone-full-ha.xml with which is possible to reproduce the issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2919) [DMN Designer] Data-types: Clean-up

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2919?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2919: -------------------------------- Description: During review of the PRs adding support to the different grids, both [~jomarko] and [~karreiro] found some re-occurring issues that need addressing. Rather than fix at the point of discovery, i.e. when my colleagues review the PR, I prefer to circle back and fix all together once the queue of pending PRs are merged. Current action items: * (/) https://github.com/kiegroup/kie-wb-common/pull/2055#discussion_r212084447 * (/) https://github.com/kiegroup/kie-wb-common/pull/2041#discussion_r212250221 * (/) https://github.com/kiegroup/kie-wb-common/pull/2075/files#diff-5192d74da9... and https://github.com/kiegroup/kie-wb-common/pull/2075/files#diff-5192d74da9... - check for other occurrences too. If we pass a parameter as to whether to update "Stunner" title or not we can remove these methods accessing the super implementation. * (/) Review whether _legacy_ {{BaseExpressionGrid.HeaderTextAreaFactory}} related methods are required when all grids support "in place" editing of name and data-type. Removing if possible. h2. Acceptance test Data type can be changed for - All supported node types (/) - All supported expression types (/) was: During review of the PRs adding support to the different grids, both [~jomarko] and [~karreiro] found some re-occurring issues that need addressing. Rather than fix at the point of discovery, i.e. when my colleagues review the PR, I prefer to circle back and fix all together once the queue of pending PRs are merged. Current action items: * (/) https://github.com/kiegroup/kie-wb-common/pull/2055#discussion_r212084447 * (/) https://github.com/kiegroup/kie-wb-common/pull/2041#discussion_r212250221 * (/) https://github.com/kiegroup/kie-wb-common/pull/2075/files#diff-5192d74da9... and https://github.com/kiegroup/kie-wb-common/pull/2075/files#diff-5192d74da9... - check for other occurrences too. If we pass a parameter as to whether to update "Stunner" title or not we can remove these methods accessing the super implementation. * (/) Review whether _legacy_ {{BaseExpressionGrid.HeaderTextAreaFactory}} related methods are required when all grids support "in place" editing of name and data-type. Removing if possible. h2. Acceptance test Data type can be changed for - All supported node types - All supported expression types > [DMN Designer] Data-types: Clean-up > ----------------------------------- > > Key: DROOLS-2919 > URL: https://issues.jboss.org/browse/DROOLS-2919 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.10.0.Final > Reporter: Michael Anstis > Assignee: Michael Anstis > Labels: drools-tools > > During review of the PRs adding support to the different grids, both [~jomarko] and [~karreiro] found some re-occurring issues that need addressing. Rather than fix at the point of discovery, i.e. when my colleagues review the PR, I prefer to circle back and fix all together once the queue of pending PRs are merged. > Current action items: > * (/) https://github.com/kiegroup/kie-wb-common/pull/2055#discussion_r212084447 > * (/) https://github.com/kiegroup/kie-wb-common/pull/2041#discussion_r212250221 > * (/) https://github.com/kiegroup/kie-wb-common/pull/2075/files#diff-5192d74da9... and https://github.com/kiegroup/kie-wb-common/pull/2075/files#diff-5192d74da9... - check for other occurrences too. If we pass a parameter as to whether to update "Stunner" title or not we can remove these methods accessing the super implementation. > * (/) Review whether _legacy_ {{BaseExpressionGrid.HeaderTextAreaFactory}} related methods are required when all grids support "in place" editing of name and data-type. Removing if possible. > h2. Acceptance test > Data type can be changed for > - All supported node types (/) > - All supported expression types (/) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4018) Remove alias and read-aliases in a batch causes blocking behavior

by Michal Petrov (JIRA)

[ https://issues.jboss.org/browse/WFCORE-4018?page=com.atlassian.jira.plugi... ] Michal Petrov commented on WFCORE-4018: --------------------------------------- [~brian.stansberry] this doesn't happen in domain mode, from what I'm seeing the steps of the composite operation are executed separately (by the time they reach host) and as such under different OperationContexts so the first one is locking the second one out. I haven't found out what component is responsible for that. > Remove alias and read-aliases in a batch causes blocking behavior > ----------------------------------------------------------------- > > Key: WFCORE-4018 > URL: https://issues.jboss.org/browse/WFCORE-4018 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Claudio Miranda > Assignee: Michal Petrov > > Calling :remove-alias and :read-aliases on key-store resource in a composite operation makes the resource blocked. > Generate two self signed certificates on a key-store resource and store it. > {code} > /host=master/server=server-three/subsystem=elytron/key-store=keysto1:generate-key-pair(alias=foobar,distinguished-name="cn=claudio,c=BR") > /host=master/server=server-three/subsystem=elytron/key-store=keysto1:generate-key-pair(alias=foobar2,distinguished-name="cn=claudio2,c=BR") > /host=master/server=server-three/subsystem=elytron/key-store=keysto1:store() > /host=master/server=server-three/subsystem=elytron/key-store=keysto1:read-aliases > { > "outcome" => "success", > "result" => [ > "foobar2", > "foobar" > ] > } > {code} > {code} > batch > /host=master/server=server-three/subsystem=elytron/key-store=keysto1:remove-alias(alias=foobar) > /host=master/server=server-three/subsystem=elytron/key-store=keysto1:read-aliases > run-batch > {code} > The above just blocks the prompt. > Then the blocking operation is show as: > {code} > /host=master/core-service=management/service=management-operations:read-resource(include-runtime,recursive) > { > "outcome" => "success", > "result" => {"active-operation" => { > "352328021" => { > "access-mechanism" => "NATIVE", > "address" => [ > ("host" => "master"), > ("core-service" => "management"), > ("service" => "management-operations") > ], > "caller-thread" => "management-handler-thread - 1", > "cancelled" => false, > "domain-rollout" => false, > "domain-uuid" => undefined, > "exclusive-running-time" => -1L, > "execution-status" => "executing", > "operation" => "read-resource", > "running-time" => 10032404L > }, > "-1467399640" => { > "access-mechanism" => "NATIVE", > "address" => [], > "caller-thread" => "management-handler-thread - 2", > "cancelled" => false, > "domain-rollout" => false, > "domain-uuid" => undefined, > "exclusive-running-time" => -1L, > "execution-status" => "executing", > "operation" => "composite", > "running-time" => 260150849919L > } > }} > } > {code} > After timeout there is the following message on CLI prompt > {code} > The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the error): > WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed: > Step: step-2 > Operation: /host=master/server=server-three/subsystem=elytron/key-store=keysto1:read-aliases > Failure: WFLYCTL0409: Execution of operation 'read-aliases' on remote process at address '[ > ("host" => "master"), > ("server" => "server-three") > ]' timed out after 305000 ms while awaiting initial response; remote process has been notified to terminate operation > {code} > To fix the problem in HAL I will run it as individual commands. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2634) Executable model: Test classes starting with C from package integrationtests fail with executable model

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2634?page=com.atlassian.jira.plugi... ] Mario Fusco commented on DROOLS-2634: ------------------------------------- 7th fix https://github.com/kiegroup/drools/commit/c8f76c7c0b18695f4b0674f45be90c1... > Executable model: Test classes starting with C from package integrationtests fail with executable model > ------------------------------------------------------------------------------------------------------- > > Key: DROOLS-2634 > URL: https://issues.jboss.org/browse/DROOLS-2634 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.7.0.Final > Reporter: Tibor Zimányi > Assignee: Mario Fusco > > When running tests from package org.drools.compiler.integrationtests that start with letter C [1] with executable model, many of them fail (~200 out of ~856). PR with failing test classes can be found here [2]. > [1] https://github.com/kiegroup/drools/tree/d7ad4fb31647b5295c3cbc0321f0d8f89... > [2] https://github.com/kiegroup/drools/pull/1947 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2976) Enable hot reload on drools-wb-webapp

by Juraj Soltes (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2976?page=com.atlassian.jira.plugi... ] Juraj Soltes updated DROOLS-2976: --------------------------------- Story Points: 2 > Enable hot reload on drools-wb-webapp > ------------------------------------- > > Key: DROOLS-2976 > URL: https://issues.jboss.org/browse/DROOLS-2976 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Reporter: Juraj Soltes > Assignee: Juraj Soltes > > Currently it is not possible to use hot reload on the drools-wb-webapp. This task is about making the changes in drools-wb-webapp pom to enable it. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2976) Enable hot reload on drools-wb-webapp

by Juraj Soltes (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2976?page=com.atlassian.jira.plugi... ] Juraj Soltes updated DROOLS-2976: --------------------------------- Sprint: 2018 Week 36-38 (was: 2018 Week 39-41) > Enable hot reload on drools-wb-webapp > ------------------------------------- > > Key: DROOLS-2976 > URL: https://issues.jboss.org/browse/DROOLS-2976 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Reporter: Juraj Soltes > Assignee: Juraj Soltes > > Currently it is not possible to use hot reload on the drools-wb-webapp. This task is about making the changes in drools-wb-webapp pom to enable it. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2976) Enable hot reload on drools-wb-webapp

by Juraj Soltes (JIRA)

Juraj Soltes created DROOLS-2976: ------------------------------------ Summary: Enable hot reload on drools-wb-webapp Key: DROOLS-2976 URL: https://issues.jboss.org/browse/DROOLS-2976 Project: Drools Issue Type: Enhancement Components: Scenario Simulation and Testing Reporter: Juraj Soltes Assignee: Juraj Soltes Currently it is not possible to use hot reload on the drools-wb-webapp. This task is about making the changes in drools-wb-webapp pom to enable it. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2018