January 2021 - jboss-jira - Jboss List Archives

[Red Hat JIRA] (DROOLS-5970) Promethus integration with Kie server issue

by Ali Hussain (Jira)

[ https://issues.redhat.com/browse/DROOLS-5970?page=com.atlassian.jira.plug... ] Ali Hussain updated DROOLS-5970: -------------------------------- Description: I am using Drools Workbench Docker image and Kie server Docker image. i need to expose the Kie server rest point for Prometheus metrics. For this i updated the standalone.xml and add this {{org.kie.prometheus.server.ext.disabled}} system property to {{false}} to enable the Prometheus extension and restarted the Kie server. but kie server is not exposing the rest resource. RESTEASY003210: Could not find resource for full path: [http://localhost:8280/kie-server/services/rest/metrics] error occurred when i try to hit this endpoint {{[http://HOST:PORT/SERVER/services/rest/metric]}} although i updated the standalone.xml as it is mention in documentation. i dont know the reason. very less information is available online, Kindly update this issue. was: I am using Drools Workbench Docker image and Kie server Docker image. i need to expose the Kie server rest point for Prometheus metrics. For this i updated the standalone.xml and add this {{org.kie.prometheus.server.ext.disabled}} system property to {{false}} to enable the Prometheus extension and restarted the Kie server. but kie server is not exposing the rest resource. Page not found error when i try to hit this endpoint {{http://HOST:PORT/SERVER/services/rest/metric}} although i updated the standalone.xml as it is mention in documentation. i dont know the reason. very less information is available online, Kindly update this issue. > Promethus integration with Kie server issue > -------------------------------------------- > > Key: DROOLS-5970 > URL: https://issues.redhat.com/browse/DROOLS-5970 > Project: Drools > Issue Type: Bug > Components: docker images > Affects Versions: 7.47.0.Final > Reporter: Ali Hussain > Assignee: Roger Martinez > Priority: Blocker > > I am using Drools Workbench Docker image and Kie server Docker image. i need to expose the Kie server rest point for Prometheus metrics. For this i updated the standalone.xml and add this {{org.kie.prometheus.server.ext.disabled}} system property to {{false}} to enable the Prometheus extension and restarted the Kie server. but kie server is not exposing the rest resource. RESTEASY003210: Could not find resource for full path: [http://localhost:8280/kie-server/services/rest/metrics] error occurred when i try to hit this endpoint {{[http://HOST:PORT/SERVER/services/rest/metric]}} although i updated the standalone.xml as it is mention in documentation. > i dont know the reason. very less information is available online, Kindly update this issue. > > -- This message was sent by Atlassian Jira (v8.13.1#813001)

4 years, 8 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5970) Promethus integration with Kie server issue

by Ali Hussain (Jira)

[ https://issues.redhat.com/browse/DROOLS-5970?page=com.atlassian.jira.plug... ] Ali Hussain updated DROOLS-5970: -------------------------------- Steps to Reproduce: (was: # Execute docker run -p 8080:8080 -p 8001:8001 -d --name drools-workbench jboss/drools-workbench-showcase:latest # GO to => [http://localhost:8080/business-central/kie-wb.jsp#DataSourceManagementPer...] # Here Default drivers are not listed ( [https://tinyurl.com/y5pbzdoo] )) > Promethus integration with Kie server issue > -------------------------------------------- > > Key: DROOLS-5970 > URL: https://issues.redhat.com/browse/DROOLS-5970 > Project: Drools > Issue Type: Bug > Components: docker images > Affects Versions: 7.47.0.Final > Reporter: Ali Hussain > Assignee: Roger Martinez > Priority: Blocker > > I am using Drools Workbench Docker image and Kie server Docker image. i need to expose the Kie server rest point for Prometheus metrics. For this i updated the standalone.xml and add this {{org.kie.prometheus.server.ext.disabled}} system property to {{false}} to enable the Prometheus extension and restarted the Kie server. but kie server is not exposing the rest resource. Page not found error when i try to hit this endpoint {{http://HOST:PORT/SERVER/services/rest/metric}} although i updated the standalone.xml as it is mention in documentation. > i dont know the reason. very less information is available online, Kindly update this issue. > > -- This message was sent by Atlassian Jira (v8.13.1#813001)

4 years, 8 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5970) Promethus integration with Kie server issue

