[JBoss JIRA] (WFLY-12636) ParseAndMarshalModelsTestCase fails on the latest IBM8 with Failed to register MBean with MBeanServer
by Ondrej Kotek (Jira)
Ondrej Kotek created WFLY-12636:
-----------------------------------
Summary: ParseAndMarshalModelsTestCase fails on the latest IBM8 with Failed to register MBean with MBeanServer
Key: WFLY-12636
URL: https://issues.jboss.org/browse/WFLY-12636
Project: WildFly
Issue Type: Bug
Components: Test Suite
Reporter: Ondrej Kotek
Assignee: James Perkins
Fix For: 15.0.0.Beta1, 15.0.0.Final
org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase from manualmode module of wildlfy testsuite fails with the latest IBM 8 JDK bits.
*reproduce*
{noformat}
wildfly/testsuite]$ mvn test -DtestLogToFile=false -pl integration/manualmode -Dts.manualmode -Dtest=ParseAndMarshalModelsTestCase
...
[ERROR] Tests run: 40, Failures: 40, Errors: 0, Skipped: 0
{noformat}
*Error message appearing in the logs*
{noformat}
Jun 07, 2018 3:57:14 PM org.jboss.msc.service.ServiceContainerImpl <init>
ERROR: MSC000010: Failed to register MBean with MBeanServer
javax.management.InstanceAlreadyExistsException: jboss.msc:type=container,name=host-controller
at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:449)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerWithRepository(DefaultMBeanServerInterceptor.java:1910)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:978)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:912)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:336)
at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:534)
at org.jboss.msc.service.ServiceContainerImpl.<init>(ServiceContainerImpl.java:368)
at org.jboss.msc.service.ServiceContainer$Factory.create(ServiceContainer.java:221)
at org.wildfly.core.embedded.EmbeddedHostControllerBootstrap$ShutdownHook.register(EmbeddedHostControllerBootstrap.java:90)
at org.wildfly.core.embedded.EmbeddedHostControllerBootstrap$ShutdownHook.access$100(EmbeddedHostControllerBootstrap.java:80)
at org.wildfly.core.embedded.EmbeddedHostControllerBootstrap.<init>(EmbeddedHostControllerBootstrap.java:54)
at org.wildfly.core.embedded.EmbeddedHostControllerFactory$HostControllerImpl.start(EmbeddedHostControllerFactory.java:270)
at sun.reflect.GeneratedMethodAccessor8.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
at java.lang.reflect.Method.invoke(Method.java:508)
at org.wildfly.core.embedded.EmbeddedManagedProcessImpl.invokeOnServer(EmbeddedManagedProcessImpl.java:88)
at org.wildfly.core.embedded.EmbeddedManagedProcessImpl.start(EmbeddedManagedProcessImpl.java:58)
at org.jboss.as.cli.embedded.EmbedHostControllerHandler.doHandle(EmbedHostControllerHandler.java:268)
at org.jboss.as.cli.handlers.CommandHandlerWithHelp.handle(CommandHandlerWithHelp.java:89)
at org.jboss.as.cli.impl.CommandExecutor$2.lambda$build$0(CommandExecutor.java:685)
at org.jboss.as.cli.impl.CommandExecutor$2$$Lambda$79.00000000200064E0.execute(Unknown Source)
at org.jboss.as.cli.impl.CommandExecutor.lambda$execute$0(CommandExecutor.java:708)
at org.jboss.as.cli.impl.CommandExecutor$$Lambda$78.00000000AD3CF710.call(Unknown Source)
at java.util.concurrent.FutureTask.run(FutureTask.java:277)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1160)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at java.lang.Thread.run(Thread.java:811)
{noformat}
*Failure cause*
{noformat}
Caused by: org.jboss.as.cli.CommandLineException: Cannot start embedded server
at org.jboss.as.cli.embedded.EmbedServerHandler.doHandle(EmbedServerHandler.java:300)
at org.jboss.as.cli.handlers.CommandHandlerWithHelp.handle(CommandHandlerWithHelp.java:89)
at org.jboss.as.cli.impl.CommandExecutor$2.lambda$build$0(CommandExecutor.java:685)
at org.jboss.as.cli.impl.CommandExecutor$2$$Lambda$79.00000000200064E0.execute(Unknown Source)
at org.jboss.as.cli.impl.CommandExecutor.lambda$execute$0(CommandExecutor.java:708)
at org.jboss.as.cli.impl.CommandExecutor$$Lambda$78.00000000AD3CF710.call(Unknown Source)
at java.util.concurrent.FutureTask.run(FutureTask.java:277)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1160)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at java.lang.Thread.run(Thread.java:811)
Caused by: java.lang.ClassCastException: org.jboss.as.controller.client.helpers.DelegatingModelControllerClient incompatible with org.jboss.as.controller.client.ModelControllerClient
at org.wildfly.core.embedded.EmbeddedManagedProcessImpl.getModelControllerClient(EmbeddedManagedProcessImpl.java:72)
at org.jboss.as.cli.embedded.EmbedServerHandler.doHandle(EmbedServerHandler.java:244)
... 9 more
{noformat}
*Environment*
{noformat}
$ mvn -version
Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T19:49:05Z)
Maven home: /qa/tools/opt/maven3-latest
Java version: 1.8.0_171, vendor: IBM Corporation
Java home: /qa/tools/opt/x86_64/ibm-java-x86_64-sdk-8.0-5.15/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.10.0-862.el7.x86_64", arch: "amd64", family: "unix"
---
$ java -version
java version "1.8.0_171"
Java(TM) SE Runtime Environment (build 8.0.5.15 - pxa6480sr5fp15-20180502_01(SR5 FP15))
IBM J9 VM (build 2.9, JRE 1.8.0 Linux amd64-64 Compressed References 20180425_385365 (JIT enabled, AOT enabled)
OpenJ9 - a7ffbfe
OMR - a531219
IBM - 59ef3dc)
JCL - 20180425_01 based on Oracle jdk8u171-b11
{noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 7 months
[JBoss JIRA] (JGRP-2387) Message from a non-member causes FD_ALL to continually suspect it
by Bela Ban (Jira)
[ https://issues.jboss.org/browse/JGRP-2387?page=com.atlassian.jira.plugin.... ]
Bela Ban resolved JGRP-2387.
----------------------------
Resolution: Done
I changed FD_ALL and FD_ALL2 to drop suspicions of non-members: this way, no messages will be sent to non-existant members (e.g. by VERIFY_SUSPECT).
However, this won't fix the issue of messages being sent to non-members: if a message is sent to a non-member, the warnings will repeat until {{conn_expiry_timeout}} / {{conn_close_timeout}} in UNICAST3 will close the connection to the non-member.
> Message from a non-member causes FD_ALL to continually suspect it
> -----------------------------------------------------------------
>
> Key: JGRP-2387
> URL: https://issues.jboss.org/browse/JGRP-2387
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 4.0.1
> Reporter: Dennis Reed
> Assignee: Bela Ban
> Priority: Major
> Fix For: 4.1.6
>
> Attachments: Test.java, bla6.java
>
>
> If an FD_ALL control message from a non-member is seen by FD_ALL, it will start continually suspecting that node. If msg_counts_as_heartbeat=true then any message from a non-member triggers the issue. The issue is cleared on the next view change.
> This does not cause any functional issues in the cluster, but can cause repeated WARN logs in some cases.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 7 months
[JBoss JIRA] (WFWIP-230) no way how to force scale down
by Jeff Mesnil (Jira)
[ https://issues.jboss.org/browse/WFWIP-230?page=com.atlassian.jira.plugin.... ]
Jeff Mesnil reassigned WFWIP-230:
---------------------------------
Assignee: Ondrej Chaloupka (was: Jeff Mesnil)
> no way how to force scale down
> ------------------------------
>
> Key: WFWIP-230
> URL: https://issues.jboss.org/browse/WFWIP-230
> Project: WildFly WIP
> Issue Type: Bug
> Components: OpenShift
> Reporter: Martin Simka
> Assignee: Ondrej Chaloupka
> Priority: Critical
> Labels: operator
>
> inspired by upstream issue https://github.com/wildfly/wildfly-operator/issues/100. I take part of description from it
> {quote}
> When transaction scale down process reviews the state of transactions in the pods it checks if there are no unfinished prepared transactions. If there are found some then it does not permit the pod being terminated and the pod is moved to state SCALING_DOWN_RECOVERY_DIRTY. It's left there until all transactions are safely recovered.
> There are cases when transaction is never recovered in automated manner. It's time when transaction is in heuristic state. Such transaction needs to be handled manually by administrator and he is expected to connect to the app server with jboss-cli.sh and verify the transaction state.
> {quote}
> There is no way how to ignore status of tx processing (tx in this case, I guess there will be more cases in future) and force scale down.
> Users might want it during development, where data integrity doesn't matter.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 7 months
[JBoss JIRA] (WFWIP-230) no way how to force scale down
by Martin Simka (Jira)
Martin Simka created WFWIP-230:
----------------------------------
Summary: no way how to force scale down
Key: WFWIP-230
URL: https://issues.jboss.org/browse/WFWIP-230
Project: WildFly WIP
Issue Type: Bug
Components: OpenShift
Reporter: Martin Simka
Assignee: Jeff Mesnil
inspired by upstream issue https://github.com/wildfly/wildfly-operator/issues/100. I take part of description from it
{quote}
When transaction scale down process reviews the state of transactions in the pods it checks if there are no unfinished prepared transactions. If there are found some then it does not permit the pod being terminated and the pod is moved to state SCALING_DOWN_RECOVERY_DIRTY. It's left there until all transactions are safely recovered.
There are cases when transaction is never recovered in automated manner. It's time when transaction is in heuristic state. Such transaction needs to be handled manually by administrator and he is expected to connect to the app server with jboss-cli.sh and verify the transaction state.
{quote}
There is no way how to ignore status of tx processing (tx in this case, I guess there will be more cases in future) and force scale down.
Users might want it during development, where data integrity doesn't matter.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 7 months
[JBoss JIRA] (WFWIP-229) Configuring JGroups encryption protocols produces deprecated configuration
by Michal Jurc (Jira)
[ https://issues.jboss.org/browse/WFWIP-229?page=com.atlassian.jira.plugin.... ]
Michal Jurc updated WFWIP-229:
------------------------------
Description:
Any S2I configuration of ping protocols utilising encryption for protocols will result in deprecated configuration. S2I should not configure runtime to deprecated configuration by default, unless the user chooses to.
{code:title=Example JGroups ASYM_ENCRYPT configuration}
[standalone@localhost:9990 /] /subsystem=jgroups/stack=tcp/protocol=org.jgroups.protocols.ASYM_ENCRYPT:read-resource-description
{
"outcome" => "success",
"result" => {
"description" => "The configuration of a protocol within a protocol stac
k.",
"capabilities" => [{
"name" => "org.wildfly.clustering.jgroups.protocol",
"dynamic" => true,
"dynamic-elements" => [
"stack",
"protocol"
]
}],
"deprecated" => {
"since" => "5.0.0",
"reason" => "Deprecated. Use protocol=ASYM_ENCRYPT instead."
},
"attributes" => {
"module" => {
"type" => STRING,
"description" => "The module with which to resolve the protocol
type.",
"expressions-allowed" => true,
"required" => false,
"nillable" => true,
"default" => "org.jgroups",
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "resource-services"
},
"properties" => {
"type" => OBJECT,
"description" => "The properties of this protocol.",
"expressions-allowed" => true,
"required" => false,
"nillable" => true,
"value-type" => STRING,
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "resource-services"
},
"socket-binding" => {
"type" => STRING,
"description" => "Defines the bind address/port used of the serv
er socket used to receive messages from other cluster members.",
"expressions-allowed" => false,
"required" => false,
"nillable" => true,
"min-length" => 1L,
"max-length" => 2147483647L,
"deprecated" => {
"since" => "5.0.0",
"reason" => "Deprecated. Supports EAP 7.0 slaves."
},
"access-type" => "read-only",
"storage" => "configuration"
},
"statistics-enabled" => {
"type" => BOOLEAN,
"description" => "Indicates whether or not this protocol will co
llect statistics overriding stack configuration.",
"expressions-allowed" => true,
"required" => false,
"nillable" => true,
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "resource-services"
}
},
"operations" => undefined,
"notifications" => undefined,
"children" => {"property" => {
"description" => "A JGroups protocol property.",
"model-description" => undefined
}}
}
}
{code}
was:
Any JGroups configuration utilising encryption for protocols will result in deprecated configuration. S2I should not configure runtime to deprecated configuration by default, unless the user chooses to.
{code:title=Example JGroups ASYM_ENCRYPT configuration}
[standalone@localhost:9990 /] /subsystem=jgroups/stack=tcp/protocol=org.jgroups.protocols.ASYM_ENCRYPT:read-resource-description
{
"outcome" => "success",
"result" => {
"description" => "The configuration of a protocol within a protocol stac
k.",
"capabilities" => [{
"name" => "org.wildfly.clustering.jgroups.protocol",
"dynamic" => true,
"dynamic-elements" => [
"stack",
"protocol"
]
}],
"deprecated" => {
"since" => "5.0.0",
"reason" => "Deprecated. Use protocol=ASYM_ENCRYPT instead."
},
"attributes" => {
"module" => {
"type" => STRING,
"description" => "The module with which to resolve the protocol
type.",
"expressions-allowed" => true,
"required" => false,
"nillable" => true,
"default" => "org.jgroups",
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "resource-services"
},
"properties" => {
"type" => OBJECT,
"description" => "The properties of this protocol.",
"expressions-allowed" => true,
"required" => false,
"nillable" => true,
"value-type" => STRING,
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "resource-services"
},
"socket-binding" => {
"type" => STRING,
"description" => "Defines the bind address/port used of the serv
er socket used to receive messages from other cluster members.",
"expressions-allowed" => false,
"required" => false,
"nillable" => true,
"min-length" => 1L,
"max-length" => 2147483647L,
"deprecated" => {
"since" => "5.0.0",
"reason" => "Deprecated. Supports EAP 7.0 slaves."
},
"access-type" => "read-only",
"storage" => "configuration"
},
"statistics-enabled" => {
"type" => BOOLEAN,
"description" => "Indicates whether or not this protocol will co
llect statistics overriding stack configuration.",
"expressions-allowed" => true,
"required" => false,
"nillable" => true,
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "resource-services"
}
},
"operations" => undefined,
"notifications" => undefined,
"children" => {"property" => {
"description" => "A JGroups protocol property.",
"model-description" => undefined
}}
}
}
{code}
> Configuring JGroups encryption protocols produces deprecated configuration
> --------------------------------------------------------------------------
>
> Key: WFWIP-229
> URL: https://issues.jboss.org/browse/WFWIP-229
> Project: WildFly WIP
> Issue Type: Bug
> Components: OpenShift
> Environment: The example has been produced with the following S2I environment variables:
> {code}
> OPENSHIFT_DNS_PING_SERVICE_NAME=ping-service
> JGROUPS_ENCRYPT_PROTOCOL=ASYM_ENCRYPT
> JGROUPS_CLUSTER_PASSWORD=foobar123
> OPENSHIFT_DNS_PING_SERVICE_PORT=8888
> JGROUPS_PING_PROTOCOL=dns.DNS_PING
> SCRIPT_DEBUG=true
> {code}
> Reporter: Michal Jurc
> Assignee: Yeray Borges
> Priority: Critical
>
> Any S2I configuration of ping protocols utilising encryption for protocols will result in deprecated configuration. S2I should not configure runtime to deprecated configuration by default, unless the user chooses to.
> {code:title=Example JGroups ASYM_ENCRYPT configuration}
> [standalone@localhost:9990 /] /subsystem=jgroups/stack=tcp/protocol=org.jgroups.protocols.ASYM_ENCRYPT:read-resource-description
> {
> "outcome" => "success",
> "result" => {
> "description" => "The configuration of a protocol within a protocol stac
> k.",
> "capabilities" => [{
> "name" => "org.wildfly.clustering.jgroups.protocol",
> "dynamic" => true,
> "dynamic-elements" => [
> "stack",
> "protocol"
> ]
> }],
> "deprecated" => {
> "since" => "5.0.0",
> "reason" => "Deprecated. Use protocol=ASYM_ENCRYPT instead."
> },
> "attributes" => {
> "module" => {
> "type" => STRING,
> "description" => "The module with which to resolve the protocol
> type.",
> "expressions-allowed" => true,
> "required" => false,
> "nillable" => true,
> "default" => "org.jgroups",
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "resource-services"
> },
> "properties" => {
> "type" => OBJECT,
> "description" => "The properties of this protocol.",
> "expressions-allowed" => true,
> "required" => false,
> "nillable" => true,
> "value-type" => STRING,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "resource-services"
> },
> "socket-binding" => {
> "type" => STRING,
> "description" => "Defines the bind address/port used of the serv
> er socket used to receive messages from other cluster members.",
> "expressions-allowed" => false,
> "required" => false,
> "nillable" => true,
> "min-length" => 1L,
> "max-length" => 2147483647L,
> "deprecated" => {
> "since" => "5.0.0",
> "reason" => "Deprecated. Supports EAP 7.0 slaves."
> },
> "access-type" => "read-only",
> "storage" => "configuration"
> },
> "statistics-enabled" => {
> "type" => BOOLEAN,
> "description" => "Indicates whether or not this protocol will co
> llect statistics overriding stack configuration.",
> "expressions-allowed" => true,
> "required" => false,
> "nillable" => true,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "resource-services"
> }
> },
> "operations" => undefined,
> "notifications" => undefined,
> "children" => {"property" => {
> "description" => "A JGroups protocol property.",
> "model-description" => undefined
> }}
> }
> }
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 7 months
[JBoss JIRA] (WFWIP-229) Configuring JGroups encryption protocols produces deprecated configuration
by Michal Jurc (Jira)
[ https://issues.jboss.org/browse/WFWIP-229?page=com.atlassian.jira.plugin.... ]
Michal Jurc updated WFWIP-229:
------------------------------
Environment:
The example has been produced with the following S2I environment variables:
{code}
OPENSHIFT_DNS_PING_SERVICE_NAME=ping-service
JGROUPS_ENCRYPT_PROTOCOL=ASYM_ENCRYPT
JGROUPS_CLUSTER_PASSWORD=foobar123
OPENSHIFT_DNS_PING_SERVICE_PORT=8888
JGROUPS_PING_PROTOCOL=dns.DNS_PING
SCRIPT_DEBUG=true
{code}
was:
The example has been produced with the following S2I environment variables:
OPENSHIFT_DNS_PING_SERVICE_NAME=ping-service
JGROUPS_ENCRYPT_PROTOCOL=ASYM_ENCRYPT
JGROUPS_CLUSTER_PASSWORD=foobar123
OPENSHIFT_DNS_PING_SERVICE_PORT=8888
JGROUPS_PING_PROTOCOL=dns.DNS_PING
SCRIPT_DEBUG=true
> Configuring JGroups encryption protocols produces deprecated configuration
> --------------------------------------------------------------------------
>
> Key: WFWIP-229
> URL: https://issues.jboss.org/browse/WFWIP-229
> Project: WildFly WIP
> Issue Type: Bug
> Components: OpenShift
> Environment: The example has been produced with the following S2I environment variables:
> {code}
> OPENSHIFT_DNS_PING_SERVICE_NAME=ping-service
> JGROUPS_ENCRYPT_PROTOCOL=ASYM_ENCRYPT
> JGROUPS_CLUSTER_PASSWORD=foobar123
> OPENSHIFT_DNS_PING_SERVICE_PORT=8888
> JGROUPS_PING_PROTOCOL=dns.DNS_PING
> SCRIPT_DEBUG=true
> {code}
> Reporter: Michal Jurc
> Assignee: Jean Francois Denise
> Priority: Critical
>
> Any JGroups configuration utilising encryption for protocols will result in deprecated configuration. S2I should not configure runtime to deprecated configuration by default, unless the user chooses to.
> {code:title=Example JGroups ASYM_ENCRYPT configuration}
> [standalone@localhost:9990 /] /subsystem=jgroups/stack=tcp/protocol=org.jgroups.protocols.ASYM_ENCRYPT:read-resource-description
> {
> "outcome" => "success",
> "result" => {
> "description" => "The configuration of a protocol within a protocol stac
> k.",
> "capabilities" => [{
> "name" => "org.wildfly.clustering.jgroups.protocol",
> "dynamic" => true,
> "dynamic-elements" => [
> "stack",
> "protocol"
> ]
> }],
> "deprecated" => {
> "since" => "5.0.0",
> "reason" => "Deprecated. Use protocol=ASYM_ENCRYPT instead."
> },
> "attributes" => {
> "module" => {
> "type" => STRING,
> "description" => "The module with which to resolve the protocol
> type.",
> "expressions-allowed" => true,
> "required" => false,
> "nillable" => true,
> "default" => "org.jgroups",
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "resource-services"
> },
> "properties" => {
> "type" => OBJECT,
> "description" => "The properties of this protocol.",
> "expressions-allowed" => true,
> "required" => false,
> "nillable" => true,
> "value-type" => STRING,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "resource-services"
> },
> "socket-binding" => {
> "type" => STRING,
> "description" => "Defines the bind address/port used of the serv
> er socket used to receive messages from other cluster members.",
> "expressions-allowed" => false,
> "required" => false,
> "nillable" => true,
> "min-length" => 1L,
> "max-length" => 2147483647L,
> "deprecated" => {
> "since" => "5.0.0",
> "reason" => "Deprecated. Supports EAP 7.0 slaves."
> },
> "access-type" => "read-only",
> "storage" => "configuration"
> },
> "statistics-enabled" => {
> "type" => BOOLEAN,
> "description" => "Indicates whether or not this protocol will co
> llect statistics overriding stack configuration.",
> "expressions-allowed" => true,
> "required" => false,
> "nillable" => true,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "resource-services"
> }
> },
> "operations" => undefined,
> "notifications" => undefined,
> "children" => {"property" => {
> "description" => "A JGroups protocol property.",
> "model-description" => undefined
> }}
> }
> }
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 7 months
[JBoss JIRA] (WFWIP-229) Configuring JGroups encryption protocols produces deprecated configuration
by Jean Francois Denise (Jira)
[ https://issues.jboss.org/browse/WFWIP-229?page=com.atlassian.jira.plugin.... ]
Jean Francois Denise reassigned WFWIP-229:
------------------------------------------
Assignee: Yeray Borges (was: Jean Francois Denise)
> Configuring JGroups encryption protocols produces deprecated configuration
> --------------------------------------------------------------------------
>
> Key: WFWIP-229
> URL: https://issues.jboss.org/browse/WFWIP-229
> Project: WildFly WIP
> Issue Type: Bug
> Components: OpenShift
> Environment: The example has been produced with the following S2I environment variables:
> {code}
> OPENSHIFT_DNS_PING_SERVICE_NAME=ping-service
> JGROUPS_ENCRYPT_PROTOCOL=ASYM_ENCRYPT
> JGROUPS_CLUSTER_PASSWORD=foobar123
> OPENSHIFT_DNS_PING_SERVICE_PORT=8888
> JGROUPS_PING_PROTOCOL=dns.DNS_PING
> SCRIPT_DEBUG=true
> {code}
> Reporter: Michal Jurc
> Assignee: Yeray Borges
> Priority: Critical
>
> Any JGroups configuration utilising encryption for protocols will result in deprecated configuration. S2I should not configure runtime to deprecated configuration by default, unless the user chooses to.
> {code:title=Example JGroups ASYM_ENCRYPT configuration}
> [standalone@localhost:9990 /] /subsystem=jgroups/stack=tcp/protocol=org.jgroups.protocols.ASYM_ENCRYPT:read-resource-description
> {
> "outcome" => "success",
> "result" => {
> "description" => "The configuration of a protocol within a protocol stac
> k.",
> "capabilities" => [{
> "name" => "org.wildfly.clustering.jgroups.protocol",
> "dynamic" => true,
> "dynamic-elements" => [
> "stack",
> "protocol"
> ]
> }],
> "deprecated" => {
> "since" => "5.0.0",
> "reason" => "Deprecated. Use protocol=ASYM_ENCRYPT instead."
> },
> "attributes" => {
> "module" => {
> "type" => STRING,
> "description" => "The module with which to resolve the protocol
> type.",
> "expressions-allowed" => true,
> "required" => false,
> "nillable" => true,
> "default" => "org.jgroups",
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "resource-services"
> },
> "properties" => {
> "type" => OBJECT,
> "description" => "The properties of this protocol.",
> "expressions-allowed" => true,
> "required" => false,
> "nillable" => true,
> "value-type" => STRING,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "resource-services"
> },
> "socket-binding" => {
> "type" => STRING,
> "description" => "Defines the bind address/port used of the serv
> er socket used to receive messages from other cluster members.",
> "expressions-allowed" => false,
> "required" => false,
> "nillable" => true,
> "min-length" => 1L,
> "max-length" => 2147483647L,
> "deprecated" => {
> "since" => "5.0.0",
> "reason" => "Deprecated. Supports EAP 7.0 slaves."
> },
> "access-type" => "read-only",
> "storage" => "configuration"
> },
> "statistics-enabled" => {
> "type" => BOOLEAN,
> "description" => "Indicates whether or not this protocol will co
> llect statistics overriding stack configuration.",
> "expressions-allowed" => true,
> "required" => false,
> "nillable" => true,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "resource-services"
> }
> },
> "operations" => undefined,
> "notifications" => undefined,
> "children" => {"property" => {
> "description" => "A JGroups protocol property.",
> "model-description" => undefined
> }}
> }
> }
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 7 months
[JBoss JIRA] (WFWIP-229) Configuring JGroups encryption protocols produces deprecated configuration
by Michal Jurc (Jira)
[ https://issues.jboss.org/browse/WFWIP-229?page=com.atlassian.jira.plugin.... ]
Michal Jurc updated WFWIP-229:
------------------------------
Description:
Any JGroups configuration utilising encryption for protocols will result in deprecated configuration. S2I should not configure runtime to deprecated configuration by default, unless the user chooses to.
{code:title=Example JGroups ASYM_ENCRYPT configuration}
[standalone@localhost:9990 /] /subsystem=jgroups/stack=tcp/protocol=org.jgroups.protocols.ASYM_ENCRYPT:read-resource-description
{
"outcome" => "success",
"result" => {
"description" => "The configuration of a protocol within a protocol stac
k.",
"capabilities" => [{
"name" => "org.wildfly.clustering.jgroups.protocol",
"dynamic" => true,
"dynamic-elements" => [
"stack",
"protocol"
]
}],
"deprecated" => {
"since" => "5.0.0",
"reason" => "Deprecated. Use protocol=ASYM_ENCRYPT instead."
},
"attributes" => {
"module" => {
"type" => STRING,
"description" => "The module with which to resolve the protocol
type.",
"expressions-allowed" => true,
"required" => false,
"nillable" => true,
"default" => "org.jgroups",
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "resource-services"
},
"properties" => {
"type" => OBJECT,
"description" => "The properties of this protocol.",
"expressions-allowed" => true,
"required" => false,
"nillable" => true,
"value-type" => STRING,
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "resource-services"
},
"socket-binding" => {
"type" => STRING,
"description" => "Defines the bind address/port used of the serv
er socket used to receive messages from other cluster members.",
"expressions-allowed" => false,
"required" => false,
"nillable" => true,
"min-length" => 1L,
"max-length" => 2147483647L,
"deprecated" => {
"since" => "5.0.0",
"reason" => "Deprecated. Supports EAP 7.0 slaves."
},
"access-type" => "read-only",
"storage" => "configuration"
},
"statistics-enabled" => {
"type" => BOOLEAN,
"description" => "Indicates whether or not this protocol will co
llect statistics overriding stack configuration.",
"expressions-allowed" => true,
"required" => false,
"nillable" => true,
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "resource-services"
}
},
"operations" => undefined,
"notifications" => undefined,
"children" => {"property" => {
"description" => "A JGroups protocol property.",
"model-description" => undefined
}}
}
}
{code}
was:
Any JGroups configuration utilising encryption for protocols will result in deprecated configuration. S2I should not configure runtime to deprecated configuration by default, unless the user chooses to.
{code:title="Example JGroups ASYM_ENCRYPT configuration"}
[standalone@localhost:9990 /] /subsystem=jgroups/stack=tcp/protocol=org.jgroups.protocols.ASYM_ENCRYPT:read-resource-description
{
"outcome" => "success",
"result" => {
"description" => "The configuration of a protocol within a protocol stac
k.",
"capabilities" => [{
"name" => "org.wildfly.clustering.jgroups.protocol",
"dynamic" => true,
"dynamic-elements" => [
"stack",
"protocol"
]
}],
"deprecated" => {
"since" => "5.0.0",
"reason" => "Deprecated. Use protocol=ASYM_ENCRYPT instead."
},
"attributes" => {
"module" => {
"type" => STRING,
"description" => "The module with which to resolve the protocol
type.",
"expressions-allowed" => true,
"required" => false,
"nillable" => true,
"default" => "org.jgroups",
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "resource-services"
},
"properties" => {
"type" => OBJECT,
"description" => "The properties of this protocol.",
"expressions-allowed" => true,
"required" => false,
"nillable" => true,
"value-type" => STRING,
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "resource-services"
},
"socket-binding" => {
"type" => STRING,
"description" => "Defines the bind address/port used of the serv
er socket used to receive messages from other cluster members.",
"expressions-allowed" => false,
"required" => false,
"nillable" => true,
"min-length" => 1L,
"max-length" => 2147483647L,
"deprecated" => {
"since" => "5.0.0",
"reason" => "Deprecated. Supports EAP 7.0 slaves."
},
"access-type" => "read-only",
"storage" => "configuration"
},
"statistics-enabled" => {
"type" => BOOLEAN,
"description" => "Indicates whether or not this protocol will co
llect statistics overriding stack configuration.",
"expressions-allowed" => true,
"required" => false,
"nillable" => true,
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "resource-services"
}
},
"operations" => undefined,
"notifications" => undefined,
"children" => {"property" => {
"description" => "A JGroups protocol property.",
"model-description" => undefined
}}
}
}
{code}
> Configuring JGroups encryption protocols produces deprecated configuration
> --------------------------------------------------------------------------
>
> Key: WFWIP-229
> URL: https://issues.jboss.org/browse/WFWIP-229
> Project: WildFly WIP
> Issue Type: Bug
> Components: OpenShift
> Environment: The example has been produced with the following S2I environment variables:
> OPENSHIFT_DNS_PING_SERVICE_NAME=ping-service
> JGROUPS_ENCRYPT_PROTOCOL=ASYM_ENCRYPT
> JGROUPS_CLUSTER_PASSWORD=foobar123
> OPENSHIFT_DNS_PING_SERVICE_PORT=8888
> JGROUPS_PING_PROTOCOL=dns.DNS_PING
> SCRIPT_DEBUG=true
> Reporter: Michal Jurc
> Assignee: Jean Francois Denise
> Priority: Critical
>
> Any JGroups configuration utilising encryption for protocols will result in deprecated configuration. S2I should not configure runtime to deprecated configuration by default, unless the user chooses to.
> {code:title=Example JGroups ASYM_ENCRYPT configuration}
> [standalone@localhost:9990 /] /subsystem=jgroups/stack=tcp/protocol=org.jgroups.protocols.ASYM_ENCRYPT:read-resource-description
> {
> "outcome" => "success",
> "result" => {
> "description" => "The configuration of a protocol within a protocol stac
> k.",
> "capabilities" => [{
> "name" => "org.wildfly.clustering.jgroups.protocol",
> "dynamic" => true,
> "dynamic-elements" => [
> "stack",
> "protocol"
> ]
> }],
> "deprecated" => {
> "since" => "5.0.0",
> "reason" => "Deprecated. Use protocol=ASYM_ENCRYPT instead."
> },
> "attributes" => {
> "module" => {
> "type" => STRING,
> "description" => "The module with which to resolve the protocol
> type.",
> "expressions-allowed" => true,
> "required" => false,
> "nillable" => true,
> "default" => "org.jgroups",
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "resource-services"
> },
> "properties" => {
> "type" => OBJECT,
> "description" => "The properties of this protocol.",
> "expressions-allowed" => true,
> "required" => false,
> "nillable" => true,
> "value-type" => STRING,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "resource-services"
> },
> "socket-binding" => {
> "type" => STRING,
> "description" => "Defines the bind address/port used of the serv
> er socket used to receive messages from other cluster members.",
> "expressions-allowed" => false,
> "required" => false,
> "nillable" => true,
> "min-length" => 1L,
> "max-length" => 2147483647L,
> "deprecated" => {
> "since" => "5.0.0",
> "reason" => "Deprecated. Supports EAP 7.0 slaves."
> },
> "access-type" => "read-only",
> "storage" => "configuration"
> },
> "statistics-enabled" => {
> "type" => BOOLEAN,
> "description" => "Indicates whether or not this protocol will co
> llect statistics overriding stack configuration.",
> "expressions-allowed" => true,
> "required" => false,
> "nillable" => true,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "resource-services"
> }
> },
> "operations" => undefined,
> "notifications" => undefined,
> "children" => {"property" => {
> "description" => "A JGroups protocol property.",
> "model-description" => undefined
> }}
> }
> }
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 7 months
[JBoss JIRA] (WFWIP-229) Configuring JGroups encryption protocols produces deprecated configuration
by Michal Jurc (Jira)
Michal Jurc created WFWIP-229:
---------------------------------
Summary: Configuring JGroups encryption protocols produces deprecated configuration
Key: WFWIP-229
URL: https://issues.jboss.org/browse/WFWIP-229
Project: WildFly WIP
Issue Type: Bug
Components: OpenShift
Environment: The example has been produced with the following S2I environment variables:
{code}
OPENSHIFT_DNS_PING_SERVICE_NAME=ping-service
JGROUPS_ENCRYPT_PROTOCOL=ASYM_ENCRYPT
JGROUPS_CLUSTER_PASSWORD=foobar123
OPENSHIFT_DNS_PING_SERVICE_PORT=8888
JGROUPS_PING_PROTOCOL=dns.DNS_PING
SCRIPT_DEBUG=true
{code}
Reporter: Michal Jurc
Assignee: Jean Francois Denise
Any JGroups configuration utilising encryption for protocols will result in deprecated configuration. S2I should not configure runtime to deprecated configuration by default, unless the user chooses to.
{code:title="Example JGroups ASYM_ENCRYPT configuration"}
[standalone@localhost:9990 /] /subsystem=jgroups/stack=tcp/protocol=org.jgroups.protocols.ASYM_ENCRYPT:read-resource-description
{
"outcome" => "success",
"result" => {
"description" => "The configuration of a protocol within a protocol stac
k.",
"capabilities" => [{
"name" => "org.wildfly.clustering.jgroups.protocol",
"dynamic" => true,
"dynamic-elements" => [
"stack",
"protocol"
]
}],
"deprecated" => {
"since" => "5.0.0",
"reason" => "Deprecated. Use protocol=ASYM_ENCRYPT instead."
},
"attributes" => {
"module" => {
"type" => STRING,
"description" => "The module with which to resolve the protocol
type.",
"expressions-allowed" => true,
"required" => false,
"nillable" => true,
"default" => "org.jgroups",
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "resource-services"
},
"properties" => {
"type" => OBJECT,
"description" => "The properties of this protocol.",
"expressions-allowed" => true,
"required" => false,
"nillable" => true,
"value-type" => STRING,
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "resource-services"
},
"socket-binding" => {
"type" => STRING,
"description" => "Defines the bind address/port used of the serv
er socket used to receive messages from other cluster members.",
"expressions-allowed" => false,
"required" => false,
"nillable" => true,
"min-length" => 1L,
"max-length" => 2147483647L,
"deprecated" => {
"since" => "5.0.0",
"reason" => "Deprecated. Supports EAP 7.0 slaves."
},
"access-type" => "read-only",
"storage" => "configuration"
},
"statistics-enabled" => {
"type" => BOOLEAN,
"description" => "Indicates whether or not this protocol will co
llect statistics overriding stack configuration.",
"expressions-allowed" => true,
"required" => false,
"nillable" => true,
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "resource-services"
}
},
"operations" => undefined,
"notifications" => undefined,
"children" => {"property" => {
"description" => "A JGroups protocol property.",
"model-description" => undefined
}}
}
}
{code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 7 months