February 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-13170) AutoClosable behaviour from MP Config spec is not implemented

by Marek Kopecky (Jira)

[ https://issues.redhat.com/browse/WFLY-13170?page=com.atlassian.jira.plugi... ] Marek Kopecky moved WFWIP-304 to WFLY-13170: -------------------------------------------- Project: WildFly (was: WildFly WIP) Key: WFLY-13170 (was: WFWIP-304) > AutoClosable behaviour from MP Config spec is not implemented > ------------------------------------------------------------- > > Key: WFLY-13170 > URL: https://issues.redhat.com/browse/WFLY-13170 > Project: WildFly > Issue Type: Bug > Reporter: Marek Kopecky > Assignee: Jeff Mesnil > Priority: Critical > > Current implementation MP Config 1.4 doesn t implement AutoCloseable behaviour on ConfigSource and Converter classes. Developers create [MP issue|https://github.com/eclipse/microprofile-config/issues/136], because these specification requirements seems confusing and unclear to them. [This issue|https://github.com/eclipse/microprofile-config/issues/136] is not approved as a bug from MP community. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-309) MP Fault Tolerance - WELD-001303: No active contexts for scope type javax.enterprise.context.ApplicationScoped

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFWIP-309?page=com.atlassian.jira.plugin... ] Radoslav Husar commented on WFWIP-309: -------------------------------------- Thanks guys. Just to note, I have a fix and will update the PR with a fix later today. > MP Fault Tolerance - WELD-001303: No active contexts for scope type javax.enterprise.context.ApplicationScoped > -------------------------------------------------------------------------------------------------------------- > > Key: WFWIP-309 > URL: https://issues.redhat.com/browse/WFWIP-309 > Project: WildFly WIP > Issue Type: Bug > Components: MP Fault Tolerance > Reporter: Miroslav Novak > Assignee: Radoslav Husar > Priority: Blocker > > There is unexpected error log in following test scenario: > - Deploy MP FT service with: > {noformat} > @Asynchronous > @Bulkhead(value = 15, waitingTaskQueue = 15) > @Timeout(value = 1000) > @Fallback(fallbackMethod = "processFallback") > public CompletionStage<MyConnection> bulkheadTimeout(boolean fail) throws InterruptedException { > if (fail) { > Thread.sleep(2000); > } > return CompletableFuture.completedFuture(new MyConnection() { > @Override > public String getData() { > return "Hello from @Bulkhead @Timeout method"; > } > }); > } > private CompletionStage<MyConnection> processFallback(boolean fail) { > return CompletableFuture.completedFuture(new MyConnection() { > @Override > public String getData() { > return "Fallback Hello"; > } > }); > } > {noformat} > - Send 10+ parallel requests with fail == true > Expected result: > All requests should go to fallback. > Actual Result: > This test is currently hitting issue WFWIP-308 however additionally there is error in server log: > {code} > 16:55:41,374 ERROR [stderr] (pool-22-thread-2) Exception in thread "pool-22-thread-4" Exception in thread "pool-22-thread-2" org.jboss.weld.contexts.ContextNotActiveException: WELD-001303: No active contexts for scope type javax.enterprise.context.ApplicationScoped > 16:55:41,374 ERROR [stderr] (pool-22-thread-2) at org.jboss.weld.manager.BeanManagerImpl.getContext(BeanManagerImpl.java:647) > 16:55:41,374 ERROR [stderr] (pool-22-thread-2) at org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.getIfExists(ContextualInstanceStrategy.java:89) > 16:55:41,374 ERROR [stderr] (pool-22-thread-2) at org.jboss.weld.bean.ContextualInstanceStrategy$ApplicationScopedContextualInstanceStrategy.getIfExists(ContextualInstanceStrategy.java:123) > 16:55:41,374 ERROR [stderr] (pool-22-thread-2) at org.jboss.weld.bean.ContextualInstance.getIfExists(ContextualInstance.java:63) > 16:55:41,374 ERROR [stderr] (pool-22-thread-2) at org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:87) > 16:55:41,375 ERROR [stderr] (pool-22-thread-2) at org.jboss.weld.bean.proxy.ProxyMethodHandler.getInstance(ProxyMethodHandler.java:131) > 16:55:41,375 ERROR [stderr] (pool-22-thread-2) at org.eclipse.microprofile.metrics.MetricRegistry$Proxy$_$$_WeldClientProxy.getHistograms(Unknown Source) > 16:55:41,375 ERROR [stderr] (pool-22-thread-2) at io.smallrye.faulttolerance.metrics.MetricsCollectorFactory$MetricsCollectorImpl.histogramOf(MetricsCollectorFactory.java:105) > 16:55:41,375 ERROR [stderr] (pool-22-thread-2) at io.smallrye.faulttolerance.metrics.MetricsCollectorFactory$MetricsCollectorImpl.histogramUpdate(MetricsCollectorFactory.java:86) > 16:55:41,375 ERROR [stderr] (pool-22-thread-2) at io.smallrye.faulttolerance.metrics.MetricsCollectorFactory$MetricsCollectorImpl.bulkheadQueueLeft(MetricsCollectorFactory.java:125) > 16:55:41,375 ERROR [stderr] (pool-22-thread-2) at io.smallrye.faulttolerance.core.bulkhead.CompletionStageBulkhead$CompletionStageBulkheadTask.run(CompletionStageBulkhead.java:78) > 16:55:41,375 ERROR [stderr] (pool-22-thread-2) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > 16:55:41,375 ERROR [stderr] (pool-22-thread-2) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > 16:55:41,375 ERROR [stderr] (pool-22-thread-2) at java.lang.Thread.run(Thread.java:748) > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13169) Enhance README of ejb-remote quickstart to be easier to setup the server

