June 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1613) NPE when evaluating a DMN decision table with multiple outputs and one of the outputs has wrong type

by Tibor Zimányi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1613?page=com.atlassian.jira.plugi... ] Tibor Zimányi updated DROOLS-1613: ---------------------------------- Description: When I have a decision table with hit policy Priority and multiple outputs and I change one of the outputs in a rule to a wrong type, the evaluation ends with NullPointerException. E.g. having output entry like this: <outputEntry id="_7f03803d-2636-40ab-8346-7fd7f38ab695-3"> <text>1</text> </outputEntry> I will provide PR with reproducer for this. was: When I have a decision table with hit policy Priority and multiple outputs and I change one of the outputs in a rule to a wrong type, the evaluation ends with NullPointerException. E.g. having output entry like this: <outputEntry id="_7f03803d-2636-40ab-8346-7fd7f38ab695-3"> <text>1</text> </outputEntry> I will provide PR for this. > NPE when evaluating a DMN decision table with multiple outputs and one of the outputs has wrong type > ---------------------------------------------------------------------------------------------------- > > Key: DROOLS-1613 > URL: https://issues.jboss.org/browse/DROOLS-1613 > Project: Drools > Issue Type: Bug > Components: dmn engine > Affects Versions: 7.0.0.Final > Reporter: Tibor Zimányi > Assignee: Edson Tirelli > Fix For: 7.1.0.Final > > > When I have a decision table with hit policy Priority and multiple outputs and I change one of the outputs in a rule to a wrong type, the evaluation ends with NullPointerException. > E.g. having output entry like this: > <outputEntry id="_7f03803d-2636-40ab-8346-7fd7f38ab695-3"> > <text>1</text> > </outputEntry> > I will provide PR with reproducer for this. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-117) Hawkular Metrics Upstream Testing

by Hayk Hovsepyan (JIRA)

Hayk Hovsepyan created HAWKULARQE-117: ----------------------------------------- Summary: Hawkular Metrics Upstream Testing Key: HAWKULARQE-117 URL: https://issues.jboss.org/browse/HAWKULARQE-117 Project: Hawkular QE Issue Type: Sub-task Reporter: Hayk Hovsepyan Assignee: Michael Foley New Mojo page describing what JON QE Team is doing for Hawkular Metrics Upstream testing. Used tools. Refs to documents. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-116) Hawkular Alerts Upstream Testing

by Hayk Hovsepyan (JIRA)

Hayk Hovsepyan created HAWKULARQE-116: ----------------------------------------- Summary: Hawkular Alerts Upstream Testing Key: HAWKULARQE-116 URL: https://issues.jboss.org/browse/HAWKULARQE-116 Project: Hawkular QE Issue Type: Sub-task Reporter: Hayk Hovsepyan Assignee: Michael Foley New Mojo page describing what JON QE Team is doing for Hawkular Alerts Upstream testing. Used tools. Refs to documents. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-114) Hawkular Services Downstream Testing

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-114?page=com.atlassian.jira.pl... ] Hayk Hovsepyan updated HAWKULARQE-114: -------------------------------------- Description: New Mojo page describing what JON QE Team is doing for Hawkular Services Downstream testing. Used tools. Refs to documents. > Hawkular Services Downstream Testing > ------------------------------------ > > Key: HAWKULARQE-114 > URL: https://issues.jboss.org/browse/HAWKULARQE-114 > Project: Hawkular QE > Issue Type: Sub-task > Reporter: Hayk Hovsepyan > Assignee: Michael Foley > > New Mojo page describing what JON QE Team is doing for Hawkular Services Downstream testing. > Used tools. > Refs to documents. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-115) Static Analysis Tools running on Hawkular Upstream

by Hayk Hovsepyan (JIRA)

