May 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBEE-201) Test Issue - please ignore

by Jason Brock (Jira)

[ https://issues.jboss.org/browse/JBEE-201?page=com.atlassian.jira.plugin.s... ] Jason Brock updated JBEE-201: ----------------------------- Security: (was: Security Issue) > Test Issue - please ignore > -------------------------- > > Key: JBEE-201 > URL: https://issues.jboss.org/browse/JBEE-201 > Project: JBoss JavaEE Spec APIs > Issue Type: Enhancement > Reporter: Jason Brock > Assignee: Jason Brock > Priority: Major > > Test issue please ignore -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1598) Out of the box SSL - or shortly after.

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/WFLY-1598?page=com.atlassian.jira.plugin.... ] Farah Juma resolved WFLY-1598. ------------------------------ Resolution: Duplicate Issue > Out of the box SSL - or shortly after. > -------------------------------------- > > Key: WFLY-1598 > URL: https://issues.jboss.org/browse/WFLY-1598 > Project: WildFly > Issue Type: Sub-task > Components: Management, Security > Reporter: Darran Lofthouse > Assignee: Farah Juma > Priority: Critical > Labels: management_security,, management_sso > Fix For: 17.0.0.Final > > > There are various reasons that we do not support SSL/TLS out of the box e.g. > - If we ship a default keystore then everyone has access to the private key. > - Generating one on first boot we do not have sufficient information to generate it correctly, also the performance overhead. > This issue is to explorer other options to encourage their use and make it easier to configure. > As an example could the admin console detect a non encrypted connection and have an box that encourages the config along with a wizard like workflow to get it set up? -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1598) Out of the box SSL - or shortly after.

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/WFLY-1598?page=com.atlassian.jira.plugin.... ] Farah Juma commented on WFLY-1598: ---------------------------------- [~jamezp] This is now being tracked via EAP7-1090 and its corresponding community issue, WFCORE-4482. I'm going to close this subtask. > Out of the box SSL - or shortly after. > -------------------------------------- > > Key: WFLY-1598 > URL: https://issues.jboss.org/browse/WFLY-1598 > Project: WildFly > Issue Type: Sub-task > Components: Management, Security > Reporter: Darran Lofthouse > Assignee: Farah Juma > Priority: Critical > Labels: management_security,, management_sso > Fix For: 17.0.0.Final > > > There are various reasons that we do not support SSL/TLS out of the box e.g. > - If we ship a default keystore then everyone has access to the private key. > - Generating one on first boot we do not have sufficient information to generate it correctly, also the performance overhead. > This issue is to explorer other options to encourage their use and make it easier to configure. > As an example could the admin console detect a non encrypted connection and have an box that encourages the config along with a wizard like workflow to get it set up? -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-966) In domain mode non existing subhandler is saved to attributes.

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFCORE-966?page=com.atlassian.jira.plugin... ] James Perkins edited comment on WFCORE-966 at 5/31/19 1:32 PM: --------------------------------------------------------------- I thought this would have been fixed by WFCORE-3337. However it does seem in {{admin-only}} mode on standalone or on a non-active domain profile you can still add invalid handler names. This is true for the loggers as well. Either capabilities can't guard against this, which I don't think is true, or there's something missing in the capability integration with the logging subsystem. was (Author: jamezp): I though this would have been fixed by WFCORE-3337. However it does seem in {{admin-only}} mode on standalone or on a non-active domain profile you can still add invalid handler names. This is true for the loggers as well. Either capabilities can't guard against this, which I don't think is true, or there's something missing in the capability integration with the logging subsystem. > In domain mode non existing subhandler is saved to attributes. > -------------------------------------------------------------- > > Key: WFCORE-966 > URL: https://issues.jboss.org/browse/WFCORE-966 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Environment: Running unsecured EAP 7.0.0 DR9 version in domain mode. > Reporter: Patrik Cyprian > Assignee: James Perkins > Priority: Major > > When you in domain mode in created async handler add non existing sub handler to attributes it is successfully saved. In standalone mode it is not possible (subhandler is not saved - saving operation failed). > 1.Run EAP in domain mode (default profile) > 2.Create async handler > 3.Try to add non existing subhandler to async handler attributes > 4.Try the same in standalone mode with standalone-full-ha profile -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4089) EvaluatedExpression not well resolved with JIT during race

