January 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-4829) An operation to add a pattern-formatter resource does not correctly marshal the XML configuration

by James Perkins (Jira)

James Perkins created WFCORE-4829: ------------------------------------- Summary: An operation to add a pattern-formatter resource does not correctly marshal the XML configuration Key: WFCORE-4829 URL: https://issues.redhat.com/browse/WFCORE-4829 Project: WildFly Core Issue Type: Bug Components: Logging Reporter: James Perkins Assignee: James Perkins Using an operation like {{/subsystem=logging/pattern-formatter=formatter:add}} will correctly add the formatter to the model. However after a reload an exception is logged as the default values are not marshalled into the XML. Along with this even if the element is marshalled, the {{pattern}} attribute seems to get set to "undefined" in the logging configuration which just logs the "undefined" for every log message. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13042) Jaeger tracer sender-binding isn't configurable

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13042?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-13042: ------------------------------------ Fix Version/s: 19.0.0.Beta2 > Jaeger tracer sender-binding isn't configurable > ----------------------------------------------- > > Key: WFLY-13042 > URL: https://issues.redhat.com/browse/WFLY-13042 > Project: WildFly > Issue Type: Bug > Components: MP OpenTracing > Affects Versions: 19.0.0.Beta1 > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Priority: Blocker > Fix For: 19.0.0.Beta2 > > > When configuring a jaeger tracer sender-binding parameter the server will no longer boot because of a NullPointerException in JaegerTracerConfiguration thus failing the boot of the server. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13043) ManagedScheduledExecutorService keeps executing tasks after an exception is thrown

by Vinicius Kopcheski (Jira)

Vinicius Kopcheski created WFLY-13043: ----------------------------------------- Summary: ManagedScheduledExecutorService keeps executing tasks after an exception is thrown Key: WFLY-13043 URL: https://issues.redhat.com/browse/WFLY-13043 Project: WildFly Issue Type: Bug Components: Concurrency Utilities Affects Versions: 18.0.1.Final Reporter: Vinicius Kopcheski Assignee: Eduardo Martins There is apparently a bug in the implementation of the ManagedScheduledExecutorService, more specifically when using the inherited method of the ScheduledExecutorService, [scheduleWithFixedDelay|https://docs.oracle.com/javase/7/docs/api/java/uti...]. On its javadoc it is stated "If any execution of the task encounters an exception, subsequent executions are suppressed.". When [this code|https://github.com/kopcheski/managed-scheduled-executor/blob/master/...] is executed in any Wildfly from 10 to 18, the task is kept alive in the scheduler after an exception is thrown and subsequent calls will happen anyway, contradicting the javadoc. To add evidences of a misbehavior, I did two extra checks: 1. Running the exact same code in another JavaEE server (Payara); 2. Using plain JavaSE with the ScheduledExecutorService. In both cases, after an exception being thrown, subsequent executions of it are - as the javadoc states - suppressed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4990) NullPointerException with executable model using accumulate max with null Date field

by Martin Weiler (Jira)