by Ali Hussain (Jira)

[ https://issues.redhat.com/browse/DROOLS-5970?page=com.atlassian.jira.plug... ] Ali Hussain updated DROOLS-5970: -------------------------------- Description: I am using Drools Workbench Docker image and Kie server Docker image. i need to expose the Kie server rest point for Prometheus metrics. For this i updated the standalone.xml and add this {{org.kie.prometheus.server.ext.disabled}} system property to {{false}} to enable the Prometheus extension and restarted the Kie server. but kie server is not exposing the rest resource. Page not found error when i try to hit this endpoint {{http://HOST:PORT/SERVER/services/rest/metric}} although i updated the standalone.xml as it is mention in documentation. i dont know the reason. very less information is available online, Kindly update this issue. was:!Business-Central.png! > Promethus integration with Kie server issue > -------------------------------------------- > > Key: DROOLS-5970 > URL: https://issues.redhat.com/browse/DROOLS-5970 > Project: Drools > Issue Type: Bug > Components: docker images > Affects Versions: 7.47.0.Final > Reporter: Ali Hussain > Assignee: Roger Martinez > Priority: Blocker > > I am using Drools Workbench Docker image and Kie server Docker image. i need to expose the Kie server rest point for Prometheus metrics. For this i updated the standalone.xml and add this {{org.kie.prometheus.server.ext.disabled}} system property to {{false}} to enable the Prometheus extension and restarted the Kie server. but kie server is not exposing the rest resource. Page not found error when i try to hit this endpoint {{http://HOST:PORT/SERVER/services/rest/metric}} although i updated the standalone.xml as it is mention in documentation. > i dont know the reason. very less information is available online, Kindly update this issue. > > -- This message was sent by Atlassian Jira (v8.13.1#813001)

4 years, 8 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5970) Promethus integration with Kie server issue

by Ali Hussain (Jira)

Ali Hussain created DROOLS-5970: ----------------------------------- Summary: Promethus integration with Kie server issue Key: DROOLS-5970 URL: https://issues.redhat.com/browse/DROOLS-5970 Project: Drools Issue Type: Bug Components: docker images Affects Versions: 7.47.0.Final Reporter: Ali Hussain Assignee: Roger Martinez !Business-Central.png! -- This message was sent by Atlassian Jira (v8.13.1#813001)

4 years, 8 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14374) Upgrade galleon-plugins to 5.0.1.Final

by Jean Francois Denise (Jira)

Jean Francois Denise created WFLY-14374: ------------------------------------------- Summary: Upgrade galleon-plugins to 5.0.1.Final Key: WFLY-14374 URL: https://issues.redhat.com/browse/WFLY-14374 Project: WildFly Issue Type: Component Upgrade Components: Build System Reporter: Jean Francois Denise Assignee: Jean Francois Denise -- This message was sent by Atlassian Jira (v8.13.1#813001)

4 years, 8 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14373) Upgrade jboss-ejb-client to 4.0.38.Final

by Tomasz Adamski (Jira)

[ https://issues.redhat.com/browse/WFLY-14373?page=com.atlassian.jira.plugi... ] Tomasz Adamski updated WFLY-14373: ---------------------------------- Description: https://github.com/wildfly/jboss-ejb-client/compare/4.0.37.Final...4.0.38... > Upgrade jboss-ejb-client to 4.0.38.Final > ---------------------------------------- > > Key: WFLY-14373 > URL: https://issues.redhat.com/browse/WFLY-14373 > Project: WildFly > Issue Type: Component Upgrade > Components: EJB > Reporter: Tomasz Adamski > Assignee: Tomasz Adamski > Priority: Major > > https://github.com/wildfly/jboss-ejb-client/compare/4.0.37.Final...4.0.38... -- This message was sent by Atlassian Jira (v8.13.1#813001)

4 years, 8 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14373) Upgrade jboss-ejb-client to 4.0.38.Final

by Tomasz Adamski (Jira)

