February 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-5008) Implement tests for PMML in exec. server (nn, naive bayes, kmeans)

by Jiri Petrlik (Jira)

Jiri Petrlik created DROOLS-5008: ------------------------------------ Summary: Implement tests for PMML in exec. server (nn, naive bayes, kmeans) Key: DROOLS-5008 URL: https://issues.redhat.com/browse/DROOLS-5008 Project: Drools Issue Type: Task Reporter: Jiri Petrlik Assignee: Jiri Petrlik Implement tests for PMML in exec. server * neural network * naive bayes * kmeans -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5008) Implement tests for PMML in exec. server (nn, naive bayes, kmeans)

by Jiri Petrlik (Jira)

[ https://issues.redhat.com/browse/DROOLS-5008?page=com.atlassian.jira.plug... ] Jiri Petrlik updated DROOLS-5008: --------------------------------- Story Points: 3 > Implement tests for PMML in exec. server (nn, naive bayes, kmeans) > ------------------------------------------------------------------ > > Key: DROOLS-5008 > URL: https://issues.redhat.com/browse/DROOLS-5008 > Project: Drools > Issue Type: Task > Reporter: Jiri Petrlik > Assignee: Jiri Petrlik > Priority: Major > Labels: TrustyAI > > Implement tests for PMML in exec. server > * neural network > * naive bayes > * kmeans -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 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 commented on DROOLS-4978: -------------------------------------- Both PRs were merged: https://github.com/kiegroup/drools/pull/2739 https://github.com/kiegroup/kie-jpmml-integration/pull/21 > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2444) Remove ExecutionService

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2444?page=com.atlassian.jira.plugin... ] Bela Ban resolved JGRP-2444. ---------------------------- Resolution: Done > Remove ExecutionService > ----------------------- > > Key: JGRP-2444 > URL: https://issues.redhat.com/browse/JGRP-2444 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 5.0 > > > Nobody uses it -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13064) EJB client-side interceptor failure when using HTTPRemoting Protocol

by Francesco Marchioni (Jira)

Francesco Marchioni created WFLY-13064: ------------------------------------------ Summary: EJB client-side interceptor failure when using HTTPRemoting Protocol Key: WFLY-13064 URL: https://issues.redhat.com/browse/WFLY-13064 Project: WildFly Issue Type: Bug Components: EJB, Test Suite Affects Versions: 19.0.0.Beta1 Reporter: Francesco Marchioni Assignee: Cheng Fang Attachments: surefire-reports-RemoteProtocolChangeClientInterceptorTestCase.zip The following [test|https://github.com/wildfly/wildfly/blob/master/testsuite/integration...] fails in counting the EJB Client Interceptor count, when the HTTP Remoting Protocol is used: {code:java} @Test @InSequence(2) @OperateOnDeployment("client") public void testHttpRemotingProtocol() throws Exception { final Hashtable<String, String> props = new Hashtable<>(); props.put(Context.URL_PKG_PREFIXES, "org.jboss.ejb.client.naming"); props.put(Context.INITIAL_CONTEXT_FACTORY, "org.jboss.naming.remote.client.InitialContextFactory"); props.put(Context.PROVIDER_URL, "http-remoting://" + TestSuiteEnvironment.getServerAddress() + ":" + (TestSuiteEnvironment.getHttpPort() + Integer.parseInt(getSystemProperty("jboss.socket.binding.port-offset", "100")))); StatelessRemote bean = getRemote(new InitialContext(props)); Assert.assertNotNull(bean); // StatelessBean.methodCount field should equal 2 after second invoking (methodCount is a static field and is shared within a single JVM) Assert.assertEquals(ProtocolSampleClientInterceptor.COUNT + 2, bean.method()); } {code} Stack Trace: {code:java} 14:46:01 [ERROR] testHttpRemotingProtocol(org.jboss.as.test.multinode.clientinterceptor.protocol.RemoteProtocolChangeClientInterceptorTestCase) Time elapsed: 0.77 s <<< FAILURE! 14:46:01 java.lang.AssertionError: expected:<12> but was:<11> 14:46:01 at org.junit.Assert.fail(Assert.java:88) 14:46:01 at org.junit.Assert.failNotEquals(Assert.java:834) 14:46:01 at org.junit.Assert.assertEquals(Assert.java:645) 14:46:01 at org.junit.Assert.assertEquals(Assert.java:631) 14:46:01 at org.jboss.as.test.multinode.clientinterceptor.protocol.RemoteProtocolChangeClientInterceptorTestCase.testHttpRemotingProtocol(RemoteProtocolChangeClientInterceptorTestCase.java:130) {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2106) Prepare for JDK 11

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2106?page=com.atlassian.jira.plugin... ] Bela Ban updated JGRP-2106: --------------------------- Description: Investigate the changes needed to run with JDK 11. Probably module.info classes are all that's needed. Other things to investigate: * Replace {{Condition}} with {{Predicate}} * Remove {{FORWARD_TO_COORD}} was: Investigate the changes needed to run with JDK 11. Probably module.info classes are all that's needed. Other things to investigate: * Replace {{Condition}} with {{Predicate}} > Prepare for JDK 11 > ------------------ > > Key: JGRP-2106 > URL: https://issues.redhat.com/browse/JGRP-2106 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 5.0 > > > Investigate the changes needed to run with JDK 11. Probably module.info classes are all that's needed. > Other things to investigate: > * Replace {{Condition}} with {{Predicate}} > * Remove {{FORWARD_TO_COORD}} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2106) Prepare for JDK 11

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2106?page=com.atlassian.jira.plugin... ] Bela Ban updated JGRP-2106: --------------------------- Description: Investigate the changes needed to run with JDK 11. Probably module.info classes are all that's needed. Other things to investigate: * Replace {{Condition}} with {{Predicate}} was:Investigate the changes needed to run with JDK 11. Probably module.info classes are all that's needed. > Prepare for JDK 11 > ------------------ > > Key: JGRP-2106 > URL: https://issues.redhat.com/browse/JGRP-2106 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 5.0 > > > Investigate the changes needed to run with JDK 11. Probably module.info classes are all that's needed. > Other things to investigate: > * Replace {{Condition}} with {{Predicate}} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13063) Change default values of id-cache-size or confirmation-window-size for cluster connections