[ https://issues.redhat.com/browse/DROOLS-4990?page=com.atlassian.jira.plug... ] Martin Weiler moved RHDM-1216 to DROOLS-4990: --------------------------------------------- Project: Drools (was: Red Hat Decision Manager) Key: DROOLS-4990 (was: RHDM-1216) Workflow: GIT Pull Request workflow (was: CDW with docs v1) Docs QE Status: NEW Component/s: core engine executable model (was: BRE) Affects Version/s: 7.32.0.Final (was: 7.6.0.GA) QE Status: NEW > NullPointerException with executable model using accumulate max with null Date field > ------------------------------------------------------------------------------------ > > Key: DROOLS-4990 > URL: https://issues.redhat.com/browse/DROOLS-4990 > Project: Drools > Issue Type: Bug > Components: core engine, executable model > Affects Versions: 7.32.0.Final > Reporter: Martin Weiler > Assignee: Mario Fusco > Priority: Major > Labels: support > > Executing a rule containing accumulate max, eg: > {code} > rule AccumulateMaxDate > when > $max1 : Number() from accumulate( > StockTick(isSetDueDate == true > ,$time : dueDate); > max($time.getTime().getTime())) > then > end > {code} > fails with a NPE at runtime if the StockDate.dueDate field is null: > {noformat} > Caused by: java.lang.NullPointerException > at defaultpkg.RulesA0DFC3D10EA29F3818B87E11918D8020RuleMethods0.lambda$rule_AccumulateMaxDate$c9e019d8$1(RulesA0DFC3D10EA29F3818B87E11918D8020RuleMethods0.java:34) > at org.drools.model.functions.Function1$Impl.apply(Function1.java:35) > at org.drools.model.view.BindViewItem1.eval(BindViewItem1.java:85) > at org.drools.modelcompiler.constraints.BindingEvaluator.evaluate(BindingEvaluator.java:39) > at org.drools.modelcompiler.constraints.BindingEvaluator.evaluate(BindingEvaluator.java:35) > at org.drools.modelcompiler.constraints.LambdaAccumulator$BindingAcc.getAccumulatedObject(LambdaAccumulator.java:154) > at org.drools.modelcompiler.constraints.LambdaAccumulator.accumulate(LambdaAccumulator.java:88) > at org.drools.core.rule.SingleAccumulate.accumulate(SingleAccumulate.java:97) > ... 53 more > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4972) Buttons stay disabled when switching to textual collection editor

by Elizabeth Clayton (Jira)

[ https://issues.redhat.com/browse/DROOLS-4972?page=com.atlassian.jira.plug... ] Elizabeth Clayton edited comment on DROOLS-4972 at 1/30/20 1:33 PM: -------------------------------------------------------------------- [~yamer] I took a closer look and imo this needs it's own jira, to support a more comprehensive fix. But in the interim, unless I'm misunderstanding the interaction, it might help to: - When it's not in "edit mode" consider moving the "Add new item" directly below the last item in the list. - Consider renaming the action to "Add list value" or whatever most closely describes the action. - Consider making the font sizes the same within the dialog. The Name field looks too small, while the Edit name looks too large, but the "Add new item" looks about right. !Screen Shot 2020-01-30 at 1.24.18 PM.png|thumbnail! - Also when the Edit form is open is it scrolled out of view by default. Maybe as a short term patch could the area auto scroll somehow to make sure the form area is in view? Would be best to just redesign this though in the long run imo. Thanks! Liz was (Author: uxdlc): [~yamer] I took a closer look and imo this needs it's own jira, to support a more comprehensive fix. But in the interim, unless I'm misunderstanding the interaction, it might help to: - When it's not in "edit mode" consider moving the "Add new item" directly below the last item in the list. - Consider renaming the action to "Add list value" or whatever most closely describes the action. - Consider making the font sizes the same within the dialog. The Name field looks too small, while the Edit name looks too large, while the "Add new item" looks about right. !Screen Shot 2020-01-30 at 1.24.18 PM.png|thumbnail! - Also when the Edit form is open is it scrolled out of view by default. Maybe as a short term patch could the area auto scroll somehow to make sure the form area is in view? Would be best to just redesign this though in the long run imo. Thanks! Liz > Buttons stay disabled when switching to textual collection editor > ----------------------------------------------------------------- > > Key: DROOLS-4972 > URL: https://issues.redhat.com/browse/DROOLS-4972 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.32.0.Final > Reporter: Jozef Marko > Assignee: Yeser Amer > Priority: Minor > Labels: drools-tools > Attachments: Screen Shot 2020-01-30 at 1.24.18 PM.png, define-list-and-save.webm > > > If user starts to create list using UI editor, then he decides to switch to textual editor - define list as expression, the buttons are disabled if user didn't canceled items 'in progress' in the UI editor. See the attached video. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4972) Buttons stay disabled when switching to textual collection editor

by Elizabeth Clayton (Jira)

[ https://issues.redhat.com/browse/DROOLS-4972?page=com.atlassian.jira.plug... ] Elizabeth Clayton edited comment on DROOLS-4972 at 1/30/20 1:32 PM: -------------------------------------------------------------------- [~yamer] I took a closer look and imo this needs it's own jira, to support a more comprehensive fix. But in the interim, unless I'm misunderstanding the interaction, it might help to: - When it's not in "edit mode" consider moving the "Add new item" directly below the last item in the list. - Consider renaming the action to "Add list value" or whatever most closely describes the action. - Consider making the font sizes the same within the dialog. The Name field looks too small, while the Edit name looks too large, while the "Add new item" looks about right. !Screen Shot 2020-01-30 at 1.24.18 PM.png|thumbnail! - Also when the Edit form is open is it scrolled out of view by default. Maybe as a short term patch could the area auto scroll somehow to make sure the form area is in view? Would be best to just redesign this though in the long run imo. Thanks! Liz was (Author: uxdlc): [~yamer] I took a closer look and imo this needs it's own jira, to support a more comprehensive fix. But in the interim, unless I'm misunderstanding the interaction, it might help to: - Move the "Add new item" directly below the last item in the list. - Consider renaming the action to "Add list value" or whatever most closely describes the action. - Consider making the font sizes the same within the dialog. The Name field looks too small, while the Edit name looks too large, while the "Add new item" looks about right. !Screen Shot 2020-01-30 at 1.24.18 PM.png|thumbnail! - Also when the Edit form is open is it scrolled out of view by default. Maybe as a short term patch could the area auto scroll somehow to make sure the form area is in view? Would be best to just redesign this though in the long run imo. Thanks! Liz > Buttons stay disabled when switching to textual collection editor > ----------------------------------------------------------------- > > Key: DROOLS-4972 > URL: https://issues.redhat.com/browse/DROOLS-4972 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.32.0.Final > Reporter: Jozef Marko > Assignee: Yeser Amer > Priority: Minor > Labels: drools-tools > Attachments: Screen Shot 2020-01-30 at 1.24.18 PM.png, define-list-and-save.webm > > > If user starts to create list using UI editor, then he decides to switch to textual editor - define list as expression, the buttons are disabled if user didn't canceled items 'in progress' in the UI editor. See the attached video. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4972) Buttons stay disabled when switching to textual collection editor

by Elizabeth Clayton (Jira)

[ https://issues.redhat.com/browse/DROOLS-4972?page=com.atlassian.jira.plug... ] Elizabeth Clayton updated DROOLS-4972: -------------------------------------- Attachment: Screen Shot 2020-01-30 at 1.24.18 PM.png > Buttons stay disabled when switching to textual collection editor > ----------------------------------------------------------------- > > Key: DROOLS-4972 > URL: https://issues.redhat.com/browse/DROOLS-4972 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.32.0.Final > Reporter: Jozef Marko > Assignee: Yeser Amer > Priority: Minor > Labels: drools-tools > Attachments: Screen Shot 2020-01-30 at 1.24.18 PM.png, define-list-and-save.webm > > > If user starts to create list using UI editor, then he decides to switch to textual editor - define list as expression, the buttons are disabled if user didn't canceled items 'in progress' in the UI editor. See the attached video. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4972) Buttons stay disabled when switching to textual collection editor

by Elizabeth Clayton (Jira)

[ https://issues.redhat.com/browse/DROOLS-4972?page=com.atlassian.jira.plug... ] Elizabeth Clayton commented on DROOLS-4972: ------------------------------------------- [~yamer] I took a closer look and imo this needs it's own jira, to support a more comprehensive fix. But in the interim, unless I'm misunderstanding the interaction, it might help to: - Move the "Add new item" directly below the last item in the list. - Consider renaming the action to "Add list value" or whatever most closely describes the action. - Consider making the font sizes the same within the dialog. The Name field looks too small, while the Edit name looks too large, while the "Add new item" looks about right. !Screen Shot 2020-01-30 at 1.24.18 PM.png|thumbnail! - Also when the Edit form is open is it scrolled out of view by default. Maybe as a short term patch could the area auto scroll somehow to make sure the form area is in view? Would be best to just redesign this though in the long run imo. Thanks! Liz > Buttons stay disabled when switching to textual collection editor > ----------------------------------------------------------------- > > Key: DROOLS-4972 > URL: https://issues.redhat.com/browse/DROOLS-4972 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.32.0.Final > Reporter: Jozef Marko > Assignee: Yeser Amer > Priority: Minor > Labels: drools-tools > Attachments: Screen Shot 2020-01-30 at 1.24.18 PM.png, define-list-and-save.webm > > > If user starts to create list using UI editor, then he decides to switch to textual editor - define list as expression, the buttons are disabled if user didn't canceled items 'in progress' in the UI editor. See the attached video. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

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

by Ilia Vassilev (Jira)

[ https://issues.redhat.com/browse/WFCORE-4820?page=com.atlassian.jira.plug... ] Ilia Vassilev updated WFCORE-4820: ---------------------------------- Labels: downstream_dependency (was: ) > Error: WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN) > ---------------------------------------------------------------------------------- > > Key: WFCORE-4820 > URL: https://issues.redhat.com/browse/WFCORE-4820 > Project: WildFly Core > Issue Type: Bug > Components: Management, Security > Affects Versions: 10.0.3.Final > Reporter: Mark Sanchez > Assignee: Darran Lofthouse > Priority: Major > Labels: downstream_dependency > Fix For: 11.0.0.Beta8 > > > 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, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4828) Errors Missing on Invalid Configuration

by James Perkins (Jira)

James Perkins created WFCORE-4828: ------------------------------------- Summary: Errors Missing on Invalid Configuration Key: WFCORE-4828 URL: https://issues.redhat.com/browse/WFCORE-4828 Project: WildFly Core Issue Type: Bug Components: Security Affects Versions: 11.0.0.Beta7 Reporter: Darran Lofthouse Assignee: Richard Opalka [~ropalka] I believe this is caused by the MSC refactoring. Steps, in the default host.xml for domain mode. 1. Define the following security realm: - {noformat} <security-realms> <security-realm name="ldap_security_realm"> <server-identities> <ssl> <keystore path="generated.keystore" relative-to="jboss.server.config.dir" keystore-password="password" alias="server" key-password="password" generate-self-signed-certificate-host="localhost"/> </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> {noformat} 2. Define the following outbound connection: - {noformat} <outbound-connections> <ldap name="testLdap" url="ldap://localhost:636" search-dn="CN=mxxxxxx,OU=GenericID,OU=testUsers,DC=testServices,DC=test,DC=com" search-credential="passowrd" /> </outbound-connections> {noformat} 3. Update the management interfaces to: - {noformat} <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> {noformat} The server fails to boot with just the following error: - {noformat} [Host Controller] 17:56:40,052 FATAL [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0034: Host Controller boot has failed in an unrecoverable manner; exiting. See previous messages for details. {noformat} If the management interface is then updated to reference the ManagementRealm instead the error is now: - {noformat} [Host Controller] 18:01:48,595 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ [Host Controller] ("host" => "master"), [Host Controller] ("core-service" => "management"), [Host Controller] ("security-realm" => "ldap_security_realm") [Host Controller] ]) - failure description: { [Host Controller] "WFLYCTL0412: Required services that are not installed:" => ["jboss.server.path.\"jboss.server.config.dir\""], [Host Controller] "WFLYCTL0180: Services with missing/unavailable dependencies" => ["org.wildfly.core.management.security.realm.ldap_security_realm.key-manager is missing [jboss.server.path.\"jboss.server.config.dir\"]"] [Host Controller] } {noformat} This error is expected as the realm defined in step 1 referenced an invalid path. I believe the error reporting should come from this method: - org.jboss.as.controller.ServiceVerificationHelper.execute(OperationContext, ModelNode) However something seems to have changes with the MSC migration. This was recently encountered debugging the bug report in https://issues.redhat.com/browse/WFCORE-4820, if you see an error "Multiple CallbackHandlerServices for the same mechanism (PLAIN)" that has been covered by WFCORE-4820. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4827) Errors Missing on Invalid Configuration

by Darran Lofthouse (Jira)

Darran Lofthouse created WFCORE-4827: ---------------------------------------- Summary: Errors Missing on Invalid Configuration Key: WFCORE-4827 URL: https://issues.redhat.com/browse/WFCORE-4827 Project: WildFly Core Issue Type: Bug Components: Security Affects Versions: 11.0.0.Beta7 Reporter: Darran Lofthouse Assignee: Richard Opalka [~ropalka] I believe this is caused by the MSC refactoring. Steps, in the default host.xml for domain mode. 1. Define the following security realm: - {noformat} <security-realms> <security-realm name="ldap_security_realm"> <server-identities> <ssl> <keystore path="generated.keystore" relative-to="jboss.server.config.dir" keystore-password="password" alias="server" key-password="password" generate-self-signed-certificate-host="localhost"/> </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> {noformat} 2. Define the following outbound connection: - {noformat} <outbound-connections> <ldap name="testLdap" url="ldap://localhost:636" search-dn="CN=mxxxxxx,OU=GenericID,OU=testUsers,DC=testServices,DC=test,DC=com" search-credential="passowrd" /> </outbound-connections> {noformat} 3. Update the management interfaces to: - {noformat} <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> {noformat} The server fails to boot with just the following error: - {noformat} [Host Controller] 17:56:40,052 FATAL [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0034: Host Controller boot has failed in an unrecoverable manner; exiting. See previous messages for details. {noformat} If the management interface is then updated to reference the ManagementRealm instead the error is now: - {noformat} [Host Controller] 18:01:48,595 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ [Host Controller] ("host" => "master"), [Host Controller] ("core-service" => "management"), [Host Controller] ("security-realm" => "ldap_security_realm") [Host Controller] ]) - failure description: { [Host Controller] "WFLYCTL0412: Required services that are not installed:" => ["jboss.server.path.\"jboss.server.config.dir\""], [Host Controller] "WFLYCTL0180: Services with missing/unavailable dependencies" => ["org.wildfly.core.management.security.realm.ldap_security_realm.key-manager is missing [jboss.server.path.\"jboss.server.config.dir\"]"] [Host Controller] } {noformat} This error is expected as the realm defined in step 1 referenced an invalid path. I believe the error reporting should come from this method: - org.jboss.as.controller.ServiceVerificationHelper.execute(OperationContext, ModelNode) However something seems to have changes with the MSC migration. This was recently encountered debugging the bug report in https://issues.redhat.com/browse/WFCORE-4820, if you see an error "Multiple CallbackHandlerServices for the same mechanism (PLAIN)" that has been covered by WFCORE-4820. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

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

by Mark Sanchez (Jira)

[ https://issues.redhat.com/browse/WFCORE-4820?page=com.atlassian.jira.plug... ] Mark Sanchez commented on WFCORE-4820: -------------------------------------- Darran, Is it possible for you to take our current configuration and map it to Elytron? It looks fairly complicated. Thanks Mark Sanchez > Error: WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN) > ---------------------------------------------------------------------------------- > > Key: WFCORE-4820 > URL: https://issues.redhat.com/browse/WFCORE-4820 > Project: WildFly Core > Issue Type: Bug > Components: Management, Security > Affects Versions: 10.0.3.Final > Reporter: Mark Sanchez > Assignee: Darran Lofthouse > Priority: Major > Fix For: 11.0.0.Beta8 > > > 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, 4 months

1
0
0 / 0

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

by James Perkins (Jira)

James Perkins created WFCORE-4826: ------------------------------------- Summary: Error: WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN) Key: WFCORE-4826 URL: https://issues.redhat.com/browse/WFCORE-4826 Project: WildFly Core Issue Type: Bug Components: Management, Security Affects Versions: 10.0.3.Final Reporter: Mark Sanchez Assignee: Darran Lofthouse Fix For: 11.0.0.Beta8 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, 4 months

1
0
0 / 0

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

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFCORE-4820?page=com.atlassian.jira.plug... ] Darran Lofthouse updated WFCORE-4820: ------------------------------------- Fix Version/s: 11.0.0.Beta8 > Error: WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN) > ---------------------------------------------------------------------------------- > > Key: WFCORE-4820 > URL: https://issues.redhat.com/browse/WFCORE-4820 > Project: WildFly Core > Issue Type: Bug > Components: Management, Security > Affects Versions: 10.0.3.Final > Reporter: Mark Sanchez > Assignee: Darran Lofthouse > Priority: Major > Fix For: 11.0.0.Beta8 > > > 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, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13042) Jaeger tracer sender-binding isn't configurable

by Emmanuel Hugonnet (Jira)

[ https://issues.redhat.com/browse/WFLY-13042?page=com.atlassian.jira.plugi... ] Emmanuel Hugonnet updated WFLY-13042: ------------------------------------- Priority: Blocker (was: Major) > Jaeger tracer sender-binding isn't configurable > ----------------------------------------------- > > Key: WFLY-13042 > URL: https://issues.redhat.com/browse/WFLY-13042 > Project: WildFly > Issue Type: Bug > Components: MP OpenTracing > Affects Versions: 19.0.0.Beta1 > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Priority: Blocker > > When configuring a jaeger tracer sender-binding parameter the server will no longer boot because of a NullPointerException in JaegerTracerConfiguration -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13042) Jaeger tracer sender-binding isn't configurable

by Emmanuel Hugonnet (Jira)

[ https://issues.redhat.com/browse/WFLY-13042?page=com.atlassian.jira.plugi... ] Emmanuel Hugonnet updated WFLY-13042: ------------------------------------- Description: When configuring a jaeger tracer sender-binding parameter the server will no longer boot because of a NullPointerException in JaegerTracerConfiguration thus failing the boot of the server. (was: When configuring a jaeger tracer sender-binding parameter the server will no longer boot because of a NullPointerException in JaegerTracerConfiguration) > Jaeger tracer sender-binding isn't configurable > ----------------------------------------------- > > Key: WFLY-13042 > URL: https://issues.redhat.com/browse/WFLY-13042 > Project: WildFly > Issue Type: Bug > Components: MP OpenTracing > Affects Versions: 19.0.0.Beta1 > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Priority: Blocker > > When configuring a jaeger tracer sender-binding parameter the server will no longer boot because of a NullPointerException in JaegerTracerConfiguration thus failing the boot of the server. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13042) Jaeger tracer sender-binding isn't configurable

by Emmanuel Hugonnet (Jira)

Emmanuel Hugonnet created WFLY-13042: ---------------------------------------- Summary: Jaeger tracer sender-binding isn't configurable Key: WFLY-13042 URL: https://issues.redhat.com/browse/WFLY-13042 Project: WildFly Issue Type: Bug Components: MP OpenTracing Affects Versions: 19.0.0.Beta1 Reporter: Emmanuel Hugonnet Assignee: Emmanuel Hugonnet When configuring a jaeger tracer sender-binding parameter the server will no longer boot because of a NullPointerException in JaegerTracerConfiguration -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

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

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFCORE-4820?page=com.atlassian.jira.plug... ] Darran Lofthouse updated WFCORE-4820: ------------------------------------- Steps to Reproduce: *Scenario One* The minimal steps to reproduce are to add the following entries to the default host.xml and then start domain mode. {noformat} <security-realm name="ldap_security_realm"> <authentication> <ldap connection="testLdap" base-dn="dc=test,dc=sbc,dc=com" recursive="true"> <username-filter attribute="samaccountname"/> </ldap> </authentication> </security-realm> <outbound-connections> <ldap name="testLdap" url="ldap://localhost:636" search-dn="CN=mxxxxxx,OU=GenericID,OU=testUsers,DC=testServices,DC=test,DC=com" search-credential="passowrd" /> </outbound-connections> {noformat} This results in the error: - {noformat} [Host Controller] 17:05:25,154 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service org.wildfly.core.management.security.realm.ldap_security_realm: org.jboss.msc.service.StartException in service org.wildfly.core.management.security.realm.ldap_security_realm: WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN) [Host Controller] at org.jboss.as.domain.management.security.SecurityRealmService.start(SecurityRealmService.java:226) [Host Controller] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739) {noformat} *Scenario Two* A second scenario can be triggerd by defining the security realm as: - {noformat} <security-realm name="ldap_security_realm"> <server-identities> <ssl> <keystore path="generated.keystore" relative-to="jboss.server.config.dir" keystore-password="password" alias="server" key-password="password" generate-self-signed-certificate-host="localhost"/> </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> {noformat} With the same outbound connection as in the first scenario. The management-interfaces should be updated to: - {noformat} <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> {noformat} This results in no clear error. {noformat} [Host Controller] 17:09:12,854 FATAL [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0034: Host Controller boot has failed in an unrecoverable manner; exiting. See previous messages for details. {noformat} This scenario should actually be logging an error similar to the following as the realm is referencing a path which is not defined. {noformat} [Host Controller] 17:08:41,763 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ [Host Controller] ("host" => "master"), [Host Controller] ("core-service" => "management"), [Host Controller] ("security-realm" => "ldap_security_realm") [Host Controller] ]) - failure description: { [Host Controller] "WFLYCTL0412: Required services that are not installed:" => ["jboss.server.path.\"jboss.server.config.dir\""], [Host Controller] "WFLYCTL0180: Services with missing/unavailable dependencies" => ["org.wildfly.core.management.security.realm.ldap_security_realm.key-manager is missing [jboss.server.path.\"jboss.server.config.dir\"]"] {noformat} In the last scenario if jboss.server.config.dir is replaced with jboss.domain.config.dir in the realm then the error reported in the first scenario is again reported. was: *Scenario One* The minimal steps to reproduce are to add the following entries to the default host.xml and then start domain mode. {noformat} <security-realm name="ldap_security_realm"> <authentication> <ldap connection="testLdap" base-dn="dc=test,dc=sbc,dc=com" recursive="true"> <username-filter attribute="samaccountname"/> </ldap> </authentication> </security-realm> <outbound-connections> <ldap name="testLdap" url="ldap://localhost:636" search-dn="CN=mxxxxxx,OU=GenericID,OU=testUsers,DC=testServices,DC=test,DC=com" search-credential="passowrd" /> </outbound-connections> {noformat} This results in the error: - {noformat} [Host Controller] 17:05:25,154 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service org.wildfly.core.management.security.realm.ldap_security_realm: org.jboss.msc.service.StartException in service org.wildfly.core.management.security.realm.ldap_security_realm: WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN) [Host Controller] at org.jboss.as.domain.management.security.SecurityRealmService.start(SecurityRealmService.java:226) [Host Controller] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739) {noformat} *Scenario Two* A second scenario can be triggerd by defining the security realm as: - {noformat} <security-realm name="ldap_security_realm"> <server-identities> <ssl> <keystore path="generated.keystore" relative-to="jboss.server.config.dir" keystore-password="password" alias="server" key-password="password" generate-self-signed-certificate-host="localhost"/> </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> {noformat} With the same outbound connection as in the first scenario. The management-interfaces should be updated to: - {noformat} <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> {noformat} This results in no clear error. {noformat} [Host Controller] 17:09:12,854 FATAL [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0034: Host Controller boot has failed in an unrecoverable manner; exiting. See previous messages for details. {noformat} This scenario should actually be logging an error similar to the following as the realm is referencing a path which is not defined. {noformat} [Host Controller] 17:08:41,763 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ [Host Controller] ("host" => "master"), [Host Controller] ("core-service" => "management"), [Host Controller] ("security-realm" => "ldap_security_realm") [Host Controller] ]) - failure description: { [Host Controller] "WFLYCTL0412: Required services that are not installed:" => ["jboss.server.path.\"jboss.server.config.dir\""], [Host Controller] "WFLYCTL0180: Services with missing/unavailable dependencies" => ["org.wildfly.core.management.security.realm.ldap_security_realm.key-manager is missing [jboss.server.path.\"jboss.server.config.dir\"]"] {noformat} > Error: WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN) > ---------------------------------------------------------------------------------- > > Key: WFCORE-4820 > URL: https://issues.redhat.com/browse/WFCORE-4820 > Project: WildFly Core > Issue Type: Bug > Components: Management, Security > Affects Versions: 10.0.3.Final > Reporter: Mark Sanchez > Assignee: Darran Lofthouse > Priority: Major > > 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, 4 months

