[JBoss JIRA] (JGRP-2152) ASYM_ENCRYPT failure on Wildfly 10.1.0
by Richard Achmatowicz (JIRA)
[ https://issues.jboss.org/browse/JGRP-2152?page=com.atlassian.jira.plugin.... ]
Richard Achmatowicz edited comment on JGRP-2152 at 1/12/17 12:34 PM:
---------------------------------------------------------------------
I can't find any references to ENCRYPT in the testsuite, so probably not.
[~mvinkler] Michal, are you aware of any QA testing for JGroups security protocols?
I'll do a test myself to see what is going on. Report back later today.
Richard
was (Author: rachmato):
I can't find any references to ENCRYPT in the testsuite, so probably
not. Copying Michal to see if there is any testing from QA which makes
use of JGroups authentication or encryption.
I'll do a test myself to see what is going on. Report back later today.
Richard
> ASYM_ENCRYPT failure on Wildfly 10.1.0
> --------------------------------------
>
> Key: JGRP-2152
> URL: https://issues.jboss.org/browse/JGRP-2152
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.6.10
> Reporter: Matt Wringe
> Assignee: Bela Ban
> Fix For: 4.0, 3.6.13
>
> Attachments: hawkular-metrics-1.log, hawkular-metrics-2.log, standalone.xml
>
>
> Using ASYM_ENCRYPT on Wildfly 10.1.0 seems to be broken.
> I am using the parameters for ASYM_ENCRYPT specified in http://www.jgroups.org/manual/index.html#Security
> Note: running with SYM_ENCRYPT doesn't cause any issues and it works fine with my setup. Its only ASYM_ENCRYPT which is currently failing.
> Note: running this on EAP fails in a similar manner.
> Eg:
> <protocol type="ASYM_ENCRYPT">
> <property name="encrypt_entire_message">true</property>
> <property name="sym_keylength">128</property>
> <property name="sym_algorithm">AES/ECB/PKCS5Padding</property>
> <property name="asym_keylength">512</property>
> <property name="asym_algorithm">RSA</property>
> </protocol>
> If I run a single instance, then I don't see any problems appear in the logs. Its when I start a second instance that I start to see errors about unrecognised ciphers and timeouts.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JGRP-2152) ASYM_ENCRYPT failure on Wildfly 10.1.0
by Richard Achmatowicz (JIRA)
[ https://issues.jboss.org/browse/JGRP-2152?page=com.atlassian.jira.plugin.... ]
Richard Achmatowicz edited comment on JGRP-2152 at 1/12/17 12:30 PM:
---------------------------------------------------------------------
I can't find any references to ENCRYPT in the testsuite, so probably
not. Copying Michal to see if there is any testing from QA which makes
use of JGroups authentication or encryption.
I'll do a test myself to see what is going on. Report back later today.
Richard
was (Author: rachmato):
I can't find any references to ENCRYPT in the testsuite, so probably
not. Copying Michal to see if there is any testing from QA which makes
use of JGroups authentication or encryption.
You have a configuration (asym_encrypt) which uses the same
configuration, so I assume that that sym_algorithm format used in the
test is supported.
It could be a problem with the forward slashes. I'll do a test myself to
see what is going on. Report back later today.
Richard
> ASYM_ENCRYPT failure on Wildfly 10.1.0
> --------------------------------------
>
> Key: JGRP-2152
> URL: https://issues.jboss.org/browse/JGRP-2152
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.6.10
> Reporter: Matt Wringe
> Assignee: Bela Ban
> Fix For: 4.0, 3.6.13
>
> Attachments: hawkular-metrics-1.log, hawkular-metrics-2.log, standalone.xml
>
>
> Using ASYM_ENCRYPT on Wildfly 10.1.0 seems to be broken.
> I am using the parameters for ASYM_ENCRYPT specified in http://www.jgroups.org/manual/index.html#Security
> Note: running with SYM_ENCRYPT doesn't cause any issues and it works fine with my setup. Its only ASYM_ENCRYPT which is currently failing.
> Note: running this on EAP fails in a similar manner.
> Eg:
> <protocol type="ASYM_ENCRYPT">
> <property name="encrypt_entire_message">true</property>
> <property name="sym_keylength">128</property>
> <property name="sym_algorithm">AES/ECB/PKCS5Padding</property>
> <property name="asym_keylength">512</property>
> <property name="asym_algorithm">RSA</property>
> </protocol>
> If I run a single instance, then I don't see any problems appear in the logs. Its when I start a second instance that I start to see errors about unrecognised ciphers and timeouts.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (WFCORE-2186) Salted password cannot be set through CLI for Elytron filesystem-realm identity
by Jean-Francois Denise (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2186?page=com.atlassian.jira.plugi... ]
Jean-Francois Denise commented on WFCORE-2186:
----------------------------------------------
I just check, you are right. The CLI parser has no knowledge of the bytes{0xnn, ...} syntax. It considers it to be a string.
> Salted password cannot be set through CLI for Elytron filesystem-realm identity
> -------------------------------------------------------------------------------
>
> Key: WFCORE-2186
> URL: https://issues.jboss.org/browse/WFCORE-2186
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Affects Versions: 3.0.0.Alpha16
> Reporter: Ondrej Lukas
> Assignee: Michal Petrov
>
> Password encryption/hash mechanisms which contain {{salt}} attribute for filesystem-realm identity cannot be added through CLI. {{set-password}} operation fails and finishes with failure-description "WFLYCTL0155: password may not be null" even if password was set. It seems when {{salt}} attribute with {{bytes}} value is used then {{password}} attribute is ignored by CLI.
> Following password encryption/hash mechanisms from filesystem-realm identity are affected by issue:
> - {{bcrypt}}
> - {{salted-simple-digest}}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (WFCORE-2189) JmxControlledStateNotificationsTestCase fails on IBM JDK (domain module)
by ehsavoie Hugonnet (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2189?page=com.atlassian.jira.plugi... ]
ehsavoie Hugonnet moved JBEAP-8252 to WFCORE-2189:
--------------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-2189 (was: JBEAP-8252)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Test Suite
(was: Test Suite)
Affects Testing: (was: Regression)
> JmxControlledStateNotificationsTestCase fails on IBM JDK (domain module)
> ------------------------------------------------------------------------
>
> Key: WFCORE-2189
> URL: https://issues.jboss.org/browse/WFCORE-2189
> Project: WildFly Core
> Issue Type: Bug
> Components: Test Suite
> Reporter: ehsavoie Hugonnet
> Assignee: ehsavoie Hugonnet
>
> *Description of problem:*
> org.jboss.as.test.integration.domain.events.JmxControlledStateNotificationsTestCase from domain module fails on IBM JDK
> This is regression against EAP 7.1.0.DR8.
> *How reproducible:*
> 100%
> *Actual results:*
> Stack trace:
> {noformat}
> java.lang.AssertionError: File not found /mnt/hudson_workspace/workspace/eap-7x-as-testsuite-test-core-rhel/b7cade8d/testsuite/domain/target/wildfly-core/target/notifications/data/jmx-facade/runtime-configuration-notifications.txt
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.jboss.as.test.integration.domain.events.JmxControlledStateNotificationsTestCase.readAndCheckFile(JmxControlledStateNotificationsTestCase.java:129)
> at org.jboss.as.test.integration.domain.events.JmxControlledStateNotificationsTestCase.checkFacadeJmxNotifications(JmxControlledStateNotificationsTestCase.java:106)
> at org.jboss.as.test.integration.domain.events.JmxControlledStateNotificationsTestCase.checkNotifications(JmxControlledStateNotificationsTestCase.java:87)
> {noformat}
> Standard Output:
> {noformat}
> &#27;[0m17:21:42,227 INFO [org.jboss.modules] (main) JBoss Modules version 1.6.0.Beta3-redhat-1
> &#27;[0m&#27;[0m17:21:42,615 INFO [org.jboss.as.process.Host Controller.status] (main) WFLYPC0018: Starting process 'Host Controller'
> &#27;[0m[Host Controller] &#27;[0m17:21:43,350 INFO [org.jboss.modules] (main) JBoss Modules version 1.6.0.Beta3-redhat-1&#27;[0m
> [Host Controller] &#27;[0m&#27;[0m17:21:43,773 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.7.Final-redhat-1&#27;[0m
> [Host Controller] &#27;[0m&#27;[0m17:21:43,824 INFO [org.jboss.as] (MSC service thread 1-1) WFLYSRV0049: WildFly Core 3.0.0.Alpha17-redhat-1 "Kenny" starting&#27;[0m
> [Host Controller] &#27;[0m&#27;[0m17:21:44,168 INFO [org.jboss.as.domain.management] (Controller Boot Thread) WFLYDM0136: Registered OpenSSL provider&#27;[0m
> [Host Controller] &#27;[0m&#27;[0m17:21:44,343 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/host=master/core-service=management/management-interface=native-interface' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.&#27;[0m
> [Host Controller] &#27;[0m&#27;[0m17:21:44,344 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/host=master/core-service=management/management-interface=http-interface' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.&#27;[0m
> [Host Controller] &#27;[0m&#27;[0m17:21:44,443 INFO [org.xnio] (MSC service thread 1-4) XNIO version 3.4.3.Final-redhat-1&#27;[0m
> [Host Controller] &#27;[0m&#27;[0m17:21:44,449 INFO [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0003: Creating http management service using network interface (management) port (9990) securePort (-1)&#27;[0m
> [Host Controller] &#27;[0m&#27;[0m17:21:44,450 INFO [org.xnio.nio] (MSC service thread 1-4) XNIO NIO Implementation Version 3.4.3.Final-redhat-1&#27;[0m
> [Host Controller] &#27;[0m&#27;[0m17:21:44,493 INFO [org.jboss.as.patching] (MSC service thread 1-2) WFLYPAT0050: WildFly cumulative patch ID is: base, one-off patches include: none&#27;[0m
> [Host Controller] &#27;[0m&#27;[0m17:21:44,604 INFO [org.jboss.remoting] (MSC service thread 1-4) JBoss Remoting version 5.0.0.Beta12-redhat-1&#27;[0m
> [Host Controller] &#27;[0m&#27;[0m17:21:44,617 INFO [org.wildfly.security] (MSC service thread 1-4) ELY00001: WildFly Elytron version 1.1.0.Beta18-redhat-1&#27;[0m
> [Host Controller] &#27;[0m&#27;[33m17:21:44,634 WARN [org.jboss.as.domain.http.api.undertow] (MSC service thread 1-2) WFLYDMHTTP0003: Unable to load console module for slot main, disabling console&#27;[0m
> [Host Controller] &#27;[33m&#27;[0m&#27;[0m17:21:44,691 INFO [org.jboss.as.remoting] (MSC service thread 1-4) WFLYRMT0001: Listening on 10.19.70.129:9999&#27;[0m
> [Host Controller] &#27;[0m&#27;[0m17:21:45,118 INFO [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0023: Starting server main-one&#27;[0m
> &#27;[0m17:21:45,175 INFO [org.jboss.as.process.Server:main-one.status] (ProcessController-threads - 3) WFLYPC0018: Starting process 'Server:main-one'
> &#27;[0m[Server:main-one] &#27;[0m17:21:46,060 INFO [org.jboss.modules] (main) JBoss Modules version 1.6.0.Beta3-redhat-1&#27;[0m
> [Server:main-one] &#27;[0m&#27;[0m17:21:46,527 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.7.Final-redhat-1&#27;[0m
> [Server:main-one] &#27;[0m&#27;[0m17:21:46,633 INFO [org.jboss.as] (MSC service thread 1-1) WFLYSRV0049: WildFly Core 3.0.0.Alpha17-redhat-1 "Kenny" starting&#27;[0m
> [Server:main-one] &#27;[0m&#27;[0m17:21:46,702 INFO [org.xnio] (MSC service thread 1-1) XNIO version 3.4.3.Final-redhat-1&#27;[0m
> [Server:main-one] &#27;[0m&#27;[0m17:21:46,708 INFO [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.4.3.Final-redhat-1&#27;[0m
> [Server:main-one] &#27;[0m&#27;[0m17:21:46,757 INFO [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 5.0.0.Beta12-redhat-1&#27;[0m
> [Server:main-one] &#27;[0m&#27;[0m17:21:46,768 INFO [org.wildfly.security] (MSC service thread 1-1) ELY00001: WildFly Elytron version 1.1.0.Beta18-redhat-1&#27;[0m
> [Server:main-one] &#27;[0m&#27;[0m17:21:47,034 INFO [org.jboss.as.domain.management] (MSC service thread 1-1) WFLYDM0136: Registered OpenSSL provider&#27;[0m
> [Host Controller] &#27;[0m&#27;[0m17:21:47,522 INFO [org.jboss.as.host.controller] (management task-5) WFLYHC0021: Server [Server:main-one] connected using connection [Channel ID 23ed0526 (inbound) of Remoting connection 739aecce to /10.19.64.169:55242 of endpoint "master:MANAGEMENT" <6469d62>]&#27;[0m
> [Host Controller] &#27;[0m&#27;[0m17:21:47,546 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://10.19.70.129:9990/management&#27;[0m
> [Host Controller] &#27;[0m&#27;[0m17:21:47,547 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://10.19.70.129:9990&#27;[0m
> [Host Controller] &#27;[0m&#27;[0m17:21:47,547 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Core 3.0.0.Alpha17-redhat-1 "Kenny" (Host Controller) started in 4632ms - Started 50 of 50 services (13 services are lazy, passive or on-demand)&#27;[0m
> [Host Controller] &#27;[0m&#27;[0m17:21:47,548 INFO [org.jboss.as.host.controller] (server-registration-threads - 1) WFLYHC0020: Registering server main-one&#27;[0m
> [Server:main-one] &#27;[0m17:21:47,784 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 13) WFLYIO001: Worker 'default' has auto-configured to 4 core threads with 32 task threads based on your 2 available processors&#27;[0m
> INFO [org.jboss.as.test.integration.domain.management.util.DomainLifecycleUtil] ServerIdentity{name=main-one, host=master, server-group=main-server-group} status is starting
> [Server:main-one] 17:21:47,838 INFO [org.jboss.as.patching] (MSC service thread 1-3) WFLYPAT0050: WildFly cumulative patch ID is: base, one-off patches include: none
> [Server:main-one] 17:21:47,972 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Core 3.0.0.Alpha17-redhat-1 "Kenny" started in 2458ms - Started 49 of 66 services (24 services are lazy, passive or on-demand)
> [Server:main-one] 17:21:47,974 INFO [org.jboss.as.server] (ServerService Thread Pool -- 2) WFLYSRV0212: Resuming server
> INFO [org.jboss.as.test.integration.domain.management.util.DomainLifecycleUtil] All servers started in 6743 ms
> INFO [org.jboss.as.test.integration.domain.management.util.DomainLifecycleUtil] HostController started in 6998 ms
> [Host Controller] &#27;[0m&#27;[0m17:21:48,404 INFO [org.jboss.as.repository] (management-handler-thread - 4) WFLYDR0001: Content added at location /mnt/hudson_workspace/workspace/eap-7x-as-testsuite-test-core-rhel/b7cade8d/testsuite/domain/target/domains/JmxControlledStateNotificationsTestCase/master/data/content/4a/f5498a9b4d6b041875e0e679dbc31d60f0e5be/content&#27;[0m
> [Server:main-one] 17:21:48,513 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "test-jmx-notifications-deployment.jar" (runtime-name: "test-jmx-notifications-deployment.jar")
> [Server:main-one] 17:21:48,543 WARN [org.jboss.as.dependency.private] (MSC service thread 1-2) WFLYSRV0018: Deployment "deployment.test-jmx-notifications-deployment.jar" is using a private module ("org.jboss.as.jmx:main") which may be changed or removed in future versions without notice.
> [Server:main-one] 17:21:48,543 WARN [org.jboss.as.dependency.private] (MSC service thread 1-2) WFLYSRV0018: Deployment "deployment.test-jmx-notifications-deployment.jar" is using a private module ("org.jboss.as.server:main") which may be changed or removed in future versions without notice.
> [Server:main-one] 17:21:48,543 WARN [org.jboss.as.dependency.private] (MSC service thread 1-2) WFLYSRV0018: Deployment "deployment.test-jmx-notifications-deployment.jar" is using a private module ("org.jboss.as.controller:main") which may be changed or removed in future versions without notice.
> [Server:main-one] 17:21:48,548 INFO [stdout] (MSC service thread 1-2) Properties found
> [Server:main-one] 17:21:48,630 INFO [org.jboss.as.server] (ServerService Thread Pool -- 2) WFLYSRV0010: Deployed "test-jmx-notifications-deployment.jar" (runtime-name : "test-jmx-notifications-deployment.jar")
> [Host Controller] &#27;[0m&#27;[0m17:21:48,672 INFO [org.jboss.as.host.controller] (Host Controller Service Threads - 8) WFLYHC0024: Stopping server main-one&#27;[0m
> &#27;[0m17:21:48,676 INFO [org.jboss.as.process.Server:main-one.status] (ProcessController-threads - 3) WFLYPC0019: Stopping process 'Server:main-one'
> &#27;[0m[Server:main-one] 17:21:48,678 INFO [org.jboss.as.server] (main) WFLYSRV0240: ProcessController has signalled to shut down; shutting down
> [Server:main-one] 17:21:48,696 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0028: Stopped deployment test-jmx-notifications-deployment.jar (runtime-name: test-jmx-notifications-deployment.jar) in 11ms
> [Host Controller] &#27;[0m&#27;[0m17:21:48,707 INFO [org.jboss.as.host.controller] (management I/O-2) WFLYHC0027: Unregistering server main-one&#27;[0m
> [Server:main-one] 17:21:48,712 INFO [org.jboss.as] (MSC service thread 1-4) WFLYSRV0050: WildFly Core 3.0.0.Alpha17-redhat-1 "Kenny" stopped in 27ms
> &#27;[0m17:21:48,719 INFO [org.jboss.as.process.Server:main-one.status] (reaper for Server:main-one) WFLYPC0011: Process 'Server:main-one' finished with an exit status of 0
> &#27;[0m[Host Controller] &#27;[0m&#27;[0m17:21:48,721 INFO [org.jboss.as.host.controller] (ProcessControllerConnection-thread - 2) WFLYHC0027: Unregistering server main-one&#27;[0m
> [Host Controller] &#27;[0m&#27;[0m17:21:48,779 INFO [org.jboss.as] (MSC service thread 1-3) WFLYSRV0050: WildFly Core 3.0.0.Alpha17-redhat-1 "Kenny" stopped in 116ms&#27;[0m
> [Host Controller] &#27;[0m&#27;[0m17:21:48,782 INFO [org.jboss.as] (MSC service thread 1-3) WFLYSRV0049: WildFly Core 3.0.0.Alpha17-redhat-1 "Kenny" starting&#27;[0m
> [Host Controller] &#27;[0m&#27;[0m17:21:48,825 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/host=master/core-service=management/management-interface=native-interface' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.&#27;[0m
> [Host Controller] &#27;[0m&#27;[0m17:21:48,826 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/host=master/core-service=management/management-interface=http-interface' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.&#27;[0m
> [Host Controller] &#27;[0m&#27;[0m17:21:48,852 INFO [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0003: Creating http management service using network interface (management) port (9990) securePort (-1)&#27;[0m
> [Host Controller] &#27;[0m&#27;[0m17:21:48,867 INFO [org.jboss.as.patching] (MSC service thread 1-1) WFLYPAT0050: WildFly cumulative patch ID is: base, one-off patches include: none&#27;[0m
> [Host Controller] &#27;[0m&#27;[33m17:21:48,878 WARN [org.jboss.as.domain.http.api.undertow] (MSC service thread 1-3) WFLYDMHTTP0003: Unable to load console module for slot main, disabling console&#27;[0m
> [Host Controller] &#27;[33m&#27;[0m&#27;[0m17:21:48,880 INFO [org.jboss.as.remoting] (MSC service thread 1-3) WFLYRMT0001: Listening on 10.19.70.129:9999&#27;[0m
> [Host Controller] &#27;[0m&#27;[0m17:21:49,011 INFO [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0023: Starting server main-one&#27;[0m
> &#27;[0m17:21:49,054 INFO [org.jboss.as.process.Server:main-one.status] (ProcessController-threads - 3) WFLYPC0018: Starting process 'Server:main-one'
> &#27;[0m[Server:main-one] 17:21:49,850 INFO [org.jboss.modules] (main) JBoss Modules version 1.6.0.Beta3-redhat-1
> [Server:main-one] 17:21:50,337 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.7.Final-redhat-1
> [Server:main-one] 17:21:50,455 INFO [org.jboss.as] (MSC service thread 1-1) WFLYSRV0049: WildFly Core 3.0.0.Alpha17-redhat-1 "Kenny" starting
> [Server:main-one] 17:21:50,517 INFO [org.xnio] (MSC service thread 1-1) XNIO version 3.4.3.Final-redhat-1
> [Server:main-one] 17:21:50,529 INFO [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.4.3.Final-redhat-1
> [Server:main-one] 17:21:50,589 INFO [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 5.0.0.Beta12-redhat-1
> [Server:main-one] 17:21:50,601 INFO [org.wildfly.security] (MSC service thread 1-1) ELY00001: WildFly Elytron version 1.1.0.Beta18-redhat-1
> [Server:main-one] 17:21:50,861 INFO [org.jboss.as.domain.management] (MSC service thread 1-3) WFLYDM0136: Registered OpenSSL provider
> [Host Controller] &#27;[0m&#27;[0m17:21:51,139 INFO [org.jboss.as.host.controller] (management task-4) WFLYHC0021: Server [Server:main-one] connected using connection [Channel ID 099d966a (inbound) of Remoting connection 4014ff22 to /10.19.64.169:45280 of endpoint "master:MANAGEMENT" <9b6ce020>]&#27;[0m
> [Host Controller] &#27;[0m&#27;[0m17:21:51,154 INFO [org.jboss.as.host.controller] (server-registration-threads - 1) WFLYHC0020: Registering server main-one&#27;[0m
> [Host Controller] &#27;[0m&#27;[0m17:21:51,167 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://10.19.70.129:9990/management&#27;[0m
> [Host Controller] &#27;[0m&#27;[0m17:21:51,167 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://10.19.70.129:9990&#27;[0m
> [Host Controller] &#27;[0m&#27;[0m17:21:51,167 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Core 3.0.0.Alpha17-redhat-1 "Kenny" (Host Controller) started in 2384ms - Started 50 of 50 services (13 services are lazy, passive or on-demand)&#27;[0m
> INFO [org.jboss.as.test.integration.domain.management.util.DomainLifecycleUtil] ServerIdentity{name=main-one, host=master, server-group=main-server-group} status is starting
> [Server:main-one] 17:21:51,405 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 14) WFLYIO001: Worker 'default' has auto-configured to 4 core threads with 32 task threads based on your 2 available processors
> [Server:main-one] 17:21:51,465 INFO [org.jboss.as.patching] (MSC service thread 1-2) WFLYPAT0050: WildFly cumulative patch ID is: base, one-off patches include: none
> [Server:main-one] 17:21:51,491 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "test-jmx-notifications-deployment.jar" (runtime-name: "test-jmx-notifications-deployment.jar")
> [Server:main-one] 17:21:51,523 WARN [org.jboss.as.dependency.private] (MSC service thread 1-4) WFLYSRV0018: Deployment "deployment.test-jmx-notifications-deployment.jar" is using a private module ("org.jboss.as.jmx:main") which may be changed or removed in future versions without notice.
> [Server:main-one] 17:21:51,523 WARN [org.jboss.as.dependency.private] (MSC service thread 1-4) WFLYSRV0018: Deployment "deployment.test-jmx-notifications-deployment.jar" is using a private module ("org.jboss.as.server:main") which may be changed or removed in future versions without notice.
> [Server:main-one] 17:21:51,523 WARN [org.jboss.as.dependency.private] (MSC service thread 1-4) WFLYSRV0018: Deployment "deployment.test-jmx-notifications-deployment.jar" is using a private module ("org.jboss.as.controller:main") which may be changed or removed in future versions without notice.
> [Server:main-one] 17:21:51,529 INFO [stdout] (MSC service thread 1-4) Properties found
> [Server:main-one] 17:21:51,554 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Deployed "test-jmx-notifications-deployment.jar" (runtime-name : "test-jmx-notifications-deployment.jar")
> [Server:main-one] 17:21:51,665 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Core 3.0.0.Alpha17-redhat-1 "Kenny" started in 2320ms - Started 67 of 84 services (26 services are lazy, passive or on-demand)
> [Server:main-one] 17:21:51,668 INFO [org.jboss.as.server] (ServerService Thread Pool -- 6) WFLYSRV0212: Resuming server
> &#27;[0m17:21:51,804 INFO [org.jboss.as.process.Server:main-one.status] (ProcessController-threads - 3) WFLYPC0019: Stopping process 'Server:main-one'
> &#27;[0m[Host Controller] &#27;[0m&#27;[0m17:21:51,802 INFO [org.jboss.as.host.controller] (Host Controller Service Threads - 20) WFLYHC0024: Stopping server main-one&#27;[0m
> [Server:main-one] 17:21:51,806 INFO [org.jboss.as.server] (main) WFLYSRV0240: ProcessController has signalled to shut down; shutting down
> [Server:main-one] 17:21:51,825 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment test-jmx-notifications-deployment.jar (runtime-name: test-jmx-notifications-deployment.jar) in 11ms
> [Host Controller] &#27;[0m&#27;[0m17:21:51,834 INFO [org.jboss.as.host.controller] (management I/O-2) WFLYHC0027: Unregistering server main-one&#27;[0m
> [Server:main-one] 17:21:51,845 INFO [org.jboss.as] (MSC service thread 1-3) WFLYSRV0050: WildFly Core 3.0.0.Alpha17-redhat-1 "Kenny" stopped in 31ms
> &#27;[0m17:21:51,852 INFO [org.jboss.as.process.Server:main-one.status] (reaper for Server:main-one) WFLYPC0011: Process 'Server:main-one' finished with an exit status of 0
> &#27;[0m[Host Controller] &#27;[0m&#27;[0m17:21:51,892 INFO [org.jboss.as.host.controller] (ProcessControllerConnection-thread - 2) WFLYHC0027: Unregistering server main-one&#27;[0m
> [Host Controller] &#27;[0m&#27;[0m17:21:51,943 INFO [org.jboss.as] (MSC service thread 1-4) WFLYSRV0050: WildFly Core 3.0.0.Alpha17-redhat-1 "Kenny" stopped in 149ms&#27;[0m
> [Host Controller] &#27;[0m&#27;[0m17:21:51,944 INFO [org.jboss.as] (MSC service thread 1-4) WFLYSRV0049: WildFly Core 3.0.0.Alpha17-redhat-1 "Kenny" starting&#27;[0m
> [Host Controller] &#27;[0m&#27;[0m17:21:51,987 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/host=master/core-service=management/management-interface=native-interface' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.&#27;[0m
> [Host Controller] &#27;[0m&#27;[0m17:21:51,988 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/host=master/core-service=management/management-interface=http-interface' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.&#27;[0m
> [Host Controller] &#27;[0m&#27;[0m17:21:52,014 INFO [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0003: Creating http management service using network interface (management) port (9990) securePort (-1)&#27;[0m
> [Host Controller] &#27;[0m&#27;[0m17:21:52,028 INFO [org.jboss.as.patching] (MSC service thread 1-3) WFLYPAT0050: WildFly cumulative patch ID is: base, one-off patches include: none&#27;[0m
> [Host Controller] &#27;[0m&#27;[33m17:21:52,052 WARN [org.jboss.as.domain.http.api.undertow] (MSC service thread 1-2) WFLYDMHTTP0003: Unable to load console module for slot main, disabling console&#27;[0m
> [Host Controller] &#27;[33m&#27;[0m&#27;[0m17:21:52,057 INFO [org.jboss.as.remoting] (MSC service thread 1-3) WFLYRMT0001: Listening on 10.19.70.129:9999&#27;[0m
> [Host Controller] &#27;[0m&#27;[0m17:21:52,230 INFO [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0023: Starting server main-one&#27;[0m
> &#27;[0m17:21:52,275 INFO [org.jboss.as.process.Server:main-one.status] (ProcessController-threads - 3) WFLYPC0018: Starting process 'Server:main-one'
> &#27;[0m[Server:main-one] 17:21:53,100 INFO [org.jboss.modules] (main) JBoss Modules version 1.6.0.Beta3-redhat-1
> [Server:main-one] 17:21:53,538 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.7.Final-redhat-1
> [Server:main-one] 17:21:53,659 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Core 3.0.0.Alpha17-redhat-1 "Kenny" starting
> [Server:main-one] 17:21:53,731 INFO [org.xnio] (MSC service thread 1-3) XNIO version 3.4.3.Final-redhat-1
> [Server:main-one] 17:21:53,737 INFO [org.xnio.nio] (MSC service thread 1-3) XNIO NIO Implementation Version 3.4.3.Final-redhat-1
> [Server:main-one] 17:21:53,790 INFO [org.jboss.remoting] (MSC service thread 1-3) JBoss Remoting version 5.0.0.Beta12-redhat-1
> [Server:main-one] 17:21:53,802 INFO [org.wildfly.security] (MSC service thread 1-3) ELY00001: WildFly Elytron version 1.1.0.Beta18-redhat-1
> [Server:main-one] 17:21:54,060 INFO [org.jboss.as.domain.management] (MSC service thread 1-3) WFLYDM0136: Registered OpenSSL provider
> [Host Controller] &#27;[0m&#27;[0m17:21:54,419 INFO [org.jboss.as.host.controller] (management task-5) WFLYHC0021: Server [Server:main-one] connected using connection [Channel ID 02c651a4 (inbound) of Remoting connection a017baea to /10.19.64.169:37110 of endpoint "master:MANAGEMENT" <a7414457>]&#27;[0m
> [Host Controller] &#27;[0m&#27;[0m17:21:54,432 INFO [org.jboss.as.host.controller] (server-registration-threads - 1) WFLYHC0020: Registering server main-one&#27;[0m
> [Host Controller] &#27;[0m&#27;[0m17:21:54,440 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://10.19.70.129:9990/management&#27;[0m
> [Host Controller] &#27;[0m&#27;[0m17:21:54,441 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://10.19.70.129:9990&#27;[0m
> [Host Controller] &#27;[0m&#27;[0m17:21:54,441 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Core 3.0.0.Alpha17-redhat-1 "Kenny" (Host Controller) started in 2496ms - Started 50 of 50 services (13 services are lazy, passive or on-demand)&#27;[0m
> [Server:main-one] 17:21:54,679 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 13) WFLYIO001: Worker 'default' has auto-configured to 4 core threads with 32 task threads based on your 2 available processors
> INFO [org.jboss.as.test.integration.domain.management.util.DomainLifecycleUtil] ServerIdentity{name=main-one, host=master, server-group=main-server-group} status is starting
> [Server:main-one] 17:21:54,747 INFO [org.jboss.as.patching] (MSC service thread 1-3) WFLYPAT0050: WildFly cumulative patch ID is: base, one-off patches include: none
> [Server:main-one] 17:21:54,757 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "test-jmx-notifications-deployment.jar" (runtime-name: "test-jmx-notifications-deployment.jar")
> [Server:main-one] 17:21:54,810 WARN [org.jboss.as.dependency.private] (MSC service thread 1-3) WFLYSRV0018: Deployment "deployment.test-jmx-notifications-deployment.jar" is using a private module ("org.jboss.as.jmx:main") which may be changed or removed in future versions without notice.
> [Server:main-one] 17:21:54,810 WARN [org.jboss.as.dependency.private] (MSC service thread 1-3) WFLYSRV0018: Deployment "deployment.test-jmx-notifications-deployment.jar" is using a private module ("org.jboss.as.server:main") which may be changed or removed in future versions without notice.
> [Server:main-one] 17:21:54,811 WARN [org.jboss.as.dependency.private] (MSC service thread 1-3) WFLYSRV0018: Deployment "deployment.test-jmx-notifications-deployment.jar" is using a private module ("org.jboss.as.controller:main") which may be changed or removed in future versions without notice.
> [Server:main-one] 17:21:54,816 INFO [stdout] (MSC service thread 1-3) Properties found
> [Server:main-one] 17:21:54,839 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Deployed "test-jmx-notifications-deployment.jar" (runtime-name : "test-jmx-notifications-deployment.jar")
> [Server:main-one] 17:21:54,935 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Core 3.0.0.Alpha17-redhat-1 "Kenny" started in 2321ms - Started 67 of 84 services (26 services are lazy, passive or on-demand)
> [Server:main-one] 17:21:54,941 INFO [org.jboss.as.server] (ServerService Thread Pool -- 15) WFLYSRV0212: Resuming server
> {noformat}
> *Expected results:*
> No error
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JGRP-2152) ASYM_ENCRYPT failure on Wildfly 10.1.0
by Richard Achmatowicz (JIRA)
[ https://issues.jboss.org/browse/JGRP-2152?page=com.atlassian.jira.plugin.... ]
Richard Achmatowicz commented on JGRP-2152:
-------------------------------------------
I can't find any references to ENCRYPT in the testsuite, so probably
not. Copying Michal to see if there is any testing from QA which makes
use of JGroups authentication or encryption.
You have a configuration (asym_encrypt) which uses the same
configuration, so I assume that that sym_algorithm format used in the
test is supported.
It could be a problem with the forward slashes. I'll do a test myself to
see what is going on. Report back later today.
Richard
> ASYM_ENCRYPT failure on Wildfly 10.1.0
> --------------------------------------
>
> Key: JGRP-2152
> URL: https://issues.jboss.org/browse/JGRP-2152
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.6.10
> Reporter: Matt Wringe
> Assignee: Bela Ban
> Fix For: 4.0, 3.6.13
>
> Attachments: hawkular-metrics-1.log, hawkular-metrics-2.log, standalone.xml
>
>
> Using ASYM_ENCRYPT on Wildfly 10.1.0 seems to be broken.
> I am using the parameters for ASYM_ENCRYPT specified in http://www.jgroups.org/manual/index.html#Security
> Note: running with SYM_ENCRYPT doesn't cause any issues and it works fine with my setup. Its only ASYM_ENCRYPT which is currently failing.
> Note: running this on EAP fails in a similar manner.
> Eg:
> <protocol type="ASYM_ENCRYPT">
> <property name="encrypt_entire_message">true</property>
> <property name="sym_keylength">128</property>
> <property name="sym_algorithm">AES/ECB/PKCS5Padding</property>
> <property name="asym_keylength">512</property>
> <property name="asym_algorithm">RSA</property>
> </protocol>
> If I run a single instance, then I don't see any problems appear in the logs. Its when I start a second instance that I start to see errors about unrecognised ciphers and timeouts.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (ELY-870) AbstractAlgorithmParametersSpiImpl::engineInit is using wrong reference
by Zoran Regvart (JIRA)
Zoran Regvart created ELY-870:
---------------------------------
Summary: AbstractAlgorithmParametersSpiImpl::engineInit is using wrong reference
Key: ELY-870
URL: https://issues.jboss.org/browse/ELY-870
Project: WildFly Elytron
Issue Type: Bug
Components: Utils
Reporter: Zoran Regvart
Assignee: Darran Lofthouse
Priority: Minor
The {{AbstractAlgorithmParametersSpiImpl::engineInit(AlgorithmParameterSpec)}} to test the instance of the given {{AlgorithmParameterSpec}} is using the class's field instead of the given parameter.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months