April 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-11962) Unable to start wildfly in domain mode when metrics and health extensions are enabled

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-11962?page=com.atlassian.jira.plugin... ] Brian Stansberry resolved WFLY-11962. ------------------------------------- Resolution: Rejected These extensions are not supported in a managed domain. They expose data over the management interface and in a domain mode server that is not directly accessible to any caller other than the Host Controller that manages the server. [~jmesnil] I don't see this noted in the community docs for these subsystems (https://docs.wildfly.org/16/Admin_Guide.html#MicroProfile_Health_SmallRye) or in the proposal docs. I remember it being discussed but it looks like text didn't get in the final documents. > Unable to start wildfly in domain mode when metrics and health extensions are enabled > ------------------------------------------------------------------------------------- > > Key: WFLY-11962 > URL: https://issues.jboss.org/browse/WFLY-11962 > Project: WildFly > Issue Type: Bug > Affects Versions: 16.0.0.Final > Reporter: Vlasta Ramik > Assignee: Brian Stansberry > Priority: Major > > When WF is started in domain mode as described in steps to reproduce there is following in console {noformat} > [Host Controller] 09:10:13,260 INFO [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0023: Starting server server-one > 09:10:13,396 INFO [org.jboss.as.process.Server:server-one.status] (ProcessController-threads - 3) WFLYPC0018: Starting process 'Server:server-one' > [Host Controller] 09:10:14,876 INFO [org.jboss.as.host.controller] (management task-1) WFLYHC0021: Server [Server:server-one] connected using connection [Channel ID 24b9374c (inbound) of Remoting connection 408c47e7 to localhost/127.0.0.1:38776 of endpoint "master:MANAGEMENT" <a16e023>] > [Host Controller] 09:10:14,906 INFO [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0023: Starting server server-two > [Host Controller] 09:10:14,921 INFO [org.jboss.as.host.controller] (server-registration-threads - 1) WFLYHC0020: Registering server server-one > 09:10:15,031 INFO [org.jboss.as.process.Server:server-two.status] (ProcessController-threads - 3) WFLYPC0018: Starting process 'Server:server-two' > 09:10:16,854 INFO [org.jboss.as.process.Server:server-one.status] (reaper for Server:server-one) WFLYPC0011: Process 'Server:server-one' finished with an exit status of 1 > [Host Controller] 09:10:16,896 INFO [org.jboss.as.host.controller] (ProcessControllerConnection-thread - 2) WFLYHC0027: Unregistering server server-one > [Host Controller] 09:10:17,172 INFO [org.jboss.as.host.controller] (management task-1) WFLYHC0021: Server [Server:server-two] connected using connection [Channel ID 3d4db366 (inbound) of Remoting connection 382df477 to localhost/127.0.0.1:38794 of endpoint "master:MANAGEMENT" <a16e023>] > [Host Controller] 09:10:17,207 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0062: Http management interface listening on http://127.0.0.1:9990/management and https://127.0.0.1:-1/management > [Host Controller] 09:10:17,208 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0053: Admin console listening on http://127.0.0.1:9990 and https://127.0.0.1:-1 > [Host Controller] 09:10:17,212 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 16.0.0.Final (WildFly Core 8.0.0.Final) (Host Controller) started in 6589ms - Started 79 of 81 services (23 services are lazy, passive or on-demand) > [Host Controller] 09:10:17,232 INFO [org.jboss.as.host.controller] (server-registration-threads - 1) WFLYHC0020: Registering server server-two > 09:10:18,663 INFO [org.jboss.as.process.Server:server-two.status] (reaper for Server:server-two) WFLYPC0011: Process 'Server:server-two' finished with an exit status of 1 > [Host Controller] 09:10:18,665 INFO [org.jboss.as.host.controller] (ProcessControllerConnection-thread - 2) WFLYHC0027: Unregistering server server-two > {noformat} > and there is following in domain/servers/server-one/log/server.log {noformat}2019-04-09 09:04:52,385 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/subsystem=microprofile-health-smallrye' are not available: > org.wildfly.management.http.extensible; There are no known registration points which can provide this capability. > 2019-04-09 09:04:52,386 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/subsystem=microprofile-metrics-smallrye' are not available: > org.wildfly.management.http.extensible; There are no known registration points which can provide this capability. > 2019-04-09 09:04:52,389 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details. > 2019-04-09 09:04:52,420 INFO [org.jboss.as] (MSC service thread 1-1) WFLYSRV0050: WildFly Full 16.0.0.Final (WildFly Core 8.0.0.Final) stopped in 18ms{noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10996) [Postgres] Database queries result in NoClassDefFound for org/wildfly/transaction/client/ContextTransactionManager

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-10996?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-10996: --------------------------------- Fix Version/s: 15.0.0.Final > [Postgres] Database queries result in NoClassDefFound for org/wildfly/transaction/client/ContextTransactionManager > ------------------------------------------------------------------------------------------------------------------ > > Key: WFLY-10996 > URL: https://issues.jboss.org/browse/WFLY-10996 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: 14.0.1.Final, 14.0.0.Final > Environment: CentOS 7/Mac OS > WildFly 14.0.0 / WildFly 14.0.1 > Reporter: Rakesh Cherukuri > Assignee: Scott Marlow > Priority: Blocker > Fix For: 15.0.0.Final > > Attachments: error.log, jpa-war.tar.gz, pgsql.driver.tar.gz, standalone-full.diff > > > Basically WildFly is unable to either build the persistence context or it fails to query postgres db. > The changes are so minimal that it should basically work. > Attached: > # error.log - exception in the server log > # jpa-war.tar.gz - maven module that can be used to reproduce the issue > # pgsql.module.tar.gz - postgres driver module that can be unpacked under modules/system/layers/base/org/postgresql > # standalone-full.diff - diff that can be applied to standalone-full.xml to define required datasource > Note: > - Tested same steps with wildfly 13 and there its woking fine. > - Tested with latest postgres driver and issue exists with v14.0.0 (and v14.0.1). Postgres driver is thus ruled out. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3415) guided decision tree updation is not hapening

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3415?page=com.atlassian.jira.plugi... ] Jozef Marko closed DROOLS-3415. ------------------------------- Resolution: Rejected Closing this due to missing resources for this component. > guided decision tree updation is not hapening > --------------------------------------------- > > Key: DROOLS-3415 > URL: https://issues.jboss.org/browse/DROOLS-3415 > Project: Drools > Issue Type: Bug > Components: Guided Decision Tree Editor > Reporter: Shankar Prasad > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > Attachments: Screenshot 2018-12-07 at 9.42.13 AM.png, Screenshot 2018-12-07 at 9.42.25 AM.png, Screenshot 2018-12-07 at 9.42.37 AM.png > > > I have a guided decision tree where I am trying to update a ENUM field but once I click OK on the workbench, it is taking the default value. I am using KIE workbench 7.12.0. > I have given complete screenshot and details in > https://groups.google.com/forum/#!topic/drools-usage/xjVBBtyPbdc -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3440) Guided decision tables: Single 'comma separated value' does not work

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3440?page=com.atlassian.jira.plugi... ] Jozef Marko closed DROOLS-3440. ------------------------------- Resolution: Rejected Closing as it is not reported by customer and the guided decision tables are not under active development anymore. > Guided decision tables: Single 'comma separated value' does not work > -------------------------------------------------------------------- > > Key: DROOLS-3440 > URL: https://issues.jboss.org/browse/DROOLS-3440 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Affects Versions: 7.16.0.Final > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > Type "1" into a "Value list (optional):" field and the table shows a drowdown without content. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-536) [RS] Prototype Automation Test Runs Into Polarion

