April 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-2034) SASLTest-functional and SASL_SimpleAuthorizingCallbackTest-functional fails on IBM jdk 1.8

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2034?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-2034: --------------------------- Fix Version/s: (was: 4.0) > SASLTest-functional and SASL_SimpleAuthorizingCallbackTest-functional fails on IBM jdk 1.8 > ------------------------------------------------------------------------------------------ > > Key: JGRP-2034 > URL: https://issues.jboss.org/browse/JGRP-2034 > Project: JGroups > Issue Type: Bug > Reporter: Ivan Straka > Assignee: Tristan Tarrant > Fix For: 3.6.10 > > > We see these two tests failing on IBM jdk 1.8 > org.jgroups.protocols.SASLTest-functional > org.jgroups.protocols.SASL_SimpleAuthorizingCallbackTest-functional > This issue may be related to https://issues.jboss.org/browse/JGRP-1993 somehow. > There is standard output of tests. > {code} > ------------- testSASLDigestMD5 ----------- > ------------------------------------------------------------------- > GMS: address=A, cluster=SaslTest > ------------------------------------------------------------------- > 521823 [TRACE] GMS: A: no members discovered after 3000 ms: creating cluster as first member > 521823 [DEBUG] GMS: A: installing view [A|0] (1) [A] > 521823 [DEBUG] GMS: A: created cluster (first member). My view is [A|0], impl is org.jgroups.protocols.pbcast.CoordGmsImpl > ------------------------------------------------------------------- > GMS: address=B, cluster=SaslTest > ------------------------------------------------------------------- > 521825 [TRACE] GMS: B: discovery took 0 ms, members: 1 rsps (1 coords) [done] > 521826 [DEBUG] GMS: B: sending JOIN(B) to A > 521826 [TRACE] SASL: B: received CHALLENGE from A > 521827 [WARN] SASL: B: failed to validate CHALLENGE from A, token > javax.security.sasl.SaslException: DIGEST-MD5: Error acquiring realm, authentication ID or password > at com.ibm.security.sasl.digest.DigestMD5Client.processChallenge(DigestMD5Client.java:380) ~[ibmsaslprovider.jar:8.0 build_20150506] > at com.ibm.security.sasl.digest.DigestMD5Client.evaluateChallenge(DigestMD5Client.java:236) ~[ibmsaslprovider.jar:8.0 build_20150506] > at org.jgroups.auth.sasl.SaslClientContext.evaluateChallenge(SaslClientContext.java:119) ~[classes/:?] > at org.jgroups.auth.sasl.SaslClientContext.addHeader(SaslClientContext.java:92) ~[classes/:?] > at org.jgroups.auth.sasl.SaslClientContext.nextMessage(SaslClientContext.java:72) ~[classes/:?] > at org.jgroups.protocols.SASL.up(SASL.java:239) [classes/:?] > at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:234) [classes/:?] > at org.jgroups.protocols.UNICAST3.deliverMessage(UNICAST3.java:1064) [classes/:?] > at org.jgroups.protocols.UNICAST3.handleDataReceived(UNICAST3.java:779) [classes/:?] > at org.jgroups.protocols.UNICAST3.up(UNICAST3.java:426) [classes/:?] > at org.jgroups.protocols.pbcast.NAKACK2.up(NAKACK2.java:645) [classes/:?] > at org.jgroups.protocols.Discovery.up(Discovery.java:296) [classes/:?] > at org.jgroups.protocols.TP.passMessageUp(TP.java:1567) [classes/:?] > at org.jgroups.protocols.TP$SingleMessageHandler.run(TP.java:1783) [classes/:?] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1153) [?:1.8.0-internal] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:1.8.0-internal] > at java.lang.Thread.run(Thread.java:785) [?:1.8.0-internal] > Caused by: java.io.IOException: Invalid realm A > at org.jgroups.auth.sasl.SimpleAuthorizingCallbackHandler.handle(SimpleAuthorizingCallbackHandler.java:119) ~[classes/:?] > at com.ibm.security.sasl.digest.DigestMD5Client.processChallenge(DigestMD5Client.java:353) ~[ibmsaslprovider.jar:8.0 build_20150506] > ... 16 more > 524826 [WARN] GMS: B: JOIN(B) sent to A timed out (after 3000 ms), on try 1 > 524827 [TRACE] GMS: B: discovery took 1 ms, members: 1 rsps (1 coords) [done] > 524827 [DEBUG] GMS: B: sending JOIN(B) to A > 524828 [TRACE] SASL: B: received CHALLENGE from A > 524828 [WARN] SASL: B: failed to validate CHALLENGE from A, token > javax.security.sasl.SaslException: DIGEST-MD5: Error acquiring realm, authentication ID or password > at com.ibm.security.sasl.digest.DigestMD5Client.processChallenge(DigestMD5Client.java:380) ~[ibmsaslprovider.jar:8.0 build_20150506] > at com.ibm.security.sasl.digest.DigestMD5Client.evaluateChallenge(DigestMD5Client.java:236) ~[ibmsaslprovider.jar:8.0 build_20150506] > at org.jgroups.auth.sasl.SaslClientContext.evaluateChallenge(SaslClientContext.java:119) ~[classes/:?] > at org.jgroups.auth.sasl.SaslClientContext.addHeader(SaslClientContext.java:92) ~[classes/:?] > at org.jgroups.auth.sasl.SaslClientContext.nextMessage(SaslClientContext.java:72) ~[classes/:?] > at org.jgroups.protocols.SASL.up(SASL.java:239) [classes/:?] > at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:234) [classes/:?] > at org.jgroups.protocols.UNICAST3.deliverMessage(UNICAST3.java:1064) [classes/:?] > at org.jgroups.protocols.UNICAST3.handleDataReceived(UNICAST3.java:779) [classes/:?] > at org.jgroups.protocols.UNICAST3.up(UNICAST3.java:426) [classes/:?] > at org.jgroups.protocols.pbcast.NAKACK2.up(NAKACK2.java:645) [classes/:?] > at org.jgroups.protocols.Discovery.up(Discovery.java:296) [classes/:?] > at org.jgroups.protocols.TP.passMessageUp(TP.java:1567) [classes/:?] > at org.jgroups.protocols.TP$SingleMessageHandler.run(TP.java:1783) [classes/:?] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1153) [?:1.8.0-internal] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:1.8.0-internal] > at java.lang.Thread.run(Thread.java:785) [?:1.8.0-internal] > Caused by: java.io.IOException: Invalid realm A > at org.jgroups.auth.sasl.SimpleAuthorizingCallbackHandler.handle(SimpleAuthorizingCallbackHandler.java:119) ~[classes/:?] > at com.ibm.security.sasl.digest.DigestMD5Client.processChallenge(DigestMD5Client.java:353) ~[ibmsaslprovider.jar:8.0 build_20150506] > ... 16 more > 526826 [WARN] SASL: failed to validate SaslHeader from B, header: payload=[B@ad737f58 > ------------- testSASLDigestMD5Failure ----------- > ------------------------------------------------------------------- > GMS: address=A, cluster=SaslTest > ------------------------------------------------------------------- > 529863 [TRACE] GMS: A: no members discovered after 3000 ms: creating cluster as first member > 529864 [DEBUG] GMS: A: installing view [A|0] (1) [A] > 529864 [DEBUG] GMS: A: created cluster (first member). My view is [A|0], impl is org.jgroups.protocols.pbcast.CoordGmsImpl > ------------------------------------------------------------------- > GMS: address=B, cluster=SaslTest > ------------------------------------------------------------------- > 529866 [TRACE] GMS: B: discovery took 1 ms, members: 1 rsps (1 coords) [done] > 529866 [DEBUG] GMS: B: sending JOIN(B) to A > 529867 [TRACE] SASL: B: received CHALLENGE from A > 529867 [WARN] SASL: B: failed to validate CHALLENGE from A, token > javax.security.sasl.SaslException: DIGEST-MD5: Error acquiring realm, authentication ID or password > at com.ibm.security.sasl.digest.DigestMD5Client.processChallenge(DigestMD5Client.java:380) ~[ibmsaslprovider.jar:8.0 build_20150506] > at com.ibm.security.sasl.digest.DigestMD5Client.evaluateChallenge(DigestMD5Client.java:236) ~[ibmsaslprovider.jar:8.0 build_20150506] > at org.jgroups.auth.sasl.SaslClientContext.evaluateChallenge(SaslClientContext.java:119) ~[classes/:?] > at org.jgroups.auth.sasl.SaslClientContext.addHeader(SaslClientContext.java:92) ~[classes/:?] > at org.jgroups.auth.sasl.SaslClientContext.nextMessage(SaslClientContext.java:72) ~[classes/:?] > at org.jgroups.protocols.SASL.up(SASL.java:239) [classes/:?] > at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:234) [classes/:?] > at org.jgroups.protocols.UNICAST3.deliverMessage(UNICAST3.java:1064) [classes/:?] > at org.jgroups.protocols.UNICAST3.handleDataReceived(UNICAST3.java:779) [classes/:?] > at org.jgroups.protocols.UNICAST3.up(UNICAST3.java:426) [classes/:?] > at org.jgroups.protocols.pbcast.NAKACK2.up(NAKACK2.java:645) [classes/:?] > at org.jgroups.protocols.Discovery.up(Discovery.java:296) [classes/:?] > at org.jgroups.protocols.TP.passMessageUp(TP.java:1567) [classes/:?] > at org.jgroups.protocols.TP$SingleMessageHandler.run(TP.java:1783) [classes/:?] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1153) [?:1.8.0-internal] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:1.8.0-internal] > at java.lang.Thread.run(Thread.java:785) [?:1.8.0-internal] > Caused by: java.io.IOException: Invalid realm A > at org.jgroups.auth.sasl.SimpleAuthorizingCallbackHandler.handle(SimpleAuthorizingCallbackHandler.java:119) ~[classes/:?] > at com.ibm.security.sasl.digest.DigestMD5Client.processChallenge(DigestMD5Client.java:353) ~[ibmsaslprovider.jar:8.0 build_20150506] > ... 16 more > 532867 [WARN] GMS: B: JOIN(B) sent to A timed out (after 3000 ms), on try 1 > 532867 [TRACE] GMS: B: discovery took 0 ms, members: 1 rsps (1 coords) [done] > 532867 [DEBUG] GMS: B: sending JOIN(B) to A > 532868 [TRACE] SASL: B: received CHALLENGE from A > 532869 [WARN] SASL: B: failed to validate CHALLENGE from A, token > javax.security.sasl.SaslException: DIGEST-MD5: Error acquiring realm, authentication ID or password > at com.ibm.security.sasl.digest.DigestMD5Client.processChallenge(DigestMD5Client.java:380) ~[ibmsaslprovider.jar:8.0 build_20150506] > at com.ibm.security.sasl.digest.DigestMD5Client.evaluateChallenge(DigestMD5Client.java:236) ~[ibmsaslprovider.jar:8.0 build_20150506] > at org.jgroups.auth.sasl.SaslClientContext.evaluateChallenge(SaslClientContext.java:119) ~[classes/:?] > at org.jgroups.auth.sasl.SaslClientContext.addHeader(SaslClientContext.java:92) ~[classes/:?] > at org.jgroups.auth.sasl.SaslClientContext.nextMessage(SaslClientContext.java:72) ~[classes/:?] > at org.jgroups.protocols.SASL.up(SASL.java:239) [classes/:?] > at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:234) [classes/:?] > at org.jgroups.protocols.UNICAST3.deliverMessage(UNICAST3.java:1064) [classes/:?] > at org.jgroups.protocols.UNICAST3.handleDataReceived(UNICAST3.java:779) [classes/:?] > at org.jgroups.protocols.UNICAST3.up(UNICAST3.java:426) [classes/:?] > at org.jgroups.protocols.pbcast.NAKACK2.up(NAKACK2.java:645) [classes/:?] > at org.jgroups.protocols.Discovery.up(Discovery.java:296) [classes/:?] > at org.jgroups.protocols.TP.passMessageUp(TP.java:1567) [classes/:?] > at org.jgroups.protocols.TP$SingleMessageHandler.run(TP.java:1783) [classes/:?] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1153) [?:1.8.0-internal] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:1.8.0-internal] > at java.lang.Thread.run(Thread.java:785) [?:1.8.0-internal] > Caused by: java.io.IOException: Invalid realm A > at org.jgroups.auth.sasl.SimpleAuthorizingCallbackHandler.handle(SimpleAuthorizingCallbackHandler.java:119) ~[classes/:?] > at com.ibm.security.sasl.digest.DigestMD5Client.processChallenge(DigestMD5Client.java:353) ~[ibmsaslprovider.jar:8.0 build_20150506] > ... 16 more > 534867 [WARN] SASL: failed to validate SaslHeader from B, header: payload=[B@6f6c2511 > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JGRP-2047) Reduce number of threads in default configurations

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2047?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-2047: --------------------------- Description: Reduce the defaults for thread pools that have no queue enabled. If no queue is enabled, we can set min-threads to 0 but have a keep-alive time of 30s or 60s. > Reduce number of threads in default configurations > -------------------------------------------------- > > Key: JGRP-2047 > URL: https://issues.jboss.org/browse/JGRP-2047 > Project: JGroups > Issue Type: Enhancement > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 4.0 > > > Reduce the defaults for thread pools that have no queue enabled. If no queue is enabled, we can set min-threads to 0 but have a keep-alive time of 30s or 60s. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JGRP-2047) Reduce number of threads in default configurations