Hayk Hovsepyan created HAWKULARQE-115: ----------------------------------------- Summary: Static Analysis Tools running on Hawkular Upstream Key: HAWKULARQE-115 URL: https://issues.jboss.org/browse/HAWKULARQE-115 Project: Hawkular QE Issue Type: Task Reporter: Hayk Hovsepyan Assignee: Michael Foley Research the possible tools to apply. Take into account tools used by Dev's and QE's. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1186) Elytron - authentication fails when a realm name is not specified for DIGEST-MD5 mechanism on server side

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-1186?page=com.atlassian.jira.plugin.s... ] David Lloyd commented on ELY-1186: ---------------------------------- What if the mechanism treated the fallback/host-name realm as a "no realm"? In org.wildfly.security.sasl.digest.DigestServerFactory#createSaslServer we could set a flag that is sent to DigestSaslServer which indicates that only the host-name realm was added, so the javax.security.sasl.RealmCallback should never be called. This does mean that the server will have to rely on using DigestPasswordAlgorithmSpec to get a realm-specific credential, but I think this is OK in ths case. WDYT? > Elytron - authentication fails when a realm name is not specified for DIGEST-MD5 mechanism on server side > --------------------------------------------------------------------------------------------------------- > > Key: ELY-1186 > URL: https://issues.jboss.org/browse/ELY-1186 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Josef Cacek > Assignee: Darran Lofthouse > Priority: Blocker > > When a default configuration is used for DIGEST-MD5 SASL mechanism, then server suggest hostname as a realm name, but authentication fails because ServerAuthenticationContext checks mechanism configuration and fails with following exception: > {code} > @Message(id = 1092, value = "Invalid mechanism realm selection \"%s\"") > IllegalArgumentException invalidMechRealmSelection(String realmName); > {code} > *Suggested fix:* > If the server suggests realm name, then it should be able to consume it. Or if the realm name is really mandatory, then server should not suggest such a default value. IMO allowing such a default and simplifying configuration would have positive impact on user experience. > The full stacktrace (hidden): > {noformat} > javax.security.sasl.SaslException: ELY05053: [DIGEST-MD5] Callback handler failed for unknown reason [Caused by java.lang.IllegalArgumentException: ELY01092: Invalid mechanism realm selection "localhost"] > at org.wildfly.security.sasl.util.AbstractSaslParticipant.tryHandleCallbacks(AbstractSaslParticipant.java:105) > at org.wildfly.security.sasl.digest.AbstractDigestMechanism.getPredigestedSaltedPassword(AbstractDigestMechanism.java:482) > at org.wildfly.security.sasl.digest.DigestSaslServer.validateDigestResponse(DigestSaslServer.java:259) > at org.wildfly.security.sasl.digest.DigestSaslServer.evaluateMessage(DigestSaslServer.java:355) > at org.wildfly.security.sasl.util.AbstractSaslParticipant.evaluateMessage(AbstractSaslParticipant.java:180) > at org.wildfly.security.sasl.digest.DigestSaslServer.evaluateResponse(DigestSaslServer.java:328) > at org.wildfly.security.sasl.util.AuthenticationCompleteCallbackSaslServerFactory$1.evaluateResponse(AuthenticationCompleteCallbackSaslServerFactory.java:58) > at org.wildfly.security.sasl.util.AuthenticationTimeoutSaslServerFactory$DelegatingTimeoutSaslServer.evaluateResponse(AuthenticationTimeoutSaslServerFactory.java:106) > at org.wildfly.security.sasl.util.SecurityIdentitySaslServerFactory$1.evaluateResponse(SecurityIdentitySaslServerFactory.java:57) > at org.xnio.sasl.SaslUtils.evaluateResponse(SaslUtils.java:245) > at org.xnio.sasl.SaslUtils.evaluateResponse(SaslUtils.java:217) > at org.jboss.remoting3.remote.ServerConnectionOpenListener$AuthStepRunnable.run(ServerConnectionOpenListener.java:470) > at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:897) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:748) > Caused by: java.lang.IllegalArgumentException: ELY01092: Invalid mechanism realm selection "localhost" > at org.wildfly.security.auth.server.ServerAuthenticationContext$InitialState.setMechanismRealmName(ServerAuthenticationContext.java:1615) > at org.wildfly.security.auth.server.ServerAuthenticationContext.setMechanismRealmName(ServerAuthenticationContext.java:712) > at org.wildfly.security.auth.server.ServerAuthenticationContext$1.handleOne(ServerAuthenticationContext.java:927) > at org.wildfly.security.auth.server.ServerAuthenticationContext$1.handle(ServerAuthenticationContext.java:735) > at org.wildfly.security.sasl.util.TrustManagerSaslServerFactory.lambda$createSaslServer$0(TrustManagerSaslServerFactory.java:96) > at org.wildfly.security.sasl.util.AbstractSaslParticipant.tryHandleCallbacks(AbstractSaslParticipant.java:101) > ... 15 more > {noformat} > Attached also server configuration and WireShark log. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8915) Unexpected update of configuration file standalone.xml if an archive is dropped to deployments folder

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-8915?page=com.atlassian.jira.plugin.... ] Brian Stansberry commented on WFLY-8915: ---------------------------------------- I think there was another issue about this, or perhaps an internal support list discussion. I don't think it's likely we'll change this as doing it would be probably be quite invasive and bug prone. > Unexpected update of configuration file standalone.xml if an archive is dropped to deployments folder > ----------------------------------------------------------------------------------------------------- > > Key: WFLY-8915 > URL: https://issues.jboss.org/browse/WFLY-8915 > Project: WildFly > Issue Type: Bug > Affects Versions: 11.0.0.Alpha1 > Reporter: Wolf-Dieter Fink > Assignee: Jason Greene > Priority: Minor > > It is not expected that the standalone.xml is written and versions or other content is updated. > e.g. the top level element > <server xmlns="urn:jboss:domain:x.y"> > It is expected that the standalone configuration is updated with the latest namespace versions, or other changes, if the configuration needs to be persisted. > But for any unmanged deployment it is not expected and not necessary to update the configuration file. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-114) Hawkular Services Downstream Testing