Tomasz Adamski created WFLY-14373: ------------------------------------- Summary: Upgrade jboss-ejb-client to 4.0.38.Final Key: WFLY-14373 URL: https://issues.redhat.com/browse/WFLY-14373 Project: WildFly Issue Type: Component Upgrade Components: EJB Reporter: Tomasz Adamski Assignee: Tomasz Adamski -- This message was sent by Atlassian Jira (v8.13.1#813001)

4 years, 8 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14284) WildFly doesn't stop while waiting for PeriodicRecovery

by Ondrej Chaloupka (Jira)

[ https://issues.redhat.com/browse/WFLY-14284?page=com.atlassian.jira.plugi... ] Ondrej Chaloupka commented on WFLY-14284: ----------------------------------------- [~adrianots] ok, I see. Then assigned WFLY-14369 to me. Thank you. [~tomekadamski] I marked the WEJBHTTP-53 being the cause of this issue as I assume the observed behaviour is caused there. > WildFly doesn't stop while waiting for PeriodicRecovery > ------------------------------------------------------- > > Key: WFLY-14284 > URL: https://issues.redhat.com/browse/WFLY-14284 > Project: WildFly > Issue Type: Bug > Components: EJB, Transactions > Affects Versions: 18.0.1.Final, 20.0.1.Final > Reporter: Adriano Teixeira de Souza > Assignee: Michael Musgrove > Priority: Major > Attachments: ejb-configs.sh, jboss-ejb-client.xml, server(transaction).log, thread-dump-stop-1.txt > > > I'm testing wildfly 20.0.1 (and 21.0.2 was tested too) for replace our old version of Wildfly 10. > it happens that frequently we have seen that the stop function of server does not work and we need to kill the process by manual operation on the OS. > It sounds like a dead look. > I attatch the thread dump on this. -- This message was sent by Atlassian Jira (v8.13.1#813001)

4 years, 8 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14369) Wrong documentation about remoting outbound connection on developer guide

by Ondrej Chaloupka (Jira)

[ https://issues.redhat.com/browse/WFLY-14369?page=com.atlassian.jira.plugi... ] Ondrej Chaloupka commented on WFLY-14369: ----------------------------------------- [~tomekadamski] I assigned this issue to me. First, I'm not experienced in all details, second I don't know when I will be able to get to this. If you have mood to work on this, feel free to re-assign it :-) > Wrong documentation about remoting outbound connection on developer guide > ------------------------------------------------------------------------- > > Key: WFLY-14369 > URL: https://issues.redhat.com/browse/WFLY-14369 > Project: WildFly > Issue Type: Bug > Components: Documentation > Reporter: Adriano Teixeira de Souza > Assignee: Ondrej Chaloupka > Priority: Major > > According to https://issues.redhat.com/browse/WFLY-14284 the oficial documentation on Wildfly Developer Guide is wrong on topics about Remote Outbound Connection and remote protocol as 19.11. > It have instructions that uses deprecated way of configurations and doesn't refers to "remote+http" protocol and how each protocol works. -- This message was sent by Atlassian Jira (v8.13.1#813001)

4 years, 8 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5816) executable-model doesn't resolve kcontext with mvel dialect

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5816?page=com.atlassian.jira.plug... ] Toshiya Kobayashi updated DROOLS-5816: -------------------------------------- Sprint: 2021 Week 04-06 (from Jan 25) Story Points: 3 > executable-model doesn't resolve kcontext with mvel dialect > ----------------------------------------------------------- > > Key: DROOLS-5816 > URL: https://issues.redhat.com/browse/DROOLS-5816 > Project: Drools > Issue Type: Bug > Components: executable model > Affects Versions: 7.46.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > > org.drools.mvel.integrationtests.KnowledgeContextTest in test-compiler-integration fails with some tests when executable-model is enabled. See TODO comment in the test class. Once fixed (or the test failure is justified), we can remove the TODO comment and let the test run with executable-model. > Currently, executable-model is disabled: > {code:java} > // TODO: .... > return TestParametersUtil.getKieBaseCloudConfigurations(false); > {code} > If the test failure contains multiple bugs, we may split this JIRA into multiple JIRAs. -- This message was sent by Atlassian Jira (v8.13.1#813001)

4 years, 8 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2021