February 2021 - jboss-jira - Jboss List Archives

[Red Hat JIRA] (DROOLS-6030) Evaluate "KieBase.addPackage" replacement effort from PMML

by Gabriele Cardosi (Jira)

[ https://issues.redhat.com/browse/DROOLS-6030?page=com.atlassian.jira.plug... ] Gabriele Cardosi updated DROOLS-6030: ------------------------------------- Summary: Evaluate "KieBase.addPackage" replacement effort from PMML (was: Evaluate "KieBase.addPackage" removal from PMML) > Evaluate "KieBase.addPackage" replacement effort from PMML > ---------------------------------------------------------- > > Key: DROOLS-6030 > URL: https://issues.redhat.com/browse/DROOLS-6030 > Project: Drools > Issue Type: Task > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Major > > Currently, the method KieBase.addPackage(s) is used inside PMML in two classes > 1) PMMLLoaderService.loadPMMLRuleMappers > 2) PMMLRuntimeFactoryInternal.getPMMLRuntime(String, String, KieBase) > 3) PMMLRuntimeFactoryInternal.createKieBase(KnowledgeBuilderImpl) > In all those cases the needs is to create a "clean" kiebase that contains only the model-specific packages, to avoid name/session clashing. > Scope of the current ticket is to evaluate an alternative, since the method itself is going to be deprecated. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-6030) Evaluate "KieBase.addPackage" removal from PMML

by Gabriele Cardosi (Jira)

Gabriele Cardosi created DROOLS-6030: ---------------------------------------- Summary: Evaluate "KieBase.addPackage" removal from PMML Key: DROOLS-6030 URL: https://issues.redhat.com/browse/DROOLS-6030 Project: Drools Issue Type: Task Reporter: Gabriele Cardosi Assignee: Gabriele Cardosi Currently, the method KieBase.addPackage(s) is used inside PMML in two classes 1) PMMLLoaderService.loadPMMLRuleMappers 2) PMMLRuntimeFactoryInternal.getPMMLRuntime(String, String, KieBase) 3) PMMLRuntimeFactoryInternal.createKieBase(KnowledgeBuilderImpl) In all those cases the needs is to create a "clean" kiebase that contains only the model-specific packages, to avoid name/session clashing. Scope of the current ticket is to evaluate an alternative, since the method itself is going to be deprecated. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (SWSQE-1286) Kiali REST API - Add health filters

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1286?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan commented on SWSQE-1286: --------------------------------------- https://github.com/Kiali-QE/kiali-qe-python/pull/387 > Kiali REST API - Add health filters > ----------------------------------- > > Key: SWSQE-1286 > URL: https://issues.redhat.com/browse/SWSQE-1286 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > > Currently health filters are not applied in list items in kiali_api. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-4397) Make Drools dialect agnostic

by Luca Molteni (Jira)

[ https://issues.redhat.com/browse/DROOLS-4397?page=com.atlassian.jira.plug... ] Luca Molteni updated DROOLS-4397: --------------------------------- Sprint: 2019 Week 44-46 (from Okt 28), 2021 Week 07-09 (from Feb 15) (was: 2019 Week 44-46 (from Okt 28)) > Make Drools dialect agnostic > ---------------------------- > > Key: DROOLS-4397 > URL: https://issues.redhat.com/browse/DROOLS-4397 > Project: Drools > Issue Type: Task > Components: executable model > Reporter: Luca Molteni > Assignee: Luca Molteni > Priority: Major > > By preprocessing it with the mvel compiler before going into the drools-executable-model -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-4397) Make Drools dialect agnostic

by Luca Molteni (Jira)

[ https://issues.redhat.com/browse/DROOLS-4397?page=com.atlassian.jira.plug... ] Luca Molteni updated DROOLS-4397: --------------------------------- Sprint: 2019 Week 44-46 (from Okt 28) (was: 2019 Week 44-46 (from Okt 28), 2021 Week 07-09 (from Feb 15)) > Make Drools dialect agnostic > ---------------------------- > > Key: DROOLS-4397 > URL: https://issues.redhat.com/browse/DROOLS-4397 > Project: Drools > Issue Type: Task > Components: executable model > Reporter: Luca Molteni > Assignee: Luca Molteni > Priority: Major > > By preprocessing it with the mvel compiler before going into the drools-executable-model -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14436) [GSS](7.3.z) Improve error for incorrect class for xa-datasource-class, etc.

by Sudeshna Sur (Jira)

[ https://issues.redhat.com/browse/WFLY-14436?page=com.atlassian.jira.plugi... ] Sudeshna Sur moved JBEAP-21016 to WFLY-14436: --------------------------------------------- Component/s: Server (was: Server) Key: WFLY-14436 (was: JBEAP-21016) Affects Version/s: (was: 7.2.0.GA) (was: 7.3.0.GA) (was: 7.3.6.GA) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Project: WildFly (was: JBoss Enterprise Application Platform) > [GSS](7.3.z) Improve error for incorrect class for xa-datasource-class, etc. > ---------------------------------------------------------------------------- > > Key: WFLY-14436 > URL: https://issues.redhat.com/browse/WFLY-14436 > Project: WildFly > Issue Type: Enhancement > Components: Server > Reporter: Sudeshna Sur > Assignee: Sudeshna Sur > Priority: Minor > > If a driver class (a class implementing {{java.sql.Driver}}) is specified as an {{xa-datasource-class}} in a {{driver}} configuration (in {{[standalone*/domain].xml}}), a generic error is reported: > {noformat} > ... ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 43) WFLYCTL0013: Operation ("add") failed - address: ([ > ("subsystem" => "datasources"), > ("jdbc-driver" => "oracle") > ]) - failure description: "WFLYJCA0114: Failed to load datasource class: oracle.jdbc.OracleDriver" > {noformat} > A similar sort of (generic) failure will arise if a driver class is specified as a {{<datasource-class>}} (though it is not typical to specify a non-XA datasource class). > It would be more helpful to provide something descriptive indicating that the class cannot be cast to {{javax.sql.XADataSource}} which is the underlying reason for the failure - {{OracleDriver}} implements the {{java.sql.Driver}} interface instead of {{javax.sql.XADataSource}} or {{javax.sql.DataSource}}. There is a class cast exception raised at a low level - as captured by a Byteman rule (for exception exit from org.jboss.as.connector.subsystems.datasources.JdbcDriverAdd) - and we should know the type to which cast is attempted in the context of the code below. > {noformat} > ... [BMAN] WFLYJCA0114: Failed to load datasource class: oracle.jdbc.OracleDriver > ... org.jboss.as.controller.OperationFailedException: WFLYJCA0114: Failed to load datasource class: oracle.jdbc.OracleDriver [ "WFLYJCA0114: Failed to load datasource class: oracle.jdbc.OracleDriver" ] > ... at org.jboss.as.connector.subsystems.datasources.JdbcDriverAdd.performRuntime(JdbcDriverAdd.java:128) > ... at org.jboss.as.controller.AbstractAddStepHandler.performRuntime(AbstractAddStepHandler.java:338) > ... at org.jboss.as.controller.AbstractAddStepHandler$1.execute(AbstractAddStepHandler.java:159) > ... at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:999) > ... at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:743) > ... at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:467) > ... at org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:384) > ... at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > ... at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982) > ... at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) > ... at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1348) > ... at java.lang.Thread.run(Thread.java:748) > ... at org.jboss.threads.JBossThread.run(JBossThread.java:485) > ... Caused by: java.lang.ClassCastException: class oracle.jdbc.OracleDriver > ... at java.lang.Class.asSubclass(Class.java:3404) > ... at org.jboss.as.connector.subsystems.datasources.JdbcDriverAdd.performRuntime(JdbcDriverAdd.java:126) > {noformat} > This type of misconfiguration (specifying a driver class as an {{xa-datasource-class}}) could go undetected prior to 7.2 as there was no attempt to instantiate the class (e.g. the {{xa-datasource-class}}) unless a pool of the relevant type (an {{xa-datasource}} pool) was declared. The resolution is to specify an Oracle implementation class that implements the relevant interface (usually {{javax.sql.XADataSource}}) or to remove the {{xa-datasource-class}} (e.g. if no {{xa-datasource}} pool is to be used) or {{datasource-class}} (for non-XA pools neither a driver nor datasource class implementation is usually needed for JDBC 4 compliant implementations). > To reproduce, configuration like the below can be used in {{standalone*.xml}}: > {code:xml} > <datasource jndi-name="java:jboss/datasources/oracle" pool-name="Oracle" enabled="true" jta="true"> > ... > <driver>oracle</driver> > <security> > ... > </security> > </datasource> > ... > <drivers> > <driver name="oracle" module="com.oracle"> > <xa-datasource-class>oracle.jdbc.OracleDriver</xa-datasource-class> > </driver> > ... > </drivers> > {code} > -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14435) Upgrade smallrye-health from 2.2.0 to 2.2.5

by Martin Stefanko (Jira)

Martin Stefanko created WFLY-14435: -------------------------------------- Summary: Upgrade smallrye-health from 2.2.0 to 2.2.5 Key: WFLY-14435 URL: https://issues.redhat.com/browse/WFLY-14435 Project: WildFly Issue Type: Component Upgrade Components: MP Health Affects Versions: 22.0.1.Final Reporter: Martin Stefanko Assignee: Martin Stefanko [https://github.com/smallrye/smallrye-health/releases/tag/2.2.5] Note that this is rendered irrelevant in case MP 4 upgrade will be merged sooner. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (SWSQE-1288) UPI OCP provisioning failing because of missing haproxy package

by Filip Brychta (Jira)

[ https://issues.redhat.com/browse/SWSQE-1288?page=com.atlassian.jira.plugi... ] Filip Brychta resolved SWSQE-1288. ---------------------------------- Release Notes Text: Some tmp issue with subscription manager Resolution: Done > UPI OCP provisioning failing because of missing haproxy package > --------------------------------------------------------------- > > Key: SWSQE-1288 > URL: https://issues.redhat.com/browse/SWSQE-1288 > Project: Kiali QE > Issue Type: Bug > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > The upi job fails because of: > TASK [Install haproxy] ********************************************************* > fatal: [ocp46-sk-services]: FAILED! => \{"changed": false, "msg": "No package matching 'haproxy' found available, installed or updated", "rc": 126, "results": ["No package matching 'haproxy' found available, installed or updated"]} -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14434) Heap usage continuously growing and exhausting available heap memory in production

by Manas Panda (Jira)

Manas Panda created WFLY-14434: ---------------------------------- Summary: Heap usage continuously growing and exhausting available heap memory in production Key: WFLY-14434 URL: https://issues.redhat.com/browse/WFLY-14434 Project: WildFly Issue Type: Task Reporter: Manas Panda Assignee: Brian Stansberry Attachments: Heap_Size_keeps_increasing.jpg, Heap_dump_analysis_1.jpg # Problem description: Critical issue of heap usage continuously growing and exhausting available heap memory in production. As you can see in below heap dump org.infinispan.container.impl.DefaultDataContainer is growing as the time passes and not garbage collected by GC. This increase in heap happening after upgrading from Wildfly 10.1 to Wildfly 18.0.1. There is no change in JDK in both cases ( Wildfly 10.1 and Wildfly 18.0.1). 2. Web application environment * OS: RHEL 7.5 * Wildfly 18.0.1 * JDK 1.8 * Wildfly is being run in cluster mode * Integrated with Keycloak 3.4.3 for SSO ( SAML) * Enabled Wildfly clustering mode * G1GC garbage collector used. And 20gigs of heap allocated ( -Xmx) * Environment of Web App on Wildfly 10.1 is same ( except Wildfly 18) with same hardware * Web application uses Spring web framework and security 3. Heap dump analysis * We have few web users logging in and every second and external application consuming few API’s exposed by same application. * As you can see infinispan.container.impl.DefaultDataContainer Has already grown 14gigs. * Please note that web application does not use infinispan directly. * The heap does not grow in wildfly 10.1 and its normal ( garbage gets collected and size gets reduced after GC) Please find the snapshot as attached. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-10862) Log warning when MP Health reports DOWN

by Martin Stefanko (Jira)

[ https://issues.redhat.com/browse/WFLY-10862?page=com.atlassian.jira.plugi... ] Martin Stefanko edited comment on WFLY-10862 at 2/15/21 7:26 AM: ----------------------------------------------------------------- This is already present in SR Health - [https://github.com/smallrye/smallrye-health/blob/2.2.5/implementation/src... will be solved by upgrading to 2.2.5 or later. was (Author: mstefank): This is already present in SR Health - [https://github.com/smallrye/smallrye-health/blob/2.2.5/implementation/src... will solved by upgrading to 2.2.5 or later. > Log warning when MP Health reports DOWN > --------------------------------------- > > Key: WFLY-10862 > URL: https://issues.redhat.com/browse/WFLY-10862 > Project: WildFly > Issue Type: Enhancement > Components: MP Health > Reporter: Rostislav Svoboda > Assignee: Martin Stefanko > Priority: Major > > Enhance MP Health functionality to log warning when MP Health reports DOWN. > This can be useful when working on investigation / retrospective analysis. > Open Liberty prints following warning when http://localhost:9080/health reports DOWN > {code} > [WARNING ] CWMH0051W: The class com.ibm.ws.microprofile.health.impl.HealthCheckResponseImpl implementing HealthCheckResponse > in the microprofile-health application in module microprofile-health.war, > reported a DOWN outcome DOWN with data Optional[{availability=not available}]. > {code} -- 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 February 2021