February 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-13077) Support protostream-based marshalling of user objects

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFLY-13077?page=com.atlassian.jira.plugi... ] Paul Ferraro updated WFLY-13077: -------------------------------- Description: Currently, WildFly uses JBoss Marshalling to marshal user objects (session attributes, SFSB instances) for the purposes of replication and persistence. Protostream (developed by the Infinispan team) offers several advantages over JBoss Marshalling. * Lower memory footprint (marshalling schemas are built during compilation time) * Faster marshalling - as it does not rely on reflection * Produces generally smaller replication payloads (see https://docs.google.com/spreadsheets/d/1f6FlXqxX7dYm44naHZfqLc5TjqlmscIdG... ) * Resolves security concerns due to JBM's reliance on reflection and Java serialization inherently permitting arbitrary execution of rogue code * JBoss Marshalling is effectively in maintenance mode We can either auto-detect the intended marshaller by looking for requisite SerializationContextInitializers in the deployment classpath, and/or use an explicit configuration attribute. was: Currently, WildFly uses JBoss Marshalling to marshal user objects (session attributes, SFSB instances) for the purposes of replication and persistence. Protostream (developed by the Infinispan team) offers several advantages over JBoss Marshalling. * Lower memory footprint (marshalling schemas are built during compilation time) * Faster marshalling - as it does not rely on reflection * Produces generally smaller replication payloads (see https://docs.google.com/spreadsheets/d/1f6FlXqxX7dYm44naHZfqLc5TjqlmscIdG... ) * Resolves security concerns due to JBM's reliance on reflection and Java serialization inherently permitting arbitrary execution of rogue code * JBoss Marshalling is effectively in maintenance mode > Support protostream-based marshalling of user objects > ----------------------------------------------------- > > Key: WFLY-13077 > URL: https://issues.redhat.com/browse/WFLY-13077 > Project: WildFly > Issue Type: Feature Request > Reporter: Paul Ferraro > Priority: Major > > Currently, WildFly uses JBoss Marshalling to marshal user objects (session attributes, SFSB instances) for the purposes of replication and persistence. > Protostream (developed by the Infinispan team) offers several advantages over JBoss Marshalling. > * Lower memory footprint (marshalling schemas are built during compilation time) > * Faster marshalling - as it does not rely on reflection > * Produces generally smaller replication payloads (see https://docs.google.com/spreadsheets/d/1f6FlXqxX7dYm44naHZfqLc5TjqlmscIdG... ) > * Resolves security concerns due to JBM's reliance on reflection and Java serialization inherently permitting arbitrary execution of rogue code > * JBoss Marshalling is effectively in maintenance mode > We can either auto-detect the intended marshaller by looking for requisite SerializationContextInitializers in the deployment classpath, and/or use an explicit configuration attribute. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13077) Support protostream-based marshalling of user objects

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFLY-13077?page=com.atlassian.jira.plugi... ] Paul Ferraro moved EAP7-1436 to WFLY-13077: ------------------------------------------- Project: WildFly (was: JBoss EAP Planning for version 7 and above) Key: WFLY-13077 (was: EAP7-1436) Issue Type: Feature Request (was: Requirement) Workflow: GIT Pull Request workflow (was: EAP Agile Workflow 2.0) EAP PT Pre-Checked (PC): (was: TODO) EAP PT Community Docs (CD): (was: TODO) EAP PT Product Docs (PD): (was: New) EAP PT Test Dev (TD): (was: TODO) EAP PT Docs Analysis (DA): (was: TODO) EAP PT Test Plan (TP): (was: TODO) EAP PT Analysis Document (AD): (was: TODO) > Support protostream-based marshalling of user objects > ----------------------------------------------------- > > Key: WFLY-13077 > URL: https://issues.redhat.com/browse/WFLY-13077 > Project: WildFly > Issue Type: Feature Request > Reporter: Paul Ferraro > Priority: Major > > Currently, WildFly uses JBoss Marshalling to marshal user objects (session attributes, SFSB instances) for the purposes of replication and persistence. > Protostream (developed by the Infinispan team) offers several advantages over JBoss Marshalling. > * Lower memory footprint (marshalling schemas are built during compilation time) > * Faster marshalling - as it does not rely on reflection > * Produces generally smaller replication payloads (see https://docs.google.com/spreadsheets/d/1f6FlXqxX7dYm44naHZfqLc5TjqlmscIdG... ) > * Resolves security concerns due to JBM's reliance on reflection and Java serialization inherently permitting arbitrary execution of rogue code > * JBoss Marshalling is effectively in maintenance mode -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4781) Ability to enable shutdown operation for EmbeddedServer