by Simon Priadka (Jira)

[ https://issues.redhat.com/browse/WFLY-13063?page=com.atlassian.jira.plugi... ] Simon Priadka moved JBEAP-18643 to WFLY-13063: ---------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-13063 (was: JBEAP-18643) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Clustering (was: ActiveMQ) Affects Version/s: 19.0.0.Beta2 (was: 7.3.0.GA) > Change default values of id-cache-size or confirmation-window-size for cluster connections > ------------------------------------------------------------------------------------------ > > Key: WFLY-13063 > URL: https://issues.redhat.com/browse/WFLY-13063 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 19.0.0.Beta2 > Reporter: Simon Priadka > Assignee: Justin Bertram > Priority: Major > > When establishing a new messaging cluster, default values of *id-cache-size* and *confirmation-window-size* are producing a *WARN* with following message: > {code} > 2020-02-04 21:35:20,228 WARN [org.apache.activemq.artemis.core.server] (Thread-2 (ActiveMQ-client-global-threads)) AMQ224078: The size of duplicate cache detection (<id_cache-size/>) appears to be too large 20,000. It should be no greater than the number of messages that can be squeezed into confirmation window buffer (<confirmation-window-size/>) 1,048,576. > {code} > According to the [method|https://github.com/apache/activemq-artemis/blob/3743bc9d9f39b0731f...] validating these values, this variable combination is "invalid" -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2446) MessageBatch: iterate with filter

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2446?page=com.atlassian.jira.plugin... ] Bela Ban resolved JGRP-2446. ---------------------------- Resolution: Done > MessageBatch: iterate with filter > --------------------------------- > > Key: JGRP-2446 > URL: https://issues.redhat.com/browse/JGRP-2446 > Project: JGroups > Issue Type: Enhancement > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 5.0 > > > Create a {{MessageBatch.BatchIterator}} with a predicate that defines which messages are selected by the iterator. Non-selected messages are skipped. > See the code in Pedro's branch [1]. > [1] https://github.com/pruivo/JGroups/tree/t_msg_batch_iterator -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4482) Out of the box SSL with Wildfly Elytron

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFCORE-4482?page=com.atlassian.jira.plug... ] Darran Lofthouse updated WFCORE-4482: ------------------------------------- Fix Version/s: (was: 11.0.0.Beta9) > Out of the box SSL with Wildfly Elytron > --------------------------------------- > > Key: WFCORE-4482 > URL: https://issues.redhat.com/browse/WFCORE-4482 > Project: WildFly Core > Issue Type: Feature Request > Components: Security > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > Labels: EAP-CD19 > > The details of this RFE will be explored within the analysis, presently Undertow depends on a security-realm that generates a self signed cert on start up so we will require an Elytron equivalent. > There may be opportunities to tie this in in some way with the new CA integration support but that can be explored in the analysis. -- This message was sent by Atlassian Jira (v7.13.8#713008)

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