September 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-5559) Kie-workbench and kie-server going OOM with subsequent build and deployment

by Sachin Kamath (Jira)

[ https://issues.redhat.com/browse/DROOLS-5559?page=com.atlassian.jira.plug... ] Sachin Kamath updated DROOLS-5559: ---------------------------------- Priority: Critical (was: Major) > Kie-workbench and kie-server going OOM with subsequent build and deployment > --------------------------------------------------------------------------- > > Key: DROOLS-5559 > URL: https://issues.redhat.com/browse/DROOLS-5559 > Project: Drools > Issue Type: Bug > Components: Examples (Workbench), kie server > Affects Versions: 7.31.0.Final > Reporter: Sachin Kamath > Assignee: David Gutierrez > Priority: Critical > > Hi Team, > We are using kie-workbench and kie-server for managing the rules using decision table spreadsheet. What we see is that, with continuous build and deployments being done, the servers are going out of memory. This is resulting in instability of the environment and frequent restarts are required to fix the issue. > Here are the parameters: > *kie-workbench* : > Xms: 20G > Xmx: 20G > Metaspace Xmx:8G Xms:8G > Using G1GC algorithm. > *kie-server:* > Xms: 4G > Xmx: 4G > Metaspace: Xmx:2G Xms:2G > Using G1GC algorithm. > *Steps for replication :* > # Excel sheet has 50k rows. > # Build the artifacts and deploy with version V1. The first deployment would be successful. > # Change the version to V2 and deploy once again. Now we will have version V1 and V2 both in the kie-servers but V2 would be serving he requests. > # Before deploying version V3, remove version V1. Build and deploy V3. > # Now when deploying version V4, after removing the version V2, the kie-servers are going out of memory. > Even though we are making sure that only last 2 valid versions are present, the servers are going out of memory. After restarting the servers, the last two valid versions V3 and V4 are successfully deployed again. The error in kie-servers clearly says Java heap space issue. But the point here is, it is fine after restart. I could sense there is some other problem. With visual VM, i could see that the memory consumption gradually increases with deployment of different versions but its not released as we remove the old version. > Any pointers would be helpful here. > Im really unsure if its a bug or im missing some parameters around it. > > Thanks > Sachin > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-5414) DMN Validation rule check DecisionService at least 1 outputDecision

by Matteo Mortari (Jira)

[ https://issues.redhat.com/browse/DROOLS-5414?page=com.atlassian.jira.plug... ] Matteo Mortari updated DROOLS-5414: ----------------------------------- Description: it is redundant to XSD !screenshot-1.png|thumbnail! but the DMN specification version 1.3 contains a bug in the XSD implementation https://issues.omg.org/browse/DMN14-93 so this would solve until it is resolved at the DMN specification level with the XSD correction. was: it is redundant to XSD !screenshot-1.png|thumbnail! however given the low effort is good to implement anyway for those use-case where XSD validation is skipped. > DMN Validation rule check DecisionService at least 1 outputDecision > ------------------------------------------------------------------- > > Key: DROOLS-5414 > URL: https://issues.redhat.com/browse/DROOLS-5414 > Project: Drools > Issue Type: Feature Request > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Major > Labels: good-first-issue > Attachments: screenshot-1.png > > > it is redundant to XSD > !screenshot-1.png|thumbnail! > but the DMN specification version 1.3 contains a bug in the XSD implementation https://issues.omg.org/browse/DMN14-93 so this would solve until it is resolved at the DMN specification level with the XSD correction. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (WFLY-13793) Attribute enable-amq1-prefix doesn't work (remote artemis)

by Chao Wang (Jira)

[ https://issues.redhat.com/browse/WFLY-13793?page=com.atlassian.jira.plugi... ] Chao Wang commented on WFLY-13793: ---------------------------------- hmm.. queue/topic prefix is hardcoded as part of queue/topic name https://github.com/wildfly/wildfly/blob/20.0.1.Final/messaging-activemq/s... https://github.com/wildfly/wildfly/blob/20.0.1.Final/messaging-activemq/s... Hi [~ehugonnet], what's your thought on this? should it be allowed to configure the prefix of external jms queue/topic as {{enable-amq1-prefix}} does ? > Attribute enable-amq1-prefix doesn't work (remote artemis) > ---------------------------------------------------------- > > Key: WFLY-13793 > URL: https://issues.redhat.com/browse/WFLY-13793 > Project: WildFly > Issue Type: Bug > Components: JMS, Management > Affects Versions: 20.0.1.Final > Reporter: Nicolas De Amicis > Assignee: Chao Wang > Priority: Major > Fix For: 21.0.0.Beta1 > > > I need to connect Wildfly 17.0.1 to a remote Artemis server. I follow the doc here: [https://docs.wildfly.org/17/Admin_Guide.html#Messaging_Connect_a_pooled-c...] No problem for point 1 to 3. But when I follow the instruction for disabling the compatibility mode (enable-amq1-prefix) I have this error: > {quote}{{[standalone@localhost:9990 /] /subsystem=messaging-activemq/pooled-connection-factory=remote-artemis:write-attribute(name="enable-amq1-prefix", value="false")}} > \{{{}} > \{{ "outcome" => "failed",}} > \{{ "failure-description" => "WFLYCTL0248: Invalid value false for enable-amq1-prefix; legal values are [XA_GENERIC, GENERIC, XA_T}} > {{OPIC, TOPIC, QUEUE, XA_QUEUE]",}} > \{{ "rolled-back" => true}} > {{}}} > {quote} > If I deploy my MDB that connects to queue myqueue, I see in artemis console my MDB is connected to jms.queue.myqueue. > I also tried to add the attribute manually but it seems it doesn't work: > {quote}{{<pooled-connection-factory name="remote-artemis" entries="java:/}}{{jms/remoteCF}}{{" connectors="remote-artemis" enable-amq1-prefix="false"/>}} > {quote} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-5120) Automatic registration of client side / JVM wide default SSLContext

by Diana Vilkolakova (Jira)

Diana Vilkolakova created WFCORE-5120: ----------------------------------------- Summary: Automatic registration of client side / JVM wide default SSLContext Key: WFCORE-5120 URL: https://issues.redhat.com/browse/WFCORE-5120 Project: WildFly Core Issue Type: Feature Request Components: Security Reporter: Diana Vilkolakova Assignee: Diana Vilkolakova -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (WFLY-13827) Manual IIOP/CORBA stub generation fails on IBM JDK when running the Galleon Layers testsuite

by Yeray Borges Santana (Jira)

[ https://issues.redhat.com/browse/WFLY-13827?page=com.atlassian.jira.plugi... ] Yeray Borges Santana deleted WFLY-13827: ---------------------------------------- > Manual IIOP/CORBA stub generation fails on IBM JDK when running the Galleon Layers testsuite > -------------------------------------------------------------------------------------------- > > Key: WFLY-13827 > URL: https://issues.redhat.com/browse/WFLY-13827 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Affects Versions: 20.0.1.Final > Reporter: Yeray Borges Santana > Assignee: Yeray Borges Santana > Priority: Major > > The Galleon Layers basic integration test suite fails on IBM JDK with the following error: > {noformat} > [INFO] --- exec-maven-plugin:1.6.0:exec (ibmjdk.iiop.stub-creation) @ wildfly-ts-integ-basic --- > error: Class javax.ejb.EJBHome not found in interface org.jboss.as.test.integration.ejb.iiop.naming.IIOPStatefulNamingHome. > error: Class javax.ejb.EJBHome not found. > error: Class javax.ejb.EJBHome not found in interface org.jboss.as.test.integration.ejb.iiop.naming.IIOPNamingHome. > error: Class javax.ejb.EJBHome not found. > 4 errors > [ERROR] Command execution failed. > org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1) > at org.apache.commons.exec.DefaultExecutor.executeInternal (DefaultExecutor.java:404) > at org.apache.commons.exec.DefaultExecutor.execute (DefaultExecutor.java:166) > at org.codehaus.mojo.exec.ExecMojo.executeCommandLine (ExecMojo.java:804) > at org.codehaus.mojo.exec.ExecMojo.executeCommandLine (ExecMojo.java:751) > at org.codehaus.mojo.exec.ExecMojo.execute (ExecMojo.java:313) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81) > at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56) > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) > at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) > at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956) > at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288) > at org.apache.maven.cli.MavenCli.main (MavenCli.java:192) > at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:90) > at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:55) > at java.lang.reflect.Method.invoke (Method.java:508) > at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282) > at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225) > at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406) > at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347) > {noformat} > The reason is the ibmjdk.profile is activated independently if we are generating a slimmer server by using Galleon layers, failing in such cases. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (WFLY-13827) Manual IIOP/CORBA stub generation fails on IBM JDK when running the Galleon Layers testsuite

by Yeray Borges Santana (Jira)

Yeray Borges Santana created WFLY-13827: ------------------------------------------- Summary: Manual IIOP/CORBA stub generation fails on IBM JDK when running the Galleon Layers testsuite Key: WFLY-13827 URL: https://issues.redhat.com/browse/WFLY-13827 Project: WildFly Issue Type: Bug Components: Test Suite Affects Versions: 20.0.1.Final Reporter: Yeray Borges Santana Assignee: Yeray Borges Santana The Galleon Layers basic integration test suite fails on IBM JDK with the following error: {noformat} [INFO] --- exec-maven-plugin:1.6.0:exec (ibmjdk.iiop.stub-creation) @ wildfly-ts-integ-basic --- error: Class javax.ejb.EJBHome not found in interface org.jboss.as.test.integration.ejb.iiop.naming.IIOPStatefulNamingHome. error: Class javax.ejb.EJBHome not found. error: Class javax.ejb.EJBHome not found in interface org.jboss.as.test.integration.ejb.iiop.naming.IIOPNamingHome. error: Class javax.ejb.EJBHome not found. 4 errors [ERROR] Command execution failed. org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1) at org.apache.commons.exec.DefaultExecutor.executeInternal (DefaultExecutor.java:404) at org.apache.commons.exec.DefaultExecutor.execute (DefaultExecutor.java:166) at org.codehaus.mojo.exec.ExecMojo.executeCommandLine (ExecMojo.java:804) at org.codehaus.mojo.exec.ExecMojo.executeCommandLine (ExecMojo.java:751) at org.codehaus.mojo.exec.ExecMojo.execute (ExecMojo.java:313) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956) at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288) at org.apache.maven.cli.MavenCli.main (MavenCli.java:192) at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:90) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:55) at java.lang.reflect.Method.invoke (Method.java:508) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282) at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406) at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347) {noformat} The reason is the ibmjdk.profile is activated independently if we are generating a slimmer server by using Galleon layers, failing in such cases. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (WFLY-13793) Attribute enable-amq1-prefix doesn't work (remote artemis)

by Nicolas De Amicis (Jira)

[ https://issues.redhat.com/browse/WFLY-13793?page=com.atlassian.jira.plugi... ] Nicolas De Amicis commented on WFLY-13793: ------------------------------------------ I located the problem in wildfly-messaging-activemq lib: * org.wildfly.extension.messaging.activemq.jms.ExternalJMSQueueService line 54, a prefix "jms.queue." is always added to the queue name * org.wildfly.extension.messaging.activemq.jms.ExternalJMSTopicService line 55, a prefix "jms.topic." is always added to the topic name I think a new attribute should be define for <external-jms-queue /> and <external-jms-topic /> like enable-amq1-prefix to append or not the prefix? What do you think? > Attribute enable-amq1-prefix doesn't work (remote artemis) > ---------------------------------------------------------- > > Key: WFLY-13793 > URL: https://issues.redhat.com/browse/WFLY-13793 > Project: WildFly > Issue Type: Bug > Components: JMS, Management > Affects Versions: 20.0.1.Final > Reporter: Nicolas De Amicis > Assignee: Chao Wang > Priority: Major > Fix For: 21.0.0.Beta1 > > > I need to connect Wildfly 17.0.1 to a remote Artemis server. I follow the doc here: [https://docs.wildfly.org/17/Admin_Guide.html#Messaging_Connect_a_pooled-c...] No problem for point 1 to 3. But when I follow the instruction for disabling the compatibility mode (enable-amq1-prefix) I have this error: > {quote}{{[standalone@localhost:9990 /] /subsystem=messaging-activemq/pooled-connection-factory=remote-artemis:write-attribute(name="enable-amq1-prefix", value="false")}} > \{{{}} > \{{ "outcome" => "failed",}} > \{{ "failure-description" => "WFLYCTL0248: Invalid value false for enable-amq1-prefix; legal values are [XA_GENERIC, GENERIC, XA_T}} > {{OPIC, TOPIC, QUEUE, XA_QUEUE]",}} > \{{ "rolled-back" => true}} > {{}}} > {quote} > If I deploy my MDB that connects to queue myqueue, I see in artemis console my MDB is connected to jms.queue.myqueue. > I also tried to add the attribute manually but it seems it doesn't work: > {quote}{{<pooled-connection-factory name="remote-artemis" entries="java:/}}{{jms/remoteCF}}{{" connectors="remote-artemis" enable-amq1-prefix="false"/>}} > {quote} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (WFLY-13779) MicroProfile Metrics tests started to fail since changes in ConfigSource

by Sultan Zhantemirov (Jira)

[ https://issues.redhat.com/browse/WFLY-13779?page=com.atlassian.jira.plugi... ] Sultan Zhantemirov commented on WFLY-13779: ------------------------------------------- [~jmesnil] thank you for the response, already working on that. > MicroProfile Metrics tests started to fail since changes in ConfigSource > ------------------------------------------------------------------------ > > Key: WFLY-13779 > URL: https://issues.redhat.com/browse/WFLY-13779 > Project: WildFly > Issue Type: Bug > Components: MP Metrics > Reporter: Sultan Zhantemirov > Assignee: Jeff Mesnil > Priority: Major > > WildFly build: 21.0.0.Beta1-SNAPSHOT > Java: oracle-java-11 > A several failures appeared in our small standalone test suite [1] for MicroProfile on WF/EAP. To be more specific, a few failures in MP Metrics that have one common cause: > {noformat} > java.lang.RuntimeException: config.source.properties.path property not defined > {noformat} > caused by line [2]. > I have a reason to believe that this PR [3] could be reason of these failures. What should be done in this case? > Thank you. > [1] - https://github.com/jboss-eap-qe/eap-microprofile-test-suite/tree/master/m... > [2] - https://github.com/jboss-eap-qe/eap-microprofile-test-suite/blob/8b726042... > [3] - https://github.com/wildfly/wildfly/pull/13247 > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-5118) Cannot get resources from ContextClassLoader with Server Lifecycle Events

by Ricardo Martin Camarero (Jira)

[ https://issues.redhat.com/browse/WFCORE-5118?page=com.atlassian.jira.plug... ] Ricardo Martin Camarero updated WFCORE-5118: -------------------------------------------- Git Pull Request: https://github.com/keycloak/keycloak/pull/7396 > Cannot get resources from ContextClassLoader with Server Lifecycle Events > ------------------------------------------------------------------------- > > Key: WFCORE-5118 > URL: https://issues.redhat.com/browse/WFCORE-5118 > Project: WildFly Core > Issue Type: Bug > Components: Management > Affects Versions: 13.0.0.Beta5 > Reporter: Ricardo Martin Camarero > Assignee: Ricardo Martin Camarero > Priority: Major > Attachments: reproduce.zip > > > Listener application cannot refer to their own resources from ContextClassLoader. In general the TCCL is not assigned to the module of the {{ProcessStateListener}}. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-5118) Cannot get resources from ContextClassLoader with Server Lifecycle Events

by Ricardo Martin Camarero (Jira)

[ https://issues.redhat.com/browse/WFCORE-5118?page=com.atlassian.jira.plug... ] Ricardo Martin Camarero updated WFCORE-5118: -------------------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/4320 (was: https://github.com/keycloak/keycloak/pull/7396) > Cannot get resources from ContextClassLoader with Server Lifecycle Events > ------------------------------------------------------------------------- > > Key: WFCORE-5118 > URL: https://issues.redhat.com/browse/WFCORE-5118 > Project: WildFly Core > Issue Type: Bug > Components: Management > Affects Versions: 13.0.0.Beta5 > Reporter: Ricardo Martin Camarero > Assignee: Ricardo Martin Camarero > Priority: Major > Attachments: reproduce.zip > > > Listener application cannot refer to their own resources from ContextClassLoader. In general the TCCL is not assigned to the module of the {{ProcessStateListener}}. -- 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