June 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1825) [Guided Decision Table] Ability to change HIT policy in a decision table anytime

by Juliano Boesel Mohr (Jira)

[ https://issues.jboss.org/browse/DROOLS-1825?page=com.atlassian.jira.plugi... ] Juliano Boesel Mohr commented on DROOLS-1825: --------------------------------------------- [~tirelli] There are no comments on why this issue has been closed with a "Won't Do" resolution? Are there any plans to support this feature? Thank you. > [Guided Decision Table] Ability to change HIT policy in a decision table anytime > -------------------------------------------------------------------------------- > > Key: DROOLS-1825 > URL: https://issues.jboss.org/browse/DROOLS-1825 > Project: Drools > Issue Type: Enhancement > Components: Guided Decision Table Editor > Affects Versions: 7.1.0.Beta2 > Reporter: Ivo Bek > Assignee: Toni Rikkola > Priority: Critical > Labels: UX, UXTeam, drools-tools, verifier > Attachments: DROOLS-1825 (Parent Rule).png, DecisionTable1.png, DecisionTable2.png, GDTAnalysis(a)2x.png, GDTColumns(a)2x.png > > Original Estimate: 1 week > Remaining Estimate: 1 week > > Today, it's possible to set 1 of 5 HIT policies when we create a new guided decision table. However, the user might not know which HIT policy he/she should use at this early beginning. Therefore, it should be possible to set the policy to None when we create a new guided decision table and set the HIT policy later after we add columns and rows, fill in some data and see and decide based on the created table how the rules should behave using the HIT policy. > Thus, it should be possible to change HIT policy in a decision table anytime. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2353) Enabling ASYM_ENCRYPT#change_key_on_leave logs "unrecognized cipher; discarding message from X" during normal operation

by Bela Ban (Jira)

[ https://issues.jboss.org/browse/JGRP-2353?page=com.atlassian.jira.plugin.... ] Bela Ban resolved JGRP-2353. ---------------------------- Resolution: Done > Enabling ASYM_ENCRYPT#change_key_on_leave logs "unrecognized cipher; discarding message from X" during normal operation > ----------------------------------------------------------------------------------------------------------------------- > > Key: JGRP-2353 > URL: https://issues.jboss.org/browse/JGRP-2353 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.0.19 > Reporter: Radoslav Husar > Assignee: Bela Ban > Priority: Minor > Fix For: 4.1.1 > > > The problem is in design, when a message with out of date key is received, its dropped and retransmitted with the new key, however, logging the "WARN [org.jgroups.protocols.ASYM_ENCRYPT] (thread-3,null,null) Y: unrecognized cipher; discarding message from X". > Unless a better solution is implemented, the least we could do, is improve the message to indicate this is part of normal operation. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2353) Enabling ASYM_ENCRYPT#change_key_on_leave logs "unrecognized cipher; discarding message from X" during normal operation

by Bela Ban (Jira)

[ https://issues.jboss.org/browse/JGRP-2353?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-2353: --------------------------- Fix Version/s: 4.1.1 Priority: Minor (was: Major) > Enabling ASYM_ENCRYPT#change_key_on_leave logs "unrecognized cipher; discarding message from X" during normal operation > ----------------------------------------------------------------------------------------------------------------------- > > Key: JGRP-2353 > URL: https://issues.jboss.org/browse/JGRP-2353 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.0.19 > Reporter: Radoslav Husar > Assignee: Bela Ban > Priority: Minor > Fix For: 4.1.1 > > > The problem is in design, when a message with out of date key is received, its dropped and retransmitted with the new key, however, logging the "WARN [org.jgroups.protocols.ASYM_ENCRYPT] (thread-3,null,null) Y: unrecognized cipher; discarding message from X". > Unless a better solution is implemented, the least we could do, is improve the message to indicate this is part of normal operation. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11991) Applications that extend certain Hibernate classes should be updated to use type SharedSessionContractImplementor instead of SessionImplementor

by Scott Marlow (Jira)

[ https://issues.jboss.org/browse/WFLY-11991?page=com.atlassian.jira.plugin... ] Scott Marlow closed WFLY-11991. ------------------------------- > Applications that extend certain Hibernate classes should be updated to use type SharedSessionContractImplementor instead of SessionImplementor > ----------------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-11991 > URL: https://issues.jboss.org/browse/WFLY-11991 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > Priority: Major > Fix For: 17.0.0.Final > > Attachments: afterchange.zip, beforechange.zip > > > The idea is to transform any class method parameter of type org.hibernate.engine.spi.SessionImplementor, in user application, to instead use type org.hibernate.engine.spi.SharedSessionContractImplementor. > The above is done for any application class that has any of the following Hibernate classes as its super class: > {code} > org.hibernate.usertype.UserType > org.hibernate.usertype.CompositeUserType > org.hibernate.usertype.UserCollectionType > org.hibernate.usertype.UserVersionType > org.hibernate.type.Type > org.hibernate.type.SingleColumnType > org.hibernate.type.AbstractStandardBasicType > org.hibernate.type.ProcedureParameterExtractionAware > org.hibernate.type.ProcedureParameterNamedBinder > org.hibernate.type.VersionType > org.hibernate.collection.spi.PersistentCollection > {code} > The code change is required to handle application classes like: [https://github.com/simkam/wildfly/compare/hibernate_transformer]. > The test case change is adding an internalNullSafeGet method that should also be transformed to use the SharedSessionContractImplementor type but was not, which led to an application failure with code: > {code} > public Object nullSafeGet(ResultSet rs, String[] names, SessionImplementor session, Object owner) throws HibernateException, SQLException { > return internalNullSafeGet(rs, names, session, owner); > } > private Object internalNullSafeGet(ResultSet rs, String[] names, SessionImplementor session, Object owner) throws HibernateException, SQLException { > internalSessionImplementorUsingMethod(session); > session.isTransactionInProgress(); > int result = rs.getInt( names[0] ); > if ( rs.wasNull() ) return null; > return State.values()[result]; > } > } > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12163) [org.jgroups.protocols.SYM_ENCRYPT] rejected decryption of unicast message from non-member

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-12163?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-12163: ---------------------------------- Priority: Critical (was: Major) > [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.Beta1 > Reporter: Tommasso Borgato > Assignee: Paul Ferraro > Priority: Critical > > 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

1
0
0 / 0

[JBoss JIRA] (WFLY-12163) [org.jgroups.protocols.SYM_ENCRYPT] rejected decryption of unicast message from non-member

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-12163?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-12163: ---------------------------------- Affects Version/s: 17.0.0.Beta1 (was: 17.0.0.Final) > [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.Beta1 > 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

1
0
0 / 0

[JBoss JIRA] (WFLY-12169) Remove use of deprecated ServiceBuilder.addAliases(...) within Infinispan subsystem

by Paul Ferraro (Jira)

Paul Ferraro created WFLY-12169: ----------------------------------- Summary: Remove use of deprecated ServiceBuilder.addAliases(...) within Infinispan subsystem Key: WFLY-12169 URL: https://issues.jboss.org/browse/WFLY-12169 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 17.0.0.Final Reporter: Paul Ferraro Assignee: Paul Ferraro JBoss MSC 1.4.6.Final deprecates ServiceBuilder.addAliases(...). The Infinispan subsystem currently uses this method to support cache-container aliases. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3944) DMN Editor: Data type usability study

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3944?page=com.atlassian.jira.plugi... ] Elizabeth Clayton updated DROOLS-3944: -------------------------------------- Sprint: 2019 Week 23-25 > DMN Editor: Data type usability study > ------------------------------------- > > Key: DROOLS-3944 > URL: https://issues.jboss.org/browse/DROOLS-3944 > Project: Drools > Issue Type: Task > Components: DMN Editor > Environment: Version 7.4 > Reporter: Elizabeth Clayton > Assignee: Sarahjane Clark > Priority: Major > Labels: UX, UXTeam, Usability, drools-tools > > Lightweight usability study to test the ease of use in viewing, creating, editing and deleting data types, particularly structured data types. > GOALS: Access the Data Type editor in terms of productivity and usability. > * Ease of use when creating a complex type (concern: minimizing the mouse usage.) > * Ease of use when saving a basic data type (e.g. age: number) > * Discoverability of actions in the kebab menu, especially, insert nested, delete. > * Ease of use/accuracy: Type-ahead of the data type selector. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3944) DMN Editor: Data type usability study

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3944?page=com.atlassian.jira.plugi... ] Elizabeth Clayton updated DROOLS-3944: -------------------------------------- Sprint: (was: 2019 Week 23-25) > DMN Editor: Data type usability study > ------------------------------------- > > Key: DROOLS-3944 > URL: https://issues.jboss.org/browse/DROOLS-3944 > Project: Drools > Issue Type: Task > Components: DMN Editor > Environment: Version 7.4 > Reporter: Elizabeth Clayton > Assignee: Sarahjane Clark > Priority: Major > Labels: UX, UXTeam, Usability, drools-tools > > Lightweight usability study to test the ease of use in viewing, creating, editing and deleting data types, particularly structured data types. > GOALS: Access the Data Type editor in terms of productivity and usability. > * Ease of use when creating a complex type (concern: minimizing the mouse usage.) > * Ease of use when saving a basic data type (e.g. age: number) > * Discoverability of actions in the kebab menu, especially, insert nested, delete. > * Ease of use/accuracy: Type-ahead of the data type selector. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4127) Review current implementation of Data Types section.

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-4127?page=com.atlassian.jira.plugi... ] Elizabeth Clayton updated DROOLS-4127: -------------------------------------- Description: Preparatory work for a usability study to test the ease of use in viewing, creating, editing and deleting data types, particularly structured data types. * Review the current CICD implementation of the 7.x DMN editor, data types section. * Review documented usability concerns. > Review current implementation of Data Types section. > ----------------------------------------------------- > > Key: DROOLS-4127 > URL: https://issues.jboss.org/browse/DROOLS-4127 > Project: Drools > Issue Type: Sub-task > Reporter: Elizabeth Clayton > Assignee: Sarahjane Clark > Priority: Major > Labels: UX, UXTeam > > Preparatory work for a usability study to test the ease of use in viewing, creating, editing and deleting data types, particularly structured data types. > * Review the current CICD implementation of the 7.x DMN editor, data types section. > * Review documented usability concerns. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2019