July 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2674) Save, reload and open a scenario

by Juraj Soltes (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2674?page=com.atlassian.jira.plugi... ] Juraj Soltes updated DROOLS-2674: --------------------------------- Description: As a business analyst I want to save a scenario so that all the data I fill in are stored and can be reloaded. Including opening non-empty file (needs marshalling). was:As a business analyst I want to save a scenario so that all the data I fill in are stored and can be reloaded. > Save, reload and open a scenario > -------------------------------- > > Key: DROOLS-2674 > URL: https://issues.jboss.org/browse/DROOLS-2674 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Juraj Soltes > Assignee: Daniele Zonca > > As a business analyst I want to save a scenario so that all the data I fill in are stored and can be reloaded. > Including opening non-empty file (needs marshalling). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2673) Open a simulation test scenario

by Juraj Soltes (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2673?page=com.atlassian.jira.plugi... ] Juraj Soltes deleted DROOLS-2673: --------------------------------- > Open a simulation test scenario > ------------------------------- > > Key: DROOLS-2673 > URL: https://issues.jboss.org/browse/DROOLS-2673 > Project: Drools > Issue Type: Task > Reporter: Toni Rikkola > Assignee: Daniele Zonca > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2674) Save, reload and open a scenario

by Juraj Soltes (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2674?page=com.atlassian.jira.plugi... ] Juraj Soltes updated DROOLS-2674: --------------------------------- Summary: Save, reload and open a scenario (was: Save and reload a scenario) > Save, reload and open a scenario > -------------------------------- > > Key: DROOLS-2674 > URL: https://issues.jboss.org/browse/DROOLS-2674 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Juraj Soltes > Assignee: Daniele Zonca > > As a business analyst I want to save a scenario so that all the data I fill in are stored and can be reloaded. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2674) Save and reload a scenario

