August 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-10843) WFLYWELD0012 warning while parsing valid beans.xml: Cannot find the declaration of element 'beans'.

by Rostislav Svoboda (JIRA)

[ https://issues.jboss.org/browse/WFLY-10843?page=com.atlassian.jira.plugin... ] Rostislav Svoboda updated WFLY-10843: ------------------------------------- Component/s: MP Health > WFLYWELD0012 warning while parsing valid beans.xml: Cannot find the declaration of element 'beans'. > --------------------------------------------------------------------------------------------------- > > Key: WFLY-10843 > URL: https://issues.jboss.org/browse/WFLY-10843 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld, MP Health > Reporter: Rostislav Svoboda > Assignee: Matej Novotny > Priority: Critical > > WFLYWELD0012 warning while parsing valid beans.xml: Cannot find the declaration of element 'beans'. > {code} > WFLYWELD0012: > Warning while parsing jar:file:/Users/rsvoboda/tmp/wildfly/dist/target/wildfly-14.0.0.Beta2-SNAPSHOT/modules/system/layers/base/io/smallrye/health/main/ > smallrye-health-1.0.2.jar!/META-INF/beans.xml:4 cvc-elt.1.a: > Cannot find the declaration of element 'beans'. > {code} > Some details in https://issues.jboss.org/browse/WFWIP-107 > [~mkouba] says that https://github.com/wildfly/wildfly/blob/master/weld/subsystem/src/main/ja... needs to be adjusted to correctly detect error messages which should be ignored ++ follow Weld code in https://github.com/weld/core/blob/master/impl/src/main/java/org/jboss/wel... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10864) MP Health reports UP when there is port collision for port 8080

by Rostislav Svoboda (JIRA)

[ https://issues.jboss.org/browse/WFLY-10864?page=com.atlassian.jira.plugin... ] Rostislav Svoboda moved WFWIP-81 to WFLY-10864: ----------------------------------------------- Project: WildFly (was: WildFly WIP) Key: WFLY-10864 (was: WFWIP-81) Component/s: MP Health (was: MP Health) > MP Health reports UP when there is port collision for port 8080 > --------------------------------------------------------------- > > Key: WFLY-10864 > URL: https://issues.jboss.org/browse/WFLY-10864 > Project: WildFly > Issue Type: Bug > Components: MP Health > Reporter: Rostislav Svoboda > Assignee: Jeff Mesnil > Priority: Critical > > MP Health reports UP when there is port collision for port 8080. > I have simple python app to acquire port 8080 and once it runs I start WF server > {code} > import SimpleHTTPServer > import SocketServer > PORT = 8080 > Handler = SimpleHTTPServer.SimpleHTTPRequestHandler > httpd = SocketServer.TCPServer(("127.0.0.1", PORT), Handler) > print "serving at port", PORT > httpd.serve_forever() > {code} > WF reports Address already in use /127.0.0.1:8080, deployments are not deployed. > Accessing http://localhost:9990/health/ reports "outcome":"UP" > I think this is wrong and DOWN should be reported. > Spec is misleading because it says {{A producer without health check procedures installed MUST returns positive overall outcome (i.e. HTTP 200)}} but it silently assumes server started correctly. > I believe authors of the spec expected that if there is some trouble like port collision the server doesn't start, WildFly is a bit further as it allows to boot even if some services are not started properly. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10862) Log warning when MP Health reports DOWN

by Rostislav Svoboda (JIRA)

[ https://issues.jboss.org/browse/WFLY-10862?page=com.atlassian.jira.plugin... ] Rostislav Svoboda updated WFLY-10862: ------------------------------------- Issue Type: Enhancement (was: Bug) > Log warning when MP Health reports DOWN > --------------------------------------- > > Key: WFLY-10862 > URL: https://issues.jboss.org/browse/WFLY-10862 > Project: WildFly > Issue Type: Enhancement > Components: MP Health > Reporter: Rostislav Svoboda > Assignee: Jeff Mesnil > > Enhance MP Health functionality to log warning when MP Health reports DOWN. > This can be useful when working on investigation / retrospective analysis. > Open Liberty prints following warning when http://localhost:9080/health reports DOWN > {code} > [WARNING ] CWMH0051W: The class com.ibm.ws.microprofile.health.impl.HealthCheckResponseImpl implementing HealthCheckResponse > in the microprofile-health application in module microprofile-health.war, > reported a DOWN outcome DOWN with data Optional[{availability=not available}]. > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10863) MP Health is not available in domain mode

by Rostislav Svoboda (JIRA)

[ https://issues.jboss.org/browse/WFLY-10863?page=com.atlassian.jira.plugin... ] Rostislav Svoboda moved WFWIP-98 to WFLY-10863: ----------------------------------------------- Project: WildFly (was: WildFly WIP) Key: WFLY-10863 (was: WFWIP-98) Component/s: MP Health (was: MP Health) > MP Health is not available in domain mode > ----------------------------------------- > > Key: WFLY-10863 > URL: https://issues.jboss.org/browse/WFLY-10863 > Project: WildFly > Issue Type: Bug > Components: MP Health > Reporter: Rostislav Svoboda > Assignee: Jeff Mesnil > Priority: Critical > > MP Health is not available in domain mode. > Analysis is not saying that domain is out of scope, EAP7 RFE is not explicit about this either. > We may resolve this just by making it explicit, that MP health is just fo standalone for now. > For domain we should at least have a plan what to do and how -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10862) Log warning when MP Health reports DOWN

by Rostislav Svoboda (JIRA)

[ https://issues.jboss.org/browse/WFLY-10862?page=com.atlassian.jira.plugin... ] Rostislav Svoboda moved WFWIP-80 to WFLY-10862: ----------------------------------------------- Project: WildFly (was: WildFly WIP) Key: WFLY-10862 (was: WFWIP-80) Issue Type: Bug (was: Enhancement) Component/s: MP Health (was: MP Health) > Log warning when MP Health reports DOWN > --------------------------------------- > > Key: WFLY-10862 > URL: https://issues.jboss.org/browse/WFLY-10862 > Project: WildFly > Issue Type: Bug > Components: MP Health > Reporter: Rostislav Svoboda > Assignee: Jeff Mesnil > > Enhance MP Health functionality to log warning when MP Health reports DOWN. > This can be useful when working on investigation / retrospective analysis. > Open Liberty prints following warning when http://localhost:9080/health reports DOWN > {code} > [WARNING ] CWMH0051W: The class com.ibm.ws.microprofile.health.impl.HealthCheckResponseImpl implementing HealthCheckResponse > in the microprofile-health application in module microprofile-health.war, > reported a DOWN outcome DOWN with data Optional[{availability=not available}]. > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10861) MP Health - security enabled, no user yed added, user get info about adding user to access web console, HTTP code is 200, should be 500

by Rostislav Svoboda (JIRA)

[ https://issues.jboss.org/browse/WFLY-10861?page=com.atlassian.jira.plugin... ] Rostislav Svoboda updated WFLY-10861: ------------------------------------- Component/s: Management Priority: Blocker (was: Critical) Marking as Blocker for WF 14 {code} [10:18 AM] Rostislav Svoboda: what's the plan for https://issues.jboss.org/browse/WFWIP-96 ? [10:22 AM] Jeff Mesnil: that's a bug that needs to be fixed for WFLY 14 but it lust fit both the management console and additional management handlers like /health {code} > MP Health - security enabled, no user yed added, user get info about adding user to access web console, HTTP code is 200, should be 500 > --------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-10861 > URL: https://issues.jboss.org/browse/WFLY-10861 > Project: WildFly > Issue Type: Bug > Components: Management, MP Health > Reporter: Rostislav Svoboda > Assignee: Jeff Mesnil > Priority: Blocker > > I do {{:write-attribute(name=security-enabled, value=true)}} ++ reload of the server > Note: I didn't add user via {{bin/add-user.sh}} > When I'm trying to access http://127.0.0.1:9990/health I receive page which is there primarily for web console: > {code} > <h3>Your WildFly Application Server is running.</h3> > <p>However you have <strong>not</strong> yet <strong>added any users</strong> to be able > to access the admin console.</p> > <p>To add a new user execute the <code>add-user.sh</code> script within the bin folder of > your WildFly installation and enter the requested information.</p> > {code} > Can /health endpoint get customized response in case no mgmt user is defined on server side ? > Current response can be little confusing if user is not yet so familiar with WildFly. > I marked this as minor bug. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10861) MP Health - security enabled, no user yed added, user get info about adding user to access web console, HTTP code is 200, should be 500

by Rostislav Svoboda (JIRA)

[ https://issues.jboss.org/browse/WFLY-10861?page=com.atlassian.jira.plugin... ] Rostislav Svoboda moved WFWIP-96 to WFLY-10861: ----------------------------------------------- Project: WildFly (was: WildFly WIP) Key: WFLY-10861 (was: WFWIP-96) Component/s: MP Health (was: MP Health) > MP Health - security enabled, no user yed added, user get info about adding user to access web console, HTTP code is 200, should be 500 > --------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-10861 > URL: https://issues.jboss.org/browse/WFLY-10861 > Project: WildFly > Issue Type: Bug > Components: MP Health > Reporter: Rostislav Svoboda > Assignee: Jeff Mesnil > Priority: Critical > > I do {{:write-attribute(name=security-enabled, value=true)}} ++ reload of the server > Note: I didn't add user via {{bin/add-user.sh}} > When I'm trying to access http://127.0.0.1:9990/health I receive page which is there primarily for web console: > {code} > <h3>Your WildFly Application Server is running.</h3> > <p>However you have <strong>not</strong> yet <strong>added any users</strong> to be able > to access the admin console.</p> > <p>To add a new user execute the <code>add-user.sh</code> script within the bin folder of > your WildFly installation and enter the requested information.</p> > {code} > Can /health endpoint get customized response in case no mgmt user is defined on server side ? > Current response can be little confusing if user is not yet so familiar with WildFly. > I marked this as minor bug. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10860) jdbc-network-timeout is set in seconds instead of milliseconds causing Artemis to fail on Critical IO Error when jdbc store is used

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-10860?page=com.atlassian.jira.plugin... ] Jeff Mesnil moved WFWIP-116 to WFLY-10860: ------------------------------------------ Project: WildFly (was: WildFly WIP) Key: WFLY-10860 (was: WFWIP-116) Component/s: JMS (was: JMS) > jdbc-network-timeout is set in seconds instead of milliseconds causing Artemis to fail on Critical IO Error when jdbc store is used > ----------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-10860 > URL: https://issues.jboss.org/browse/WFLY-10860 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: Miroslav Novak > Assignee: Jeff Mesnil > Priority: Blocker > > jdbc-network-timeout is set in seconds instead of milliseconds in: > https://github.com/wildfly/wildfly/blob/master/messaging-activemq/src/mai... > This line must be removed as before it is: > {code} > long networkTimeout = SECONDS.toMillis(JOURNAL_JDBC_NETWORK_TIMEOUT.resolveModelAttribute(context, model).asInt()); > // ARTEMIS-1493: Artemis API is not correct. the value must be in millis but it requires an int instead of a long. > storageConfiguration.setJdbcNetworkTimeout((int)networkTimeout); > {code} > which sets this timeout properly in milliseconds. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-90) [Artemis 2.x upgrade] Undelivered messages in remote jca topology after restart

by Miroslav Novak (JIRA)

[ https://issues.jboss.org/browse/WFWIP-90?page=com.atlassian.jira.plugin.s... ] Miroslav Novak edited comment on WFWIP-90 at 8/16/18 3:15 AM: -------------------------------------------------------------- I've found issue in WF master integration which sets jdbc-network-timeout in seconds instead of milliseconds. Thus when it passes value 20 by default then it's considered as 20ms which is very low value. :-) I've created jira: https://issues.jboss.org/browse/WFWIP-116 for [~jmesnil] to fix. In the mean time I'll reconfigure this value to 20 000 to workaround the issue in integration testsuite and run the reproducer again -> https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-messag... fyi this issue is not present in Martyn's WF branch EAPAMQUpgradeBranch. was (Author: mnovak): I've found issue in WF master integration which sets jdbc-network-timeout in seconds instead of milliseconds. Thus when it passes value 20 by default then it's considered as 20ms which is very low value. :-) I've created jira: https://issues.jboss.org/browse/WFWIP-116 for [~jmesnil] to fix. In the mean time I'll reconfigure this value to 20 000 to workaround the issue in integration testsuite and run the reproducer again -> https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-messag... > [Artemis 2.x upgrade] Undelivered messages in remote jca topology after restart > ------------------------------------------------------------------------------- > > Key: WFWIP-90 > URL: https://issues.jboss.org/browse/WFWIP-90 > Project: WildFly WIP > Issue Type: Bug > Components: Artemis > Reporter: Miroslav Novak > Assignee: Martyn Taylor > Priority: Blocker > > There are undelivered messages in scenario with where servers in remote JCA topology are restarted. There are undelivered message after test. > Test scenario: > * Start 2 server in Artemis cluster > * Start 2 servers with MDB connected to Artemis cluster > ** MDB resends messages from InQueue to OutQueue from/to remote cluster > * Send messages to InQueue > * Restart all server (one by one) > * Consumes messages from OutQueue > Results: > After the test there are missing messages in OutQueue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-90) [Artemis 2.x upgrade] Undelivered messages in remote jca topology after restart

by Miroslav Novak (JIRA)

[ https://issues.jboss.org/browse/WFWIP-90?page=com.atlassian.jira.plugin.s... ] Miroslav Novak edited comment on WFWIP-90 at 8/16/18 3:14 AM: -------------------------------------------------------------- I've found issue in WF master integration which sets jdbc-network-timeout in seconds instead of milliseconds. Thus when it passes value 20 by default then it's considered as 20ms which is very low value. :-) I've created jira: https://issues.jboss.org/browse/WFWIP-116 for [~jmesnil] to fix. In the mean time I'll reconfigure this value to 20 000 to workaround the issue in integration testsuite and run the reproducer again -> https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-messag... was (Author: mnovak): I've found issue in WF master integration which sets jdbc-network-timeout in seconds instead of milliseconds. Thus when it passes value 20 by default then it's considered as 20ms which is very low value. :-) I've created jira: https://issues.jboss.org/browse/WFWIP-116 for [~jmesnil] to fix. In the mean time I'll reconfigure this value to 20 000 to workaround the issue in integration testsuite and run the reproducer again. > [Artemis 2.x upgrade] Undelivered messages in remote jca topology after restart > ------------------------------------------------------------------------------- > > Key: WFWIP-90 > URL: https://issues.jboss.org/browse/WFWIP-90 > Project: WildFly WIP > Issue Type: Bug > Components: Artemis > Reporter: Miroslav Novak > Assignee: Martyn Taylor > Priority: Blocker > > There are undelivered messages in scenario with where servers in remote JCA topology are restarted. There are undelivered message after test. > Test scenario: > * Start 2 server in Artemis cluster > * Start 2 servers with MDB connected to Artemis cluster > ** MDB resends messages from InQueue to OutQueue from/to remote cluster > * Send messages to InQueue > * Restart all server (one by one) > * Consumes messages from OutQueue > Results: > After the test there are missing messages in OutQueue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 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 August 2018