[JBoss JIRA] (DROOLS-3625) [DMN Designer] Remove Stunners Explorer widget from the RHS dock
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-3625?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-3625:
-----------------------------------
Sprint: 2019 Week 23-25
> [DMN Designer] Remove Stunners Explorer widget from the RHS dock
> ----------------------------------------------------------------
>
> Key: DROOLS-3625
> URL: https://issues.jboss.org/browse/DROOLS-3625
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Affects Versions: 7.17.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Major
> Labels: drools-tools
>
> The DMN Editor has a "Decision Navigator" widget (in the LHS dock) that currently shows the content of the whole DRG however it will also become the DRD explorer too. This duplicates Stunner's _default_ Explorer widget in the RHS dock.
> The DMN Editor should have Stunner's _default_ widget removed.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (DROOLS-4123) Drools project build failure with kjar packaging starting from version 7.7
by Bekarys Kuspan (Jira)
[ https://issues.jboss.org/browse/DROOLS-4123?page=com.atlassian.jira.plugi... ]
Bekarys Kuspan updated DROOLS-4123:
-----------------------------------
Description: When I want to build a project using kjar packaging type, with drools versions higher than 7.7.0,by typing the command "mvn clean package" it throws an error message. However, for lower versions of drools, for example 7.6.0, build is successful. I tried all versions up to 7.22.0 (was: When I want to build a project using kjar packaging type, with drools versions higher than 7.7.0,by typing the command mvn clean package it throws an error message. However, for lower versions of drools, for example 7.6.0, build is successful. )
> Drools project build failure with kjar packaging starting from version 7.7
> --------------------------------------------------------------------------
>
> Key: DROOLS-4123
> URL: https://issues.jboss.org/browse/DROOLS-4123
> Project: Drools
> Issue Type: Bug
> Components: build
> Affects Versions: 7.7.0.Final, 7.22.0.Final
> Environment: ubuntu18.04
> Reporter: Bekarys Kuspan
> Assignee: Ant Stephenson
> Priority: Major
> Attachments: testProject.zip
>
>
> When I want to build a project using kjar packaging type, with drools versions higher than 7.7.0,by typing the command "mvn clean package" it throws an error message. However, for lower versions of drools, for example 7.6.0, build is successful. I tried all versions up to 7.22.0
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (DROOLS-4123) Drools project build failure with kjar packaging starting from version 7.7
by Bekarys Kuspan (Jira)
[ https://issues.jboss.org/browse/DROOLS-4123?page=com.atlassian.jira.plugi... ]
Bekarys Kuspan updated DROOLS-4123:
-----------------------------------
Affects Version/s: 7.22.0.Final
> Drools project build failure with kjar packaging starting from version 7.7
> --------------------------------------------------------------------------
>
> Key: DROOLS-4123
> URL: https://issues.jboss.org/browse/DROOLS-4123
> Project: Drools
> Issue Type: Bug
> Components: build
> Affects Versions: 7.7.0.Final, 7.22.0.Final
> Environment: ubuntu18.04
> Reporter: Bekarys Kuspan
> Assignee: Ant Stephenson
> Priority: Major
> Attachments: testProject.zip
>
>
> When I want to build a project using kjar packaging type, with drools versions higher than 7.7.0,by typing the command "mvn clean package" it throws an error message. However, for lower versions of drools, for example 7.6.0, build is successful. I tried all versions up to 7.22.0
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (DROOLS-4123) Drools project build failure with kjar packaging starting from version 7.7
by Bekarys Kuspan (Jira)
[ https://issues.jboss.org/browse/DROOLS-4123?page=com.atlassian.jira.plugi... ]
Bekarys Kuspan updated DROOLS-4123:
-----------------------------------
Description: When I want to build a project using kjar packaging type, with drools versions higher than 7.7.0,by typing the command mvn clean package it throws an error message. However, for lower versions of drools, for example 7.6.0, build is successful. (was: When I want to build a project using kjar packaging type, with drools versions higher than 7.7.0,by typing the command mvn clean package it throws an error message. However, for lower versions of drools, for example 7.6.0, build is successful.
I tried to change versions of drools, so I stopped at 7.6.0. It is highest successful version. Also, I changed type of packaging to jar and maven successfully built the project for all versions)
> Drools project build failure with kjar packaging starting from version 7.7
> --------------------------------------------------------------------------
>
> Key: DROOLS-4123
> URL: https://issues.jboss.org/browse/DROOLS-4123
> Project: Drools
> Issue Type: Bug
> Components: build
> Affects Versions: 7.7.0.Final
> Environment: ubuntu18.04
> Reporter: Bekarys Kuspan
> Assignee: Ant Stephenson
> Priority: Major
> Attachments: testProject.zip
>
>
> When I want to build a project using kjar packaging type, with drools versions higher than 7.7.0,by typing the command mvn clean package it throws an error message. However, for lower versions of drools, for example 7.6.0, build is successful.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (DROOLS-4123) Drools project build failure with kjar packaging starting from version 7.7
by Bekarys Kuspan (Jira)
[ https://issues.jboss.org/browse/DROOLS-4123?page=com.atlassian.jira.plugi... ]
Bekarys Kuspan updated DROOLS-4123:
-----------------------------------
Environment: ubuntu18.04 (was: ubunut 18.04)
> Drools project build failure with kjar packaging starting from version 7.7
> --------------------------------------------------------------------------
>
> Key: DROOLS-4123
> URL: https://issues.jboss.org/browse/DROOLS-4123
> Project: Drools
> Issue Type: Bug
> Components: build
> Affects Versions: 7.7.0.Final
> Environment: ubuntu18.04
> Reporter: Bekarys Kuspan
> Assignee: Ant Stephenson
> Priority: Major
> Attachments: testProject.zip
>
>
> When I want to build a project using kjar packaging type, with drools versions higher than 7.7.0,by typing the command mvn clean package it throws an error message. However, for lower versions of drools, for example 7.6.0, build is successful.
> I tried to change versions of drools, so I stopped at 7.6.0. It is highest successful version. Also, I changed type of packaging to jar and maven successfully built the project for all versions
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (DROOLS-4123) Drools project build failure with kjar packaging starting from version 7.7
by Bekarys Kuspan (Jira)
Bekarys Kuspan created DROOLS-4123:
--------------------------------------
Summary: Drools project build failure with kjar packaging starting from version 7.7
Key: DROOLS-4123
URL: https://issues.jboss.org/browse/DROOLS-4123
Project: Drools
Issue Type: Bug
Components: build
Affects Versions: 7.7.0.Final
Environment: ubunut 18.04
Reporter: Bekarys Kuspan
Assignee: Ant Stephenson
Attachments: testProject.zip
When I want to build a project using kjar packaging type, with drools versions higher than 7.7.0,by typing the command mvn clean package it throws an error message. However, for lower versions of drools, for example 7.6.0, build is successful.
I tried to change versions of drools, so I stopped at 7.6.0. It is highest successful version. Also, I changed type of packaging to jar and maven successfully built the project for all versions
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (WFCORE-4502) Unify line-endings of bat and ps1 scripts (regression against WF15)
by Radoslav Husar (Jira)
[ https://issues.jboss.org/browse/WFCORE-4502?page=com.atlassian.jira.plugi... ]
Radoslav Husar updated WFCORE-4502:
-----------------------------------
Summary: Unify line-endings of bat and ps1 scripts (regression against WF15) (was: Unify line-endings of bat scripts (regression against WF15))
> Unify line-endings of bat and ps1 scripts (regression against WF15)
> -------------------------------------------------------------------
>
> Key: WFCORE-4502
> URL: https://issues.jboss.org/browse/WFCORE-4502
> Project: WildFly Core
> Issue Type: Bug
> Components: Scripts
> Affects Versions: 9.0.0.Beta7
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Critical
>
> Line-endings of bat scripts should be unified. This is regression against WF15.
> Some files in WF16 uses CRLF, another LF only. We need to clarify the recommended line ending and use this line ending in all Windows scripts.
> WF16:
> {noformat}
> $ find | grep bat$ | xargs file
> ./wsprovide.bat: DOS batch file, ASCII text, with CRLF line terminators
> ./jboss-cli.bat: DOS batch file, ASCII text
> ./elytron-tool.bat: DOS batch file, ASCII text
> ./domain.bat: DOS batch file, ASCII text, with CRLF line terminators
> ./wsconsume.bat: DOS batch file, ASCII text, with CRLF line terminators
> ./standalone.bat: DOS batch file, ASCII text, with CRLF line terminators
> ./vault.bat: DOS batch file, ASCII text, with CRLF line terminators
> ./domain.conf.bat: ASCII text, with CRLF line terminators
> ./common.bat: DOS batch file, ASCII text, with CRLF line terminators
> ./jdr.bat: DOS batch file, ASCII text
> ./jconsole.bat: DOS batch file, ASCII text
> ./appclient.bat: DOS batch file, ASCII text, with CRLF line terminators
> ./appclient.conf.bat: ASCII text, with CRLF line terminators
> ./standalone.conf.bat: ASCII text, with CRLF line terminators
> ./add-user.bat: DOS batch file, ASCII text
> $
> {noformat}
> WF15:
> {noformat}
> $ find | grep bat$ | xargs file
> ./wsprovide.bat: DOS batch file, ASCII text, with CRLF line terminators
> ./jboss-cli.bat: DOS batch file, ASCII text, with CRLF line terminators
> ./elytron-tool.bat: DOS batch file, ASCII text, with CRLF line terminators
> ./domain.bat: DOS batch file, ASCII text, with CRLF line terminators
> ./wsconsume.bat: DOS batch file, ASCII text, with CRLF line terminators
> ./standalone.bat: DOS batch file, ASCII text, with CRLF line terminators
> ./vault.bat: DOS batch file, ASCII text, with CRLF line terminators
> ./domain.conf.bat: ASCII text, with CRLF line terminators
> ./common.bat: DOS batch file, ASCII text, with CRLF line terminators
> ./jdr.bat: DOS batch file, ASCII text, with CRLF line terminators
> ./jconsole.bat: DOS batch file, ASCII text, with CRLF line terminators
> ./appclient.bat: DOS batch file, ASCII text, with CRLF line terminators
> ./appclient.conf.bat: ASCII text, with CRLF line terminators
> ./standalone.conf.bat: ASCII text, with CRLF line terminators
> ./add-user.bat: DOS batch file, ASCII text, with CRLF line terminators
> $
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (WFLY-12163) [org.jgroups.protocols.SYM_ENCRYPT] rejected decryption of unicast message from non-member
by Tommasso Borgato (Jira)
[ https://issues.jboss.org/browse/WFLY-12163?page=com.atlassian.jira.plugin... ]
Tommasso Borgato updated WFLY-12163:
------------------------------------
Description:
The error is observed in EAP Clustering fail-over tests where the communication at the JGroups level is symmetrically encrypted .
The error causes sampling errors on the client (about 3000) and an overall 0.65% fail rate.
Basically, right after the deployment when the cache starts, we observe a big number of the following errors in the logs:
{noformat}
2019-05-30 12:19:34,445 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 82) WFLYUT0021: Registered web context: '/clusterbench-passivating' for server 'default-server'
2019-05-30 12:19:34,592 INFO [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0010: Deployed "clusterbench-ee8.ear" (runtime-name : "clusterbench-ee8.ear")
2019-05-30 12:20:21,180 ERROR [org.jgroups.protocols.SYM_ENCRYPT] (thread-4,null,null) wildfly1: rejected decryption of unicast message from non-member wildfly2
2019-05-30 12:20:21,182 WARN [org.jgroups.protocols.SYM_ENCRYPT] (thread-4,null,null) wildfly1: unrecognized cipher; discarding message from wildfly2
{noformat}
Complete logs:
* [eap-7.x-clustering-http-session-encrypt-sym/27|https://eap-qe-jenkins.rhe...]
* [eap-7.x-clustering-http-session-encrypt-sym/28|https://eap-qe-jenkins.rhe...]
* [eap-7.x-clustering-http-session-encrypt-sym/29|https://eap-qe-jenkins.rhe...]
This is the setup for every node in the cluster that can be used to reproduce the issue:
{noformat}
embed-server --server-config=standalone-ha.xml
/subsystem=infinispan/cache-container=web/distributed-cache=testDist:add()
/subsystem=infinispan/cache-container=web/distributed-cache=testDist/component=locking:write-attribute(name=isolation, value=REPEATABLE_READ)
/subsystem=infinispan/cache-container=web/distributed-cache=testDist/component=transaction:write-attribute(name=mode, value=BATCH)
/subsystem=infinispan/cache-container=web:write-attribute(name=default-cache, value=testDist)
/subsystem=jgroups/channel=ee:write-attribute(name=stack,value=tcp)
batch
/subsystem=jgroups/stack=udp/protocol=AUTH:add(add-index=8)
/subsystem=jgroups/stack=udp/protocol=AUTH/token=digest:add(algorithm=SHA-512, shared-secret-reference={clear-text=123PIPPOBAUDO})
/subsystem=jgroups/stack=tcp/protocol=AUTH:add(add-index=8)
/subsystem=jgroups/stack=tcp/protocol=AUTH/token=digest:add(algorithm=SHA-512, shared-secret-reference={clear-text=123PIPPOBAUDO})
run-batch
/subsystem=elytron/key-store=jgroups-keystore:add(path=jgroups.keystore,credential-reference={clear-text=123PIPPOBAUDO},type=JCEKS,relative-to=jboss.server.config.dir)
/subsystem=jgroups/stack=udp/protocol=SYM_ENCRYPT:add(add-index=5,key-store=jgroups-keystore,key-alias=mykey,key-credential-reference={clear-text=123PIPPOBAUDO})
/subsystem=jgroups/stack=tcp/protocol=SYM_ENCRYPT:add(add-index=5,key-store=jgroups-keystore,key-alias=mykey,key-credential-reference={clear-text=123PIPPOBAUDO})
{noformat}
This is the command used to generate the key-store referenced in the cli script above:
{noformat}
cd $JBOSS_HOME/standalone/configuration/
java -cp $(find /tmp/tests-clustering/jboss-eap-1/modules -name "jgroups-[0-9]*.jar") org.jgroups.demos.KeyStoreGenerator --alg AES --size 128 --storeName jgroups.keystore --storepass 123PIPPOBAUDO --alias mykey
{noformat}
was:
The error is observed in EAP Clustering fail-over tests where the communication at the JGroups level is symmetrically encrypted .
The error causes sampling errors on the client and an overall 0.65% fail rate.
Basically, right after the deployment when the cache starts, we observe a big number of the following errors in the logs:
{noformat}
2019-05-30 12:19:34,445 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 82) WFLYUT0021: Registered web context: '/clusterbench-passivating' for server 'default-server'
2019-05-30 12:19:34,592 INFO [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0010: Deployed "clusterbench-ee8.ear" (runtime-name : "clusterbench-ee8.ear")
2019-05-30 12:20:21,180 ERROR [org.jgroups.protocols.SYM_ENCRYPT] (thread-4,null,null) wildfly1: rejected decryption of unicast message from non-member wildfly2
2019-05-30 12:20:21,182 WARN [org.jgroups.protocols.SYM_ENCRYPT] (thread-4,null,null) wildfly1: unrecognized cipher; discarding message from wildfly2
{noformat}
Complete logs:
* [eap-7.x-clustering-http-session-encrypt-sym/27|https://eap-qe-jenkins.rhe...]
* [eap-7.x-clustering-http-session-encrypt-sym/28|https://eap-qe-jenkins.rhe...]
* [eap-7.x-clustering-http-session-encrypt-sym/29|https://eap-qe-jenkins.rhe...]
This is the setup for every node in the cluster that can be used to reproduce the issue:
{noformat}
embed-server --server-config=standalone-ha.xml
/subsystem=infinispan/cache-container=web/distributed-cache=testDist:add()
/subsystem=infinispan/cache-container=web/distributed-cache=testDist/component=locking:write-attribute(name=isolation, value=REPEATABLE_READ)
/subsystem=infinispan/cache-container=web/distributed-cache=testDist/component=transaction:write-attribute(name=mode, value=BATCH)
/subsystem=infinispan/cache-container=web:write-attribute(name=default-cache, value=testDist)
/subsystem=jgroups/channel=ee:write-attribute(name=stack,value=tcp)
batch
/subsystem=jgroups/stack=udp/protocol=AUTH:add(add-index=8)
/subsystem=jgroups/stack=udp/protocol=AUTH/token=digest:add(algorithm=SHA-512, shared-secret-reference={clear-text=123PIPPOBAUDO})
/subsystem=jgroups/stack=tcp/protocol=AUTH:add(add-index=8)
/subsystem=jgroups/stack=tcp/protocol=AUTH/token=digest:add(algorithm=SHA-512, shared-secret-reference={clear-text=123PIPPOBAUDO})
run-batch
/subsystem=elytron/key-store=jgroups-keystore:add(path=jgroups.keystore,credential-reference={clear-text=123PIPPOBAUDO},type=JCEKS,relative-to=jboss.server.config.dir)
/subsystem=jgroups/stack=udp/protocol=SYM_ENCRYPT:add(add-index=5,key-store=jgroups-keystore,key-alias=mykey,key-credential-reference={clear-text=123PIPPOBAUDO})
/subsystem=jgroups/stack=tcp/protocol=SYM_ENCRYPT:add(add-index=5,key-store=jgroups-keystore,key-alias=mykey,key-credential-reference={clear-text=123PIPPOBAUDO})
{noformat}
This is the command used to generate the key-store referenced in the cli script above:
{noformat}
cd $JBOSS_HOME/standalone/configuration/
java -cp $(find /tmp/tests-clustering/jboss-eap-1/modules -name "jgroups-[0-9]*.jar") org.jgroups.demos.KeyStoreGenerator --alg AES --size 128 --storeName jgroups.keystore --storepass 123PIPPOBAUDO --alias mykey
{noformat}
> [org.jgroups.protocols.SYM_ENCRYPT] rejected decryption of unicast message from non-member
> ------------------------------------------------------------------------------------------
>
> Key: WFLY-12163
> URL: https://issues.jboss.org/browse/WFLY-12163
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 17.0.0.Final
> Reporter: Tommasso Borgato
> Assignee: Paul Ferraro
> Priority: Major
>
> The error is observed in EAP Clustering fail-over tests where the communication at the JGroups level is symmetrically encrypted .
> The error causes sampling errors on the client (about 3000) and an overall 0.65% fail rate.
> Basically, right after the deployment when the cache starts, we observe a big number of the following errors in the logs:
> {noformat}
> 2019-05-30 12:19:34,445 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 82) WFLYUT0021: Registered web context: '/clusterbench-passivating' for server 'default-server'
> 2019-05-30 12:19:34,592 INFO [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0010: Deployed "clusterbench-ee8.ear" (runtime-name : "clusterbench-ee8.ear")
> 2019-05-30 12:20:21,180 ERROR [org.jgroups.protocols.SYM_ENCRYPT] (thread-4,null,null) wildfly1: rejected decryption of unicast message from non-member wildfly2
> 2019-05-30 12:20:21,182 WARN [org.jgroups.protocols.SYM_ENCRYPT] (thread-4,null,null) wildfly1: unrecognized cipher; discarding message from wildfly2
> {noformat}
> Complete logs:
> * [eap-7.x-clustering-http-session-encrypt-sym/27|https://eap-qe-jenkins.rhe...]
> * [eap-7.x-clustering-http-session-encrypt-sym/28|https://eap-qe-jenkins.rhe...]
> * [eap-7.x-clustering-http-session-encrypt-sym/29|https://eap-qe-jenkins.rhe...]
> This is the setup for every node in the cluster that can be used to reproduce the issue:
> {noformat}
> embed-server --server-config=standalone-ha.xml
> /subsystem=infinispan/cache-container=web/distributed-cache=testDist:add()
> /subsystem=infinispan/cache-container=web/distributed-cache=testDist/component=locking:write-attribute(name=isolation, value=REPEATABLE_READ)
> /subsystem=infinispan/cache-container=web/distributed-cache=testDist/component=transaction:write-attribute(name=mode, value=BATCH)
> /subsystem=infinispan/cache-container=web:write-attribute(name=default-cache, value=testDist)
> /subsystem=jgroups/channel=ee:write-attribute(name=stack,value=tcp)
> batch
> /subsystem=jgroups/stack=udp/protocol=AUTH:add(add-index=8)
> /subsystem=jgroups/stack=udp/protocol=AUTH/token=digest:add(algorithm=SHA-512, shared-secret-reference={clear-text=123PIPPOBAUDO})
> /subsystem=jgroups/stack=tcp/protocol=AUTH:add(add-index=8)
> /subsystem=jgroups/stack=tcp/protocol=AUTH/token=digest:add(algorithm=SHA-512, shared-secret-reference={clear-text=123PIPPOBAUDO})
> run-batch
> /subsystem=elytron/key-store=jgroups-keystore:add(path=jgroups.keystore,credential-reference={clear-text=123PIPPOBAUDO},type=JCEKS,relative-to=jboss.server.config.dir)
> /subsystem=jgroups/stack=udp/protocol=SYM_ENCRYPT:add(add-index=5,key-store=jgroups-keystore,key-alias=mykey,key-credential-reference={clear-text=123PIPPOBAUDO})
> /subsystem=jgroups/stack=tcp/protocol=SYM_ENCRYPT:add(add-index=5,key-store=jgroups-keystore,key-alias=mykey,key-credential-reference={clear-text=123PIPPOBAUDO})
> {noformat}
> This is the command used to generate the key-store referenced in the cli script above:
> {noformat}
> cd $JBOSS_HOME/standalone/configuration/
> java -cp $(find /tmp/tests-clustering/jboss-eap-1/modules -name "jgroups-[0-9]*.jar") org.jgroups.demos.KeyStoreGenerator --alg AES --size 128 --storeName jgroups.keystore --storepass 123PIPPOBAUDO --alias mykey
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (WFLY-12163) [org.jgroups.protocols.SYM_ENCRYPT] rejected decryption of unicast message from non-member
by Tommasso Borgato (Jira)
[ https://issues.jboss.org/browse/WFLY-12163?page=com.atlassian.jira.plugin... ]
Tommasso Borgato updated WFLY-12163:
------------------------------------
Description:
The error is observed in EAP Clustering fail-over tests where the communication at the JGroups level is symmetrically encrypted .
The error causes sampling errors on the client and an overall 0.65% fail rate.
Basically, right after the deployment when the cache starts, we observe a big number of the following errors in the logs:
{noformat}
2019-05-30 12:19:34,445 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 82) WFLYUT0021: Registered web context: '/clusterbench-passivating' for server 'default-server'
2019-05-30 12:19:34,592 INFO [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0010: Deployed "clusterbench-ee8.ear" (runtime-name : "clusterbench-ee8.ear")
2019-05-30 12:20:21,180 ERROR [org.jgroups.protocols.SYM_ENCRYPT] (thread-4,null,null) wildfly1: rejected decryption of unicast message from non-member wildfly2
2019-05-30 12:20:21,182 WARN [org.jgroups.protocols.SYM_ENCRYPT] (thread-4,null,null) wildfly1: unrecognized cipher; discarding message from wildfly2
{noformat}
Complete logs:
* [eap-7.x-clustering-http-session-encrypt-sym/27|https://eap-qe-jenkins.rhe...]
* [eap-7.x-clustering-http-session-encrypt-sym/28|https://eap-qe-jenkins.rhe...]
* [eap-7.x-clustering-http-session-encrypt-sym/29|https://eap-qe-jenkins.rhe...]
This is the setup for every node in the cluster that can be used to reproduce the issue:
{noformat}
embed-server --server-config=standalone-ha.xml
/subsystem=infinispan/cache-container=web/distributed-cache=testDist:add()
/subsystem=infinispan/cache-container=web/distributed-cache=testDist/component=locking:write-attribute(name=isolation, value=REPEATABLE_READ)
/subsystem=infinispan/cache-container=web/distributed-cache=testDist/component=transaction:write-attribute(name=mode, value=BATCH)
/subsystem=infinispan/cache-container=web:write-attribute(name=default-cache, value=testDist)
/subsystem=jgroups/channel=ee:write-attribute(name=stack,value=tcp)
batch
/subsystem=jgroups/stack=udp/protocol=AUTH:add(add-index=8)
/subsystem=jgroups/stack=udp/protocol=AUTH/token=digest:add(algorithm=SHA-512, shared-secret-reference={clear-text=123PIPPOBAUDO})
/subsystem=jgroups/stack=tcp/protocol=AUTH:add(add-index=8)
/subsystem=jgroups/stack=tcp/protocol=AUTH/token=digest:add(algorithm=SHA-512, shared-secret-reference={clear-text=123PIPPOBAUDO})
run-batch
/subsystem=elytron/key-store=jgroups-keystore:add(path=jgroups.keystore,credential-reference={clear-text=123PIPPOBAUDO},type=JCEKS,relative-to=jboss.server.config.dir)
/subsystem=jgroups/stack=udp/protocol=SYM_ENCRYPT:add(add-index=5,key-store=jgroups-keystore,key-alias=mykey,key-credential-reference={clear-text=123PIPPOBAUDO})
/subsystem=jgroups/stack=tcp/protocol=SYM_ENCRYPT:add(add-index=5,key-store=jgroups-keystore,key-alias=mykey,key-credential-reference={clear-text=123PIPPOBAUDO})
{noformat}
This is the command used to generate the key-store referenced in the cli script above:
{noformat}
cd $JBOSS_HOME/standalone/configuration/
java -cp $(find /tmp/tests-clustering/jboss-eap-1/modules -name "jgroups-[0-9]*.jar") org.jgroups.demos.KeyStoreGenerator --alg AES --size 128 --storeName jgroups.keystore --storepass 123PIPPOBAUDO --alias mykey
{noformat}
was:
The error is present in EAP Clustering fail-over tests where the communication at the JGroups level is symmetrically encrypted .
The error causes sampling errors on the client and an overall 0.65% fail rate.
Basically, right after the deployment when the cache starts, we observe a big number of the following errors in the logs:
{noformat}
2019-05-30 12:19:34,445 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 82) WFLYUT0021: Registered web context: '/clusterbench-passivating' for server 'default-server'
2019-05-30 12:19:34,592 INFO [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0010: Deployed "clusterbench-ee8.ear" (runtime-name : "clusterbench-ee8.ear")
2019-05-30 12:20:21,180 ERROR [org.jgroups.protocols.SYM_ENCRYPT] (thread-4,null,null) wildfly1: rejected decryption of unicast message from non-member wildfly2
2019-05-30 12:20:21,182 WARN [org.jgroups.protocols.SYM_ENCRYPT] (thread-4,null,null) wildfly1: unrecognized cipher; discarding message from wildfly2
{noformat}
Complete logs:
* [eap-7.x-clustering-http-session-encrypt-sym/27|https://eap-qe-jenkins.rhe...]
* [eap-7.x-clustering-http-session-encrypt-sym/28|https://eap-qe-jenkins.rhe...]
* [eap-7.x-clustering-http-session-encrypt-sym/29|https://eap-qe-jenkins.rhe...]
This is the setup for every node in the cluster that can be used to reproduce the issue:
{noformat}
embed-server --server-config=standalone-ha.xml
/subsystem=infinispan/cache-container=web/distributed-cache=testDist:add()
/subsystem=infinispan/cache-container=web/distributed-cache=testDist/component=locking:write-attribute(name=isolation, value=REPEATABLE_READ)
/subsystem=infinispan/cache-container=web/distributed-cache=testDist/component=transaction:write-attribute(name=mode, value=BATCH)
/subsystem=infinispan/cache-container=web:write-attribute(name=default-cache, value=testDist)
/subsystem=jgroups/channel=ee:write-attribute(name=stack,value=tcp)
batch
/subsystem=jgroups/stack=udp/protocol=AUTH:add(add-index=8)
/subsystem=jgroups/stack=udp/protocol=AUTH/token=digest:add(algorithm=SHA-512, shared-secret-reference={clear-text=123PIPPOBAUDO})
/subsystem=jgroups/stack=tcp/protocol=AUTH:add(add-index=8)
/subsystem=jgroups/stack=tcp/protocol=AUTH/token=digest:add(algorithm=SHA-512, shared-secret-reference={clear-text=123PIPPOBAUDO})
run-batch
/subsystem=elytron/key-store=jgroups-keystore:add(path=jgroups.keystore,credential-reference={clear-text=123PIPPOBAUDO},type=JCEKS,relative-to=jboss.server.config.dir)
/subsystem=jgroups/stack=udp/protocol=SYM_ENCRYPT:add(add-index=5,key-store=jgroups-keystore,key-alias=mykey,key-credential-reference={clear-text=123PIPPOBAUDO})
/subsystem=jgroups/stack=tcp/protocol=SYM_ENCRYPT:add(add-index=5,key-store=jgroups-keystore,key-alias=mykey,key-credential-reference={clear-text=123PIPPOBAUDO})
{noformat}
This is the command used to generate the key-store referenced in the cli script above:
{noformat}
cd $JBOSS_HOME/standalone/configuration/
java -cp $(find /tmp/tests-clustering/jboss-eap-1/modules -name "jgroups-[0-9]*.jar") org.jgroups.demos.KeyStoreGenerator --alg AES --size 128 --storeName jgroups.keystore --storepass 123PIPPOBAUDO --alias mykey
{noformat}
> [org.jgroups.protocols.SYM_ENCRYPT] rejected decryption of unicast message from non-member
> ------------------------------------------------------------------------------------------
>
> Key: WFLY-12163
> URL: https://issues.jboss.org/browse/WFLY-12163
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 17.0.0.Final
> Reporter: Tommasso Borgato
> Assignee: Paul Ferraro
> Priority: Major
>
> The error is observed in EAP Clustering fail-over tests where the communication at the JGroups level is symmetrically encrypted .
> The error causes sampling errors on the client and an overall 0.65% fail rate.
> Basically, right after the deployment when the cache starts, we observe a big number of the following errors in the logs:
> {noformat}
> 2019-05-30 12:19:34,445 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 82) WFLYUT0021: Registered web context: '/clusterbench-passivating' for server 'default-server'
> 2019-05-30 12:19:34,592 INFO [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0010: Deployed "clusterbench-ee8.ear" (runtime-name : "clusterbench-ee8.ear")
> 2019-05-30 12:20:21,180 ERROR [org.jgroups.protocols.SYM_ENCRYPT] (thread-4,null,null) wildfly1: rejected decryption of unicast message from non-member wildfly2
> 2019-05-30 12:20:21,182 WARN [org.jgroups.protocols.SYM_ENCRYPT] (thread-4,null,null) wildfly1: unrecognized cipher; discarding message from wildfly2
> {noformat}
> Complete logs:
> * [eap-7.x-clustering-http-session-encrypt-sym/27|https://eap-qe-jenkins.rhe...]
> * [eap-7.x-clustering-http-session-encrypt-sym/28|https://eap-qe-jenkins.rhe...]
> * [eap-7.x-clustering-http-session-encrypt-sym/29|https://eap-qe-jenkins.rhe...]
> This is the setup for every node in the cluster that can be used to reproduce the issue:
> {noformat}
> embed-server --server-config=standalone-ha.xml
> /subsystem=infinispan/cache-container=web/distributed-cache=testDist:add()
> /subsystem=infinispan/cache-container=web/distributed-cache=testDist/component=locking:write-attribute(name=isolation, value=REPEATABLE_READ)
> /subsystem=infinispan/cache-container=web/distributed-cache=testDist/component=transaction:write-attribute(name=mode, value=BATCH)
> /subsystem=infinispan/cache-container=web:write-attribute(name=default-cache, value=testDist)
> /subsystem=jgroups/channel=ee:write-attribute(name=stack,value=tcp)
> batch
> /subsystem=jgroups/stack=udp/protocol=AUTH:add(add-index=8)
> /subsystem=jgroups/stack=udp/protocol=AUTH/token=digest:add(algorithm=SHA-512, shared-secret-reference={clear-text=123PIPPOBAUDO})
> /subsystem=jgroups/stack=tcp/protocol=AUTH:add(add-index=8)
> /subsystem=jgroups/stack=tcp/protocol=AUTH/token=digest:add(algorithm=SHA-512, shared-secret-reference={clear-text=123PIPPOBAUDO})
> run-batch
> /subsystem=elytron/key-store=jgroups-keystore:add(path=jgroups.keystore,credential-reference={clear-text=123PIPPOBAUDO},type=JCEKS,relative-to=jboss.server.config.dir)
> /subsystem=jgroups/stack=udp/protocol=SYM_ENCRYPT:add(add-index=5,key-store=jgroups-keystore,key-alias=mykey,key-credential-reference={clear-text=123PIPPOBAUDO})
> /subsystem=jgroups/stack=tcp/protocol=SYM_ENCRYPT:add(add-index=5,key-store=jgroups-keystore,key-alias=mykey,key-credential-reference={clear-text=123PIPPOBAUDO})
> {noformat}
> This is the command used to generate the key-store referenced in the cli script above:
> {noformat}
> cd $JBOSS_HOME/standalone/configuration/
> java -cp $(find /tmp/tests-clustering/jboss-eap-1/modules -name "jgroups-[0-9]*.jar") org.jgroups.demos.KeyStoreGenerator --alg AES --size 128 --storeName jgroups.keystore --storepass 123PIPPOBAUDO --alias mykey
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months