by Jean Francois Denise (Jira)

[ https://issues.redhat.com/browse/WFCORE-4781?page=com.atlassian.jira.plug... ] Jean Francois Denise commented on WFCORE-4781: ---------------------------------------------- [~jamezp], instead of Runnable, a Consumer<Integer> would allow to implement a restart based on status. > Ability to enable shutdown operation for EmbeddedServer > ------------------------------------------------------- > > Key: WFCORE-4781 > URL: https://issues.redhat.com/browse/WFCORE-4781 > Project: WildFly Core > Issue Type: Enhancement > Components: Embedded > Affects Versions: 11.0.0.Beta5 > Reporter: Jean Francois Denise > Assignee: James Perkins > Priority: Major > > Having the shutdown operation available for embedded is needed when the embedder process and embedded server shutdown phase are bound. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4967) decision table rules are not loaded into kiebase

by Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-4967?page=com.atlassian.jira.plug... ] Mario Fusco updated DROOLS-4967: -------------------------------- Sprint: 2020 Week 07-09 (from Feb 10) (was: 2020 Week 04-06 (from Jan 20)) > decision table rules are not loaded into kiebase > ------------------------------------------------ > > Key: DROOLS-4967 > URL: https://issues.redhat.com/browse/DROOLS-4967 > Project: Drools > Issue Type: Bug > Components: decision tables > Affects Versions: 7.21.0.Final, 7.22.0.Final, 7.23.0.Final, 7.24.0.Final, 7.25.0.Final, 7.26.0.Final, 7.27.0.Final, 7.28.0.Final, 7.29.0.Final, 7.30.0.Final, 7.31.0.Final > Reporter: Volodymyr Shymkiv > Assignee: Mario Fusco > Priority: Blocker > Attachments: CanDrink2.xls, CanNotDrink2.xls, DROOLS-4967_package_highlight.png > > > When compiling xls decision table, wrong ruleset name is parsed from the xls file. This can lead to multiple issues, like rules being filtered out by kmodule.xml configuration. > According to documentation, decision table begins with a cell at second or third column, having value RuleSet. The cell on the right of this one contains the name of the rule set, which we want to use as a package name. > The problem lies in naive approach to parsing the package name from the xls file. As you can see in project drools-compiler, class org.drools.compiler.kie.builder.impl.KieBuilderImpl method packageNameFromDtable, it execute as follows: > # find "RuleSet" string in the binary data > # find and return the nearest string which can act as a valid java package name > The problem is, the string returned from packageNameFromDtable is NOT the value of the cell next to the RuleSet. It is actually a value of a random cell. > To understand the problem, we need to understand the binary content of the actual xls file. Every cell is presented as a few bytes, containing cell's value, position, and other information. The "problematic" thing here is, the _order_ of the cells in the binary data is NOT constant. BUT the code really just reads the cell _binary_ next to the "RuleSet" cell. > Problem is present since version 7.21 as it is caused by a fix for DROOLS-3888 - commit 9a179b6e6b955889200b0258ccd18cd1a5f14b46 > In our case, this results in rules not being loaded, as they are filtered out by kmodule.xml configuration. We have a lot of decision tables we want to migrate from an older drools version, and most of them are now ignored due to this bug. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5030) Allow to create the executable model directly from descr objects (drl AST)

by Mario Fusco (Jira)

Mario Fusco created DROOLS-5030: ----------------------------------- Summary: Allow to create the executable model directly from descr objects (drl AST) Key: DROOLS-5030 URL: https://issues.redhat.com/browse/DROOLS-5030 Project: Drools Issue Type: Task Reporter: Mario Fusco Assignee: Mario Fusco -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13076) Opentracing fails to load on EAR deployment

by Roy Golan (Jira)