by Mario Fusco (Jira)

[ https://issues.jboss.org/browse/DROOLS-4089?page=com.atlassian.jira.plugi... ] Mario Fusco resolved DROOLS-4089. --------------------------------- Resolution: Done Fixed by https://github.com/kiegroup/drools/commit/3495f287a9d648e3e3944c349a75ffd... > EvaluatedExpression not well resolved with JIT during race > ------------------------------------------------------------ > > Key: DROOLS-4089 > URL: https://issues.jboss.org/browse/DROOLS-4089 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.20.0.Final, 7.22.0.Final > Reporter: vincent palau > Assignee: Mario Fusco > Priority: Major > Attachments: debugging-1.png > > > We recently moved from Drools 7.9.0 to 7.20. > Some errors started appearing in ours tests when calling static methods in LHS drools. > This started happening when all tests were run simultaneously. > It seems the mvel JIT compiler kicks in and it incorrectly evaluates the property name: > A simple call to {noformat}ValidationUtils.isNullOrEmpty(interestedPartyNumber){noformat} ends up with this kind of error: > {noformat} > "java.lang.RuntimeException: Unknown property 'nullOrEmpty' on class tech.stage.utils.cwr.model.PublisherRecord" > {noformat} > Debugging info: > Related source-code: https://github.com/kiegroup/drools/blob/7.20.0.Final/drools-core/src/main... > !debugging-1.png|full! > 1) is the current evaluated property > 2) Should be the right property of WriterRecord > 3) Perhaps the expression which should be executed instead of invocations.get(0) > We fixed that somehow disabling JIT with {noformat}ConstraintJittingThresholdOption{noformat} > Is there any chance to this bug fixed? > Do you need more info? > Thanks in advance for your support. > {panel:title=Reproducer} > https://github.com/vp-stage/evaluatedexpressionandjit > {panel} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-392) Stack trace improvements, summarize the things that broke to make them not so intimidating

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFCORE-392?page=com.atlassian.jira.plugin... ] James Perkins commented on WFCORE-392: -------------------------------------- Could or should this be considered done now? > Stack trace improvements, summarize the things that broke to make them not so intimidating > ------------------------------------------------------------------------------------------ > > Key: WFCORE-392 > URL: https://issues.jboss.org/browse/WFCORE-392 > Project: WildFly Core > Issue Type: Feature Request > Components: Management > Reporter: Jim Tyrrell > Assignee: Brian Stansberry > Priority: Critical > Labels: eap6-ux > Attachments: log.txt > > > See the typical attached stack dump: > It would be nice if the stack dump could include all of the information above as a summary as shown below, basically just the first lines of the errors w/o the whole stack dump: > 11:51:45,391 INFO [org.jboss.as.server.controller] (HttpManagementService-threads - 5) Deployment of "SpringWAR.war" was rolled back with failure message {"Failed services" => {"jboss.web.deployment.default-host./SpringWAR" => "org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./SpringWAR: failed to start context"}} > 11:51:45,392 INFO [org.jboss.as.controller] (HttpManagementService-threads - 5) Service status report > Services which failed to start: > service jboss.web.deployment.default-host./SpringWAR: org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./SpringWAR: failed to start context > 11:51:45,417 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) Stopped deployment SpringWAR.war in 26ms > 11:51:45,417 Error Summary of Exceptions in deployment: > - [org.springframework.web.context.ContextLoader] (MSC service thread 1-5) Context initialization failed: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jbossQueue' defined in class path resource [applicationContextServices.xml]: Invocation of init method failed; nested exception is javax.naming.NameNotFoundException: queue/B -- service jboss.naming.context.java.queue.B > - [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/SpringWAR]] (MSC service thread 1-5) Exception sending context initialized event to listener instance of class org.springframework.web.context.ContextLoaderListener: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jbossQueue' defined in class path resource [applicationContextServices.xml]: Invocation of init method failed; nested exception is javax.naming.NameNotFoundException: queue/B -- service jboss.naming.context.java.queue.B > - [org.apache.catalina.core.StandardContext] (MSC service thread 1-5) Error listenerStart > - ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-5) Context [/SpringWAR] startup failed due to previous errors > - [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/SpringWAR]] (MSC service thread 1-5) Closing Spring root WebApplicationContext > - [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC00001: Failed to start service jboss.web.deployment.default-host./SpringWAR: > ERROR Scroll up to see more info... > Or > 11:51:45,417 Error Summary of Exceptions in deployment: > [1] [org.springframework.web.context.ContextLoader] (MSC service thread 1-5) Context initialization failed: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jbossQueue' defined in class path resource [applicationContextServices.xml]: Invocation of init method failed; nested exception is javax.naming.NameNotFoundException: queue/B -- service jboss.naming.context.java.queue.B > [2] [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/SpringWAR]] (MSC service thread 1-5) Exception sending context initialized event to listener instance of class org.springframework.web.context.ContextLoaderListener: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jbossQueue' defined in class path resource [applicationContextServices.xml]: Invocation of init method failed; nested exception is javax.naming.NameNotFoundException: queue/B -- service jboss.naming.context.java.queue.B > [3] [org.apache.catalina.core.StandardContext] (MSC service thread 1-5) Error listenerStart > [4] ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-5) Context [/SpringWAR] startup failed due to previous errors > [5] [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/SpringWAR]] (MSC service thread 1-5) Closing Spring root WebApplicationContext > [6] [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC00001: Failed to start service jboss.web.deployment.default-host./SpringWAR: > ERROR Scroll up to see more info... -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4070) Improve service discovery/wiring to allow defining the order of alternative services

