March 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1705) Audit remaining Class.forName in static factory methods

by Edoardo Vacchi (Jira)

[ https://issues.jboss.org/browse/DROOLS-1705?page=com.atlassian.jira.plugi... ] Edoardo Vacchi updated DROOLS-1705: ----------------------------------- Sprint: (was: 2019 Week 11-13) > Audit remaining Class.forName in static factory methods > ------------------------------------------------------- > > Key: DROOLS-1705 > URL: https://issues.jboss.org/browse/DROOLS-1705 > Project: Drools > Issue Type: Task > Components: core engine > Reporter: Matteo Mortari > Assignee: Edoardo Vacchi > Priority: Minor > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11902) Deprecated configuration for TCPGOSSIP not usable

by Richard Janík (Jira)

[ https://issues.jboss.org/browse/WFLY-11902?page=com.atlassian.jira.plugin... ] Richard Janík updated WFLY-11902: --------------------------------- Summary: Deprecated configuration for TCPGOSSIP not usable (was: Deprecated configuration for TCPGOSSIP not usable.) > Deprecated configuration for TCPGOSSIP not usable > ------------------------------------------------- > > Key: WFLY-11902 > URL: https://issues.jboss.org/browse/WFLY-11902 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 17.0.0.Beta1 > Reporter: Richard Janík > Assignee: Paul Ferraro > Priority: Critical > > Related to WFLY-11901. Found on current master. > Running the example files produces: > {code} > ./standalone.sh -Djboss.jgroups.gossip.initial_hosts=127.0.0.1[12004] -Djboss.jgroups.gossip.num_initial_members=1 --server-config=../../docs/examples/configs/standalone-gossip-full-ha.xml > 12:49:01,924 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 84) MSC000001: Failed to start service org.wildfly.clustering.jgroups.channel.ee: org.jboss.msc.service.StartException in service org.wildfly.clustering.jgroups.channel.ee: java.lang.IllegalStateException: java.lang.IllegalArgumentException: java.security.PrivilegedActionException: java.lang.IllegalArgumentException: Unrecognized TCPGOSSIP properties: [num_initial_members] > at org.wildfly.clustering.service.FunctionalService.start(FunctionalService.java:70) > at org.wildfly.clustering.service.AsyncServiceConfigurator$AsyncService.lambda$start$0(AsyncServiceConfigurator.java:117) > 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) > at org.jboss.threads.JBossThread.run(JBossThread.java:485) > Caused by: java.lang.IllegalStateException: java.lang.IllegalArgumentException: java.security.PrivilegedActionException: java.lang.IllegalArgumentException: Unrecognized TCPGOSSIP properties: [num_initial_members] > at org.jboss.as.clustering.jgroups.subsystem.ChannelServiceConfigurator.get(ChannelServiceConfigurator.java:116) > at org.jboss.as.clustering.jgroups.subsystem.ChannelServiceConfigurator.get(ChannelServiceConfigurator.java:58) > at org.wildfly.clustering.service.FunctionalService.start(FunctionalService.java:67) > ... 7 more > Caused by: java.lang.IllegalArgumentException: java.security.PrivilegedActionException: java.lang.IllegalArgumentException: Unrecognized TCPGOSSIP properties: [num_initial_members] > at org.jboss.as.clustering.jgroups.subsystem.AbstractProtocolConfigurationServiceConfigurator.createProtocol(AbstractProtocolConfigurationServiceConfigurator.java:130) > at org.jboss.as.clustering.jgroups.JChannelFactory.createChannel(JChannelFactory.java:106) > at org.jboss.as.clustering.jgroups.subsystem.ChannelServiceConfigurator.get(ChannelServiceConfigurator.java:96) > ... 9 more > Caused by: java.security.PrivilegedActionException: java.lang.IllegalArgumentException: Unrecognized TCPGOSSIP properties: [num_initial_members] > at org.wildfly.security.manager.WildFlySecurityManager.doUnchecked(WildFlySecurityManager.java:851) > at org.jboss.as.clustering.jgroups.subsystem.AbstractProtocolConfigurationServiceConfigurator.createProtocol(AbstractProtocolConfigurationServiceConfigurator.java:125) > ... 11 more > Caused by: java.lang.IllegalArgumentException: Unrecognized TCPGOSSIP properties: [num_initial_members] > at org.jgroups.stack.Protocol.setProperties(Protocol.java:144) > at org.jboss.as.clustering.jgroups.subsystem.AbstractProtocolConfigurationServiceConfigurator.lambda$createProtocol$0(AbstractProtocolConfigurationServiceConfigurator.java:119) > at org.wildfly.security.manager.WildFlySecurityManager.doUnchecked(WildFlySecurityManager.java:849) > ... 12 more > {code} > Even though the configuration in the examples is deprecated, it should still work as changes between minor versions should be backward compatible. While this incompatibility is fine for WFLY, it is an issue for the product, where 17.0 will only translate to a minor version update. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11902) Deprecated configuration for TCPGOSSIP not usable.

by Richard Janík (Jira)

Richard Janík created WFLY-11902: ------------------------------------ Summary: Deprecated configuration for TCPGOSSIP not usable. Key: WFLY-11902 URL: https://issues.jboss.org/browse/WFLY-11902 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 17.0.0.Beta1 Reporter: Richard Janík Assignee: Paul Ferraro Related to WFLY-11901. Found on current master. Running the example files produces: {code} ./standalone.sh -Djboss.jgroups.gossip.initial_hosts=127.0.0.1[12004] -Djboss.jgroups.gossip.num_initial_members=1 --server-config=../../docs/examples/configs/standalone-gossip-full-ha.xml 12:49:01,924 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 84) MSC000001: Failed to start service org.wildfly.clustering.jgroups.channel.ee: org.jboss.msc.service.StartException in service org.wildfly.clustering.jgroups.channel.ee: java.lang.IllegalStateException: java.lang.IllegalArgumentException: java.security.PrivilegedActionException: java.lang.IllegalArgumentException: Unrecognized TCPGOSSIP properties: [num_initial_members] at org.wildfly.clustering.service.FunctionalService.start(FunctionalService.java:70) at org.wildfly.clustering.service.AsyncServiceConfigurator$AsyncService.lambda$start$0(AsyncServiceConfigurator.java:117) 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) at org.jboss.threads.JBossThread.run(JBossThread.java:485) Caused by: java.lang.IllegalStateException: java.lang.IllegalArgumentException: java.security.PrivilegedActionException: java.lang.IllegalArgumentException: Unrecognized TCPGOSSIP properties: [num_initial_members] at org.jboss.as.clustering.jgroups.subsystem.ChannelServiceConfigurator.get(ChannelServiceConfigurator.java:116) at org.jboss.as.clustering.jgroups.subsystem.ChannelServiceConfigurator.get(ChannelServiceConfigurator.java:58) at org.wildfly.clustering.service.FunctionalService.start(FunctionalService.java:67) ... 7 more Caused by: java.lang.IllegalArgumentException: java.security.PrivilegedActionException: java.lang.IllegalArgumentException: Unrecognized TCPGOSSIP properties: [num_initial_members] at org.jboss.as.clustering.jgroups.subsystem.AbstractProtocolConfigurationServiceConfigurator.createProtocol(AbstractProtocolConfigurationServiceConfigurator.java:130) at org.jboss.as.clustering.jgroups.JChannelFactory.createChannel(JChannelFactory.java:106) at org.jboss.as.clustering.jgroups.subsystem.ChannelServiceConfigurator.get(ChannelServiceConfigurator.java:96) ... 9 more Caused by: java.security.PrivilegedActionException: java.lang.IllegalArgumentException: Unrecognized TCPGOSSIP properties: [num_initial_members] at org.wildfly.security.manager.WildFlySecurityManager.doUnchecked(WildFlySecurityManager.java:851) at org.jboss.as.clustering.jgroups.subsystem.AbstractProtocolConfigurationServiceConfigurator.createProtocol(AbstractProtocolConfigurationServiceConfigurator.java:125) ... 11 more Caused by: java.lang.IllegalArgumentException: Unrecognized TCPGOSSIP properties: [num_initial_members] at org.jgroups.stack.Protocol.setProperties(Protocol.java:144) at org.jboss.as.clustering.jgroups.subsystem.AbstractProtocolConfigurationServiceConfigurator.lambda$createProtocol$0(AbstractProtocolConfigurationServiceConfigurator.java:119) at org.wildfly.security.manager.WildFlySecurityManager.doUnchecked(WildFlySecurityManager.java:849) ... 12 more {code} Even though the configuration in the examples is deprecated, it should still work as changes between minor versions should be backward compatible. While this incompatibility is fine for WFLY, it is an issue for the product, where 17.0 will only translate to a minor version update. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11901) Old TCPGOSSIP example configurations

by Richard Janík (Jira)

Richard Janík created WFLY-11901: ------------------------------------ Summary: Old TCPGOSSIP example configurations Key: WFLY-11901 URL: https://issues.jboss.org/browse/WFLY-11901 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 17.0.0.Beta1 Reporter: Richard Janík Assignee: Paul Ferraro Found on current master by [~mkopecky]. The two provided TCPGOSSIP configuration files {code} docs/examples/configs/standalone-gossip-ha.xml docs/examples/configs/standalone-gossip-full-ha.xml {code} use deprecated configuration (via protocol properties) for TCPGOSSIP. Up to date configuration should be the result of https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_ap... (configuration using {{remote-outbound-socket-binding}}). -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-9407) Upgrade Artemis 2.6.3.jbossorg-001

by Seckin Pulatkan (Jira)

[ https://issues.jboss.org/browse/WFLY-9407?page=com.atlassian.jira.plugin.... ] Seckin Pulatkan edited comment on WFLY-9407 at 3/25/19 7:24 AM: ---------------------------------------------------------------- Update: I couldn't delete my comment here. If you are able to please delete. I have put my question to JBOSS Developer forum: https://developer.jboss.org/thread/279855 was (Author: spulatkan): Hi [~jmesnil] We were using Wildfly 13.0.0 Final with remote connector to Artemis 2.6.2 server with following change on broker.xml {code:xml|title=broker.xml acceptor definition} <acceptor name="artemis">tcp://0.0.0.0:61616?anycastPrefix=jms.queue.;multicastPrefix=jms.topic.; {code} We wanted to upgrade to Wildfly 15.0.1 Final but we noticed that topics are created with prefix "jms.topic." . I tried to find a configuration to disable it but it did not work {code:xml|title=standalone.xml system property} <property name="org.apache.activemq.artemis.api.jms.ActiveMQJMSClient.enable1xPrefixes" value="false" /> {code} With WFLY-9407, it seems this flag is set to true explicitly (ActiveMQResourceAdapter constructor and ConnectionFactoryAdd.createConfiguration method). And still it is true on master branch. Will this be the case on all future releases of Wildfly or will there be a configuration to disable 1x prefixes? Since we had the topics and queues without the prefix on our active environments, we would like to use without prefix. For consumers, we can set topicPrefix as ActivationConfigProperty but while producing the message, the messages are being set to the topic with "jms.topic." prefix. > Upgrade Artemis 2.6.3.jbossorg-001 > ---------------------------------- > > Key: WFLY-9407 > URL: https://issues.jboss.org/browse/WFLY-9407 > Project: WildFly > Issue Type: Component Upgrade > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Major > Labels: downstream_dependency > Fix For: 14.0.0.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11900) Wildfly 14 + JGroups + Singleton Cluster Not Working

by Bhavesh Kharwa (Jira)

[ https://issues.jboss.org/browse/WFLY-11900?page=com.atlassian.jira.plugin... ] Bhavesh Kharwa updated WFLY-11900: ---------------------------------- Fix Version/s: 14.0.0.Final > Wildfly 14 + JGroups + Singleton Cluster Not Working > ---------------------------------------------------- > > Key: WFLY-11900 > URL: https://issues.jboss.org/browse/WFLY-11900 > Project: WildFly > Issue Type: Bug > Reporter: Bhavesh Kharwa > Assignee: Brian Stansberry > Priority: Major > Fix For: 14.0.0.Final > > > Singleton cluster is not working if starts both servers at same time. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11900) Wildfly 14 + JGroups + Singleton Cluster Not Working

by Bhavesh Kharwa (Jira)

Bhavesh Kharwa created WFLY-11900: ------------------------------------- Summary: Wildfly 14 + JGroups + Singleton Cluster Not Working Key: WFLY-11900 URL: https://issues.jboss.org/browse/WFLY-11900 Project: WildFly Issue Type: Bug Reporter: Bhavesh Kharwa Assignee: Brian Stansberry Singleton cluster is not working if starts both servers at same time. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3791) Create an API to scroll events received on the topics

by Massimiliano Dessi (Jira)

Massimiliano Dessi created DROOLS-3791: ------------------------------------------ Summary: Create an API to scroll events received on the topics Key: DROOLS-3791 URL: https://issues.jboss.org/browse/DROOLS-3791 Project: Drools Issue Type: Sub-task Reporter: Massimiliano Dessi Assignee: Massimiliano Dessi -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFWIP-156) spec.containers[0].securityContext.securityContext.runAsUser: Invalid value: 1000: must be in the ranges: [1000080000, 1000089999]

by Martin Choma (Jira)

[ https://issues.jboss.org/browse/WFWIP-156?page=com.atlassian.jira.plugin.... ] Martin Choma edited comment on WFWIP-156 at 3/25/19 5:42 AM: ------------------------------------------------------------- Eap images can run with any uid. They make it by running as root group https://docs.openshift.com/container-platform/3.11/creating_images/guidel.... {code} Marek Schmidt: @Martin Choma https://docs.openshift.com/container-platform/3.11/creating_images/guidel... Martin Choma: hmm, I cant find similar steps in cct_module, jboss-eap-modules, jboss-container-images. Searching chgrp and anyuid Marek Schmidt: @Martin Choma https://github.com/jboss-openshift/cct_module/blob/master/jboss/container... Marek Schmidt: @Martin Choma this is also an important piece https://github.com/jboss-openshift/cct_module/blob/master/jboss/container... Marek Schmidt: @Martin Choma Basically the idea is: 1. Make any file owned by the jboss:root 2. make the jboss user part of the root group, 3. hack /etc/passwd at runtime to make the runtime UID user the "jboss" user Martin Choma: thanks, that answers my question {code} was (Author: mchoma): Eap images can run with any uid. They make it by running as root group https://docs.openshift.com/container-platform/3.11/creating_images/guidel.... {code} Marek Schmidt: @Martin Choma https://docs.openshift.com/container-platform/3.11/creating_images/guidel... Martin Choma: hmm, I cant find similar steps in cct_module, jboss-eap-modules, jboss-container-images. Searching chgrp and anyuid Marek Schmidt: @Martin Choma https://github.com/jboss-openshift/cct_module/blob/master/jboss/container... Marek Schmidt: @Martin Choma this is also an important piece https://github.com/jboss-openshift/cct_module/blob/master/jboss/container... Marek Schmidt: @Martin Choma Basically the idea is: 1. Make any file owned by the jboss:root 2. make the jboss user part of the root group, 3. hack /etc/passwd at runtime to make the runtime UID user the "jboss" user Martin Choma: thanks, that is answers my question {code} > spec.containers[0].securityContext.securityContext.runAsUser: Invalid value: 1000: must be in the ranges: [1000080000, 1000089999] > ---------------------------------------------------------------------------------------------------------------------------------- > > Key: WFWIP-156 > URL: https://issues.jboss.org/browse/WFWIP-156 > Project: WildFly WIP > Issue Type: Bug > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Major > > Trying https://github.com/jmesnil/wildfly-operator/blob/master/README.adoc to install operator on OpenShift. I get error. > {noformat} > create Pod myapp-wildflyserver-0 in StatefulSet myapp-wildflyserver failed error: pods "myapp-wildflyserver-0" is forbidden: unable to validate against any security context constraint: [spec.containers[0].securityContext.securityContext.runAsUser: Invalid value: 1000: must be in the ranges: [1000080000, 1000089999]] > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFWIP-156) spec.containers[0].securityContext.securityContext.runAsUser: Invalid value: 1000: must be in the ranges: [1000080000, 1000089999]

by Martin Choma (Jira)

[ https://issues.jboss.org/browse/WFWIP-156?page=com.atlassian.jira.plugin.... ] Martin Choma commented on WFWIP-156: ------------------------------------ Eap images can run with any uid. They make it by running as root group https://docs.openshift.com/container-platform/3.11/creating_images/guidel.... {code} Marek Schmidt: @Martin Choma https://docs.openshift.com/container-platform/3.11/creating_images/guidel... Martin Choma: hmm, I cant find similar steps in cct_module, jboss-eap-modules, jboss-container-images. Searching chgrp and anyuid Marek Schmidt: @Martin Choma https://github.com/jboss-openshift/cct_module/blob/master/jboss/container... Marek Schmidt: @Martin Choma this is also an important piece https://github.com/jboss-openshift/cct_module/blob/master/jboss/container... Marek Schmidt: @Martin Choma Basically the idea is: 1. Make any file owned by the jboss:root 2. make the jboss user part of the root group, 3. hack /etc/passwd at runtime to make the runtime UID user the "jboss" user Martin Choma: thanks, that is answers my question {code} > spec.containers[0].securityContext.securityContext.runAsUser: Invalid value: 1000: must be in the ranges: [1000080000, 1000089999] > ---------------------------------------------------------------------------------------------------------------------------------- > > Key: WFWIP-156 > URL: https://issues.jboss.org/browse/WFWIP-156 > Project: WildFly WIP > Issue Type: Bug > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Major > > Trying https://github.com/jmesnil/wildfly-operator/blob/master/README.adoc to install operator on OpenShift. I get error. > {noformat} > create Pod myapp-wildflyserver-0 in StatefulSet myapp-wildflyserver failed error: pods "myapp-wildflyserver-0" is forbidden: unable to validate against any security context constraint: [spec.containers[0].securityContext.securityContext.runAsUser: Invalid value: 1000: must be in the ranges: [1000080000, 1000089999]] > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

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 March 2019