Roy Golan created WFLY-13076: -------------------------------- Summary: Opentracing fails to load on EAR deployment Key: WFLY-13076 URL: https://issues.redhat.com/browse/WFLY-13076 Project: WildFly Issue Type: Bug Components: MP OpenTracing Affects Versions: 18.0.1.Final Reporter: Roy Golan Assignee: Emmanuel Hugonnet wildfly 18, an EAR application (ovirt-engine ), I'm trying to enable opentracing, and failing. I added this to our xml: ``` <extension module="org.wildfly.extension.microprofile.opentracing-smallrye"/> ... <subsystem xmlns="urn:wildfly:microprofile-opentracing-smallrye:1.0"/> ``` Exported Jaeger environment vars: ``` export JAEGER_SERVICE_NAME=ovirt-engine export JAEGER_REPORTER_LOG_SPANS=true export JAEGER_SAMPLER_TYPE=const export JAEGER_SAMPLER_PARAM=1 ``` And debugged the `TracerProducer` which throws: ``` "Method threw 'org.jboss.weld.exceptions.IllegalStateException' exception. Cannot evaluate org.jboss.weldx.servlet.ServletContext$$Proxy$_$$_WeldClientProxy.toString()" ``` The deployment structure is: | engine.ear - bll.jar EJB and CDI beans - lib/vdsbroker CDI | restapi.war JAXRS , also CDI beans | Jboss-Modules common.jar utils.jar dal.jar CDI -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10655) SEVERE error on deploy of ear: "Unable to obtain CDI 1.1 utilities for Mojarra"

by Lorenzo Verri (Jira)