by Juraj Soltes (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2674?page=com.atlassian.jira.plugi... ] Juraj Soltes updated DROOLS-2674: --------------------------------- Story Points: 3 > Save and reload a scenario > -------------------------- > > Key: DROOLS-2674 > URL: https://issues.jboss.org/browse/DROOLS-2674 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Juraj Soltes > Assignee: Daniele Zonca > > As a business analyst I want to save a scenario so that all the data I fill in are stored and can be reloaded. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2227) Use of AUTH does not result in a SecurityException, but instead nodes create separate clusters with the same name

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2227?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-2227: --------------------------- Fix Version/s: 4.0.13 (was: 4.0.12) > Use of AUTH does not result in a SecurityException, but instead nodes create separate clusters with the same name > ----------------------------------------------------------------------------------------------------------------- > > Key: JGRP-2227 > URL: https://issues.jboss.org/browse/JGRP-2227 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.0.6 > Reporter: Robert Cernak > Assignee: Bela Ban > Fix For: 4.0.13 > > Attachments: jgroupsDoesNotThrowSecurityExceptionWithJgroups4012.zip, jgroupsLogs.zip, traceLogs.zip > > > I implemented method org.jgroups.auth.AuthToken#authenticate(AuthToken token, Message msg) in my class and its body contained only one line: return false; > In this way authentication should be false and I should get SecurityException. > When I started joining of nodes together to form a cluster, instead of getting SecurityException, nodes formed 2 different clusters with the same name. > I am sure method was evaluated, since I tried to run it also with breakpoint, which was triggered during joining process. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2279) Error during ASYM_ENCRYPT-----exception occurred decrypting messagejavax.crypto.BadPaddingException: Given final block not properly padded

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2279?page=com.atlassian.jira.plugin.... ] Bela Ban resolved JGRP-2279. ---------------------------- Resolution: Cannot Reproduce Please re-open if you can reproduce the issue > Error during ASYM_ENCRYPT-----exception occurred decrypting messagejavax.crypto.BadPaddingException: Given final block not properly padded > ------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JGRP-2279 > URL: https://issues.jboss.org/browse/JGRP-2279 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.0.1 > Environment: OS:Red Hat > JDK:1.8 > Reporter: George Jiang > Assignee: Bela Ban > Priority: Critical > Fix For: 4.0.13 > > Attachments: asym-ssl2.xml, jgroups-protocol.xml > > > *asym parameters:* > <ASYM_ENCRYPT encrypt_entire_message="true" > sign_msgs="true" > sym_keylength="128" > sym_algorithm="AES/ECB/PKCS5Padding" > asym_keylength="2048" > asym_algorithm="RSA" > change_key_on_leave="true"/> > *Throws the following error:* > 2018-05-23T03:11:53,891 +2903450778 [jgroups--12467,-1491537117,1] ERROR org.jgroups.protocols.ASYM_ENCRYPT - 1: failed decrypting message from 2 (offset=0, length=1136, buf.length=1136): javax.crypto.BadPaddingException: Given final block not properly padded, headers are ASYM_ENCRYPT: [ENCRYPT version=16 bytes], TP: [cluster_name=-1491537117] > 2018-05-23T03:11:53,893 +2903450780 [jgroups--12467,-1491537117,1] TRACE org.jgroups.protocols.TCP_NIO2 - 1: received message batch of 1 messages from 2 > 2018-05-23T03:11:53,895 +2903450782 [jgroups--12467,-1491537117,1] DEBUG org.jgroups.protocols.ASYM_ENCRYPT - 1: received secret key from keyserver 2 > 2018-05-23T03:11:53,895 +2903450782 [jgroups--12467,-1491537117,1] DEBUG org.jgroups.protocols.ASYM_ENCRYPT - 1: created 8 symmetric ciphers with secret key (16 bytes) > 2018-05-23T03:11:54,369 +2903451256 [jgroups--12467,-1491537117,1] TRACE org.jgroups.protocols.TCP_NIO2 - 1: received [dst:*** > 2018-05-23T03:11:54,369 +2903451256 [jgroups--12467,-1491537117,1] WARN org.jgroups.protocols.ASYM_ENCRYPT - 1: exception occurred decrypting message > javax.crypto.BadPaddingException: Given final block not properly padded > at com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:991) ~[sunjce_provider.jar:1.8.0_162] > at com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:847) ~[sunjce_provider.jar:1.8.0_162] > at com.sun.crypto.provider.AESCipher.engineDoFinal(AESCipher.java:446) ~[sunjce_provider.jar:1.8.0_162] > at javax.crypto.Cipher.doFinal(Cipher.java:2222) ~[?:1.8.0_171] > at org.jgroups.protocols.Encrypt.code(Encrypt.java:365) ~[jgroups-4.0.1.Final.jar:4.0.1.Final] > at org.jgroups.protocols.Encrypt.decryptChecksum(Encrypt.java:387) ~[jgroups-4.0.1.Final.jar:4.0.1.Final] > at org.jgroups.protocols.Encrypt._decrypt(Encrypt.java:299) ~[jgroups-4.0.1.Final.jar:4.0.1.Final] > at org.jgroups.protocols.Encrypt.decryptMessage(Encrypt.java:283) ~[jgroups-4.0.1.Final.jar:4.0.1.Final] > at org.jgroups.protocols.Encrypt.handleEncryptedMessage(Encrypt.java:242) ~[jgroups-4.0.1.Final.jar:4.0.1.Final] > at org.jgroups.protocols.Encrypt.handleUpMessage(Encrypt.java:229) ~[jgroups-4.0.1.Final.jar:4.0.1.Final] > at org.jgroups.protocols.Encrypt.up(Encrypt.java:155) [jgroups-4.0.1.Final.jar:4.0.1.Final] > at org.jgroups.protocols.ASYM_ENCRYPT.up(ASYM_ENCRYPT.java:143) [jgroups-4.0.1.Final.jar:4.0.1.Final] > at org.jgroups.protocols.VERIFY_SUSPECT.up(VERIFY_SUSPECT.java:129) [jgroups-4.0.1.Final.jar:4.0.1.Final] > at org.jgroups.protocols.FD_ALL.up(FD_ALL.java:197) [jgroups-4.0.1.Final.jar:4.0.1.Final] > at org.jgroups.protocols.FD_SOCK.up(FD_SOCK.java:252) [jgroups-4.0.1.Final.jar:4.0.1.Final] > at org.jgroups.protocols.MERGE3.up(MERGE3.java:277) [jgroups-4.0.1.Final.jar:4.0.1.Final] > at org.jgroups.protocols.Discovery.up(Discovery.java:262) [jgroups-4.0.1.Final.jar:4.0.1.Final] > at org.jgroups.protocols.TP.passMessageUp(TP.java:1203) [jgroups-4.0.1.Final.jar:4.0.1.Final] > at org.jgroups.util.SubmitToThreadPool$SingleMessageHandler.run(SubmitToThreadPool.java:87) [jgroups-4.0.1.Final.jar:4.0.1.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_162] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_162] > at java.lang.Thread.run(Thread.java:748) [?:1.8.0_162] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2277) GMS: change the way a coordinator leaves gracefully

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2277?page=com.atlassian.jira.plugin.... ] Bela Ban resolved JGRP-2277. ---------------------------- Resolution: Done > GMS: change the way a coordinator leaves gracefully > --------------------------------------------------- > > Key: JGRP-2277 > URL: https://issues.jboss.org/browse/JGRP-2277 > Project: JGroups > Issue Type: Enhancement > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 4.0.13 > > > Consider a cluster \{A,B,C,D\} with view A|5. > There's a discrepancy in handling coordinator A (1) leaving gracefully and (2) crashing. > When A crashes, the second-in-line (B) will install new view B|6=\{B,C,D\} in the cluster. > However, when A leaves _gracefully_, then *A itself* installs view B|6=\{B,C,D\}. The problem with this is that A is not able to retransmit the {{VIEW}} message to a member which dropped it, so inconsistencies may arise, which have to be healed by {{MERGE3}} (see JGRP-2276 for a description). > A better scheme would be for A to send a LEAVE message to the second-in-line (B), which then creates and installs view B|6, and then replies with a {{LEAVE_RSP}} message to A. > This has the following advantages: > * The code for handling a crashed coordinator, and a coordinator which leaves gracefully, is similar, and in both cases the second-in-line member installs the new view > * The second-in-line (B) stays up and can therefore retransmit a dropped {{VIEW}} message (contrary to A which terminates after a timeout). As long as A is able to send a {{LEAVE-REQ}} to B, B will handle it. If A crashes, B can also handle the view installation. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2690) Create an Scenario asset