by Matteo Mortari (Jira)

[ https://issues.jboss.org/browse/DROOLS-4070?page=com.atlassian.jira.plugi... ] Matteo Mortari updated DROOLS-4070: ----------------------------------- Tester: Tibor Zimanyi (was: Matteo Mortari) > Improve service discovery/wiring to allow defining the order of alternative services > ------------------------------------------------------------------------------------ > > Key: DROOLS-4070 > URL: https://issues.jboss.org/browse/DROOLS-4070 > Project: Drools > Issue Type: Enhancement > Components: core engine > Reporter: Mario Fusco > Assignee: Mario Fusco > Priority: Critical > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10188) Setting Undertow default server needs validation of provided server to avoid broken Wildfly configuration

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-10188?page=com.atlassian.jira.plugin... ] James Perkins reassigned WFLY-10188: ------------------------------------ Assignee: Flavia Rainone (was: Stuart Douglas) > Setting Undertow default server needs validation of provided server to avoid broken Wildfly configuration > --------------------------------------------------------------------------------------------------------- > > Key: WFLY-10188 > URL: https://issues.jboss.org/browse/WFLY-10188 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 14.0.1.Final, 12.0.0.Final, 13.0.0.Final > Reporter: Pavel Jelinek > Assignee: Flavia Rainone > Priority: Critical > > Undertow server needs default-host to be set to be able to be used as Undertow subsystem default-server otherwise Wildfly would not start due to: > {code} > ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/subsystem=undertow' are not available: > org.wildfly.undertow.host.test-server.default-host; Possible registration points for this capability: > /subsystem=undertow/server=*/host=* > {code} > This is dangerous as after calling a {{reload}} operation, the server simply fails and crashes. One can accidentaly kill the server with this and \!manual\! fix is necessary to the configuration to be able to start server again. > I think that there should be some check that configuration of the newly created server is complete and valid before it is set as a default server. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4097) Unify old and new RuleUnit APIs

by Mario Fusco (Jira)

Mario Fusco created DROOLS-4097: ----------------------------------- Summary: Unify old and new RuleUnit APIs Key: DROOLS-4097 URL: https://issues.jboss.org/browse/DROOLS-4097 Project: Drools Issue Type: Enhancement Components: core engine Reporter: Mario Fusco Assignee: Mario Fusco -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4096) Create Kogito presentation and demo for Devoxx Poland

by Mario Fusco (Jira)

[ https://issues.jboss.org/browse/DROOLS-4096?page=com.atlassian.jira.plugi... ] Mario Fusco updated DROOLS-4096: -------------------------------- Story Points: 8 > Create Kogito presentation and demo for Devoxx Poland > ----------------------------------------------------- > > Key: DROOLS-4096 > URL: https://issues.jboss.org/browse/DROOLS-4096 > Project: Drools > Issue Type: Task > Reporter: Mario Fusco > Assignee: Mario Fusco > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 4 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2019