[ https://issues.redhat.com/browse/WFLY-10655?page=com.atlassian.jira.plugi... ] Lorenzo Verri commented on WFLY-10655: -------------------------------------- Also happening on WildFly 18.0.0.Final. > SEVERE error on deploy of ear: "Unable to obtain CDI 1.1 utilities for Mojarra" > ------------------------------------------------------------------------------- > > Key: WFLY-10655 > URL: https://issues.redhat.com/browse/WFLY-10655 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld, JSF > Affects Versions: 13.0.0.Final > Reporter: Tommasso Borgato > Assignee: Dmitrii Tikhomirov > Priority: Major > Labels: downstream_dependency > Fix For: 14.0.0.Beta2 > > Attachments: clusterbench-ee7-bugged.ear, clusterbench-ee7.ear > > > Affected scenario is [eap-7x-failover-ejb-ejbservlet-undeploy-repl-sync|https://jenkins.hosts.m...]. > Every time the server is stated or re-started, we observed the following SEVERE logs just after clusterbench is deployed (clusterbench is an ear that uses JSF); we observed them systematically on each of the 4 nodes composing the cluster: > {noformat} > 2018-06-27 02:47:07,439 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 72) WFLYCLINF0002: Started clusterbench-ee7.ear.clusterbench-ee7-web-granular.war cache from web container > 2018-06-27 02:47:07,440 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 75) WFLYCLINF0002: Started client-mappings cache from ejb container > 2018-06-27 02:47:07,440 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 73) WFLYCLINF0002: Started clusterbench-ee7.ear.clusterbench-ee7-web-default.war cache from web container > 2018-06-27 02:47:07,440 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 74) WFLYCLINF0002: Started default-server cache from web container > 2018-06-27 02:47:07,439 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 76) WFLYCLINF0002: Started clusterbench-ee7.ear.clusterbench-ee7-web-passivating.war cache from web container > 2018-06-27 02:47:07,578 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 75) WFLYCLINF0002: Started clusterbench-ee7.ear/clusterbench-ee7-ejb.jar cache from ejb container > 2018-06-27 02:47:07,673 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-7) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class org.jberet.creation.BatchBeanProducer is deprecated from CDI 1.1! > 2018-06-27 02:47:07,713 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-7) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class org.hibernate.validator.internal.cdi.interceptor.ValidationInterceptor is deprecated from CDI 1.1! > 2018-06-27 02:47:07,739 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-7) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class com.sun.faces.flow.FlowDiscoveryCDIHelper is deprecated from CDI 1.1! > 2018-06-27 02:47:08,149 SEVERE [javax.enterprise.resource.webcontainer.jsf.flow] (MSC service thread 1-7) Unable to obtain CDI 1.1 utilities for Mojarra > 2018-06-27 02:47:08,163 SEVERE [javax.enterprise.resource.webcontainer.jsf.application.view] (MSC service thread 1-7) Unable to obtain CDI 1.1 utilities for Mojarra > 2018-06-27 02:47:08,586 INFO [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 76) Initializing Mojarra 2.2.13.SP5 for context '/clusterbench-granular' > 2018-06-27 02:47:08,586 INFO [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 72) Initializing Mojarra 2.2.13.SP5 for context '/clusterbench' > 2018-06-27 02:47:08,587 INFO [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 78) Initializing Mojarra 2.2.13.SP5 for context '/clusterbench-passivating' > 2018-06-27 02:47:09,860 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 76) WFLYUT0021: Registered web context: '/clusterbench-granular' for server 'default-server' > 2018-06-27 02:47:09,863 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 72) WFLYUT0021: Registered web context: '/clusterbench' for server 'default-server' > 2018-06-27 02:47:09,863 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 78) WFLYUT0021: Registered web context: '/clusterbench-passivating' for server 'default-server' > 2018-06-27 02:47:09,889 INFO [org.jboss.as.server] (ServerService Thread Pool -- 42) WFLYSRV0010: Deployed "clusterbench-ee7.ear" (runtime-name : "clusterbench-ee7.ear") > 2018-06-27 02:47:09,989 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server > {noformat} > > Complete log [here|https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/job/perflab_eap...] > Already observed a very long time ago: https://issues.jboss.org/browse/WFLY-1946 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5018) DMN internal refactor for itemDef isCollection

by Matteo Mortari (Jira)

[ https://issues.redhat.com/browse/DROOLS-5018?page=com.atlassian.jira.plug... ] Matteo Mortari updated DROOLS-5018: ----------------------------------- Description: Externalise feel collection type synthesis out of the DMNType constructors. Ref: https://github.com/kiegroup/drools-wb/pull/1303#issue-371882901 (was: Avoid .setCollection() that means avoid clone()) > DMN internal refactor for itemDef isCollection > ---------------------------------------------- > > Key: DROOLS-5018 > URL: https://issues.redhat.com/browse/DROOLS-5018 > Project: Drools > Issue Type: Task > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Major > > Externalise feel collection type synthesis out of the DMNType constructors. Ref: https://github.com/kiegroup/drools-wb/pull/1303#issue-371882901 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5018) DMN internal refactor for itemDef isCollection

by Matteo Mortari (Jira)

[ https://issues.redhat.com/browse/DROOLS-5018?page=com.atlassian.jira.plug... ] Matteo Mortari updated DROOLS-5018: ----------------------------------- Summary: DMN internal refactor for itemDef isCollection (was: DMN internal refactor for itemDef isCollection/clone) > DMN internal refactor for itemDef isCollection > ---------------------------------------------- > > Key: DROOLS-5018 > URL: https://issues.redhat.com/browse/DROOLS-5018 > Project: Drools > Issue Type: Task > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Major > > Avoid .setCollection() > that means avoid clone() -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5029) Loose of focus after cloasing Collection Editor

by Daniele Zonca (Jira)

[ https://issues.redhat.com/browse/DROOLS-5029?page=com.atlassian.jira.plug... ] Daniele Zonca reassigned DROOLS-5029: ------------------------------------- Assignee: Yeser Amer (was: Daniele Zonca) > Loose of focus after cloasing Collection Editor > ----------------------------------------------- > > Key: DROOLS-5029 > URL: https://issues.redhat.com/browse/DROOLS-5029 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Affects Versions: 7.33.0.Final > Reporter: Anna Dupliak > Assignee: Yeser Amer > Priority: Optional > Labels: drools-tools > > When user finishes with editing collections, using Collection Editor and push *Close* or *Save* or *Cansel* then Grid of Test scenario is loosing focus and user unable to navigate it by keyboard. > Suggested behaviour: > When Collection Editor disappears after editing Collection cell A then focus should be on the cell of A. -- This message was sent by Atlassian Jira (v7.13.8#713008)

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