January 2021 - jboss-jira - Jboss List Archives

[Red Hat JIRA] (DROOLS-5955) KieScanner not properly updating model assets (classes) on incremental updates

by Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-5955?page=com.atlassian.jira.plug... ] Mario Fusco updated DROOLS-5955: -------------------------------- Sprint: 2021 Week 04-06 (from Jan 25) > KieScanner not properly updating model assets (classes) on incremental updates > ------------------------------------------------------------------------------ > > Key: DROOLS-5955 > URL: https://issues.redhat.com/browse/DROOLS-5955 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.48.0.Final > Reporter: B Brown > Assignee: Mario Fusco > Priority: Major > Attachments: LogFile.txt, RunTest.java, TestScannerUpdate-1.0.0-SNAPSHOT.jar > > > KieScanner is not correctly applying incremental kjar updates to KieContainer when those updates include changes to "Model" assets authored in Business Central. > Adding a new field to a model in business central, then updating a rule to reference that value will work the first time. If you repeat this again, adding another new field and new reference in a rule, after updating the KieContainer using KieScanner, executing fireAllRules on a new session will fail with an exception, claiming it cannot find the setter method for the new attribute. > It is expected that the KieScanner should be able to take new kjars produced from BC and consistently update KieContainers with their updates. There is no workaround for this. Please refer to the "Steps to Reproduce". > This was using 7.48.Final drools libraries and Business Central 7.48.Final but experienced similar issue before on 7.43.1.Final as well. > I've attached the final kjar that caused the error, the RunTest.java containing the main method that ran the test as well as the log file. > > My dependencies in maven for RunTest.java were: > * group: org.drools artifact: drools-bom ,version: 7.48.Final > * group: org.kie artifact: kie-ci > * group: org.drools artifact: drools-workbench-models-guided-dtable > * group: org.drools artifact: drools-workbench-models-guided-template -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (LOGMGR-283) The TCCL should be set when configuring resources

by James Perkins (Jira)

James Perkins created LOGMGR-283: ------------------------------------ Summary: The TCCL should be set when configuring resources Key: LOGMGR-283 URL: https://issues.redhat.com/browse/LOGMGR-283 Project: JBoss Log Manager Issue Type: Bug Reporter: James Perkins Assignee: James Perkins When configuring resources the TCCL should be set to the class loader for the type being configured. In the case of a modular environment the type may use the TCCL to initialize other types. For example in WildFly if a {{custom-handler}} is used that handler may be in it's own module and attempt to use the TCCL to initialize another type. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (ELYWEB-124) Add documentation to ServletSecurityContextImpl$IdentityContainer attribute name that describes special handling in WildFly

by Paul Ferraro (Jira)

Paul Ferraro created ELYWEB-124: ----------------------------------- Summary: Add documentation to ServletSecurityContextImpl$IdentityContainer attribute name that describes special handling in WildFly Key: ELYWEB-124 URL: https://issues.redhat.com/browse/ELYWEB-124 Project: Elytron Web Issue Type: Task Components: Undertow Servlet Affects Versions: 2.0.0.Alpha5, 1.8.0.Final Reporter: Paul Ferraro Assignee: Paul Ferraro See: https://github.com/wildfly/wildfly/pull/13879#discussion_r559192174 -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14300) Create Jakarta Bean Validation TCK runner for WildFly EE 9

by Jason Lee (Jira)