by Juraj Soltes (JIRA)

Juraj Soltes created DROOLS-2690: ------------------------------------ Summary: Create an Scenario asset Key: DROOLS-2690 URL: https://issues.jboss.org/browse/DROOLS-2690 Project: Drools Issue Type: Task Components: Scenario Simulation and Testing Reporter: Juraj Soltes Assignee: Daniele Zonca -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2687) Guidance / cheatsheet how to write ranges

by Ivo Bek (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2687?page=com.atlassian.jira.plugi... ] Ivo Bek updated DROOLS-2687: ---------------------------- Description: As a business analyst I want to find a guidance / cheatsheet how to write ranges so that I don’t need to look up for documentation. > Guidance / cheatsheet how to write ranges > ----------------------------------------- > > Key: DROOLS-2687 > URL: https://issues.jboss.org/browse/DROOLS-2687 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Juraj Soltes > Assignee: Daniele Zonca > > As a business analyst I want to find a guidance / cheatsheet how to write ranges so that I don’t need to look up for documentation. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2682) Ability to review simulation test results

by Ivo Bek (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2682?page=com.atlassian.jira.plugi... ] Ivo Bek updated DROOLS-2682: ---------------------------- Summary: Ability to review simulation test results (was: [EPIC] the ability to review simulation test results) > Ability to review simulation test results > ----------------------------------------- > > Key: DROOLS-2682 > URL: https://issues.jboss.org/browse/DROOLS-2682 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Juraj Soltes > Assignee: Daniele Zonca > > As a business analyst I want the ability to review simulation test results so that I can view the accuracy of my rules. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 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 July 2018