1
0
0 / 0

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

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFCORE-4820?page=com.atlassian.jira.plug... ] Darran Lofthouse updated WFCORE-4820: ------------------------------------- Steps to Reproduce: *Scenario One* The minimal steps to reproduce are to add the following entries to the default host.xml and then start domain mode. {noformat} <security-realm name="ldap_security_realm"> <authentication> <ldap connection="testLdap" base-dn="dc=test,dc=sbc,dc=com" recursive="true"> <username-filter attribute="samaccountname"/> </ldap> </authentication> </security-realm> <outbound-connections> <ldap name="testLdap" url="ldap://localhost:636" search-dn="CN=mxxxxxx,OU=GenericID,OU=testUsers,DC=testServices,DC=test,DC=com" search-credential="passowrd" /> </outbound-connections> {noformat} This results in the error: - {noformat} [Host Controller] 17:05:25,154 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service org.wildfly.core.management.security.realm.ldap_security_realm: org.jboss.msc.service.StartException in service org.wildfly.core.management.security.realm.ldap_security_realm: WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN) [Host Controller] at org.jboss.as.domain.management.security.SecurityRealmService.start(SecurityRealmService.java:226) [Host Controller] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739) {noformat} *Scenario Two* A second scenario can be triggerd by defining the security realm as: - {noformat} <security-realm name="ldap_security_realm"> <server-identities> <ssl> <keystore path="generated.keystore" relative-to="jboss.server.config.dir" keystore-password="password" alias="server" key-password="password" generate-self-signed-certificate-host="localhost"/> </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> {noformat} With the same outbound connection as in the first scenario. The management-interfaces should be updated to: - {noformat} <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> {noformat} This results in no clear error. {noformat} [Host Controller] 17:09:12,854 FATAL [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0034: Host Controller boot has failed in an unrecoverable manner; exiting. See previous messages for details. {noformat} This scenario should actually be logging an error similar to the following as the realm is referencing a path which is not defined. {noformat} [Host Controller] 17:08:41,763 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ [Host Controller] ("host" => "master"), [Host Controller] ("core-service" => "management"), [Host Controller] ("security-realm" => "ldap_security_realm") [Host Controller] ]) - failure description: { [Host Controller] "WFLYCTL0412: Required services that are not installed:" => ["jboss.server.path.\"jboss.server.config.dir\""], [Host Controller] "WFLYCTL0180: Services with missing/unavailable dependencies" => ["org.wildfly.core.management.security.realm.ldap_security_realm.key-manager is missing [jboss.server.path.\"jboss.server.config.dir\"]"] {noformat} was: *Scenario One* The minimal steps to reproduce are to add the following entries to the default host.xml and then start domain mode. {noformat} <security-realm name="ldap_security_realm"> <authentication> <ldap connection="testLdap" base-dn="dc=test,dc=sbc,dc=com" recursive="true"> <username-filter attribute="samaccountname"/> </ldap> </authentication> </security-realm> <outbound-connections> <ldap name="testLdap" url="ldap://localhost:636" search-dn="CN=mxxxxxx,OU=GenericID,OU=testUsers,DC=testServices,DC=test,DC=com" search-credential="passowrd" /> </outbound-connections> {noformat} This results in the error: - {noformat} [Host Controller] 17:05:25,154 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service org.wildfly.core.management.security.realm.ldap_security_realm: org.jboss.msc.service.StartException in service org.wildfly.core.management.security.realm.ldap_security_realm: WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN) [Host Controller] at org.jboss.as.domain.management.security.SecurityRealmService.start(SecurityRealmService.java:226) [Host Controller] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739) {noformat} *Scenario Two* A second scenario can be triggerd by defining the security realm as: - {noformat} <security-realm name="ldap_security_realm"> <server-identities> <ssl> <keystore path="generated.keystore" relative-to="jboss.server.config.dir" keystore-password="password" alias="server" key-password="password" generate-self-signed-certificate-host="localhost"/> </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> {noformat} With the same outbound connection as in the first scenario. The management-interfaces should be updated to: - {noformat} <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> {noformat} This results in no clear error. {noformat} [Host Controller] 17:09:12,854 FATAL [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0034: Host Controller boot has failed in an unrecoverable manner; exiting. See previous messages for details. {noformat} > Error: WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN) > ---------------------------------------------------------------------------------- > > Key: WFCORE-4820 > URL: https://issues.redhat.com/browse/WFCORE-4820 > Project: WildFly Core > Issue Type: Bug > Components: Management, Security > Affects Versions: 10.0.3.Final > Reporter: Mark Sanchez > Assignee: Darran Lofthouse > Priority: Major > > 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2441) Changes to MembershipListener, StateListener, MessageListener

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2441?page=com.atlassian.jira.plugin... ] Bela Ban edited comment on JGRP-2441 at 1/30/20 12:13 PM: ---------------------------------------------------------- * Merged all {{X}} Listener interfaces into {{Receiver}} * Removed {{ReceiverAdapter}} ({{Receiver}} has default methods) * Removed {{suspect()}}: this method is only an indication that a member is suspected, and as such not very useful. The subsequent {{View}} is what counts. * Replaced {{MessageListener}}, {{MembershipListener}} and {{StateListener}} with {{Receiver}} was (Author: belaban): * Merged all {{X}} Listener interfaces into {{Receiver}} * Removed {{ReceiverAdapter}} ({{Receiver}} has default methods) * Removed {{suspect()}}: this method is only an indication that a member is suspected, and as such not very useful. The subsequent {{View}} is what counts. > Changes to MembershipListener,StateListener,MessageListener > ----------------------------------------------------------- > > Key: JGRP-2441 > URL: https://issues.redhat.com/browse/JGRP-2441 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 5.0 > > > Investigate > * Why is MessageListener still needed? Can't we just use {{Receiver}}? > * Why does {{MessageListener}} subclass {{StateListener}}? > * Are callbacks {{block()}}, {{unblock()}} and {{suspect()}} still needed? -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

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

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFCORE-4820?page=com.atlassian.jira.plug... ] Darran Lofthouse updated WFCORE-4820: ------------------------------------- Steps to Reproduce: *Scenario One* The minimal steps to reproduce are to add the following entries to the default host.xml and then start domain mode. {noformat} <security-realm name="ldap_security_realm"> <authentication> <ldap connection="testLdap" base-dn="dc=test,dc=sbc,dc=com" recursive="true"> <username-filter attribute="samaccountname"/> </ldap> </authentication> </security-realm> <outbound-connections> <ldap name="testLdap" url="ldap://localhost:636" search-dn="CN=mxxxxxx,OU=GenericID,OU=testUsers,DC=testServices,DC=test,DC=com" search-credential="passowrd" /> </outbound-connections> {noformat} This results in the error: - {noformat} [Host Controller] 17:05:25,154 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service org.wildfly.core.management.security.realm.ldap_security_realm: org.jboss.msc.service.StartException in service org.wildfly.core.management.security.realm.ldap_security_realm: WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN) [Host Controller] at org.jboss.as.domain.management.security.SecurityRealmService.start(SecurityRealmService.java:226) [Host Controller] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739) {noformat} *Scenario Two* A second scenario can be triggerd by defining the security realm as: - {noformat} <security-realm name="ldap_security_realm"> <server-identities> <ssl> <keystore path="generated.keystore" relative-to="jboss.server.config.dir" keystore-password="password" alias="server" key-password="password" generate-self-signed-certificate-host="localhost"/> </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> {noformat} With the same outbound connection as in the first scenario. The management-interfaces should be updated to: - {noformat} <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> {noformat} This results in no clear error. {noformat} [Host Controller] 17:09:12,854 FATAL [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0034: Host Controller boot has failed in an unrecoverable manner; exiting. See previous messages for details. {noformat} was: The minimal steps to reproduce are to add the following entries to the default host.xml and then start domain mode. {noformat} <security-realm name="ldap_security_realm"> <authentication> <ldap connection="testLdap" base-dn="dc=test,dc=sbc,dc=com" recursive="true"> <username-filter attribute="samaccountname"/> </ldap> </authentication> </security-realm> <outbound-connections> <ldap name="testLdap" url="ldap://localhost:636" search-dn="CN=mxxxxxx,OU=GenericID,OU=testUsers,DC=testServices,DC=test,DC=com" search-credential="passowrd" /> </outbound-connections> {noformat} This results in the error: - {noformat} [Host Controller] 17:05:25,154 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service org.wildfly.core.management.security.realm.ldap_security_realm: org.jboss.msc.service.StartException in service org.wildfly.core.management.security.realm.ldap_security_realm: WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN) [Host Controller] at org.jboss.as.domain.management.security.SecurityRealmService.start(SecurityRealmService.java:226) [Host Controller] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739) {noformat} > Error: WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN) > ---------------------------------------------------------------------------------- > > Key: WFCORE-4820 > URL: https://issues.redhat.com/browse/WFCORE-4820 > Project: WildFly Core > Issue Type: Bug > Components: Management, Security > Affects Versions: 10.0.3.Final > Reporter: Mark Sanchez > Assignee: Darran Lofthouse > Priority: Major > > 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, 4 months

1
0
0 / 0

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

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFCORE-4820?page=com.atlassian.jira.plug... ] Darran Lofthouse updated WFCORE-4820: ------------------------------------- Steps to Reproduce: The minimal steps to reproduce are to add the following entries to the default host.xml and then start domain mode. {noformat} <security-realm name="ldap_security_realm">  <authentication> <ldap connection="testLdap" base-dn="dc=test,dc=sbc,dc=com" recursive="true"> <username-filter attribute="samaccountname"/> </ldap> </authentication> </security-realm> <outbound-connections> <ldap name="testLdap" url="ldap://localhost:636" search-dn="CN=mxxxxxx,OU=GenericID,OU=testUsers,DC=testServices,DC=test,DC=com" search-credential="passowrd" /> </outbound-connections> {noformat} This results in the error: - {noformat} [Host Controller] 17:05:25,154 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service org.wildfly.core.management.security.realm.ldap_security_realm: org.jboss.msc.service.StartException in service org.wildfly.core.management.security.realm.ldap_security_realm: WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN) [Host Controller] at org.jboss.as.domain.management.security.SecurityRealmService.start(SecurityRealmService.java:226) [Host Controller] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739) {noformat} > Error: WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN) > ---------------------------------------------------------------------------------- > > Key: WFCORE-4820 > URL: https://issues.redhat.com/browse/WFCORE-4820 > Project: WildFly Core > Issue Type: Bug > Components: Management, Security > Affects Versions: 10.0.3.Final > Reporter: Mark Sanchez > Assignee: Darran Lofthouse > Priority: Major > > 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, 4 months

1
0
0 / 0

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

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFCORE-4820?page=com.atlassian.jira.plug... ] Darran Lofthouse updated WFCORE-4820: ------------------------------------- Steps to Reproduce: The minimal steps to reproduce are to add the following entries to the default host.xml and then start domain mode. {noformat} <security-realm name="ldap_security_realm"> <authentication> <ldap connection="testLdap" base-dn="dc=test,dc=sbc,dc=com" recursive="true"> <username-filter attribute="samaccountname"/> </ldap> </authentication> </security-realm> <outbound-connections> <ldap name="testLdap" url="ldap://localhost:636" search-dn="CN=mxxxxxx,OU=GenericID,OU=testUsers,DC=testServices,DC=test,DC=com" search-credential="passowrd" /> </outbound-connections> {noformat} This results in the error: - {noformat} [Host Controller] 17:05:25,154 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service org.wildfly.core.management.security.realm.ldap_security_realm: org.jboss.msc.service.StartException in service org.wildfly.core.management.security.realm.ldap_security_realm: WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN) [Host Controller] at org.jboss.as.domain.management.security.SecurityRealmService.start(SecurityRealmService.java:226) [Host Controller] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739) {noformat} was: The minimal steps to reproduce are to add the following entries to the default host.xml and then start domain mode. {noformat} <security-realm name="ldap_security_realm">  <authentication> <ldap connection="testLdap" base-dn="dc=test,dc=sbc,dc=com" recursive="true"> <username-filter attribute="samaccountname"/> </ldap> </authentication> </security-realm> <outbound-connections> <ldap name="testLdap" url="ldap://localhost:636" search-dn="CN=mxxxxxx,OU=GenericID,OU=testUsers,DC=testServices,DC=test,DC=com" search-credential="passowrd" /> </outbound-connections> {noformat} This results in the error: - {noformat} [Host Controller] 17:05:25,154 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service org.wildfly.core.management.security.realm.ldap_security_realm: org.jboss.msc.service.StartException in service org.wildfly.core.management.security.realm.ldap_security_realm: WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN) [Host Controller] at org.jboss.as.domain.management.security.SecurityRealmService.start(SecurityRealmService.java:226) [Host Controller] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739) {noformat} > Error: WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN) > ---------------------------------------------------------------------------------- > > Key: WFCORE-4820 > URL: https://issues.redhat.com/browse/WFCORE-4820 > Project: WildFly Core > Issue Type: Bug > Components: Management, Security > Affects Versions: 10.0.3.Final > Reporter: Mark Sanchez > Assignee: Darran Lofthouse > Priority: Major > > 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2441) Changes to MembershipListener, StateListener, MessageListener

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2441?page=com.atlassian.jira.plugin... ] Bela Ban edited comment on JGRP-2441 at 1/30/20 11:37 AM: ---------------------------------------------------------- * Merged all {{X}} Listener interfaces into {{Receiver}} * Removed {{ReceiverAdapter}} ({{Receiver}} has default methods) * Removed {{suspect()}}: this method is only an indication that a member is suspected, and as such not very useful. The subsequent {{View}} is what counts. was (Author: belaban): * Merged all {{X}}Listener interfaces into {{Receiver}} * Removed {{ReceiverAdapter}} ({{Receiver}} has default methods) > Changes to MembershipListener,StateListener,MessageListener > ----------------------------------------------------------- > > Key: JGRP-2441 > URL: https://issues.redhat.com/browse/JGRP-2441 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 5.0 > > > Investigate > * Why is MessageListener still needed? Can't we just use {{Receiver}}? > * Why does {{MessageListener}} subclass {{StateListener}}? > * Are callbacks {{block()}}, {{unblock()}} and {{suspect()}} still needed? -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2441) Changes to MembershipListener, StateListener, MessageListener

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2441?page=com.atlassian.jira.plugin... ] Bela Ban commented on JGRP-2441: -------------------------------- * Merged all {{X}}Listener interfaces into {{Receiver}} * Removed {{ReceiverAdapter}} ({{Receiver}} has default methods) > Changes to MembershipListener,StateListener,MessageListener > ----------------------------------------------------------- > > Key: JGRP-2441 > URL: https://issues.redhat.com/browse/JGRP-2441 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 5.0 > > > Investigate > * Why is MessageListener still needed? Can't we just use {{Receiver}}? > * Why does {{MessageListener}} subclass {{StateListener}}? > * Are callbacks {{block()}}, {{unblock()}} and {{suspect()}} still needed? -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

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

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFCORE-4820?page=com.atlassian.jira.plug... ] Darran Lofthouse commented on WFCORE-4820: ------------------------------------------ At the moment this does seem to be broken in WildFly 18 with the only workaround being migrating to an Elytron based configuration - presently looking at options for a fix in WildFly 19. > Error: WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN) > ---------------------------------------------------------------------------------- > > Key: WFCORE-4820 > URL: https://issues.redhat.com/browse/WFCORE-4820 > Project: WildFly Core > Issue Type: Bug > Components: Management, Security > Affects Versions: 10.0.3.Final > Reporter: Mark Sanchez > Assignee: Darran Lofthouse > Priority: Major > > 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, 4 months