by Hayk Hovsepyan (JIRA)

Hayk Hovsepyan created HAWKULARQE-114: ----------------------------------------- Summary: Hawkular Services Downstream Testing Key: HAWKULARQE-114 URL: https://issues.jboss.org/browse/HAWKULARQE-114 Project: Hawkular QE Issue Type: Sub-task Reporter: Hayk Hovsepyan Assignee: Michael Foley -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-113) Hawkular Services Upstream Testing

by Hayk Hovsepyan (JIRA)

Hayk Hovsepyan created HAWKULARQE-113: ----------------------------------------- Summary: Hawkular Services Upstream Testing Key: HAWKULARQE-113 URL: https://issues.jboss.org/browse/HAWKULARQE-113 Project: Hawkular QE Issue Type: Sub-task Reporter: Hayk Hovsepyan Assignee: Michael Foley New Mojo page describing what JON QE Team is doing for Hawkular Services Upstream testing. Used tools. Refs to documents. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-108) Mojo page describing CFME Upstream/Downstream test processes

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-108?page=com.atlassian.jira.pl... ] Hayk Hovsepyan updated HAWKULARQE-108: -------------------------------------- Description: Intended audience: PM, DEV, QE. Create several Mojo pages in hierarchy, which will describe JON QE Team Testing Strategies and processes for JON, Hawkular Upstream/Downstream testing processes, used tools, strategies. was:Intended audience: PM, DEV, QE. > Mojo page describing CFME Upstream/Downstream test processes > ------------------------------------------------------------ > > Key: HAWKULARQE-108 > URL: https://issues.jboss.org/browse/HAWKULARQE-108 > Project: Hawkular QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Michael Foley > > Intended audience: PM, DEV, QE. > Create several Mojo pages in hierarchy, which will describe JON QE Team Testing Strategies and processes for JON, Hawkular Upstream/Downstream testing processes, used tools, strategies. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

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 2017