by Matthew Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-536?page=com.atlassian.jira.plugin.... ] Matthew Mahoney commented on SWSQE-536: --------------------------------------- PR for change_status enhancement: https://gitlab.cee.redhat.com/istio/pylarion/merge_requests/3 > [RS] Prototype Automation Test Runs Into Polarion > ------------------------------------------------- > > Key: SWSQE-536 > URL: https://issues.jboss.org/browse/SWSQE-536 > Project: Kiali QE > Issue Type: QE Task > Reporter: Matthew Mahoney > Assignee: Matthew Mahoney > Priority: Major > Labels: infrastructure, pqi > Attachments: junit-output.xml, junit-output_single.xml, kiali-0.15.0_signed-output.xml > > > What is the mechanism to import automation runs into Polarion. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2912) [Guided Rule] Unify help icons

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-2912?page=com.atlassian.jira.plugi... ] Jozef Marko closed DROOLS-2912. ------------------------------- Resolution: Rejected Closing this as it is not reported by customer and the component is not anymore under active development. > [Guided Rule] Unify help icons > ------------------------------ > > Key: DROOLS-2912 > URL: https://issues.jboss.org/browse/DROOLS-2912 > Project: Drools > Issue Type: Task > Components: Guided Rule Editor > Affects Versions: 7.10.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > Attachments: Screenshot from 2018-08-22 11-00-04.png, Screenshot from 2018-08-22 11-02-21.png, Screenshot from 2018-08-22 11-02-33.png, Screenshot from 2018-08-22 11-02-51.png > > > The guided rule editor uses different help icons, see: > - !Screenshot from 2018-08-22 11-02-51.png|thumbnail! > - !Screenshot from 2018-08-22 11-02-21.png|thumbnail! > - !Screenshot from 2018-08-22 11-02-33.png|thumbnail! > I think we should unify help icons across product, for example we could use icons used in settings page: > - !Screenshot from 2018-08-22 11-00-04.png|thumbnail! -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11918) Keycloak adapter broken because of missing org.jboss.metadata module

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-11918?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-11918: --------------------------------- Component/s: MP OpenTracing > Keycloak adapter broken because of missing org.jboss.metadata module > -------------------------------------------------------------------- > > Key: WFLY-11918 > URL: https://issues.jboss.org/browse/WFLY-11918 > Project: WildFly > Issue Type: Bug > Components: Clustering, MP OpenTracing > Affects Versions: 17.0.0.Beta1 > Reporter: Simon Priadka > Assignee: Yeray Borges > Priority: Blocker > Labels: blocker-WF17 > Fix For: 17.0.0.Beta1 > > > When trying to install keycloak-wildfly-subsystem described in [this guide|https://www.keycloak.org/docs/3.0/getting_started/topics/secure-jbo...], the install fails because of: > {code:java} > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0158: Operation handler failed: org.jboss.modules.ModuleLoadError: org.jboss.metadata", > "rolled-back" => true > } > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11918) Keycloak adapter broken because of missing org.jboss.metadata module

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-11918?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-11918: --------------------------------- Component/s: Clustering > Keycloak adapter broken because of missing org.jboss.metadata module > -------------------------------------------------------------------- > > Key: WFLY-11918 > URL: https://issues.jboss.org/browse/WFLY-11918 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 17.0.0.Beta1 > Reporter: Simon Priadka > Assignee: Yeray Borges > Priority: Blocker > Labels: blocker-WF17 > Fix For: 17.0.0.Beta1 > > > When trying to install keycloak-wildfly-subsystem described in [this guide|https://www.keycloak.org/docs/3.0/getting_started/topics/secure-jbo...], the install fails because of: > {code:java} > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0158: Operation handler failed: org.jboss.modules.ModuleLoadError: org.jboss.metadata", > "rolled-back" => true > } > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-669) Checklist for custom fields in order to support existing and future workflows for KIALI