1
0
0 / 0

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

by Mark Sanchez (Jira)

[ https://issues.redhat.com/browse/WFCORE-4820?page=com.atlassian.jira.plug... ] Mark Sanchez commented on WFCORE-4820: -------------------------------------- Any Status? > Error: WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN) > ---------------------------------------------------------------------------------- > > Key: WFCORE-4820 > URL: https://issues.redhat.com/browse/WFCORE-4820 > Project: WildFly Core > Issue Type: Bug > Components: Management, Security > Affects Versions: 10.0.3.Final > Reporter: Mark Sanchez > Assignee: Darran Lofthouse > Priority: Major > > 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, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4972) Buttons stay disabled when switching to textual collection editor

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-4972?page=com.atlassian.jira.plug... ] Yeser Amer updated DROOLS-4972: ------------------------------- Story Points: 1 > Buttons stay disabled when switching to textual collection editor > ----------------------------------------------------------------- > > Key: DROOLS-4972 > URL: https://issues.redhat.com/browse/DROOLS-4972 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.32.0.Final > Reporter: Jozef Marko > Assignee: Yeser Amer > Priority: Minor > Labels: drools-tools > Attachments: define-list-and-save.webm > > > If user starts to create list using UI editor, then he decides to switch to textual editor - define list as expression, the buttons are disabled if user didn't canceled items 'in progress' in the UI editor. See the attached video. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4988) Test Scenario: improve DMN validation

by Daniele Zonca (Jira)

