December 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFWIP-284) Clarify what is invalid header name

by Marek Kopecky (Jira)

[ https://issues.redhat.com/browse/WFWIP-284?page=com.atlassian.jira.plugin... ] Marek Kopecky edited comment on WFWIP-284 at 12/12/19 12:59 AM: ---------------------------------------------------------------- [~dlofthouse]: Looking to RFC2616 that you linked: {noformat} Obsoleted by: 7230, 7231, 7232, 7233, 7234, 7235 Updated by: 2817, 5785, 6266, 6585 {noformat} Looking to RFC5322 that Tomas linked: it seems that this RFC is not obsoleted. Can you link some non-obsoleted RFC? was (Author: mkopecky): [~dlofthouse]: Looking to RFC2616 that you linked: {noformat} Obsoleted by: 7230, 7231, 7232, 7233, 7234, 7235 Updated by: 2817, 5785, 6266, 6585 {noformat} Looking to rfc5322 that Tomas linked: it seems that this RFC is not obsoleted. Can you link some non-obsoleted RFC? > Clarify what is invalid header name > ----------------------------------- > > Key: WFWIP-284 > URL: https://issues.redhat.com/browse/WFWIP-284 > Project: WildFly WIP > Issue Type: Task > Reporter: Tomas Terem > Assignee: Darran Lofthouse > Priority: Blocker > Labels: management > > Header names should follow rules described here: > https://tools.ietf.org/html/rfc5322#section-2.2 > However, rules for custom headers seems to be more restrictive - for example @ or = are not allowed. > I see that these characters are mentioned in https://tools.ietf.org/html/rfc2616#page-16, but it only says that they should be in quotes. However I am not able to configure header containing them in quotes either. > Is this on purpose? > If yes, this needs to be mentioned in analysis&documentation. If not, we need to create critical JBEAP jira for 7.4 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-284) Clarify what is invalid header name

by Marek Kopecky (Jira)

[ https://issues.redhat.com/browse/WFWIP-284?page=com.atlassian.jira.plugin... ] Marek Kopecky edited comment on WFWIP-284 at 12/12/19 12:59 AM: ---------------------------------------------------------------- [~dlofthouse]: Looking to RFC2616 that you linked: {noformat} Obsoleted by: 7230, 7231, 7232, 7233, 7234, 7235 Updated by: 2817, 5785, 6266, 6585 {noformat} Looking to rfc5322 that Tomas linked: it seems that this RFC is not obsoleted. Can you link some non-obsoleted RFC? was (Author: mkopecky): [~dlofthouse]: Looking to RFC2616 that you linked: {noformat} Obsoleted by: 7230, 7231, 7232, 7233, 7234, 7235 DRAFT STANDARD Updated by: 2817, 5785, 6266, 6585 {noformat} Looking to rfc5322 that Tomas linked: it seems that this RFC is not obsoleted or updated. Can you link some non-obsoleted RFC? > Clarify what is invalid header name > ----------------------------------- > > Key: WFWIP-284 > URL: https://issues.redhat.com/browse/WFWIP-284 > Project: WildFly WIP > Issue Type: Task > Reporter: Tomas Terem > Assignee: Darran Lofthouse > Priority: Blocker > Labels: management > > Header names should follow rules described here: > https://tools.ietf.org/html/rfc5322#section-2.2 > However, rules for custom headers seems to be more restrictive - for example @ or = are not allowed. > I see that these characters are mentioned in https://tools.ietf.org/html/rfc2616#page-16, but it only says that they should be in quotes. However I am not able to configure header containing them in quotes either. > Is this on purpose? > If yes, this needs to be mentioned in analysis&documentation. If not, we need to create critical JBEAP jira for 7.4 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-284) Clarify what is invalid header name

by Marek Kopecky (Jira)

[ https://issues.redhat.com/browse/WFWIP-284?page=com.atlassian.jira.plugin... ] Marek Kopecky reopened WFWIP-284: --------------------------------- > Clarify what is invalid header name > ----------------------------------- > > Key: WFWIP-284 > URL: https://issues.redhat.com/browse/WFWIP-284 > Project: WildFly WIP > Issue Type: Task > Reporter: Tomas Terem > Assignee: Darran Lofthouse > Priority: Blocker > Labels: management > > Header names should follow rules described here: > https://tools.ietf.org/html/rfc5322#section-2.2 > However, rules for custom headers seems to be more restrictive - for example @ or = are not allowed. > I see that these characters are mentioned in https://tools.ietf.org/html/rfc2616#page-16, but it only says that they should be in quotes. However I am not able to configure header containing them in quotes either. > Is this on purpose? > If yes, this needs to be mentioned in analysis&documentation. If not, we need to create critical JBEAP jira for 7.4 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-284) Clarify what is invalid header name

by Marek Kopecky (Jira)

[ https://issues.redhat.com/browse/WFWIP-284?page=com.atlassian.jira.plugin... ] Marek Kopecky commented on WFWIP-284: ------------------------------------- [~dlofthouse]: Looking to RFC2616 that you linked: {noformat} Obsoleted by: 7230, 7231, 7232, 7233, 7234, 7235 DRAFT STANDARD Updated by: 2817, 5785, 6266, 6585 {noformat} Looking to rfc5322 that Tomas linked: it seems that this RFC is not obsoleted or updated. Can you link some non-obsoleted RFC? > Clarify what is invalid header name > ----------------------------------- > > Key: WFWIP-284 > URL: https://issues.redhat.com/browse/WFWIP-284 > Project: WildFly WIP > Issue Type: Task > Reporter: Tomas Terem > Assignee: Darran Lofthouse > Priority: Blocker > Labels: management > > Header names should follow rules described here: > https://tools.ietf.org/html/rfc5322#section-2.2 > However, rules for custom headers seems to be more restrictive - for example @ or = are not allowed. > I see that these characters are mentioned in https://tools.ietf.org/html/rfc2616#page-16, but it only says that they should be in quotes. However I am not able to configure header containing them in quotes either. > Is this on purpose? > If yes, this needs to be mentioned in analysis&documentation. If not, we need to create critical JBEAP jira for 7.4 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4733) Server stops after switching from 'local' DC to 'remote' DC

by Ilia Vassilev (Jira)

[ https://issues.redhat.com/browse/WFCORE-4733?page=com.atlassian.jira.plug... ] Ilia Vassilev updated WFCORE-4733: ---------------------------------- Labels: downstream_dependency (was: ) > Server stops after switching from 'local' DC to 'remote' DC > ----------------------------------------------------------- > > Key: WFCORE-4733 > URL: https://issues.redhat.com/browse/WFCORE-4733 > Project: WildFly Core > Issue Type: Bug > Components: Management > Affects Versions: 10.0.0.Final > Environment: 2 servers started as DC on two different machines > Reporter: Joerg Baesner > Assignee: Yeray Borges > Priority: Major > Labels: downstream_dependency > Fix For: 11.0.0.Beta3 > > > Install WildFly on two different machines, add an 'admin' user and start the {{host-master.xml}} configurations on each node, like: > machineA: (10.10.10.1) > {noformat} > $JBOSS_HOME/bin/add-user.sh -u admin -p admin > $JBOSS_HOME/bin/domain.sh --host-config.xml -Djboss.bind.address.management=10.10.10.1 > {noformat} > machineB: 10.10.10.2 > {noformat} > $JBOSS_HOME/bin/add-user.sh -u admin -p admin > $JBOSS_HOME/bin/domain.sh --host-config.xml -Djboss.bind.address.management=10.10.10.2 > {noformat} > And then applying a simplified script like below to machineB: > {code} > batch > /host=master:write-attribute(name=name, value=slave) > /host=master/core-service=discovery-options/static-discovery=primary:add(host=10.10.10.1, port=9990, protocol=remote+http) > /host=master:write-remote-domain-controller(username=admin, security-realm="ManagementRealm") > /host=master/core-service=management/security-realm=ManagementRealm/server-identity=secret:add(value="YWRtaW4=") > run-batch > /host=master:reload > {code} > Executing this scripts results in a server log output like below and stopping of the 'DomainController': > {noformat} > [Host Controller] INFO [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0003: Creating http management service using network interface (management) port (9990) securePort (-1) > [Host Controller] WARN [org.jboss.as.domain.management.security] (MSC service thread 1-2) WFLYDM0111: Keystore /jboss/jboss-eap-7.2/domain/configuration/application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost > [Host Controller] WARN [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0001: Could not connect to remote domain controller remote+http://10.0.0.1:9990: 2-$-WFLYDC0015: There is already a registered host named 'master' > [Host Controller] at org.jboss.as.host.controller.RemoteDomainConnection$HostControllerConnectRequest.handleRequest(RemoteDomainConnection.java:390) > [Host Controller] at org.jboss.as.protocol.mgmt.AbstractMessageHandler.handleMessage(AbstractMessageHandler.java:321) > [Host Controller] at org.jboss.as.protocol.mgmt.AbstractMessageHandler.handleRequest(AbstractMessageHandler.java:286) > [Host Controller] at org.jboss.as.protocol.mgmt.AbstractMessageHandler.handleMessage(AbstractMessageHandler.java:234) > [Host Controller] at org.jboss.as.protocol.mgmt.ManagementChannelReceiver.handleMessage(ManagementChannelReceiver.java:85) > [Host Controller] at org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$handleMessageData$3(RemoteConnectionChannel.java:430) > [Host Controller] at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:991) > [Host Controller] at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > [Host Controller] at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) > [Host Controller] at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) > [Host Controller] at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) > [Host Controller] at java.lang.Thread.run(Thread.java:748) > [Host Controller] > [Host Controller] WARN [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0147: No domain controller discovery options remain. > [Host Controller] ERROR [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0002: Could not connect to master. Error was: java.lang.IllegalStateException: WFLYHC0120: Tried all domain controller discovery option(s) but unable to connect > [Host Controller] FATAL [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0178: Aborting with exit code 99 > [Host Controller] INFO [org.jboss.as] (MSC service thread 1-1) WFLYSRV0050: JBoss EAP 7.2.4.GA (WildFly Core 6.0.16.Final-redhat-00002) stopped in 77ms > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4761) Upgrade galleon and galleon-plugins to 4.1.2.Final

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFCORE-4761?page=com.atlassian.jira.plug... ] Brian Stansberry resolved WFCORE-4761. -------------------------------------- Resolution: Out of Date WFCORE-4759 supercedes this. > Upgrade galleon and galleon-plugins to 4.1.2.Final > -------------------------------------------------- > > Key: WFCORE-4761 > URL: https://issues.redhat.com/browse/WFCORE-4761 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Build System > Reporter: Jean Francois Denise > Assignee: Jean Francois Denise > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4767) Use descriptive error message for duplicate host/context deployments

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFCORE-4767?page=com.atlassian.jira.plug... ] Brian Stansberry commented on WFCORE-4767: ------------------------------------------ [~khermano] I believe this belongs back in WFLY with the Web (Undertow) component restored and Server removed. The 'host' and 'context' concepts are specific to that subsystem and any logic to detect duplicates would belong there. > Use descriptive error message for duplicate host/context deployments > -------------------------------------------------------------------- > > Key: WFCORE-4767 > URL: https://issues.redhat.com/browse/WFCORE-4767 > Project: WildFly Core > Issue Type: Enhancement > Components: Server > Reporter: Paul Ferraro > Assignee: Katarina Hermanova > Priority: Minor > > If a user attempts to deploy a web application to a host/context to which another application is deployed, this will fail for obvious reasons. > What isn't obvious is the error message. Currently, users will see a DuplicateServiceException. Ideally, the error message should indicate that another application is deployed for the same host and context path. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12875) Upgrade wildfly-http-client from 1.0.18 to 1.0.19

by Ilia Vassilev (Jira)

[ https://issues.redhat.com/browse/WFLY-12875?page=com.atlassian.jira.plugi... ] Ilia Vassilev moved JBEAP-18303 to WFLY-12875: ---------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-12875 (was: JBEAP-18303) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Build System (was: Build System) Fix Version/s: (was: 7.3.1.GA) > Upgrade wildfly-http-client from 1.0.18 to 1.0.19 > ------------------------------------------------- > > Key: WFLY-12875 > URL: https://issues.redhat.com/browse/WFLY-12875 > Project: WildFly > Issue Type: Component Upgrade > Components: Build System > Reporter: Ilia Vassilev > Assignee: Ilia Vassilev > Priority: Major > Labels: downstream_dependency > > https://github.com/wildfly/wildfly-http-client -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4763) interface "any" tag not working as expected

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFCORE-4763?page=com.atlassian.jira.plug... ] Brian Stansberry commented on WFCORE-4763: ------------------------------------------ A single interface resource in the configuration is meant to to produce a single InetAddress that other parts of the server can then use. The 'any' handling is working correctly in doing that -- as soon as it finds a criteria that generates an acceptable InetAddress available on the system, that is what it provides. The interface resource does not itself create a socket. Some other part of the system injects the InetAddress and creates a socket, and for whatever that is to listen on different addresses it would have to support injecting different multiple addresses. The management interface does not support that. Supporting binding the management interface to multiple different addresses would be an RFE. > interface "any" tag not working as expected > ------------------------------------------- > > Key: WFCORE-4763 > URL: https://issues.redhat.com/browse/WFCORE-4763 > Project: WildFly Core > Issue Type: Bug > Components: Management > Environment: Ubuntu 18.02 > Reporter: Yann Le Tallec > Priority: Major > > The {{<any>}} tag in the {{interface}} configuration of {{standalone.xml}} should accept any connection that matches ANY of the provided rules. This is not the case as demonstrated by the example below. > This configuration allows to run {{jboss-cli.sh -c}} from the machine where wildfly is running as expected: > {code:xml} > <interfaces> > <interface name="management"> > <any> > <inet-address value="127.0.0.1"/> > </any> > </interface> > </interfaces> > {code} > But if I add another (VALID) IP address inside the any tag, I can't connect any more: > {code:xml} > <interfaces> > <interface name="management"> > <any> > <inet-address value="127.0.0.1"/> > <inet-address value="10.20.230.26"/> > </any> > </interface> > </interfaces> > {code} > With the latter configuration, {{connect}} fails with the following error: > {noformat} > >The controller is not available at localhost:9990: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://localhost:9990. The connection failed: WFLYPRT0053: Could not connect to remote+http://localhost:9990. The connection failed: Connection refused > {noformat} > Note: to easily reproduce the problem from the cli, starting from a fresh standalone install: > {code:bash} > connect > /interface=management:undefine-attribute(name=inet-address) > /interface=management:undefine-attribute(name=any) > /interface=management:write-attribute(name=any,value={inet-address=[127.0.0.1]}) > reload > /interface=management:write-attribute(name=any,value={inet-address=[127.0.0.1,10.20.230.26]}) > reload > {code} > Notes: > - 10.20.230.26 must be a reachable IP - if I use a random one I can connect normally. > - if I use {{subnet-match}} I get the same issue -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12874) JAXB Unmarshaller tries to instantiate abstract class ignoring xsi:type if it is a list element

by Ilia Vassilev (Jira)

[ https://issues.redhat.com/browse/WFLY-12874?page=com.atlassian.jira.plugi... ] Ilia Vassilev moved JBEAP-18296 to WFLY-12874: ---------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-12874 (was: JBEAP-18296) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Affects Version/s: (was: 7.1.0.CR3) QE Test Coverage: (was: +) Fix Version/s: (was: 7.3.1.GA) > JAXB Unmarshaller tries to instantiate abstract class ignoring xsi:type if it is a list element > ----------------------------------------------------------------------------------------------- > > Key: WFLY-12874 > URL: https://issues.redhat.com/browse/WFLY-12874 > Project: WildFly > Issue Type: Bug > Reporter: Ilia Vassilev > Assignee: Viral Gohel > Priority: Major > Labels: downstream_dependency > > Upstream Issue: https://github.com/eclipse-ee4j/jaxb-ri/issues/1135 > Upstream PR: https://github.com/eclipse-ee4j/jaxb-ri/pull/1294 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 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 December 2019