by Ondrej Chaloupka (Jira)

Ondrej Chaloupka created WFLY-13169: --------------------------------------- Summary: Enhance README of ejb-remote quickstart to be easier to setup the server Key: WFLY-13169 URL: https://issues.redhat.com/browse/WFLY-13169 Project: WildFly Issue Type: Enhancement Components: Quickstarts Affects Versions: 19.0.0.Beta2 Reporter: Ondrej Chaloupka Assignee: Ondrej Chaloupka The `ejb-remote` quickstart (https://github.com/wildfly/quickstart/tree/19.0.0.Beta2/ejb-remote) provides guidelines how to configure server and run ejb remote calls from client to server. The text in README misses two points * the server has to be setup with user/password credentials for the client may connect to it (otherwise the invocation failse). There is such information in the text but at the end of the guide and not at the place before the server is started (which is the correct location for it) * there is not mentioned that's possible to run the client code without `mvn exec:exec` as the maven assembly plugin is configured in `pom.xml`. The text should contain a note how to run the assembly plugin and how then execute the client code. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-166) IllegalThreadStateException after idle jmx connection

by Shaun Appleton (Jira)

[ https://issues.redhat.com/browse/REMJMX-166?page=com.atlassian.jira.plugi... ] Shaun Appleton updated REMJMX-166: ---------------------------------- Priority: Blocker (was: Major) > IllegalThreadStateException after idle jmx connection > ----------------------------------------------------- > > Key: REMJMX-166 > URL: https://issues.redhat.com/browse/REMJMX-166 > Project: Remoting JMX > Issue Type: Bug > Components: Connection > Affects Versions: 3.0.2.Final, 3.0.3.Final > Environment: org.jboss.remotingjmx:remoting-jmx:3.0.3.Final + java8 > Reporter: Märt Bakhoff > Assignee: Darran Lofthouse > Priority: Blocker > > Start wildfly-17.0.1/bin/standalone.sh, then run this code snippet: > {noformat} > JMXServiceURL url = new JMXServiceURL("service:jmx:remote+http://127.0.0.1:9990"); > try (JMXConnector connector = new RemotingConnectorProvider().newJMXConnector(url, Collections.emptyMap())) { > connector.connect(); > MBeanServerConnection beanServer = connector.getMBeanServerConnection(); > RuntimeMXBean bean = ManagementFactory.newPlatformMXBeanProxy(beanServer, ManagementFactory.RUNTIME_MXBEAN_NAME, RuntimeMXBean.class); > Thread.sleep(70_000); > System.out.println("uptime: " + bean.getUptime()); > } > {noformat} > The following exception is always thrown: > {noformat} > Exception in thread "XNIO-1 task-12" java.lang.IllegalThreadStateException > at java.lang.ThreadGroup.addUnstarted(ThreadGroup.java:867) > at java.lang.Thread.init(Thread.java:405) > at java.lang.Thread.init(Thread.java:349) > at java.lang.Thread.<init>(Thread.java:599) > at org.jboss.remotingjmx.protocol.v2.ClientExecutorManager$1.newThread(ClientExecutorManager.java:56) > at java.util.concurrent.ThreadPoolExecutor$Worker.<init>(ThreadPoolExecutor.java:619) > at java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:932) > at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1378) > at org.jboss.remotingjmx.protocol.v2.ClientExecutorManager.execute(ClientExecutorManager.java:64) > at org.jboss.remotingjmx.protocol.v2.ClientCommon$MessageReceiver.handleMessage(ClientCommon.java:118) > at org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$handleMessageData$3(RemoteConnectionChannel.java:430) > at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:926) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > {noformat} > The cause is in org.jboss.remotingjmx.protocol.v2.ClientExecutorManager.<init>. It creates a thread pool with Executors.newCachedThreadPool that has the default keepAliveTime of 60s. > The thread factory is using a daemon thread group REMOTING_JMX that will self-destruct when the cached thread is terminated. > The same code works when using older org.jboss.remotingjmx:remoting-jmx:3.0.1.Final. The regression is likely caused by commit https://github.com/jbossas/remoting-jmx/commit/2d6ae6c26da43304b752fc48f1... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5112) DMN kie-server wrong cast message reported on FEEL failure

by Matteo Mortari (Jira)

Matteo Mortari created DROOLS-5112: -------------------------------------- Summary: DMN kie-server wrong cast message reported on FEEL failure Key: DROOLS-5112 URL: https://issues.redhat.com/browse/DROOLS-5112 Project: Drools Issue Type: Bug Components: dmn engine Reporter: Matteo Mortari Assignee: Matteo Mortari {code:java} 10:38:53,533 ERROR [org.kie.dmn.feel.runtime.functions.AbsFunction] (default task-26) Error trying to call function abs.: java.lang.ClassCastException: org.kie.server.services.prometheus.PrometheusMetricsDMNListener cannot be cast to org.kie.dmn.api.feel.runtime.events.FEELEventListener at java.lang.Iterable.forEach(Iterable.java:75) at org.kie.dmn.feel.lang.impl.FEELEventListenersManager.notifyListeners(FEELEventListenersManager.java:71) at org.kie.dmn.feel.lang.impl.FEELEventListenersManager.notifyListeners(FEELEventListenersManager.java:82) at org.kie.dmn.feel.lang.impl.EvaluationContextImpl.notifyEvt(EvaluationContextImpl.java:178) at org.kie.dmn.feel.runtime.functions.BaseFEELFunction.lambda$invokeReflectively$3(BaseFEELFunction.java:97) at org.kie.dmn.feel.util.Either.cata(Either.java:70) at org.kie.dmn.feel.runtime.functions.BaseFEELFunction.invokeReflectively(BaseFEELFunction.java:96) at org.kie.dmn.feel.lang.ast.FunctionInvocationNode.invokeTheFunction(FunctionInvocationNode.java:112) at org.kie.dmn.feel.lang.ast.FunctionInvocationNode.evaluate(FunctionInvocationNode.java:90) at org.kie.dmn.feel.lang.impl.CompiledExpressionImpl.apply(CompiledExpressionImpl.java:47) at org.kie.dmn.feel.lang.impl.InterpretedExecutableExpression.apply(InterpretedExecutableExpression.java:38) at org.kie.dmn.feel.lang.impl.InterpretedExecutableExpression.apply(InterpretedExecutableExpression.java:24) at org.kie.dmn.feel.codegen.feel11.ProcessedExpression.apply(ProcessedExpression.java:114) at org.kie.dmn.feel.codegen.feel11.ProcessedExpression.apply(ProcessedExpression.java:22) at org.kie.dmn.feel.lang.impl.FEELImpl.evaluate(FEELImpl.java:167) at org.kie.dmn.core.ast.DMNLiteralExpressionEvaluator.evaluate(DMNLiteralExpressionEvaluator.java:73) at org.kie.dmn.core.impl.DMNRuntimeImpl.evaluateDecision(DMNRuntimeImpl.java:664) at org.kie.dmn.core.impl.DMNRuntimeImpl.evaluateAll(DMNRuntimeImpl.java:163) at org.kie.dmn.core.internal.utils.DMNEvaluationUtils.evaluate(DMNEvaluationUtils.java:87) at org.kie.dmn.core.internal.utils.DMNEvaluationUtils.evaluate(DMNEvaluationUtils.java:51) at org.kie.server.services.dmn.ModelEvaluatorServiceBase.evaluateDecisions(ModelEvaluatorServiceBase.java:184) at org.kie.server.remote.rest.dmn.ModelEvaluatorResource.evaluateDecisions(ModelEvaluatorResource.java:108) {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5111) DMN editor smartcomplete prevent Save and allow leave changed page

by Daniele Zonca (Jira)

[ https://issues.redhat.com/browse/DROOLS-5111?page=com.atlassian.jira.plug... ] Daniele Zonca commented on DROOLS-5111: --------------------------------------- Changed priority to critical because user can loose his changes > DMN editor smartcomplete prevent Save and allow leave changed page > ------------------------------------------------------------------ > > Key: DROOLS-5111 > URL: https://issues.redhat.com/browse/DROOLS-5111 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Matteo Mortari > Assignee: Guilherme Gomes > Priority: Critical > Labels: drools-tools > Attachments: smartcompletePreventSaveAllowLeavePage.mov > > > While editing a smartcomplete cell, cannot Save. > Also it's possible to leave the page despite changes --which are not saved. > See attached. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5111) DMN editor smartcomplete prevent Save and allow leave changed page

by Daniele Zonca (Jira)

[ https://issues.redhat.com/browse/DROOLS-5111?page=com.atlassian.jira.plug... ] Daniele Zonca updated DROOLS-5111: ---------------------------------- Priority: Critical (was: Major) > DMN editor smartcomplete prevent Save and allow leave changed page > ------------------------------------------------------------------ > > Key: DROOLS-5111 > URL: https://issues.redhat.com/browse/DROOLS-5111 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Matteo Mortari > Assignee: Guilherme Gomes > Priority: Critical > Labels: drools-tools > Attachments: smartcompletePreventSaveAllowLeavePage.mov > > > While editing a smartcomplete cell, cannot Save. > Also it's possible to leave the page despite changes --which are not saved. > See attached. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5111) DMN editor smartcomplete prevent Save and allow leave changed page

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-5111?page=com.atlassian.jira.plug... ] Michael Anstis updated DROOLS-5111: ----------------------------------- Labels: drools-tools (was: ) > DMN editor smartcomplete prevent Save and allow leave changed page > ------------------------------------------------------------------ > > Key: DROOLS-5111 > URL: https://issues.redhat.com/browse/DROOLS-5111 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Matteo Mortari > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > Attachments: smartcompletePreventSaveAllowLeavePage.mov > > > While editing a smartcomplete cell, cannot Save. > Also it's possible to leave the page despite changes --which are not saved. > See attached. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5111) DMN editor smartcomplete prevent Save and allow leave changed page

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-5111?page=com.atlassian.jira.plug... ] Michael Anstis reassigned DROOLS-5111: -------------------------------------- Assignee: Guilherme Gomes (was: Michael Anstis) > DMN editor smartcomplete prevent Save and allow leave changed page > ------------------------------------------------------------------ > > Key: DROOLS-5111 > URL: https://issues.redhat.com/browse/DROOLS-5111 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Matteo Mortari > Assignee: Guilherme Gomes > Priority: Major > Attachments: smartcompletePreventSaveAllowLeavePage.mov > > > While editing a smartcomplete cell, cannot Save. > Also it's possible to leave the page despite changes --which are not saved. > See attached. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5111) DMN editor smartcomplete prevent Save and allow leave changed page

by Matteo Mortari (Jira)

Matteo Mortari created DROOLS-5111: -------------------------------------- Summary: DMN editor smartcomplete prevent Save and allow leave changed page Key: DROOLS-5111 URL: https://issues.redhat.com/browse/DROOLS-5111 Project: Drools Issue Type: Bug Components: DMN Editor Reporter: Matteo Mortari Assignee: Michael Anstis Attachments: smartcompletePreventSaveAllowLeavePage.mov While editing a smartcomplete cell, cannot Save. Also it's possible to leave the page despite changes --which are not saved. See attached. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 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 2020