[ https://issues.redhat.com/browse/WFLY-14300?page=com.atlassian.jira.plugi... ] Jason Lee resolved WFLY-14300. ------------------------------ Resolution: Done Guillaume Smet made some changes on the HV side. Scott and I worked with the Jenkins build to get the tests to run. > Create Jakarta Bean Validation TCK runner for WildFly EE 9 > ---------------------------------------------------------- > > Key: WFLY-14300 > URL: https://issues.redhat.com/browse/WFLY-14300 > Project: WildFly > Issue Type: Sub-task > Components: Bean Validation > Reporter: Scott Marlow > Assignee: Jason Lee > Priority: Major > Fix For: 23.0.0.Beta1 > > > This task is about creating a new TCK test runner for running the [beanvalidation-tck|https://github.com/eclipse-ee4j/beanvalidation-tck] ([binary BV TCK link |https://download.eclipse.org/jakartaee/bean-validation/3.0/beanvalidation-tck-dist-3.0.0.zip]) that can be similar to the Hibernate Validator project [tck-runner|https://github.com/hibernate/hibernate-validator/tree/master/t...] except it will be updated to work with Bean Validation 3.0 (Jakarta EE 9) instead of Bean Validation 2.0. > https://github.com/eclipse-ee4j/bvtck-porting is an example TCK runner that is used for GlassFish. > The documentation for the Bean Validation TCK is available at https://docs.jboss.org/hibernate/stable/beanvalidation/tck/reference/html... (and https://docs.jboss.org/hibernate/stable/beanvalidation/tck/reference/html...) which I believe describes how to set up a TCK runner for an EE 8 implementation. > Please note that https://github.com/eclipse-ee4j/beanvalidation-tck#jakarta-bean-validatio... points to what should be Jakarta EE 9 setup examples documentation. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-10863) MP Health is not available in domain mode

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFLY-10863?page=com.atlassian.jira.plugi... ] Jeff Mesnil reassigned WFLY-10863: ---------------------------------- Assignee: Martin Stefanko (was: Jeff Mesnil) > MP Health is not available in domain mode > ----------------------------------------- > > Key: WFLY-10863 > URL: https://issues.redhat.com/browse/WFLY-10863 > Project: WildFly > Issue Type: Feature Request > Components: MP Health > Reporter: Rostislav Svoboda > Assignee: Martin Stefanko > Priority: Major > Labels: domain-mode > > MP Health is not available in domain mode. > Analysis is not saying that domain is out of scope, EAP7 RFE is not explicit about this either. > We may resolve this just by making it explicit, that MP health is just fo standalone for now. > For domain we should at least have a plan what to do and how -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-12798) HealthCheck HTTP endpoint does not support CDI @RequestScoped scope

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFLY-12798?page=com.atlassian.jira.plugi... ] Jeff Mesnil reassigned WFLY-12798: ---------------------------------- Assignee: Martin Stefanko (was: Jeff Mesnil) > HealthCheck HTTP endpoint does not support CDI @RequestScoped scope > ------------------------------------------------------------------- > > Key: WFLY-12798 > URL: https://issues.redhat.com/browse/WFLY-12798 > Project: WildFly > Issue Type: Bug > Components: MP Health > Affects Versions: 18.0.0.Final > Reporter: Florian Sailer > Assignee: Martin Stefanko > Priority: Major > > 2019-11-15 15:26:11,717 ERROR [org.wildfly.extension.microprofile.health.smallrye] (management I/O-1) Error processing Health Checks: org.jboss.weld.contexts.ContextNotActiveException: WELD-001303: No active contexts for scope type javax.enterprise.context.RequestScoped > at org.jboss.weld.manager.BeanManagerImpl.getContext(BeanManagerImpl.java:647) > at org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.getIfExists(ContextualInstanceStrategy.java:89) > at org.jboss.weld.bean.ContextualInstanceStrategy$CachingContextualInstanceStrategy.getIfExists(ContextualInstanceStrategy.java:164) > at org.jboss.weld.bean.ContextualInstance.getIfExists(ContextualInstance.java:63) > at org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:87) > at org.jboss.weld.bean.proxy.ProxyMethodHandler.getInstance(ProxyMethodHandler.java:131) > at at.arz.bpe.boundary.PingCheck$Proxy$_$$_WeldClientProxy.call(Unknown Source) > at org.wildfly.extension.microprofile.health.HealthReporter.jsonObject(HealthReporter.java:120) > at org.wildfly.extension.microprofile.health.HealthReporter.fillCheck(HealthReporter.java:107) > at org.wildfly.extension.microprofile.health.HealthReporter.processChecks(HealthReporter.java:96) > at org.wildfly.extension.microprofile.health.HealthReporter.getHealth(HealthReporter.java:79) > at org.wildfly.extension.microprofile.health.HealthReporter.getHealth(HealthReporter.java:60) > at org.wildfly.extension.microprofile.health.HealthContextService$HealthCheckHandler.handleRequest(HealthContextService.java:100) > at org.jboss.as.domain.http.server.security.RealmReadinessHandler.handleRequest(RealmReadinessHandler.java:51) > at org.jboss.as.domain.http.server.security.ServerErrorReadinessHandler.handleRequest(ServerErrorReadinessHandler.java:35) > at io.undertow.server.handlers.PathHandler.handleRequest(PathHandler.java:91) > at io.undertow.server.handlers.ChannelUpgradeHandler.handleRequest(ChannelUpgradeHandler.java:211) > at io.undertow.server.handlers.cache.CacheHandler.handleRequest(CacheHandler.java:92) > at io.undertow.server.handlers.error.SimpleErrorPageHandler.handleRequest(SimpleErrorPageHandler.java:78) > at io.undertow.server.handlers.CanonicalPathHandler.handleRequest(CanonicalPathHandler.java:49) > at org.jboss.as.domain.http.server.ManagementHttpRequestHandler.handleRequest(ManagementHttpRequestHandler.java:57) > at org.jboss.as.domain.http.server.cors.CorsHttpHandler.handleRequest(CorsHttpHandler.java:75) > at org.jboss.as.domain.http.server.ManagementHttpServer$UpgradeFixHandler.handleRequest(ManagementHttpServer.java:666) > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:376) > at io.undertow.server.protocol.http.HttpReadListener.handleEventWithNoRunningRequest(HttpReadListener.java:255) > at io.undertow.server.protocol.http.HttpReadListener.handleEvent(HttpReadListener.java:136) > at io.undertow.server.protocol.http.HttpOpenListener.handleEvent(HttpOpenListener.java:162) > at io.undertow.server.protocol.http.HttpOpenListener.handleEvent(HttpOpenListener.java:100) > at io.undertow.server.protocol.http.HttpOpenListener.handleEvent(HttpOpenListener.java:57) > at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) > at org.xnio.ChannelListeners$10.handleEvent(ChannelListeners.java:291) > at org.xnio.ChannelListeners$10.handleEvent(ChannelListeners.java:286) > at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) > at org.xnio.nio.QueuedNioTcpServer$1.run(QueuedNioTcpServer.java:132) > at org.xnio.nio.WorkerThread.safeRun(WorkerThread.java:612) > at org.xnio.nio.WorkerThread.run(WorkerThread.java:479) > MP-Health Spec doesnt enforce a scope and it worked with wildfly 17.0.0.1-Final. > https://github.com/eclipse/microprofile-health/issues/109 -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-11272) wildfly-microprofile-health-smallrye_1_0.xsd doesn't have documentation for allowed attributes

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFLY-11272?page=com.atlassian.jira.plugi... ] Jeff Mesnil reassigned WFLY-11272: ---------------------------------- Assignee: Martin Stefanko (was: Jeff Mesnil) > wildfly-microprofile-health-smallrye_1_0.xsd doesn't have documentation for allowed attributes > ---------------------------------------------------------------------------------------------- > > Key: WFLY-11272 > URL: https://issues.redhat.com/browse/WFLY-11272 > Project: WildFly > Issue Type: Bug > Components: MP Health > Reporter: Rostislav Svoboda > Assignee: Martin Stefanko > Priority: Major > > wildfly-microprofile-health-smallrye_1_0.xsd doesn't have documentation for allowed attributes > CLI provides description via {{/subsystem=microprofile-health-smallrye:read-resource-description()}}. > Same information should be present in wildfly-microprofile-health-smallrye_1_0.xsd via <xs:annotation> and <xs:documentation> -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-13931) Allow defining HealthChecks without CDI

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFLY-13931?page=com.atlassian.jira.plugi... ] Jeff Mesnil reassigned WFLY-13931: ---------------------------------- Assignee: Martin Stefanko (was: Jeff Mesnil) > Allow defining HealthChecks without CDI > --------------------------------------- > > Key: WFLY-13931 > URL: https://issues.redhat.com/browse/WFLY-13931 > Project: WildFly > Issue Type: Feature Request > Components: MP Health > Reporter: Sebastian Laskawiec > Assignee: Martin Stefanko > Priority: Major > > The current design around MP Health enables deployments to specify HealthChecks using CDI. Some deployments (like Keycloak) doesn't use CDI at all. We would need a way to inject additional HealthCheck instances into Wildfly without enabling it. > From the implementation perspective, it would be useful to have some sort of static accessor (or maybe something defined in jboss-structure.xml) that would enable use to inject some custom HealthCheck. > References: > * [Keycloak Observability Design|https://github.com/keycloak/keycloak-community/pull/177] > * * [Keycloak Healthcheck Design|https://github.com/keycloak/keycloak-community/pull/55] -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-12835) HealthChecks in subdeployments are not registered

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFLY-12835?page=com.atlassian.jira.plugi... ] Jeff Mesnil reassigned WFLY-12835: ---------------------------------- Assignee: Martin Stefanko (was: Jeff Mesnil) > HealthChecks in subdeployments are not registered > ------------------------------------------------- > > Key: WFLY-12835 > URL: https://issues.redhat.com/browse/WFLY-12835 > Project: WildFly > Issue Type: Feature Request > Components: MP Health > Affects Versions: 18.0.1.Final > Reporter: Ivan Straka > Assignee: Martin Stefanko > Priority: Critical > > After EAR is deployed HealthChecks are not registered and not exposed under _/health_ endpoint. > EAR contains one WAR and one JAR. Both of them contains HealthChecks. > Test source: https://github.com/istraka/eap-microprofile-test-suite/blob/mp-health/mic... -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-12461) Can't use smallrye-health without weld extension

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFLY-12461?page=com.atlassian.jira.plugi... ] Jeff Mesnil reassigned WFLY-12461: ---------------------------------- Assignee: Martin Stefanko (was: Jeff Mesnil) > Can't use smallrye-health without weld extension > ------------------------------------------------ > > Key: WFLY-12461 > URL: https://issues.redhat.com/browse/WFLY-12461 > Project: WildFly > Issue Type: Bug > Components: MP Health > Affects Versions: 17.0.1.Final > Reporter: Florian Sailer > Assignee: Martin Stefanko > Priority: Major > > Since this commit in the smallrye implementation it was possible to use smallrye without CDI. > https://github.com/smallrye/smallrye-health/commit/a6a7812877d74d2c3f5b29... > I'm trying to migrate from Wildfly 15.0.1-Final to 17.0.1-Final, where the smallrye-health extension unfortunately needs weld to startup. It's not possbible for me to activate weld on my sever, because there are some problems using the org.apache.cxf.jaxrs framework with weld. > I am getting the following exception while starting: > 14:16:04,960 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/subsystem=microprofile-health-smallrye' are not available: > org.wildfly.weld; There are no known registration points which can provide this capability. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 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 2021