by Bela Ban (JIRA)

Bela Ban created JGRP-2047: ------------------------------ Summary: Reduce number of threads in default configurations Key: JGRP-2047 URL: https://issues.jboss.org/browse/JGRP-2047 Project: JGroups Issue Type: Enhancement Reporter: Bela Ban Assignee: Bela Ban Priority: Minor Fix For: 4.0 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-1127) Google App Engine support: Do not call new Thread() by allowing to plug in a custom ThreadFactory

by Geoffrey De Smet (JIRA)

Geoffrey De Smet created DROOLS-1127: ---------------------------------------- Summary: Google App Engine support: Do not call new Thread() by allowing to plug in a custom ThreadFactory Key: DROOLS-1127 URL: https://issues.jboss.org/browse/DROOLS-1127 Project: Drools Issue Type: Enhancement Components: core engine Reporter: Geoffrey De Smet Assignee: Mario Fusco We're still investigating, more info coming. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-1126) make org.kie.scanner.ArtifactResolver public

by Bernard Tison (JIRA)

Bernard Tison created DROOLS-1126: ------------------------------------- Summary: make org.kie.scanner.ArtifactResolver public Key: DROOLS-1126 URL: https://issues.jboss.org/browse/DROOLS-1126 Project: Drools Issue Type: Enhancement Components: core engine Affects Versions: 6.4.0.Final Reporter: Bernard Tison Assignee: Mario Fusco Priority: Minor At the moment org.kie.scanner.ArtifactResolver in the kie-ci package is not a public class, and is used only by other classes in the kie-ci package. However, it contains methods like getAllDependencies() which are really useful for e.g. extensions on top of kie-server. As an example, I recently implemented a kie-extension using protobuf as marshalling technology. For this use case I needed to scan the kjar and its dependencies for protobuf definition files, and ArtifactResolver is exactly what I needed to do so. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-6523) org.jboss.narayana.compensations and org.jboss.narayana.rts modules should be unsupported

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/WFLY-6523?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated WFLY-6523: -------------------------------- Fix Version/s: 10.1.0.Final > org.jboss.narayana.compensations and org.jboss.narayana.rts modules should be unsupported > ----------------------------------------------------------------------------------------- > > Key: WFLY-6523 > URL: https://issues.jboss.org/browse/WFLY-6523 > Project: WildFly > Issue Type: Task > Components: Transactions > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 10.1.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-453) Allow KieSession globals configurable via kmodule.xml

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-453?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer updated DROOLS-453: ------------------------------------------ Fix Version/s: 7.0.0.Beta1 (was: 6.4.0.Final) > Allow KieSession globals configurable via kmodule.xml > ----------------------------------------------------- > > Key: DROOLS-453 > URL: https://issues.jboss.org/browse/DROOLS-453 > Project: Drools > Issue Type: Enhancement > Affects Versions: 6.0.0.Final > Reporter: Anton Giertli > Assignee: Mark Proctor > Fix For: 7.0.0.Beta1 > > > Looking at the current xsd of kmodule.xml > https://github.com/droolsjbpm/droolsjbpm-knowledge/blob/6.0.x/kie-api/src... > It is not possible to configure KieSession globals variables via kmodule.xml. > Given the fact it is already possible to configure almost every KieSession related features like listeners, handlers, loggers, globals, also session related, should be configurable through the kmodule.xml too. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-607) Match.getObjects() should reflect the patterns' order

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-607?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer updated DROOLS-607: ------------------------------------------ Fix Version/s: 7.0.0.Beta1 (was: 6.4.0.Final) > Match.getObjects() should reflect the patterns' order > ----------------------------------------------------- > > Key: DROOLS-607 > URL: https://issues.jboss.org/browse/DROOLS-607 > Project: Drools > Issue Type: Enhancement > Affects Versions: 5.5.0.Final, 5.6.0.Final, 6.0.0.Final, 6.1.0.Final > Reporter: Davide Sottara > Assignee: Mark Proctor > Priority: Minor > Fix For: 7.0.0.Beta1 > > > if Match.getObjects() is called on a rule with LHS A() B() C(), > the resulting list will have the matching objects in reversed order > - that is, [c, b, a] - making it more difficult to analyze it. > The object's position in the list should reflect the LHS. > The order should be preserved even when subnetworks are present. > For example, A() not B() C() should then result in the list [a, *, c ] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-470) Decision Table (XLS) should support fixed conditions, such as SeatDesignation(isNeighborOf($guest))

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-470?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer updated DROOLS-470: ------------------------------------------ Fix Version/s: 7.0.0.Beta1 (was: 6.4.0.Final) > Decision Table (XLS) should support fixed conditions, such as SeatDesignation(isNeighborOf($guest)) > --------------------------------------------------------------------------------------------------- > > Key: DROOLS-470 > URL: https://issues.jboss.org/browse/DROOLS-470 > Project: Drools > Issue Type: Enhancement > Components: decision tables > Affects Versions: 6.1.0.Beta2 > Reporter: Geoffrey De Smet > Assignee: Michael Anstis > Labels: optaplanner-request-for-drools > Fix For: 7.0.0.Beta1 > > > This DT should work: > ||CONDITION||CONDITION||ACTION| > |$guest : SeatDesignation()|$neighbor : SeatDesignation(isNeighborOf($guest))|| > |guestName == "$param"|guestName == "$param"|doSomething();| > It crashes because of the "SeatDesignation(isNeighborOf($guest))". Only empty parenthesis are allowed. > Failing workaround 1: This workaround (as specified by the docs), does NOT work well, because it adds the same condition (isNeighborOf($guest)) multiple times in the same rule: > ||CONDITION||CONDITION||CONDITION||ACTION| > |$guest : SeatDesignation()|$neighbor : SeatDesignation()||| > |guestName == "$param"|isNeighborOf($guest), guestName == "$param"|isNeighborOf($guest), guestAge == "$param"|doSomething();| > Failing workaround 2: Adding an extra, hidden column with that condition does not work when new rows are added because condition columns with an empty cell are ignored. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-542) Expose more Commands through the KieCommands API

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-542?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer updated DROOLS-542: ------------------------------------------ Fix Version/s: 7.0.0.Beta1 (was: 6.4.0.Final) > Expose more Commands through the KieCommands API > ------------------------------------------------ > > Key: DROOLS-542 > URL: https://issues.jboss.org/browse/DROOLS-542 > Project: Drools > Issue Type: Feature Request > Affects Versions: 6.1.0.CR1 > Reporter: Davide Sottara > Assignee: Davide Sottara > Fix For: 7.0.0.Beta1 > > > Not all Commands are exposed by the KieCommands API interface -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

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 April 2016