January 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-13019) Error: WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN)

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13019?page=com.atlassian.jira.plugi... ] Brian Stansberry reopened WFLY-13019: ------------------------------------- > Error: WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN) > ---------------------------------------------------------------------------------- > > Key: WFLY-13019 > URL: https://issues.redhat.com/browse/WFLY-13019 > Project: WildFly > Issue Type: Bug > Reporter: Mark Sanchez > Assignee: Brian Stansberry > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13019) Error: WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN)

by Mark Sanchez (Jira)

Mark Sanchez created WFLY-13019: ----------------------------------- Summary: Error: WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN) Key: WFLY-13019 URL: https://issues.redhat.com/browse/WFLY-13019 Project: WildFly Issue Type: Bug Reporter: Mark Sanchez Assignee: Brian Stansberry -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13020) Error: WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN)

by Mark Sanchez (Jira)

Mark Sanchez created WFLY-13020: ----------------------------------- Summary: Error: WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN) Key: WFLY-13020 URL: https://issues.redhat.com/browse/WFLY-13020 Project: WildFly Issue Type: Bug Reporter: Mark Sanchez Assignee: Brian Stansberry -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13019) Error: WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN)

by Mark Sanchez (Jira)

[ https://issues.redhat.com/browse/WFLY-13019?page=com.atlassian.jira.plugi... ] Mark Sanchez closed WFLY-13019. ------------------------------- Resolution: Done > Error: WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN) > ---------------------------------------------------------------------------------- > > Key: WFLY-13019 > URL: https://issues.redhat.com/browse/WFLY-13019 > Project: WildFly > Issue Type: Bug > Reporter: Mark Sanchez > Assignee: Brian Stansberry > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13018) Multiple CallbackHandlerServices for the same mechanism (PLAIN)

by Mark Sanchez (Jira)

[ https://issues.redhat.com/browse/WFLY-13018?page=com.atlassian.jira.plugi... ] Mark Sanchez closed WFLY-13018. ------------------------------- Resolution: Done > Multiple CallbackHandlerServices for the same mechanism (PLAIN) > --------------------------------------------------------------- > > Key: WFLY-13018 > URL: https://issues.redhat.com/browse/WFLY-13018 > Project: WildFly > Issue Type: Bug > Components: Build System > Affects Versions: 18.0.1.Final > Reporter: Mark Sanchez > Assignee: Brian Stansberry > Priority: Major > Fix For: 17.0.1.Final > > > Error: > WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN) > We get an error with the following ldap configuration. This works for version 17. > > <security-realm name="ldap_security_realm"> > <server-identities> > <ssl> > <engine enabled-protocols="TLSv1.2"/> > <keystore path="/opt/app/workload/jboss/ssl_jboss/psftest2s.jboss.keystore" keystore-password="${VAULT::ssl_cert::password::1}"/> > </ssl> > </server-identities> > <authentication> > <ldap connection="testLdap" base-dn="dc=test,dc=sbc,dc=com" recursive="true"> > <username-filter attribute="samaccountname"/> > </ldap> > </authentication> > </security-realm> > </security-realms> > <outbound-connections> > <ldap name="testLdap" url="ldap://its-ad-ldap.it.test.com:636" search-dn="CN=mxxxxxx,OU=GenericID,OU=testUsers,DC=testServices,DC=test,DC=com" search-credential="${VAULT::ldap_searchdn::password::1}" security-realm="ldap_security_realm"/> > </outbound-connections> > <management-interfaces> > <http-interface security-realm="ldap_security_realm"> > <http-upgrade enabled="true"/> > <socket interface="management" port="${jboss.management.http.port:9990}"/> > </http-interface> > </management-interfaces> -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13018) Multiple CallbackHandlerServices for the same mechanism (PLAIN)

by Mark Sanchez (Jira)

Mark Sanchez created WFLY-13018: ----------------------------------- Summary: Multiple CallbackHandlerServices for the same mechanism (PLAIN) Key: WFLY-13018 URL: https://issues.redhat.com/browse/WFLY-13018 Project: WildFly Issue Type: Bug Components: Build System Affects Versions: 18.0.1.Final Reporter: Mark Sanchez Assignee: Brian Stansberry Fix For: 17.0.1.Final Error: WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN) We get an error with the following ldap configuration. This works for version 17. <security-realm name="ldap_security_realm"> <server-identities> <ssl> <engine enabled-protocols="TLSv1.2"/> <keystore path="/opt/app/workload/jboss/ssl_jboss/psftest2s.jboss.keystore" keystore-password="${VAULT::ssl_cert::password::1}"/> </ssl> </server-identities> <authentication> <ldap connection="testLdap" base-dn="dc=test,dc=sbc,dc=com" recursive="true"> <username-filter attribute="samaccountname"/> </ldap> </authentication> </security-realm> </security-realms> <outbound-connections> <ldap name="testLdap" url="ldap://its-ad-ldap.it.test.com:636" search-dn="CN=mxxxxxx,OU=GenericID,OU=testUsers,DC=testServices,DC=test,DC=com" search-credential="${VAULT::ldap_searchdn::password::1}" security-realm="ldap_security_realm"/> </outbound-connections> <management-interfaces> <http-interface security-realm="ldap_security_realm"> <http-upgrade enabled="true"/> <socket interface="management" port="${jboss.management.http.port:9990}"/> </http-interface> </management-interfaces> -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4985) A Spreadsheet decision tables does not convert to a DRL file correctly when a Function is being used in the RuleTable constraints

by Toni Rikkola (Jira)

[ https://issues.redhat.com/browse/DROOLS-4985?page=com.atlassian.jira.plug... ] Toni Rikkola updated DROOLS-4985: --------------------------------- Sprint: 2020 Week 04-06 (from Jan 20) > A Spreadsheet decision tables does not convert to a DRL file correctly when a Function is being used in the RuleTable constraints > --------------------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-4985 > URL: https://issues.redhat.com/browse/DROOLS-4985 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor, XLS Score Card Editor > Reporter: Oscar Molina > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools, support > > The attached "test_functions.xlsx" spreadsheet which is being used for creating a “Spreadsheet decision tables” asset. This spreadsheet contains a “Function” and has some rules. These rules use the “Function” in the constraints. When this XLSX Decision Table is converted to a “Guided Decision Table”, the constraints are missing the “Function” calls. Surprisingly if the “Function” call is used in a System.out.println statement, the generated DRL correctly contains it. > A wrongly generated DRL rule > {code} > rule "Row 3 Hello RuleTable" > dialect "mvel" > when > $person : Person( gender == "Female" , married == true ) > then > $person.setHelloMsg( "Miss" ); > System.out.println(hello($person.getName(), "Miss", "how are you doing")); > end > {code} > Expected correct DRL rule > {code} > rule "Row 3 Hello RuleTable DRL" > dialect "mvel" > when > $person : Person( gender == "Female" , married == true ) > then > $person.setHelloMsg( hello($person.getName(), "Miss", "how are you doing") ); > System.out.println(hello($person.getName(), "Miss", "how are you doing")); > end > {code} > Regards, > Oscar. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4985) A Spreadsheet decision tables does not convert to a DRL file correctly when a Function is being used in the RuleTable constraints

by Toni Rikkola (Jira)

[ https://issues.redhat.com/browse/DROOLS-4985?page=com.atlassian.jira.plug... ] Toni Rikkola moved RHDM-1211 to DROOLS-4985: -------------------------------------------- Project: Drools (was: Red Hat Decision Manager) Key: DROOLS-4985 (was: RHDM-1211) Workflow: GIT Pull Request workflow (was: CDW with docs v1) Docs QE Status: NEW Component/s: Guided Decision Table Editor XLS Score Card Editor (was: Decision Central) Affects Version/s: (was: 7.5.0.GA) (was: 7.5.1.GA) QE Status: NEW > A Spreadsheet decision tables does not convert to a DRL file correctly when a Function is being used in the RuleTable constraints > --------------------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-4985 > URL: https://issues.redhat.com/browse/DROOLS-4985 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor, XLS Score Card Editor > Reporter: Oscar Molina > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools, support > > The attached "test_functions.xlsx" spreadsheet which is being used for creating a “Spreadsheet decision tables” asset. This spreadsheet contains a “Function” and has some rules. These rules use the “Function” in the constraints. When this XLSX Decision Table is converted to a “Guided Decision Table”, the constraints are missing the “Function” calls. Surprisingly if the “Function” call is used in a System.out.println statement, the generated DRL correctly contains it. > A wrongly generated DRL rule > {code} > rule "Row 3 Hello RuleTable" > dialect "mvel" > when > $person : Person( gender == "Female" , married == true ) > then > $person.setHelloMsg( "Miss" ); > System.out.println(hello($person.getName(), "Miss", "how are you doing")); > end > {code} > Expected correct DRL rule > {code} > rule "Row 3 Hello RuleTable DRL" > dialect "mvel" > when > $person : Person( gender == "Female" , married == true ) > then > $person.setHelloMsg( hello($person.getName(), "Miss", "how are you doing") ); > System.out.println(hello($person.getName(), "Miss", "how are you doing")); > end > {code} > Regards, > Oscar. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4984) Enable the executable model in Optaplanner

by Luca Molteni (Jira)

Luca Molteni created DROOLS-4984: ------------------------------------ Summary: Enable the executable model in Optaplanner Key: DROOLS-4984 URL: https://issues.redhat.com/browse/DROOLS-4984 Project: Drools Issue Type: Bug Components: executable model Reporter: Luca Molteni Assignee: Luca Molteni Currently it's disabled -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-1927) Release WildFly Elytron 1.11.2.Final

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/ELY-1927?page=com.atlassian.jira.plugin.... ] Farah Juma resolved ELY-1927. ----------------------------- Resolution: Done > Release WildFly Elytron 1.11.2.Final > ------------------------------------ > > Key: ELY-1927 > URL: https://issues.redhat.com/browse/ELY-1927 > Project: WildFly Elytron > Issue Type: Release > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > Fix For: 1.11.2.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 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 January 2020