[ https://issues.redhat.com/browse/DROOLS-4988?page=com.atlassian.jira.plug... ] Daniele Zonca updated DROOLS-4988: ---------------------------------- Description: Add a check to verify if a simple type has been changed to a structured type. Please consider expression columns too (was: Add a check to verify if a simple type has been changed to a complex type. Please consider expression columns too) > Test Scenario: improve DMN validation > ------------------------------------- > > Key: DROOLS-4988 > URL: https://issues.redhat.com/browse/DROOLS-4988 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Yeser Amer > Priority: Major > Labels: drools-tools > > Add a check to verify if a simple type has been changed to a structured type. Please consider expression columns too -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4988) Test Scenario: improve DMN validation

by Daniele Zonca (Jira)

[ https://issues.redhat.com/browse/DROOLS-4988?page=com.atlassian.jira.plug... ] Daniele Zonca commented on DROOLS-4988: --------------------------------------- Updated :) > Test Scenario: improve DMN validation > ------------------------------------- > > Key: DROOLS-4988 > URL: https://issues.redhat.com/browse/DROOLS-4988 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Yeser Amer > Priority: Major > Labels: drools-tools > > Add a check to verify if a simple type has been changed to a structured type. Please consider expression columns too -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12659) Creation of a GUI for multi-version test distribution across different Multi-version Testsuites (EAT, etc)

by Panagiotis Sotiropoulos (Jira)

[ https://issues.redhat.com/browse/WFLY-12659?page=com.atlassian.jira.plugi... ] Panagiotis Sotiropoulos commented on WFLY-12659: ------------------------------------------------ A first version is done. Resolving it ... > Creation of a GUI for multi-version test distribution across different Multi-version Testsuites (EAT,etc) > --------------------------------------------------------------------------------------------------------- > > Key: WFLY-12659 > URL: https://issues.redhat.com/browse/WFLY-12659 > Project: WildFly > Issue Type: Task > Components: Test Suite > Reporter: Panagiotis Sotiropoulos > Assignee: Panagiotis Sotiropoulos > Priority: Major > > Creation of a GUI for multi-version test distribution across different Multi-version Testsuites (EAT,etc) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4780) Stax maxAttributeSize is only vaguely respected

by Ivo Studensky (Jira)

[ https://issues.redhat.com/browse/WFCORE-4780?page=com.atlassian.jira.plug... ] Ivo Studensky resolved WFCORE-4780. ----------------------------------- Resolution: Done > Stax maxAttributeSize is only vaguely respected > ----------------------------------------------- > > Key: WFCORE-4780 > URL: https://issues.redhat.com/browse/WFCORE-4780 > Project: WildFly Core > Issue Type: Bug > Reporter: Ilia Vassilev > Assignee: Ivo Studensky > Priority: Major > > System property org.apache.cxf.stax.maxAttributeSize only vaguely limits attribute values. If I set the property to 5000 I can send up to 8295 characters in an attribute value without EAP denying the request. > Reviewing the source code for woodstox reveal that the limit is checked against the size of the buffer before the last buffer expansion. After 2459 characters the buffer is grown to 3687. After 5531 characters the limit is checked against 3687 instead of 5531 and not until 8296 characters is the limit checked against the previous buffer size 5531 which is larger than 5000. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4825) Upgrade Undertow to 2.0.30.Final

by Bartosz Spyrko (Jira)

[ https://issues.redhat.com/browse/WFCORE-4825?page=com.atlassian.jira.plug... ] Bartosz Spyrko updated WFCORE-4825: ----------------------------------- Fix Version/s: (was: 11.0.0.Beta6) > Upgrade Undertow to 2.0.30.Final > -------------------------------- > > Key: WFCORE-4825 > URL: https://issues.redhat.com/browse/WFCORE-4825 > Project: WildFly Core > Issue Type: Component Upgrade > Reporter: Bartosz Spyrko > Assignee: Flavia Rainone > Priority: Major > Labels: downstream_dependency > > Upgrade Undertow to 2.0.29.Final -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4825) Upgrade Undertow to 2.0.30.Final

by Bartosz Spyrko (Jira)

[ https://issues.redhat.com/browse/WFCORE-4825?page=com.atlassian.jira.plug... ] Bartosz Spyrko updated WFCORE-4825: ----------------------------------- Labels: downstream_dependency (was: ) > Upgrade Undertow to 2.0.30.Final > -------------------------------- > > Key: WFCORE-4825 > URL: https://issues.redhat.com/browse/WFCORE-4825 > Project: WildFly Core > Issue Type: Component Upgrade > Reporter: Bartosz Spyrko > Assignee: Flavia Rainone > Priority: Major > Labels: downstream_dependency > > Upgrade Undertow to 2.0.29.Final -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4825) Upgrade Undertow to 2.0.30.Final

by Bartosz Spyrko (Jira)

Bartosz Spyrko created WFCORE-4825: -------------------------------------- Summary: Upgrade Undertow to 2.0.30.Final Key: WFCORE-4825 URL: https://issues.redhat.com/browse/WFCORE-4825 Project: WildFly Core Issue Type: Component Upgrade Reporter: Bartosz Spyrko Assignee: Flavia Rainone Fix For: 11.0.0.Beta6 Upgrade Undertow to 2.0.29.Final -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4824) Upgrade JBoss Modules from 1.9.2 to 1.9.3

by Bartosz Spyrko (Jira)

[ https://issues.redhat.com/browse/WFCORE-4824?page=com.atlassian.jira.plug... ] Bartosz Spyrko updated WFCORE-4824: ----------------------------------- Component/s: Modules (was: Build System) > Upgrade JBoss Modules from 1.9.2 to 1.9.3 > ----------------------------------------- > > Key: WFCORE-4824 > URL: https://issues.redhat.com/browse/WFCORE-4824 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Modules > Reporter: Bartosz Spyrko > Assignee: Ingo Weiss > Priority: Major > Labels: downstream_dependency > > Diff: https://github.com/jboss-modules/jboss-modules/compare/1.9.1.Final...1.9 > Tag: -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4824) Upgrade JBoss Modules from 1.9.2 to 1.9.3

by Bartosz Spyrko (Jira)

[ https://issues.redhat.com/browse/WFCORE-4824?page=com.atlassian.jira.plug... ] Bartosz Spyrko reassigned WFCORE-4824: -------------------------------------- Assignee: Richard Opalka (was: Ingo Weiss) > Upgrade JBoss Modules from 1.9.2 to 1.9.3 > ----------------------------------------- > > Key: WFCORE-4824 > URL: https://issues.redhat.com/browse/WFCORE-4824 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Modules > Reporter: Bartosz Spyrko > Assignee: Richard Opalka > Priority: Major > Labels: downstream_dependency > > Diff: https://github.com/jboss-modules/jboss-modules/compare/1.9.1.Final...1.9 > Tag: -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4824) Upgrade JBoss Modules from 1.9.2 to 1.9.3

by Bartosz Spyrko (Jira)

[ https://issues.redhat.com/browse/WFCORE-4824?page=com.atlassian.jira.plug... ] Bartosz Spyrko moved JBEAP-18597 to WFCORE-4824: ------------------------------------------------ Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-4824 (was: JBEAP-18597) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Build System (was: Build System) Affects Version/s: (was: 7.2.1.GA) Fix Version/s: (was: 7.3.1.GA) > Upgrade JBoss Modules from 1.9.2 to 1.9.3 > ----------------------------------------- > > Key: WFCORE-4824 > URL: https://issues.redhat.com/browse/WFCORE-4824 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Build System > Reporter: Bartosz Spyrko > Assignee: Ingo Weiss > Priority: Major > Labels: downstream_dependency > > Diff: https://github.com/jboss-modules/jboss-modules/compare/1.9.1.Final...1.9 > Tag: -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4989) [DMN Designer] Tab content background colour consistency

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-4989?page=com.atlassian.jira.plug... ] Michael Anstis updated DROOLS-4989: ----------------------------------- Story Points: 3 Sprint: 2020 Week 04-06 (from Jan 20) > [DMN Designer] Tab content background colour consistency > -------------------------------------------------------- > > Key: DROOLS-4989 > URL: https://issues.redhat.com/browse/DROOLS-4989 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Michael Anstis > Priority: Minor > Labels: UX, drools-tools > > Filing a jira for an issue that [~kywalker] found - tab background colors are not consistent between tabs. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4988) Test Scenario: improve DMN validation

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-4988?page=com.atlassian.jira.plug... ] Jozef Marko commented on DROOLS-4988: ------------------------------------- May we please clarify what is complex type, is it just *Structure* or also *Collection* ? > Test Scenario: improve DMN validation > ------------------------------------- > > Key: DROOLS-4988 > URL: https://issues.redhat.com/browse/DROOLS-4988 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Yeser Amer > Priority: Major > Labels: drools-tools > > Add a check to verify if a simple type has been changed to a complex type. Please consider expression columns too -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2444) Remove ExecutionService

by Bela Ban (Jira)

Bela Ban created JGRP-2444: ------------------------------ Summary: Remove ExecutionService Key: JGRP-2444 URL: https://issues.redhat.com/browse/JGRP-2444 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Fix For: 5.0 Nobody uses it -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4991) JACCTranslateServletDDTestCase failures are intermittent on CI

by Moulali Shikalwadi (Jira)

[ https://issues.redhat.com/browse/WFLY-4991?page=com.atlassian.jira.plugin... ] Moulali Shikalwadi reassigned WFLY-4991: ---------------------------------------- Assignee: Moulali Shikalwadi > JACCTranslateServletDDTestCase failures are intermittent on CI > -------------------------------------------------------------- > > Key: WFLY-4991 > URL: https://issues.redhat.com/browse/WFLY-4991 > Project: WildFly > Issue Type: Bug > Components: Security, Test Suite > Reporter: James Perkins > Assignee: Moulali Shikalwadi > Priority: Major > Labels: testsuite_stability > > http://brontes.lab.eng.brq.redhat.com/project.html?projectId=WF_PullReque... > http://brontes.lab.eng.brq.redhat.com/project.html?projectId=WF_PullReque... > http://brontes.lab.eng.brq.redhat.com/project.html?projectId=WF_PullReque... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4990) JACCForEarModulesTestCase failures are intermittent on CI

by Moulali Shikalwadi (Jira)

[ https://issues.redhat.com/browse/WFLY-4990?page=com.atlassian.jira.plugin... ] Moulali Shikalwadi reassigned WFLY-4990: ---------------------------------------- Assignee: Moulali Shikalwadi > JACCForEarModulesTestCase failures are intermittent on CI > --------------------------------------------------------- > > Key: WFLY-4990 > URL: https://issues.redhat.com/browse/WFLY-4990 > Project: WildFly > Issue Type: Bug > Components: Security, Test Suite > Reporter: James Perkins > Assignee: Moulali Shikalwadi > Priority: Major > Labels: testsuite_stability > > http://brontes.lab.eng.brq.redhat.com/project.html?projectId=WF_PullReque... > http://brontes.lab.eng.brq.redhat.com/project.html?projectId=WF_PullReque... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4905) [DMN Designer] Code Completion - Index all elements named by users

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-4905?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-4905: -------------------------------- Attachment: pick-option-move-to-other-grid.webm > [DMN Designer] Code Completion - Index all elements named by users > ------------------------------------------------------------------ > > Key: DROOLS-4905 > URL: https://issues.redhat.com/browse/DROOLS-4905 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > Attachments: pick-option-move-to-other-grid.webm > > > Create the infrastructure code that provided all elements named by the user. It will be called by the suggestion component. So users will be able to see as suggestions DRG Elements and Data Types. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2443) Merge ObjectMessage and ObjectMessageSerializable

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2443?page=com.atlassian.jira.plugin... ] Bela Ban resolved JGRP-2443. ---------------------------- Resolution: Done > Merge ObjectMessage and ObjectMessageSerializable > ------------------------------------------------- > > Key: JGRP-2443 > URL: https://issues.redhat.com/browse/JGRP-2443 > Project: JGroups > Issue Type: Enhancement > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 5.0 > > > {{ObjectMessage}} has an {{object}} as payload, {{ObjectMessageSerializable}} inherits this and adds {{serialized_obj}}. > The former has ~32 bytes in memory, the latter 40. > The goal is not to increase the size of {{ObjectMessage}} to 40. > Solution: > * Create an ObjectWrapper class, taking an object and a serialized_version > * This is used in the merged {{ObjectMessage}} class (size is still ~32 bytes) > * When we have a SizeStreamable object, we set it as payload, otherwise we create an {{ObjectWrapper}} and set it as object. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13041) Upgrade to Galleon 4.2.4

by Jean Francois Denise (Jira)

Jean Francois Denise created WFLY-13041: ------------------------------------------- Summary: Upgrade to Galleon 4.2.4 Key: WFLY-13041 URL: https://issues.redhat.com/browse/WFLY-13041 Project: WildFly Issue Type: Component Upgrade Components: Build System Reporter: Jean Francois Denise Assignee: Jean Francois Denise Both galleon-plugins and galleon. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4823) Upgrade to Galleon 4.2.4

by Jean Francois Denise (Jira)

Jean Francois Denise created WFCORE-4823: -------------------------------------------- Summary: Upgrade to Galleon 4.2.4 Key: WFCORE-4823 URL: https://issues.redhat.com/browse/WFCORE-4823 Project: WildFly Core Issue Type: Component Upgrade Components: Build System Reporter: Jean Francois Denise Assignee: Jean Francois Denise Both galleon-plugins and galleon. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13040) Global directory user experience improvements

by Martin Svehla (Jira)

Martin Svehla created WFLY-13040: ------------------------------------ Summary: Global directory user experience improvements Key: WFLY-13040 URL: https://issues.redhat.com/browse/WFLY-13040 Project: WildFly Issue Type: Feature Request Components: EE, Management Reporter: Martin Svehla Assignee: Brian Stansberry This is follow up issue for https://issues.redhat.com/browse/WFLY-1160. During development there were discussed few ways of improving user experience of global directory that weren't implemented as part of the original feature: 1. If some class from global directory throws an exception, it would be helpful is user was informed which jar contains this class. 2. If global directory contains corrupted jar file (e.g. text file which was renamed to .jar), deployment won't be successfully deployed. Server logs contains information that zip file could not be opened. Cli only prints out that deployment is missing dependencies - which isn't necessarily true. It's possible that deployment isn't missing any dependencies - in this case, it would be better just to display a warning that there is a corrupted jar in global directory. 3. It would be good if users could specify dependencies for their libraries, something like this: {code:java} /subsystem=ee/global-directory=my-common-libs:add(path=lib, relative-to=jboss.home.dir, dependencies=[{name=org.hibernate.something,export=true,import=false}]) {code} 4. If jar contains class that has same name and package as some java ee class, for example custom javax.ws.rs.client.Client, it can cause error during execution: {code:java} org.jboss.resteasy.spi.UnhandledException: java.lang.LinkageError: loader constraint violation: loader (instance of org/jboss/modules/ModuleClassLoader) previously initiated loading for a different type with name "javax/ws/rs/client/Client" {code} It would be better if user was informed about duplicity during deployment. 5. If global directory has following hierarchy: a/a.1.jar ---- A.class b/a.2.jar ---- A.class ---- B.class and class B uses A's feature that is only available in a.2.jar version of A.class then it fails during execution when class B tries to access this feature of class A (because class A is loaded from a.1.jar and A in a.2.jar is ignored). As before, it would be better if user was informed about presence of duplicate class A in global directory during deployment. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1059) Create Kiali-1.1 branch on upstream

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1059?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan reassigned SWSQE-1059: ------------------------------------- Assignee: Hayk Hovsepyan > Create Kiali-1.1 branch on upstream > ----------------------------------- > > Key: SWSQE-1059 > URL: https://issues.redhat.com/browse/SWSQE-1059 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1059) Create Kiali-1.1 branch on upstream

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1059?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan commented on SWSQE-1059: --------------------------------------- https://github.com/Kiali-QE/kiali-qe-python/tree/kiali-1.1 > Create Kiali-1.1 branch on upstream > ----------------------------------- > > Key: SWSQE-1059 > URL: https://issues.redhat.com/browse/SWSQE-1059 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4989) JACCAuthzPropagationTestCase failures are intermittent on CI

by Moulali Shikalwadi (Jira)

[ https://issues.redhat.com/browse/WFLY-4989?page=com.atlassian.jira.plugin... ] Moulali Shikalwadi reassigned WFLY-4989: ---------------------------------------- Assignee: Moulali Shikalwadi > JACCAuthzPropagationTestCase failures are intermittent on CI > ------------------------------------------------------------ > > Key: WFLY-4989 > URL: https://issues.redhat.com/browse/WFLY-4989 > Project: WildFly > Issue Type: Bug > Components: Security, Test Suite > Reporter: James Perkins > Assignee: Moulali Shikalwadi > Priority: Major > Labels: testsuite_stability > > http://brontes.lab.eng.brq.redhat.com/project.html?projectId=WF_PullReque... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11566) ConstraintDeclarationException on JAX-RS/EJB Methods with List/Set query parameter

by Guillaume Smet (Jira)

[ https://issues.redhat.com/browse/WFLY-11566?page=com.atlassian.jira.plugi... ] Guillaume Smet commented on WFLY-11566: --------------------------------------- [~tomekadamski] have you updated your PR? I don't see any test in it from a quick scan? What worries me in the attached case is that there's no test to check the constraints are enforced. We need for the app to start obviously but we also need to check that the constraints are properly enforced. Can you confirm that your added test is doing that? > ConstraintDeclarationException on JAX-RS/EJB Methods with List/Set query parameter > ---------------------------------------------------------------------------------- > > Key: WFLY-11566 > URL: https://issues.redhat.com/browse/WFLY-11566 > Project: WildFly > Issue Type: Bug > Components: Bean Validation, EJB, REST > Affects Versions: 14.0.0.Final, 15.0.1.Final > Reporter: Alexander Wagner > Assignee: Tomasz Adamski > Priority: Critical > Labels: downstream_dependency > Attachments: WFLY-11566-3.tar > > > You got an exception if you call methods on JAX-RS endpoints which are also e.g. a stateless EJB and have Set or List as query parameters. > As a workaround we use the "@Context UriInfo info" as parameter an read the parameter manually. As a downside this parameters are missing than in automated api generation with e.g. swagger. Without the @NotEmpty annotation it works fine. Without the generic type parameter ie just List it works fine. Making it a simple CDI bean makes it work fine. > This issue is caused by [commit - WFLY-9628 Allow to switch to Hibernate Validator 6.0 / Bean Validation 2.0|https://github.com/wildfly/wildfly/commit/02f230d91f55f86ee6cadf53832...] > Steps to reproduce: > {code:java} > @Stateless > @Path("/") > public class Resource { > @POST > @Path("put/list") > @Consumes(MediaType.APPLICATION_JSON) > public String putList(@NotEmpty List<String> a) { > return "Hello bars " + a.stream().collect(Collectors.joining(", ")); > } > } > {code} > {noformat} > [mkopecky@dhcp-10-40-5-71 bin]$ curl -d '["a","b","c"]' -H "Content-Type: application/json" -X POST http://localhost:8080/jaxrs-wf/put/list > javax.validation.ConstraintDeclarationException: HV000151: A method overriding another method must not redefine the parameter constraint configuration, but method Resource$$$view1#putList(List) redefines the configuration of Resource#putList(List). > [mkopecky@dhcp-10-40-5-71 bin]$ > {noformat} > {noformat} > javax.validation.ConstraintDeclarationException: HV000151: A method overriding another method must not redefine the parameter constraint configuration, but method Resource$$$view1#putList(List) redefines the configuration of Resource#putList(List). > at org.hibernate.validator.internal.metadata.aggregated.rule.OverridingMethodMustNotAlterParameterConstraints.apply(OverridingMethodMustNotAlterParameterConstraints.java:24) > at org.hibernate.validator.internal.metadata.aggregated.ExecutableMetaData$Builder.assertCorrectnessOfConfiguration(ExecutableMetaData.java:461) > at org.hibernate.validator.internal.metadata.aggregated.ExecutableMetaData$Builder.build(ExecutableMetaData.java:377) > at org.hibernate.validator.internal.metadata.aggregated.BeanMetaDataImpl$BuilderDelegate.build(BeanMetaDataImpl.java:788) > at org.hibernate.validator.internal.metadata.aggregated.BeanMetaDataImpl$BeanMetaDataBuilder.build(BeanMetaDataImpl.java:648) > at org.hibernate.validator.internal.metadata.BeanMetaDataManager.createBeanMetaData(BeanMetaDataManager.java:192) > at org.hibernate.validator.internal.metadata.BeanMetaDataManager.lambda$getBeanMetaData$0(BeanMetaDataManager.java:160) > at java.util.concurrent.ConcurrentMap.computeIfAbsent(ConcurrentMap.java:324) > at org.hibernate.validator.internal.metadata.BeanMetaDataManager.getBeanMetaData(BeanMetaDataManager.java:159) > at org.hibernate.validator.internal.engine.ValidationContext$ValidationContextBuilder.forValidateParameters(ValidationContext.java:619) > at org.hibernate.validator.internal.engine.ValidatorImpl.validateParameters(ValidatorImpl.java:254) > at org.hibernate.validator.internal.engine.ValidatorImpl.validateParameters(ValidatorImpl.java:224) > at org.jboss.resteasy.plugins.validation.GeneralValidatorImpl.validateAllParameters(GeneralValidatorImpl.java:177) > at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:118) > at org.jboss.resteasy.core.ResourceMethodInvoker.internalInvokeOnTarget(ResourceMethodInvoker.java:509) > at org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTargetAfterFilter(ResourceMethodInvoker.java:399) > at org.jboss.resteasy.core.ResourceMethodInvoker.lambda$invokeOnTarget$0(ResourceMethodInvoker.java:363) > at org.jboss.resteasy.core.interception.PreMatchContainerRequestContext.filter(PreMatchContainerRequestContext.java:355) > at org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTarget(ResourceMethodInvoker.java:365) > at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:337) > at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:310) > at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:439) > at org.jboss.resteasy.core.SynchronousDispatcher.lambda$invoke$4(SynchronousDispatcher.java:229) > at org.jboss.resteasy.core.SynchronousDispatcher.lambda$preprocess$0(SynchronousDispatcher.java:135) > at org.jboss.resteasy.core.interception.PreMatchContainerRequestContext.filter(PreMatchContainerRequestContext.java:355) > at org.jboss.resteasy.core.SynchronousDispatcher.preprocess(SynchronousDispatcher.java:138) > at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:215) > at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:227) > at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56) > at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:791) > at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:74) > at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:129) > at io.opentracing.contrib.jaxrs2.server.SpanFinishingFilter.doFilter(SpanFinishingFilter.java:55) > at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:61) > at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:131) > at io.undertow.servlet.handlers.FilterHandler.handleRequest(FilterHandler.java:84) > at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62) > at io.undertow.servlet.handlers.ServletChain$1.handleRequest(ServletChain.java:68) > at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) > at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:132) > at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) > at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) > at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60) > at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77) > at io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50) > at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at org.wildfly.extension.undertow.deployment.GlobalRequestControllerHandler.handleRequest(GlobalRequestControllerHandler.java:68) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:292) > at io.undertow.servlet.handlers.ServletInitialHandler.access$100(ServletInitialHandler.java:81) > at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:138) > at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:135) > at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:48) > at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43) > at org.wildfly.extension.undertow.security.SecurityContextThreadSetupAction.lambda$create$0(SecurityContextThreadSetupAction.java:105) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502) > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:272) > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81) > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:104) > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:360) > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:830) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) > at java.lang.Thread.run(Thread.java:748) > {noformat} > Links: > * [forum|https://developer.jboss.org/thread/278822] > * WFLY-11566 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4822) Upgrade Management API Version to 12.0

by Yeray Borges (Jira)

[ https://issues.redhat.com/browse/WFCORE-4822?page=com.atlassian.jira.plug... ] Yeray Borges updated WFCORE-4822: --------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/4073 > Upgrade Management API Version to 12.0 > -------------------------------------- > > Key: WFCORE-4822 > URL: https://issues.redhat.com/browse/WFCORE-4822 > Project: WildFly Core > Issue Type: Bug > Components: Management > Reporter: Jeff Mesnil > Assignee: Yeray Borges > Priority: Blocker > > We need to fix the version state before WildFly 19 is released. > * The KernelAPIVersion must be bumped to 12.0 > * We also need to release wildly-config-12.0.xsd with the proper host-exclude for > * WildFlY18, Version.10 > * EAP73, Version.10 > (and add those to KnownRelease too) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13039) Upgrade OpenTracing API from 1.3.1 to 1.3.2

by Emmanuel Hugonnet (Jira)

Emmanuel Hugonnet created WFLY-13039: ---------------------------------------- Summary: Upgrade OpenTracing API from 1.3.1 to 1.3.2 Key: WFLY-13039 URL: https://issues.redhat.com/browse/WFLY-13039 Project: WildFly Issue Type: Component Upgrade Components: MP OpenTracing Affects Versions: 19.0.0.Beta1 Reporter: Emmanuel Hugonnet Assignee: Emmanuel Hugonnet Fixes the http access to maven central when running the TCK -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1059) Create Kiali-1.1 branch on upstream

by Hayk Hovsepyan (Jira)

Hayk Hovsepyan created SWSQE-1059: ------------------------------------- Summary: Create Kiali-1.1 branch on upstream Key: SWSQE-1059 URL: https://issues.redhat.com/browse/SWSQE-1059 Project: Kiali QE Issue Type: QE Task Reporter: Hayk Hovsepyan -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

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

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFCORE-4820?page=com.atlassian.jira.plug... ] Darran Lofthouse reassigned WFCORE-4820: ---------------------------------------- Assignee: Darran Lofthouse > Error: WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN) > ---------------------------------------------------------------------------------- > > Key: WFCORE-4820 > URL: https://issues.redhat.com/browse/WFCORE-4820 > Project: WildFly Core > Issue Type: Bug > Components: Management, Security > Affects Versions: 10.0.3.Final > Reporter: Mark Sanchez > Assignee: Darran Lofthouse > Priority: Major > > 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, 4 months

1
0
0 / 0

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

by Luca Molteni (Jira)

[ https://issues.redhat.com/browse/DROOLS-4984?page=com.atlassian.jira.plug... ] Luca Molteni updated DROOLS-4984: --------------------------------- Sprint: 2020 Week 04-06 (from Jan 20) > 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 > Priority: Major > > Currently it's disabled -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1058) Document IPI vs UPI and how to find older cluster

by Filip Brychta (Jira)

Filip Brychta created SWSQE-1058: ------------------------------------ Summary: Document IPI vs UPI and how to find older cluster Key: SWSQE-1058 URL: https://issues.redhat.com/browse/SWSQE-1058 Project: Kiali QE Issue Type: QE Task Reporter: Filip Brychta Assignee: Filip Brychta -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4749) Add version 11 of the urn:jboss:domain / wildfly-config schema

by Yeray Borges (Jira)

[ https://issues.redhat.com/browse/WFCORE-4749?page=com.atlassian.jira.plug... ] Yeray Borges edited comment on WFCORE-4749 at 1/30/20 3:52 AM: --------------------------------------------------------------- Since the last PR was closed, I moved this issue back to resolved. The remainder points were finally addressed in WFCORE-4822 was (Author: yersan): Since the last PR was closed, I moved this issue back to resolved. The remainder points were finally adreesed in WFCORE-4822 > Add version 11 of the urn:jboss:domain / wildfly-config schema > -------------------------------------------------------------- > > Key: WFCORE-4749 > URL: https://issues.redhat.com/browse/WFCORE-4749 > Project: WildFly Core > Issue Type: Task > Components: Management > Reporter: Darran Lofthouse > Assignee: Yeray Borges > Priority: Major > Fix For: 11.0.0.Beta4 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4978) Improve test coverage for PMML integration (nn, naive bayes, knn)

by Jiri Petrlik (Jira)

[ https://issues.redhat.com/browse/DROOLS-4978?page=com.atlassian.jira.plug... ] Jiri Petrlik updated DROOLS-4978: --------------------------------- Summary: Improve test coverage for PMML integration (nn, naive bayes, knn) (was: Improve test coverage for PMML integration) > Improve test coverage for PMML integration (nn, naive bayes, knn) > ----------------------------------------------------------------- > > Key: DROOLS-4978 > URL: https://issues.redhat.com/browse/DROOLS-4978 > Project: Drools > Issue Type: Task > Components: core engine > Affects Versions: 7.33.0.Final > Reporter: Jiri Petrlik > Assignee: Jiri Petrlik > Priority: Major > Labels: TrustyAI > Fix For: 7.33.0.Final > > > Improve test coverage by testing more machine learning models: > * Naive Bayes > * Neural networks > * k-Nearest Neighbors -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4741) [DMN Designer] Basic Code Completion for DMN Literal Expressions (Backlog)

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-4741?page=com.atlassian.jira.plug... ] Jozef Marko commented on DROOLS-4741: ------------------------------------- [~karreiro] can you please link a BAPL so I can prioritize properly? Thank you. > [DMN Designer] Basic Code Completion for DMN Literal Expressions (Backlog) > -------------------------------------------------------------------------- > > Key: DROOLS-4741 > URL: https://issues.redhat.com/browse/DROOLS-4741 > Project: Drools > Issue Type: Epic > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > > Users must have a basic code completion for DMN Literal Expressions. > This task is a MVP, and don't have any backend logic. The code completion is powered by a simple autocompleted of FEEL functions and a simple code highlight. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13038) Undertow null pointer exception after changing to random election policy

by Gagannoor Singh (Jira)

Gagannoor Singh created WFLY-13038: -------------------------------------- Summary: Undertow null pointer exception after changing to random election policy Key: WFLY-13038 URL: https://issues.redhat.com/browse/WFLY-13038 Project: WildFly Issue Type: Bug Components: Web (Undertow) Affects Versions: 16.0.0.Final Reporter: Gagannoor Singh Assignee: Flavia Rainone After changing the singleton subsystem to random election policy getting undertow null pointer exception in logs after clicking deployments->server groups-> "server group name" of HAL management console and it shows zero deployments. We are having a clustered environment with 3 nodes. Logs: ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 30) WFLYCTL0013: Operation ("read-attribute") failed - address: ([ ("deployment" => "masterdata-ei-cvpartner-1.17-SNAPSHOT.war"), ("subsystem" => "undertow") ]): java.lang.NullPointerException Singleton Setting in domain.xml : <subsystem xmlns="urn:jboss:domain:singleton:1.0"> <singleton-policies default="default"> <singleton-policy name="default" cache-container="server"> <random-election-policy/> </singleton-policy> </singleton-policies> </subsystem> -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12679) Upgrade HAL from 3.2.1 to 3.2.2

by Moulali Shikalwadi (Jira)

[ https://issues.redhat.com/browse/WFLY-12679?page=com.atlassian.jira.plugi... ] Moulali Shikalwadi commented on WFLY-12679: ------------------------------------------- Hi [~soul2zimate], I tried to change the hal version from 3.2.1 to 3.2.2 but build is getting failed with below error. [WARNING] Rule 0: org.apache.maven.plugins.enforcer.BanTransitiveDependencies failed with message: org.wildfly:wildfly-galleon-pack:pom:18.0.2.Final-SNAPSHOT org.jboss.hal:hal-console:jar:resources:3.2.2.Final:provided has transitive dependencies: org.jetbrains:annotations:jar:16.0.1:provided And also in the master branch I see 3.2.5.Final not 3.2.1.Final. Could you please suggest. Thanks, Moulali > Upgrade HAL from 3.2.1 to 3.2.2 > ------------------------------- > > Key: WFLY-12679 > URL: https://issues.redhat.com/browse/WFLY-12679 > Project: WildFly > Issue Type: Component Upgrade > Components: Web Console > Affects Versions: 18.0.0.Final > Reporter: Chao Wang > Assignee: Moulali Shikalwadi > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4956) Normarize rule constraints for property reactivity and indexing

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-4956?page=com.atlassian.jira.plug... ] Toshiya Kobayashi commented on DROOLS-4956: ------------------------------------------- Executable Model has no problem with property reactivity in both cases ( "Toshiya" == name / $customer == name). However, Executable Model doesn't create index in those cases. > Normarize rule constraints for property reactivity and indexing > --------------------------------------------------------------- > > Key: DROOLS-4956 > URL: https://issues.redhat.com/browse/DROOLS-4956 > Project: Drools > Issue Type: Bug > Components: core engine, executable model > Affects Versions: 7.31.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > > Having a constraint like > {code:java} > Person(name == $customer) > {code} > is not really the same thing as > {code:java} > Person($customer == name) > {code} > In the second case not only you don't have property reactivity, but also you don't have indexing. This an inconsistent behaviour and hoping to fix it with a "normalization" phase where the second constraint got rewritten like the first before being analyzed by property reactivity and indexing. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12681) Provide a 'microprofile' Galleon layer

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFLY-12681?page=com.atlassian.jira.plugi... ] Radoslav Husar updated WFLY-12681: ---------------------------------- Summary: Provide a 'microprofile' Galleon layer (was: Create 'microprofile' layer spec) > Provide a 'microprofile' Galleon layer > -------------------------------------- > > Key: WFLY-12681 > URL: https://issues.redhat.com/browse/WFLY-12681 > Project: WildFly > Issue Type: Feature Request > Components: Build System > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > Labels: Microprofile > > We used to have a 'microprofile' layer spec aggregating all MP specs which at the moment only contained config, health and metrics which got renamed to 'observability' by WFLY-11774. > With the introduction of new specs fault tolerance, openapi, etc. we should reintroduce the 'microprofile' layer spec which contains all of the MP specs. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4989) [DMN Designer] Tab content background colour consistency

by Elizabeth Clayton (Jira)

[ https://issues.redhat.com/browse/DROOLS-4989?page=com.atlassian.jira.plug... ] Elizabeth Clayton commented on DROOLS-4989: ------------------------------------------- [~kywalker] [~karreiro] I'm guessing the PF3 "Empty State" background color would be the "master" for this, wdyt? https://www.patternfly.org/v4/design-guidelines/usage-and-behavior/empty-... Or should we consult someone in visual design? > [DMN Designer] Tab content background colour consistency > -------------------------------------------------------- > > Key: DROOLS-4989 > URL: https://issues.redhat.com/browse/DROOLS-4989 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Michael Anstis > Priority: Minor > Labels: UX, drools-tools > > Filing a jira for an issue that [~kywalker] found - tab background colors are not consistent between tabs. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4989) [DMN Designer] Tab content background colour consistency

by Elizabeth Clayton (Jira)

[ https://issues.redhat.com/browse/DROOLS-4989?page=com.atlassian.jira.plug... ] Elizabeth Clayton edited comment on DROOLS-4989 at 1/29/20 4:46 PM: -------------------------------------------------------------------- [~kywalker] [~karreiro] I'm guessing the PF3 "Empty State" background color would be the "master" for this, wdyt? Or should we consult someone in visual design? was (Author: uxdlc): [~kywalker] [~karreiro] I'm guessing the PF3 "Empty State" background color would be the "master" for this, wdyt? https://www.patternfly.org/v4/design-guidelines/usage-and-behavior/empty-... Or should we consult someone in visual design? > [DMN Designer] Tab content background colour consistency > -------------------------------------------------------- > > Key: DROOLS-4989 > URL: https://issues.redhat.com/browse/DROOLS-4989 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Michael Anstis > Priority: Minor > Labels: UX, drools-tools > > Filing a jira for an issue that [~kywalker] found - tab background colors are not consistent between tabs. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4989) [DMN Designer] Tab content background colour consistency

by Elizabeth Clayton (Jira)

[ https://issues.redhat.com/browse/DROOLS-4989?page=com.atlassian.jira.plug... ] Elizabeth Clayton commented on DROOLS-4989: ------------------------------------------- https://www.patternfly.org/v3/pattern-library/communication/empty-state/#... > [DMN Designer] Tab content background colour consistency > -------------------------------------------------------- > > Key: DROOLS-4989 > URL: https://issues.redhat.com/browse/DROOLS-4989 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Michael Anstis > Priority: Minor > Labels: UX, drools-tools > > Filing a jira for an issue that [~kywalker] found - tab background colors are not consistent between tabs. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4989) DMN editor tab color consistency

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-4989?page=com.atlassian.jira.plug... ] Michael Anstis commented on DROOLS-4989: ---------------------------------------- Thanks [~uxdlc] [~kywalker]. Can you please advise the CSS RGB for the correct colour to be used across all backgrounds (Stunner, BPMN and DMN)? > DMN editor tab color consistency > -------------------------------- > > Key: DROOLS-4989 > URL: https://issues.redhat.com/browse/DROOLS-4989 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Michael Anstis > Priority: Minor > Labels: UX, drools-tools > > Filing a jira for an issue that [~kywalker] found - tab background colors are not consistent between tabs. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4989) [DMN Designer] Tab content background colour consistency

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-4989?page=com.atlassian.jira.plug... ] Michael Anstis updated DROOLS-4989: ----------------------------------- Summary: [DMN Designer] Tab content background colour consistency (was: DMN editor tab color consistency) > [DMN Designer] Tab content background colour consistency > -------------------------------------------------------- > > Key: DROOLS-4989 > URL: https://issues.redhat.com/browse/DROOLS-4989 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Michael Anstis > Priority: Minor > Labels: UX, drools-tools > > Filing a jira for an issue that [~kywalker] found - tab background colors are not consistent between tabs. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4989) DMN editor tab color consistency

by Elizabeth Clayton (Jira)

Elizabeth Clayton created DROOLS-4989: ----------------------------------------- Summary: DMN editor tab color consistency Key: DROOLS-4989 URL: https://issues.redhat.com/browse/DROOLS-4989 Project: Drools Issue Type: Enhancement Components: DMN Editor Reporter: Elizabeth Clayton Assignee: Michael Anstis Filing a jira for an issue that [~kywalker] found - tab background colors are not consistent between tabs. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4654) [DMN Designer] Cues to help users add nodes to the diagram

by Elizabeth Clayton (Jira)

[ https://issues.redhat.com/browse/DROOLS-4654?page=com.atlassian.jira.plug... ] Elizabeth Clayton commented on DROOLS-4654: ------------------------------------------- [~manstis] my bad then, I directed [~kywalker] here. One of us will create a new jira then, thanks. > [DMN Designer] Cues to help users add nodes to the diagram > ---------------------------------------------------------- > > Key: DROOLS-4654 > URL: https://issues.redhat.com/browse/DROOLS-4654 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Major > Labels: Field, Stunner, UX, UX-Field, UXTeam, drools-tools > Fix For: 7.27.0.Final > > Attachments: Screen Shot 2020-01-29 at 10.45.16 AM.png, mouse-pointer.svg, screenshot-1.png > > > Users are unable to add nodes the process diagram. In both the legacy editor and in Stunner, they do not understand that you need to drag the components onto the canvas. Some users click and then click on the canvas, while others can't even find where, for example, the script task is. > *_Acceptance criteria_* > See https://issues.jboss.org/browse/RHPAM-2318 for acceptance criteria. > The empty state text should state "diagram" and not "business process". -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4654) [DMN Designer] Cues to help users add nodes to the diagram

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-4654?page=com.atlassian.jira.plug... ] Michael Anstis resolved DROOLS-4654. ------------------------------------ Fix Version/s: 7.27.0.Final Resolution: Done This was a change in Stunner that appears to have been released a long time ago ({{7.27.0.Final}} based on the [linked|https://issues.redhat.com/browse/JBPM-8830] Stunner JIRA ). Can you please report the colour discrepancies as a new JIRA as I do not want to re-open or re-purpose this JIRA for the new unrelated observation. > [DMN Designer] Cues to help users add nodes to the diagram > ---------------------------------------------------------- > > Key: DROOLS-4654 > URL: https://issues.redhat.com/browse/DROOLS-4654 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Major > Labels: Field, Stunner, UX, UX-Field, UXTeam, drools-tools > Fix For: 7.27.0.Final > > Attachments: Screen Shot 2020-01-29 at 10.45.16 AM.png, mouse-pointer.svg, screenshot-1.png > > > Users are unable to add nodes the process diagram. In both the legacy editor and in Stunner, they do not understand that you need to drag the components onto the canvas. Some users click and then click on the canvas, while others can't even find where, for example, the script task is. > *_Acceptance criteria_* > See https://issues.jboss.org/browse/RHPAM-2318 for acceptance criteria. > The empty state text should state "diagram" and not "business process". -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

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

by Mark Sanchez (Jira)

[ https://issues.redhat.com/browse/WFCORE-4820?page=com.atlassian.jira.plug... ] Mark Sanchez commented on WFCORE-4820: -------------------------------------- How do I turn on stack trace? Here's the full error: Host Controller] ^[[0m^[[0m11:18:22,803 INFO [org.jboss.as.patching] (MSC service thread 1-2) WFLYPAT0050: WildFly Full cumulative patch ID is: base, one-off patches include: none^[[0m [Host Controller] ^[[0m^[[33m11:18:22,880 WARN [org.jboss.as.domain.management.security] (MSC service thread 1-2) WFLYDM0111: Keystore /opt/app/workload/jboss/wildfly-18.0.1.Final/domain/configuration/application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost^[[0m [Host Controller] ^[[33m^[[0m^[[31m11:18:23,019 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service org.wildfly.core.management.security.realm.ldap_security_realm: org.jboss.msc.service.StartException in service org.wildfly.core.management.security.realm.ldap_security_realm: WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN)^[[0m [Host Controller] ^[[31m at org.jboss.as.domain.management.security.SecurityRealmService.start(SecurityRealmService.java:226)^[[0m [Host Controller] ^[[31m at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)^[[0m [Host Controller] ^[[31m at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)^[[0m [Host Controller] ^[[31m at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)^[[0m [Host Controller] ^[[31m at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)^[[0m [Host Controller] ^[[31m at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)^[[0m [Host Controller] ^[[31m at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)^[[0m [Host Controller] ^[[31m at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1363)^[[0m [Host Controller] ^[[31m at java.lang.Thread.run(Thread.java:748)^[[0m [Host Controller] ^[[31m^[[0m [Host Controller] ^[[31m^[[0m^[[0m11:18:23,102 INFO [org.jboss.as.remoting] (MSC service thread 1-2) WFLYRMT0001: Listening on 192.111.164.69:9990^[[0m [Host Controller] ^[[0m^[[31m11:18:23,509 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([^[[0m [Host Controller] ^[[31m ("host" => "domain-ctl-psftest2s"),^[[0m [Host Controller] ^[[31m ("core-service" => "management"),^[[0m [Host Controller] ^[[31m ("security-realm" => "ldap_security_realm")^[[0m [Host Controller] ^[[31m]) - failure description: {"WFLYCTL0080: Failed services" => {"org.wildfly.core.management.security.realm.ldap_security_realm" => "WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN)"}}^[[0m [Host Controller] ^[[31m^[[0m^[[31m11:18:23,549 FATAL [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0034: Host Controller boot has failed in an unrecoverable manner; exiting. See previous messages for details.^[[0m [Host Controller] ^[[31m^[[0m^[[31m11:18:23,551 FATAL [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0178: Aborting with exit code 99^[[0m [Host Controller] ^[[31m^[[0m^[[0m11:18:23,576 INFO [org.jboss.as] (MSC service thread 1-1) WFLYSRV0050: WildFly Full 18.0.1.Final (WildFly Core 10.0.3.Final) stopped in 11ms^[[0m > Error: WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN) > ---------------------------------------------------------------------------------- > > Key: WFCORE-4820 > URL: https://issues.redhat.com/browse/WFCORE-4820 > Project: WildFly Core > Issue Type: Bug > Components: Management, Security > Affects Versions: 10.0.3.Final > Reporter: Mark Sanchez > Priority: Major > > 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, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4654) [DMN Designer] Cues to help users add nodes to the diagram

by Kyle Walker (Jira)

[ https://issues.redhat.com/browse/DROOLS-4654?page=com.atlassian.jira.plug... ] Kyle Walker updated DROOLS-4654: -------------------------------- Attachment: Screen Shot 2020-01-29 at 10.45.16 AM.png > [DMN Designer] Cues to help users add nodes to the diagram > ---------------------------------------------------------- > > Key: DROOLS-4654 > URL: https://issues.redhat.com/browse/DROOLS-4654 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Major > Labels: Field, Stunner, UX, UX-Field, UXTeam, drools-tools > Attachments: Screen Shot 2020-01-29 at 10.45.16 AM.png, mouse-pointer.svg, screenshot-1.png > > > Users are unable to add nodes the process diagram. In both the legacy editor and in Stunner, they do not understand that you need to drag the components onto the canvas. Some users click and then click on the canvas, while others can't even find where, for example, the script task is. > *_Acceptance criteria_* > See https://issues.jboss.org/browse/RHPAM-2318 for acceptance criteria. > The empty state text should state "diagram" and not "business process". -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4654) [DMN Designer] Cues to help users add nodes to the diagram

by Kyle Walker (Jira)

[ https://issues.redhat.com/browse/DROOLS-4654?page=com.atlassian.jira.plug... ] Kyle Walker commented on DROOLS-4654: ------------------------------------- All the pages on DMN (at least the empty states) seem to have a different shade of gray in the background, see attachment. Can that be standardized when this is implemented? !Screen Shot 2020-01-29 at 10.45.16 AM.png|thumbnail! Thanks, Kyle > [DMN Designer] Cues to help users add nodes to the diagram > ---------------------------------------------------------- > > Key: DROOLS-4654 > URL: https://issues.redhat.com/browse/DROOLS-4654 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Major > Labels: Field, Stunner, UX, UX-Field, UXTeam, drools-tools > Attachments: Screen Shot 2020-01-29 at 10.45.16 AM.png, mouse-pointer.svg, screenshot-1.png > > > Users are unable to add nodes the process diagram. In both the legacy editor and in Stunner, they do not understand that you need to drag the components onto the canvas. Some users click and then click on the canvas, while others can't even find where, for example, the script task is. > *_Acceptance criteria_* > See https://issues.jboss.org/browse/RHPAM-2318 for acceptance criteria. > The empty state text should state "diagram" and not "business process". -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4727) Unclear message when user tries to bind a fact on the Background tab

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-4727?page=com.atlassian.jira.plug... ] Jozef Marko commented on DROOLS-4727: ------------------------------------- I can confirm [~yamer] > Unclear message when user tries to bind a fact on the Background tab > -------------------------------------------------------------------- > > Key: DROOLS-4727 > URL: https://issues.redhat.com/browse/DROOLS-4727 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.30.0.Final > Reporter: Jozef Marko > Assignee: Yeser Amer > Priority: Major > Labels: ScenarioSimulation, drools-tools > Attachments: bind.webm > > > See the attached video. There is confusing message when user bind a fact on Background tab and tries to continue work with the editor. The current message is like _Can not read GJg undefined property_. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4727) Unclear message when user tries to bind a fact on the Background tab

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-4727?page=com.atlassian.jira.plug... ] Jozef Marko closed DROOLS-4727. ------------------------------- Resolution: Out of Date > Unclear message when user tries to bind a fact on the Background tab > -------------------------------------------------------------------- > > Key: DROOLS-4727 > URL: https://issues.redhat.com/browse/DROOLS-4727 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.30.0.Final > Reporter: Jozef Marko > Assignee: Yeser Amer > Priority: Major > Labels: ScenarioSimulation, drools-tools > Attachments: bind.webm > > > See the attached video. There is confusing message when user bind a fact on Background tab and tries to continue work with the editor. The current message is like _Can not read GJg undefined property_. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4822) Upgrade Management API Version to 12.0

by Jeff Mesnil (Jira)

Jeff Mesnil created WFCORE-4822: ----------------------------------- Summary: Upgrade Management API Version to 12.0 Key: WFCORE-4822 URL: https://issues.redhat.com/browse/WFCORE-4822 Project: WildFly Core Issue Type: Bug Components: Management Reporter: Jeff Mesnil Assignee: Yeray Borges We need to fix the version state before WildFly 19 is released. * The KernelAPIVersion must be bumped to 12.0 * We also need to release wildly-config-12.0.xsd with the proper host-exclude for * WildFlY18, Version.10 * EAP73, Version.10 (and add those to KnownRelease too) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4988) Test Scenario: improve DMN validation check

by Daniele Zonca (Jira)

Daniele Zonca created DROOLS-4988: ------------------------------------- Summary: Test Scenario: improve DMN validation check Key: DROOLS-4988 URL: https://issues.redhat.com/browse/DROOLS-4988 Project: Drools Issue Type: Enhancement Components: Scenario Simulation and Testing Reporter: Daniele Zonca Assignee: Yeser Amer Add a check to verify if a simple type has been changed to a complex type. Please consider expression columns too -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4988) Test Scenario: improve DMN validation

by Daniele Zonca (Jira)

[ https://issues.redhat.com/browse/DROOLS-4988?page=com.atlassian.jira.plug... ] Daniele Zonca updated DROOLS-4988: ---------------------------------- Summary: Test Scenario: improve DMN validation (was: Test Scenario: improve DMN validation check) > Test Scenario: improve DMN validation > ------------------------------------- > > Key: DROOLS-4988 > URL: https://issues.redhat.com/browse/DROOLS-4988 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Yeser Amer > Priority: Major > Labels: drools-tools > > Add a check to verify if a simple type has been changed to a complex type. Please consider expression columns too -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4749) Add version 11 of the urn:jboss:domain / wildfly-config schema

by Yeray Borges (Jira)

[ https://issues.redhat.com/browse/WFCORE-4749?page=com.atlassian.jira.plug... ] Yeray Borges updated WFCORE-4749: --------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/4013, https://github.com/wildfly/wildfly-core/pull/4072 > Add version 11 of the urn:jboss:domain / wildfly-config schema > -------------------------------------------------------------- > > Key: WFCORE-4749 > URL: https://issues.redhat.com/browse/WFCORE-4749 > Project: WildFly Core > Issue Type: Task > Components: Management > Reporter: Darran Lofthouse > Assignee: Yeray Borges > Priority: Major > Fix For: 11.0.0.Beta4 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2443) Merge ObjectMessage and ObjectMessageSerializable

by Bela Ban (Jira)

Bela Ban created JGRP-2443: ------------------------------ Summary: Merge ObjectMessage and ObjectMessageSerializable Key: JGRP-2443 URL: https://issues.redhat.com/browse/JGRP-2443 Project: JGroups Issue Type: Enhancement Reporter: Bela Ban Assignee: Bela Ban Fix For: 5.0 {{ObjectMessage}} has an {{object}} as payload, {{ObjectMessageSerializable}} inherits this and adds {{serialized_obj}}. The former has ~32 bytes in memory, the latter 40. The goal is not to increase the size of {{ObjectMessage}} to 40. Solution: * Create an ObjectWrapper class, taking an object and a serialized_version * This is used in the merged {{ObjectMessage}} class (size is still ~32 bytes) * When we have a SizeStreamable object, we set it as payload, otherwise we create an {{ObjectWrapper}} and set it as object. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4749) Add version 11 of the urn:jboss:domain / wildfly-config schema

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFCORE-4749?page=com.atlassian.jira.plug... ] Jeff Mesnil edited comment on WFCORE-4749 at 1/29/20 8:48 AM: -------------------------------------------------------------- Bumping the management version requires additional changes: * Bump org.jboss.as.version.Version#MANAGEMENT_MAJOR_VERSION to 11 * update host-releaseType in server/src/main/resources/schema/wildfly-config_11_0.xsd was (Author: jmesnil): Bumping the management version requires additional changes: * Bump org.jboss.as.version.Version#MANAGEMENT_MAJOR_VERSION to 11 * update org.jboss.as.domain.controller.resources.HostExcludeResourceDefinition.KnownRelease * host-releaseType in server/src/main/resources/schema/wildfly-config_11_0.xsd > Add version 11 of the urn:jboss:domain / wildfly-config schema > -------------------------------------------------------------- > > Key: WFCORE-4749 > URL: https://issues.redhat.com/browse/WFCORE-4749 > Project: WildFly Core > Issue Type: Task > Components: Management > Reporter: Darran Lofthouse > Assignee: Yeray Borges > Priority: Major > Fix For: 11.0.0.Beta4 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4749) Add version 11 of the urn:jboss:domain / wildfly-config schema

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFCORE-4749?page=com.atlassian.jira.plug... ] Jeff Mesnil reassigned WFCORE-4749: ----------------------------------- Assignee: Yeray Borges (was: Jeff Mesnil) > Add version 11 of the urn:jboss:domain / wildfly-config schema > -------------------------------------------------------------- > > Key: WFCORE-4749 > URL: https://issues.redhat.com/browse/WFCORE-4749 > Project: WildFly Core > Issue Type: Task > Components: Management > Reporter: Darran Lofthouse > Assignee: Yeray Borges > Priority: Major > Fix For: 11.0.0.Beta4 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4821) Add missing host-release types to wildlfy-config_11_0.xsd

by Yeray Borges (Jira)

[ https://issues.redhat.com/browse/WFCORE-4821?page=com.atlassian.jira.plug... ] Yeray Borges closed WFCORE-4821. -------------------------------- Resolution: Duplicate Issue Changes will be addressed on WFCORE-4749 > Add missing host-release types to wildlfy-config_11_0.xsd > --------------------------------------------------------- > > Key: WFCORE-4821 > URL: https://issues.redhat.com/browse/WFCORE-4821 > Project: WildFly Core > Issue Type: Task > Components: Management > Reporter: Yeray Borges > Assignee: Yeray Borges > Priority: Major > > These entries are a requirement to allow add missing host exclusions to legacy builds. > The wildlfy-config_11_0.xsd schema is up to date until WildFly15.0, however it should be updated until WildFly18.0 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4749) Add version 11 of the urn:jboss:domain / wildfly-config schema

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFCORE-4749?page=com.atlassian.jira.plug... ] Jeff Mesnil edited comment on WFCORE-4749 at 1/29/20 8:46 AM: -------------------------------------------------------------- Bumping the management version requires additional changes: * Bump org.jboss.as.version.Version#MANAGEMENT_MAJOR_VERSION to 11 * update org.jboss.as.domain.controller.resources.HostExcludeResourceDefinition.KnownRelease * host-releaseType in server/src/main/resources/schema/wildfly-config_11_0.xsd was (Author: jmesnil): Bumping the management version requires to add new corresponding entries in: * org.jboss.as.domain.controller.transformers.KernelAPIVersion * org.jboss.as.domain.controller.resources.HostExcludeResourceDefinition.KnownRelease * host-releaseType in server/src/main/resources/schema/wildfly-config_11_0.xsd > Add version 11 of the urn:jboss:domain / wildfly-config schema > -------------------------------------------------------------- > > Key: WFCORE-4749 > URL: https://issues.redhat.com/browse/WFCORE-4749 > Project: WildFly Core > Issue Type: Task > Components: Management > Reporter: Darran Lofthouse > Assignee: Jeff Mesnil > Priority: Major > Fix For: 11.0.0.Beta4 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4821) Add missing host-release types to wildlfy-config_11_0.xsd

by Yeray Borges (Jira)

Yeray Borges created WFCORE-4821: ------------------------------------ Summary: Add missing host-release types to wildlfy-config_11_0.xsd Key: WFCORE-4821 URL: https://issues.redhat.com/browse/WFCORE-4821 Project: WildFly Core Issue Type: Task Components: Management Reporter: Yeray Borges Assignee: Yeray Borges These entries are a requirement to allow add missing host exclusions to legacy builds. The wildlfy-config_11_0.xsd schema is up to date until WildFly15.0, however it should be updated until WildFly18.0 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4749) Add version 11 of the urn:jboss:domain / wildfly-config schema

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFCORE-4749?page=com.atlassian.jira.plug... ] Jeff Mesnil reopened WFCORE-4749: --------------------------------- Assignee: Jeff Mesnil (was: Darran Lofthouse) Bumping the management version requires to add new corresponding entries in: * org.jboss.as.domain.controller.transformers.KernelAPIVersion * org.jboss.as.domain.controller.resources.HostExcludeResourceDefinition.KnownRelease * host-releaseType in server/src/main/resources/schema/wildfly-config_11_0.xsd > Add version 11 of the urn:jboss:domain / wildfly-config schema > -------------------------------------------------------------- > > Key: WFCORE-4749 > URL: https://issues.redhat.com/browse/WFCORE-4749 > Project: WildFly Core > Issue Type: Task > Components: Management > Reporter: Darran Lofthouse > Assignee: Jeff Mesnil > Priority: Major > Fix For: 11.0.0.Beta4 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4920) Scenario simulation for DMN with collections throws en error

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-4920?page=com.atlassian.jira.plug... ] Yeser Amer reassigned DROOLS-4920: ---------------------------------- Assignee: Daniele Zonca (was: Yeser Amer) > Scenario simulation for DMN with collections throws en error > ------------------------------------------------------------ > > Key: DROOLS-4920 > URL: https://issues.redhat.com/browse/DROOLS-4920 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.31.0.Final > Reporter: Jozef Marko > Assignee: Daniele Zonca > Priority: Major > Labels: drools-tools > Attachments: Screenshot from 2020-01-08 14-14-05.png, urgent.dmn > > > If a user tries to create a test scenario for [^urgent.dmn] he will get a [1] even when he is creating test scenario for the first time. > [1] > !Screenshot from 2020-01-08 14-14-05.png|thumbnail! > h3. Acceptance criteria > https://github.com/jboss-integration/bxms-qe-tests/pull/3048 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2440) CompositeMessage: add iteration

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2440?page=com.atlassian.jira.plugin... ] Bela Ban resolved JGRP-2440. ---------------------------- Resolution: Done > CompositeMessage: add iteration > ------------------------------- > > Key: JGRP-2440 > URL: https://issues.redhat.com/browse/JGRP-2440 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 5.0 > > > Make {{CompositeMessage}} implement {{Iterable<Message>}} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4921) Scrollbars in collection editor popup do not work

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-4921?page=com.atlassian.jira.plug... ] Yeser Amer updated DROOLS-4921: ------------------------------- Sprint: 2020 Week 04-06 (from Jan 20) > Scrollbars in collection editor popup do not work > ------------------------------------------------- > > Key: DROOLS-4921 > URL: https://issues.redhat.com/browse/DROOLS-4921 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.31.0.Final > Reporter: Jozef Marko > Assignee: Yeser Amer > Priority: Major > Labels: drools-tools > Attachments: Screenshot from 2020-01-08 14-20-30.png > > > Scrollbars in the popup do not work rolling wheel on mouse. User can just click on it and drag manually. > !Screenshot from 2020-01-08 14-20-30.png|thumbnail! -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4921) Scrollbars in collection editor popup do not work

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-4921?page=com.atlassian.jira.plug... ] Yeser Amer updated DROOLS-4921: ------------------------------- Story Points: 1 > Scrollbars in collection editor popup do not work > ------------------------------------------------- > > Key: DROOLS-4921 > URL: https://issues.redhat.com/browse/DROOLS-4921 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.31.0.Final > Reporter: Jozef Marko > Assignee: Yeser Amer > Priority: Major > Labels: drools-tools > Attachments: Screenshot from 2020-01-08 14-20-30.png > > > Scrollbars in the popup do not work rolling wheel on mouse. User can just click on it and drag manually. > !Screenshot from 2020-01-08 14-20-30.png|thumbnail! -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3451) [DMN Designer] Function: Not possible to select _expression_ cell

by Daniel José dos Santos (Jira)

[ https://issues.redhat.com/browse/DROOLS-3451?page=com.atlassian.jira.plug... ] Daniel José dos Santos commented on DROOLS-3451: ------------------------------------------------ [~manstis] Great! Thank you! :) > [DMN Designer] Function: Not possible to select _expression_ cell > ----------------------------------------------------------------- > > Key: DROOLS-3451 > URL: https://issues.redhat.com/browse/DROOLS-3451 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.16.0.Final > Reporter: Michael Anstis > Assignee: Daniel José dos Santos > Priority: Minor > Labels: drools-tools > Attachments: context.gif, function-grid-left-click.png, function-grid-right-click.png > > > It is not possible to select the {{FunctionGrid}} _expression_ cell. > Left-single-click does not select cell: > !function-grid-left-click.png|thumbnail! > Whereas right-single-click does (and shows _context_ menu): > !function-grid-right-click.png|thumbnail! > It should be possible to select the cell with single-left-click too. > h2. Acceptance criteria > Select function expression cell by > - Left Single click > - Right Single click > - Keyboard navigation -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13036) Update the Jira references to use issues.redhat.com

by Darran Lofthouse (Jira)

Darran Lofthouse created WFLY-13036: --------------------------------------- Summary: Update the Jira references to use issues.redhat.com Key: WFLY-13036 URL: https://issues.redhat.com/browse/WFLY-13036 Project: WildFly Issue Type: Task Components: Documentation Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 19.0.0.Beta2 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13035) Missing schema warnings in JBDS when importing quickstarts

by Sudeshna Sur (Jira)

[ https://issues.redhat.com/browse/WFLY-13035?page=com.atlassian.jira.plugi... ] Sudeshna Sur moved JBEAP-18583 to WFLY-13035: --------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-13035 (was: JBEAP-18583) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Quickstarts (was: Quickstarts) Target Release: (was: 7.backlog.GA) > Missing schema warnings in JBDS when importing quickstarts > ---------------------------------------------------------- > > Key: WFLY-13035 > URL: https://issues.redhat.com/browse/WFLY-13035 > Project: WildFly > Issue Type: Bug > Components: Quickstarts > Reporter: Sudeshna Sur > Assignee: Sudeshna Sur > Priority: Major > > The following warnings about missing schemas are produced by JBDS 10.4 upon import of {{ejb-security-context-propagation}}: > ||Description||Resource||Path||Location||Type|| > |No grammar constraints (DTD or XML Schema) referenced in the document.|jboss-ejb-client.xml|/ejb-security-context-propagation/src/main/resources/META-INF|line 1|XML Problem| > |No grammar constraints (DTD or XML Schema) referenced in the document.|wildfly-config.xml|/ejb-security-context-propagation/src/main/resources|line 1|XML Problem| > The following warnings about missing schemas are produced by JBDS 10.4 upon import of {{ejb-security-jaas}}: > ||Description||Resource||Path||Location||Type|| > |No grammar constraints (DTD or XML Schema) referenced in the document.|wildfly-config.xml|/ejb-security-jaas/src/main/resources|line 1|XML Problem| > The following warnings about missing schemas are produced by JBDS 10.4 upon import of {{helloworld-mutual-ssl-secured}}: > ||Description||Resource||Path||Location||Type|| > |No grammar constraints (DTD or XML Schema) referenced in the document.|jboss-web.xml|/helloworld-mutual-ssl-secured/src/main/webapp/WEB-INF|line 1|XML Problem| -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13034) Missing schema warnings in JBDS when importing quickstarts

by Sudeshna Sur (Jira)

Sudeshna Sur created WFLY-13034: ----------------------------------- Summary: Missing schema warnings in JBDS when importing quickstarts Key: WFLY-13034 URL: https://issues.redhat.com/browse/WFLY-13034 Project: WildFly Issue Type: Bug Components: Quickstarts Reporter: Sudeshna Sur Assignee: Sudeshna Sur The following warnings about missing schemas are produced by JBDS 10.4 upon import of {{ejb-security-context-propagation}}: ||Description||Resource||Path||Location||Type|| |No grammar constraints (DTD or XML Schema) referenced in the document.|jboss-ejb-client.xml|/ejb-security-context-propagation/src/main/resources/META-INF|line 1|XML Problem| |No grammar constraints (DTD or XML Schema) referenced in the document.|wildfly-config.xml|/ejb-security-context-propagation/src/main/resources|line 1|XML Problem| The following warnings about missing schemas are produced by JBDS 10.4 upon import of {{ejb-security-jaas}}: ||Description||Resource||Path||Location||Type|| |No grammar constraints (DTD or XML Schema) referenced in the document.|wildfly-config.xml|/ejb-security-jaas/src/main/resources|line 1|XML Problem| The following warnings about missing schemas are produced by JBDS 10.4 upon import of {{helloworld-mutual-ssl-secured}}: ||Description||Resource||Path||Location||Type|| |No grammar constraints (DTD or XML Schema) referenced in the document.|jboss-web.xml|/helloworld-mutual-ssl-secured/src/main/webapp/WEB-INF|line 1|XML Problem| -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13033) Missing schema warnings in JBDS when importing quickstarts

by Sudeshna Sur (Jira)

[ https://issues.redhat.com/browse/WFLY-13033?page=com.atlassian.jira.plugi... ] Sudeshna Sur moved JBEAP-12520 to WFLY-13033: --------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-13033 (was: JBEAP-12520) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Quickstarts (was: Quickstarts) Target Release: (was: 7.backlog.GA) Affects Version/s: (was: 7.1.0.ER3) > Missing schema warnings in JBDS when importing quickstarts > ---------------------------------------------------------- > > Key: WFLY-13033 > URL: https://issues.redhat.com/browse/WFLY-13033 > Project: WildFly > Issue Type: Bug > Components: Quickstarts > Reporter: Michal Jurc > Assignee: Sudeshna Sur > Priority: Major > > The following warnings about missing schemas are produced by JBDS 10.4 upon import of {{ejb-security-context-propagation}}: > ||Description||Resource||Path||Location||Type|| > |No grammar constraints (DTD or XML Schema) referenced in the document.|jboss-ejb-client.xml|/ejb-security-context-propagation/src/main/resources/META-INF|line 1|XML Problem| > |No grammar constraints (DTD or XML Schema) referenced in the document.|wildfly-config.xml|/ejb-security-context-propagation/src/main/resources|line 1|XML Problem| > The following warnings about missing schemas are produced by JBDS 10.4 upon import of {{ejb-security-jaas}}: > ||Description||Resource||Path||Location||Type|| > |No grammar constraints (DTD or XML Schema) referenced in the document.|wildfly-config.xml|/ejb-security-jaas/src/main/resources|line 1|XML Problem| > The following warnings about missing schemas are produced by JBDS 10.4 upon import of {{helloworld-mutual-ssl-secured}}: > ||Description||Resource||Path||Location||Type|| > |No grammar constraints (DTD or XML Schema) referenced in the document.|jboss-web.xml|/helloworld-mutual-ssl-secured/src/main/webapp/WEB-INF|line 1|XML Problem| -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13032) Missing host exclusion entries in server configuration files

by Yeray Borges (Jira)

[ https://issues.redhat.com/browse/WFLY-13032?page=com.atlassian.jira.plugi... ] Yeray Borges updated WFLY-13032: -------------------------------- Description: The latest host-exclusion entry in the server configuration files is for WildFly14.0, which means we have the list updated since WF15. For WF19, we need to complete the list of exclusions adding entries until WildFly18.0 The list extensions added in wildfly since then is the following WFLY-10712 org.wildfly.extension.microprofile.metrics-smallrye in WF15 WFLY-5550 org.wildfly.extension.clustering.web added in WF17 WFLY-12590 org.wildfly.extension.microprofile.fault-tolerance-smallrye added in WF19 WFLY-12313 org.wildfly.extension.microprofile.openapi-smallrye added in WF19 WFLY-12609 org.wildfly.extension.microprofile.jwt-smallrye added in WF19 was: The latest host-exclusion entry in the server configuration files is for WildFly14.0, which means we have the list updated since WF15. For WF19, we need to complete the list of exclusions adding entries until WildFly18.0 The list extensions added in wildfly since then is the following WFLY-5550 org.wildfly.extension.clustering.web added in WF17 WFLY-12590 org.wildfly.extension.microprofile.fault-tolerance-smallrye added in WF19 WFLY-12313 org.wildfly.extension.microprofile.openapi-smallrye added in WF19 WFLY-12609 org.wildfly.extension.microprofile.jwt-smallrye added in WF19 > Missing host exclusion entries in server configuration files > ------------------------------------------------------------ > > Key: WFLY-13032 > URL: https://issues.redhat.com/browse/WFLY-13032 > Project: WildFly > Issue Type: Bug > Components: Management > Affects Versions: 16.0.0.Final > Reporter: Yeray Borges > Assignee: Yeray Borges > Priority: Major > Fix For: 19.0.0.Beta2 > > > The latest host-exclusion entry in the server configuration files is for WildFly14.0, which means we have the list updated since WF15. > For WF19, we need to complete the list of exclusions adding entries until WildFly18.0 > The list extensions added in wildfly since then is the following > WFLY-10712 org.wildfly.extension.microprofile.metrics-smallrye in WF15 > WFLY-5550 org.wildfly.extension.clustering.web added in WF17 > WFLY-12590 org.wildfly.extension.microprofile.fault-tolerance-smallrye added in WF19 > WFLY-12313 org.wildfly.extension.microprofile.openapi-smallrye added in WF19 > WFLY-12609 org.wildfly.extension.microprofile.jwt-smallrye added in WF19 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13032) Missing host exclusion entries in server configuration files

by Yeray Borges (Jira)

Yeray Borges created WFLY-13032: ----------------------------------- Summary: Missing host exclusion entries in server configuration files Key: WFLY-13032 URL: https://issues.redhat.com/browse/WFLY-13032 Project: WildFly Issue Type: Bug Components: Management Affects Versions: 16.0.0.Final Reporter: Yeray Borges Assignee: Yeray Borges Fix For: 19.0.0.Beta2 The latest host-exclusion entry in the server configuration files is for WildFly14.0, which means we have the list updated since WF15. For WF19, we need to complete the list of exclusions adding entries until WildFly18.0 The list extensions added in wildfly since then is the following WFLY-5550 org.wildfly.extension.clustering.web added in WF17 WFLY-12590 org.wildfly.extension.microprofile.fault-tolerance-smallrye added in WF19 WFLY-12313 org.wildfly.extension.microprofile.openapi-smallrye added in WF19 WFLY-12609 org.wildfly.extension.microprofile.jwt-smallrye added in WF19 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 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