August 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFWIP-98) MP Health is not available in domain mode

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFWIP-98?page=com.atlassian.jira.plugin.s... ] Jeff Mesnil commented on WFWIP-98: ---------------------------------- I have updated the PR so that the subsystem is in all standalone profiles. For the first iteration, I don't think we need to include them in domain profiles. > MP Health is not available in domain mode > ----------------------------------------- > > Key: WFWIP-98 > URL: https://issues.jboss.org/browse/WFWIP-98 > Project: WildFly WIP > 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, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10823) [EAT] : List the methods available by the tested software and the testsuite.

by Panagiotis Sotiropoulos (JIRA)

[ https://issues.jboss.org/browse/WFLY-10823?page=com.atlassian.jira.plugin... ] Panagiotis Sotiropoulos updated WFLY-10823: ------------------------------------------- Component/s: Test Suite > [EAT] : List the methods available by the tested software and the testsuite. > ---------------------------------------------------------------------------- > > Key: WFLY-10823 > URL: https://issues.jboss.org/browse/WFLY-10823 > Project: WildFly > Issue Type: Task > Components: Test Suite > Reporter: Panagiotis Sotiropoulos > Assignee: Panagiotis Sotiropoulos > > List the methods available by the tested software and the testsuite. > These will be used to check availability of the invoked methods at the testsuite. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10823) [EAT] : List the methods available by the tested software and the testsuite.

by Panagiotis Sotiropoulos (JIRA)

[ https://issues.jboss.org/browse/WFLY-10823?page=com.atlassian.jira.plugin... ] Panagiotis Sotiropoulos moved JBEAP-15232 to WFLY-10823: -------------------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-10823 (was: JBEAP-15232) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) > [EAT] : List the methods available by the tested software and the testsuite. > ---------------------------------------------------------------------------- > > Key: WFLY-10823 > URL: https://issues.jboss.org/browse/WFLY-10823 > Project: WildFly > Issue Type: Task > Reporter: Panagiotis Sotiropoulos > Assignee: Panagiotis Sotiropoulos > > List the methods available by the tested software and the testsuite. > These will be used to check availability of the invoked methods at the testsuite. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10055) [Artemis 2.x Upgrade] Auto-create-queue creates runtime queue without jms.queue prefix

by Martyn Taylor (JIRA)

[ https://issues.jboss.org/browse/WFLY-10055?page=com.atlassian.jira.plugin... ] Martyn Taylor commented on WFLY-10055: -------------------------------------- [~mnovak] [~mtoth] I think there's been some misunderstanding of what this JIRA entails. It is not yet complete, we have a tentative fix that we'll submit today. > [Artemis 2.x Upgrade] Auto-create-queue creates runtime queue without jms.queue prefix > --------------------------------------------------------------------------------------- > > Key: WFLY-10055 > URL: https://issues.jboss.org/browse/WFLY-10055 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: Martin Styk > Assignee: Martyn Taylor > > {{Auto-create-jms-queue}} feature of EAP 7.1 creates runtime queues with name pattern {{"jms.queue.<QUEUE_NAME>"}}. > With Artemis 2.5, {{auto-create-queue}} is a successor of deprecated {{auto-create-jms-queue}} feature. {{Auto-create-queue}} creates queues with name pattern {{"<QUEUE_NAME>"}}. > {code} > session.createQueue("testQueue") > --> "jms.queue.testQueue" (EAP 7.1 + Artemis 1.5, auto-create-jms-queue=true) > --> "testQueue" (Artemis 2.5, auto-create-queue=true) > {code} > This feature is not supported. > Issue was hit with Artemis 2.5.0 with https://github.com/jmesnil/wildfly/tree/WFLY-9407_upgrade_artemis_2.4.0_w... (commit 51dd8102f103ccb0470a3cfc8713d3f9bdb1b65d) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10780) [EAT] : Parse EAT distributed files in order to detect the element types used.

by Panagiotis Sotiropoulos (JIRA)

[ https://issues.jboss.org/browse/WFLY-10780?page=com.atlassian.jira.plugin... ] Panagiotis Sotiropoulos updated WFLY-10780: ------------------------------------------- Description: Parse EAT distributed files in order to detect the element types used (classes, fields, methods, etc). This should be used to check element type availability in the software/server provided/available packages. was: Parse EAT distributed files in order to detect the classes used. This should be used to check class/constructor availability in the software/server provided/available packages. > [EAT] : Parse EAT distributed files in order to detect the element types used. > ------------------------------------------------------------------------------ > > Key: WFLY-10780 > URL: https://issues.jboss.org/browse/WFLY-10780 > Project: WildFly > Issue Type: Task > Components: Test Suite > Reporter: Panagiotis Sotiropoulos > Assignee: Panagiotis Sotiropoulos > > Parse EAT distributed files in order to detect the element types used (classes, fields, methods, etc). > This should be used to check element type availability in the software/server provided/available packages. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10055) [Artemis 2.x Upgrade] Auto-create-queue creates runtime queue without jms.queue prefix

by Miroslav Novak (JIRA)

[ https://issues.jboss.org/browse/WFLY-10055?page=com.atlassian.jira.plugin... ] Miroslav Novak commented on WFLY-10055: --------------------------------------- [~mtoth] We don't have access to [1]. Could you provide information about the fix? [1] https://bitbucket.org/msgqe/eap-testsuite-mirror/commits/fdd9fd15501432c3... > [Artemis 2.x Upgrade] Auto-create-queue creates runtime queue without jms.queue prefix > --------------------------------------------------------------------------------------- > > Key: WFLY-10055 > URL: https://issues.jboss.org/browse/WFLY-10055 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: Martin Styk > Assignee: Martyn Taylor > > {{Auto-create-jms-queue}} feature of EAP 7.1 creates runtime queues with name pattern {{"jms.queue.<QUEUE_NAME>"}}. > With Artemis 2.5, {{auto-create-queue}} is a successor of deprecated {{auto-create-jms-queue}} feature. {{Auto-create-queue}} creates queues with name pattern {{"<QUEUE_NAME>"}}. > {code} > session.createQueue("testQueue") > --> "jms.queue.testQueue" (EAP 7.1 + Artemis 1.5, auto-create-jms-queue=true) > --> "testQueue" (Artemis 2.5, auto-create-queue=true) > {code} > This feature is not supported. > Issue was hit with Artemis 2.5.0 with https://github.com/jmesnil/wildfly/tree/WFLY-9407_upgrade_artemis_2.4.0_w... (commit 51dd8102f103ccb0470a3cfc8713d3f9bdb1b65d) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10780) [EAT] : Parse EAT distributed files in order to detect the element types used.

by Panagiotis Sotiropoulos (JIRA)

[ https://issues.jboss.org/browse/WFLY-10780?page=com.atlassian.jira.plugin... ] Panagiotis Sotiropoulos updated WFLY-10780: ------------------------------------------- Summary: [EAT] : Parse EAT distributed files in order to detect the element types used. (was: [EAT] : Parse EAT distributed files in order to detect the classes used.) > [EAT] : Parse EAT distributed files in order to detect the element types used. > ------------------------------------------------------------------------------ > > Key: WFLY-10780 > URL: https://issues.jboss.org/browse/WFLY-10780 > Project: WildFly > Issue Type: Task > Components: Test Suite > Reporter: Panagiotis Sotiropoulos > Assignee: Panagiotis Sotiropoulos > > Parse EAT distributed files in order to detect the classes used. > This should be used to check class/constructor availability in the software/server provided/available packages. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-96) 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 Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFWIP-96?page=com.atlassian.jira.plugin.s... ] Jeff Mesnil commented on WFWIP-96: ---------------------------------- Note that 200 OK is only if the HTTP client follows redirection, otherwise, he will get a 307. > 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: WFWIP-96 > URL: https://issues.jboss.org/browse/WFWIP-96 > Project: WildFly WIP > 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, 9 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-96) 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/WFWIP-96?page=com.atlassian.jira.plugin.s... ] Rostislav Svoboda updated WFWIP-96: ----------------------------------- Summary: 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 (was: MP Health - security enabled, no user yed added, user get info about adding user to access web console) > 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: WFWIP-96 > URL: https://issues.jboss.org/browse/WFWIP-96 > Project: WildFly WIP > 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, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10795) Non-Elytron SSL configuration won't establish secure channel between worker and balancer

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-10795?page=com.atlassian.jira.plugin... ] Radoslav Husar commented on WFLY-10795: --------------------------------------- > Do I assume correctly, that EAP7-977 should not break backward compatibility? That's correct, no compatibility should be broken (of course you cannot use plurality of balancers in mixed domain scenario since the previous versions would not understand it). > Non-Elytron SSL configuration won't establish secure channel between worker and balancer > ---------------------------------------------------------------------------------------- > > Key: WFLY-10795 > URL: https://issues.jboss.org/browse/WFLY-10795 > Project: WildFly > Issue Type: Bug > Components: mod_cluster > Affects Versions: 14.0.0.CR1 > Environment: Latest snapshot from ci.wildfly.org > Reporter: Jan Kašík > Assignee: Radoslav Husar > Attachments: confs.zip > > > When running scenario, where connection between worker and balancer is secured with SSL, worker fails to register on balancer. > Worker obviously tries to send INFO commands, though it sends it as a 'plain text' to a secured channel. > I enabled SSL debugging, and such unsecured-secured communication causes this error: > {code} > 09:42:20,456 INFO [stdout] (default I/O-4) Using SSLEngineImpl. > 09:42:20,458 INFO [stdout] (default I/O-4) Allow unsafe renegotiation: false > 09:42:20,458 INFO [stdout] (default I/O-4) Allow legacy hello messages: true > 09:42:20,458 INFO [stdout] (default I/O-4) Is initial handshake: true > 09:42:20,459 INFO [stdout] (default I/O-4) Is secure renegotiation: false > 09:42:20,459 INFO [stdout] (default I/O-4) Ignoring unsupported cipher suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 for TLSv1 > 09:42:20,460 INFO [stdout] (default I/O-4) Ignoring unsupported cipher suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 for TLSv1 > 09:42:20,460 INFO [stdout] (default I/O-4) Ignoring unsupported cipher suite: TLS_RSA_WITH_AES_256_CBC_SHA256 for TLSv1 > 09:42:20,460 INFO [stdout] (default I/O-4) Ignoring unsupported cipher suite: TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA384 for TLSv1 > 09:42:20,460 INFO [stdout] (default I/O-4) Ignoring unsupported cipher suite: TLS_ECDH_RSA_WITH_AES_256_CBC_SHA384 for TLSv1 > 09:42:20,460 INFO [stdout] (default I/O-4) Ignoring unsupported cipher suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA256 for TLSv1 > 09:42:20,460 INFO [stdout] (default I/O-4) Ignoring unsupported cipher suite: TLS_DHE_DSS_WITH_AES_256_CBC_SHA256 for TLSv1 > 09:42:20,461 INFO [stdout] (default I/O-4) Ignoring unsupported cipher suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 for TLSv1.1 > 09:42:20,461 INFO [stdout] (default I/O-4) Ignoring unsupported cipher suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 for TLSv1.1 > 09:42:20,461 INFO [stdout] (default I/O-4) Ignoring unsupported cipher suite: TLS_RSA_WITH_AES_256_CBC_SHA256 for TLSv1.1 > 09:42:20,461 INFO [stdout] (default I/O-4) Ignoring unsupported cipher suite: TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA384 for TLSv1.1 > 09:42:20,461 INFO [stdout] (default I/O-4) Ignoring unsupported cipher suite: TLS_ECDH_RSA_WITH_AES_256_CBC_SHA384 for TLSv1.1 > 09:42:20,461 INFO [stdout] (default I/O-4) Ignoring unsupported cipher suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA256 for TLSv1.1 > 09:42:20,461 INFO [stdout] (default I/O-4) Ignoring unsupported cipher suite: TLS_DHE_DSS_WITH_AES_256_CBC_SHA256 for TLSv1.1 > 09:42:20,479 INFO [stdout] (default I/O-4) default I/O-4, fatal error: 80: problem unwrapping net record > 09:42:20,480 INFO [stdout] (default I/O-4) javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection? > 09:42:20,480 INFO [stdout] (default I/O-4) default I/O-4, SEND TLSv1.2 ALERT: fatal, description = internal_error > 09:42:20,480 INFO [stdout] (default I/O-4) default I/O-4, WRITE: TLSv1.2 Alert, length = 2 > 09:42:20,480 INFO [stdout] (default I/O-4) default I/O-4, called closeInbound() > 09:42:20,480 INFO [stdout] (default I/O-4) default I/O-4, fatal: engine already closed. Rethrowing javax.net.ssl.SSLException: Inbound closed before receiving peer's close_notify: possible truncation attack? > 09:42:20,480 INFO [stdout] (default I/O-4) default I/O-4, called closeOutbound() > 09:42:20,480 INFO [stdout] (default I/O-4) default I/O-4, closeOutboundInternal() > {code} > What bothers me, that there are no other errors (bad certificate, CLI error...) in log regarding this. Apart from: > {code} > 09:45:42,653 WARN [org.infinispan.topology.ClusterTopologyManagerImpl] (transport-thread--p14-t16) ISPN000197: Error updating cluster member list: org.infinispan.util.concurrent.TimeoutException: ISPN000476: Timed out waiting for responses for request 6 from wildfly-14.0.0.Beta2-SNAPSHOT-2 > at org.infinispan.remoting.transport.impl.MultiTargetRequest.onTimeout(MultiTargetRequest.java:167) > at org.infinispan.remoting.transport.AbstractRequest.call(AbstractRequest.java:87) > at org.infinispan.remoting.transport.AbstractRequest.call(AbstractRequest.java:22) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) > 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) > Suppressed: org.infinispan.util.logging.TraceException > at org.infinispan.remoting.transport.Transport.invokeRemotely(Transport.java:75) > at org.infinispan.topology.ClusterTopologyManagerImpl.confirmMembersAvailable(ClusterTopologyManagerImpl.java:525) > at org.infinispan.topology.ClusterTopologyManagerImpl.updateCacheMembers(ClusterTopologyManagerImpl.java:508) > at org.infinispan.topology.ClusterTopologyManagerImpl.handleClusterView(ClusterTopologyManagerImpl.java:321) > at org.infinispan.topology.ClusterTopologyManagerImpl.access$500(ClusterTopologyManagerImpl.java:87) > at org.infinispan.topology.ClusterTopologyManagerImpl$ClusterViewListener.lambda$handleViewChange$0(ClusterTopologyManagerImpl.java:731) > at org.infinispan.executors.LimitedExecutor.runTasks(LimitedExecutor.java:175) > at org.infinispan.executors.LimitedExecutor.access$100(LimitedExecutor.java:37) > at org.infinispan.executors.LimitedExecutor$Runner.run(LimitedExecutor.java:227) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at org.wildfly.clustering.service.concurrent.ClassLoaderThreadFactory.lambda$newThread$0(ClassLoaderThreadFactory.java:47) > ... 1 more > {code} > Configuration using non-Elytron configuration was possible before, hence this is a regression. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 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