by Matthew Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-669?page=com.atlassian.jira.plugin.... ] Matthew Mahoney commented on SWSQE-669: --------------------------------------- [~pyadav] What is the workflow for SFDC Cases Counter and Links fields usage? > Checklist for custom fields in order to support existing and future workflows for KIALI > --------------------------------------------------------------------------------------- > > Key: SWSQE-669 > URL: https://issues.jboss.org/browse/SWSQE-669 > Project: Kiali QE > Issue Type: QE Task > Reporter: Prachi Yadav > Assignee: Matthew Mahoney > Priority: Major > Labels: pqi > > project MUST have the following custom fields in order to support existing and future workflows and visualizations: > QE Test Coverage with values +, -, and ? (Null is supported) > SFDC Cases Counter > SFDC Cases Links > These custom fields must exist as above so that we do not need to customize logic for any one-offs. The SFDC Cases * fields are there to support "integration" with our SalesForce system used by CEE/GSS for customer cases and the links here are links to SFDC customer cases. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2048) Add ability to use Template Keys in DSL expressions

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-2048?page=com.atlassian.jira.plugi... ] Jozef Marko closed DROOLS-2048. ------------------------------- Resolution: Rejected Closing this as it is not reported by a customer and the component is not actively developed anymore. > Add ability to use Template Keys in DSL expressions > --------------------------------------------------- > > Key: DROOLS-2048 > URL: https://issues.jboss.org/browse/DROOLS-2048 > Project: Drools > Issue Type: Feature Request > Components: DSLs Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Major > > DSL Sentences only permit the entry of literal values. It'd be good to be able to use Template Keys too. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 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 April 2019