December 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4567) Remove support for jboss-as-jca_1_0.xsd

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4567?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4567. ---------------------------- > Remove support for jboss-as-jca_1_0.xsd > --------------------------------------- > > Key: WFLY-4567 > URL: https://issues.jboss.org/browse/WFLY-4567 > Project: WildFly > Issue Type: Task > Components: JCA > Reporter: Jesper Pedersen > Assignee: Stefano Maestri > Fix For: 10.0.0.Alpha5 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5280) Connector attribute max-save-post-size is neither migrated nor migration writing is shown

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5280?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5280. ---------------------------- > Connector attribute max-save-post-size is neither migrated nor migration writing is shown > ----------------------------------------------------------------------------------------- > > Key: WFLY-5280 > URL: https://issues.jboss.org/browse/WFLY-5280 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 10.0.0.Beta2 > Reporter: Radim Hatlapatka > Assignee: Stuart Douglas > Priority: Critical > Fix For: 10.0.0.CR1 > > > When migrating http connector, which has defined attribute {{max-save-post-size}} no warning that it is not possible to migrate the {{max-save-post-size}} is printed. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4817) WildFly (Undertow) fails to include jsp static content when "If-Modified-Since" header is used

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4817?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4817. ---------------------------- > WildFly (Undertow) fails to include jsp static content when "If-Modified-Since" header is used > ---------------------------------------------------------------------------------------------- > > Key: WFLY-4817 > URL: https://issues.jboss.org/browse/WFLY-4817 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 9.0.0.CR2 > Reporter: Marco Mondini > Assignee: Stuart Douglas > Fix For: 9.0.1.Final, 10.0.0.Alpha6 > > > WildFly (Undertow) doesn't correctly include static content in jsp when tag is used in combination of "If-Modified-Since" header as per https://issues.jboss.org/browse/UNDERTOW-476. > Upgrading Undertow to version 1.2.9.Final will fix the issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4628) Add ability to restart and stop batch jobs

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4628?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4628. ---------------------------- > Add ability to restart and stop batch jobs > ------------------------------------------ > > Key: WFLY-4628 > URL: https://issues.jboss.org/browse/WFLY-4628 > Project: WildFly > Issue Type: Feature Request > Components: Batch > Reporter: James Perkins > Assignee: James Perkins > Priority: Blocker > Fix For: 10.0.0.Beta1 > > > Currently there is only a way to view batch jobs for a deployment with in the batch subsystem management. There should be a way to restart and stop running jobs as well. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5283) [Migration operation] [Web to Undertow] Connector's protocol names via FQCN are not recognized as migratable

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5283?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5283. ---------------------------- > [Migration operation] [Web to Undertow] Connector's protocol names via FQCN are not recognized as migratable > ------------------------------------------------------------------------------------------------------------ > > Key: WFLY-5283 > URL: https://issues.jboss.org/browse/WFLY-5283 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 10.0.0.Beta2 > Reporter: Radim Hatlapatka > Assignee: Stuart Douglas > Priority: Critical > Fix For: 10.0.0.CR1 > > > In Web subsystem there is possible to define protocol either via its API name (e.g. {{HTTP/1.1}}, where it is taken default implementation of given API) or via FQCN. > In case of {{HTTP/1.1}} there are several implementations: > JIO => {{org.apache.coyote.http11.Http11Protocol}} - default protocol > NIO2 => {{org.apache.coyote.http11.Http11NioProtocol}} - required to be used to be able to use WebSockets > APR (default with natives) => {{org.apache.coyote.http11.Http11AprProtocol}} > The {{:migrate}} operation should also recognize these FQCN as valid HTTP/HTTPS protocols and migrate them correctly. > Note: in case of AJP there are these FQCN: > {{org.apache.coyote.ajp.AjpAprProtocol}} - AJP with natives enabled > {{org.apache.coyote.ajp.AjpProtocol}} AJP without natives -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4801) When expression is used in jndi name attribute of datasource then test-connection-in-pool operation is not working

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4801?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4801. ---------------------------- > When expression is used in jndi name attribute of datasource then test-connection-in-pool operation is not working > ------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-4801 > URL: https://issues.jboss.org/browse/WFLY-4801 > Project: WildFly > Issue Type: Bug > Components: JCA > Affects Versions: 10.0.0.Alpha3 > Reporter: Chao Wang > Assignee: Chao Wang > Fix For: 9.0.0.Final, 10.0.0.Alpha4 > > > {noformat} > Description of problem: > ======================== > - Expression is added in the datasource JNDI name attribute as below: > ----- > <datasource jndi-name="${ds}" pool-name="ExampleDS" enabled="true" use-java-context="true"> > ----- > - Value for the expression is passed to the JBoss server during the JBoss startup as below: > ----- > ./standalone.sh -Dds=java:jboss/datasources/ExampleDS > ----- > - In the server.log file below is the information regarding the datasource. > ----- > INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) JBAS010400: Bound data source [${ds}] > ----- > - Test the datasource using the below command and here is the result: > ---- > [standalone@localhost:9999 /] /subsystem=datasources/data-source=ExampleDS:test-connection-in-pool() > { > "outcome" => "failed", > "failure-description" => "JBAS010440: failed to invoke operation: JBAS010442: failed to match pool. Check JndiName: java:/${ds}", > "rolled-back" => true > } > ---- > - Here is the information regarding the JNDI name attribute: > ---- > [standalone@localhost:9999 /] /subsystem=datasources/data-source=ExampleDS:read-resource-description(recursive=true) > { > "outcome" => "success", > "result" => { > : > "jndi-name" => { > "type" => STRING, > "description" => "Specifies the JNDI name for the datasource", > "expressions-allowed" => true, > "nillable" => false, > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "no-services" > }, > : > } > ----- > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4146) Cache add operation should automatically create its child resources

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4146?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4146. ---------------------------- > Cache add operation should automatically create its child resources > ------------------------------------------------------------------- > > Key: WFLY-4146 > URL: https://issues.jboss.org/browse/WFLY-4146 > Project: WildFly > Issue Type: Enhancement > Components: Clustering > Affects Versions: 9.0.0.Alpha1 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 10.0.0.Alpha6 > > > There is effectively no difference between the behavior of a cache that does not contain a given child resource (e.g. transaction, locking, etc) and one that contains the child resource, but with default attribute values. > Consequently, the cache add operation should automatically create these resources (and the cache remove operation should automatically remove them). We can treat the child add operations as no-ops, and the child remove operations as a series of undefine-attribute operations. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4861) Unable to establish HTTP/2 connection via plain http (non https)

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4861?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4861. ---------------------------- > Unable to establish HTTP/2 connection via plain http (non https) > ---------------------------------------------------------------- > > Key: WFLY-4861 > URL: https://issues.jboss.org/browse/WFLY-4861 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 10.0.0.Alpha4 > Reporter: Radim Hatlapatka > Assignee: Stuart Douglas > Priority: Blocker > Fix For: 10.0.0.Alpha5 > > > HTTP/2 doesn't work over plain http (non-https) even when {{http-listener}}'s {{enable-http2}} option is set to {{true}}, see [1]. > I am using Http2 client from netty for trying whether it is possible to establish HHTP/2 connection via upgrade. > [1] > {code:xml} > <server name="default-server"> > <http-listener name="default" socket-binding="http" enable-http2="true" redirect-socket="https"/> > <https-listener name="https" socket-binding="https" security-realm="https" enable-http2="true"/> > <host name="default-host" alias="localhost"> > <location name="/" handler="welcome-content"/> > <filter-ref name="server-header"/> > <filter-ref name="x-powered-by-header"/> > </host> > </server> > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4730) Undertow mod_cluster proxy does not offer any Client HTTPS configuration

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4730?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4730. ---------------------------- > Undertow mod_cluster proxy does not offer any Client HTTPS configuration > ------------------------------------------------------------------------ > > Key: WFLY-4730 > URL: https://issues.jboss.org/browse/WFLY-4730 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 9.0.0.CR1, 10.0.0.Alpha2 > Reporter: Michal Karm Babacek > Assignee: Stuart Douglas > Priority: Blocker > Fix For: 10.0.0.Alpha3 > > > Undertow mod_cluster proxy acts both as a *server* and as a *client* in relation to its workers. > While the *server* configuration is quite straightforward: > {code:xml} > +++ > <system-properties> > <property name="javax.net.ssl.trustStore" value="/vault/ca-cert.jks"/> > <property name="javax.net.ssl.trustStorePassword" value="tomcat"/> > </system-properties> > +++ > <security-realm name="UndertowRealm"> > <server-identities> > <ssl> > <keystore path="/vault/server-cert-key.jks" keystore-password="tomcat" alias="javaserver" key-password="tomcat"/> > </ssl> > </server-identities> > </security-realm> > +++ > <https-listener name="https" socket-binding="https" security-realm="UndertowRealm"/> > +++ > {code} > with having {{management-socket-binding="https"}} and {{advertise-protocol="https"}} set; it seems there is no way to configure certs and keys for the *client* role of the Undertow mod_cluster proxy implementation. > With the current implementation, *worker* can connect to the Undertow mod_cluster proxy, i.e. it can send {{CONFIG}} and {{STATUS}} MCMP messages, but when the Undertow mod_cluster proxy needs to act as a *client*, sending {{STATUS-RSP}} message to the *worker*, it does not have the necessary HTTPS setup: > {noformat} > DEBUG [io.undertow] (default I/O-5) UT005055: HttpClientPingTask run for connection: https://192.168.0.122:8544/?# > DEBUG [io.undertow.server.handlers.proxy.ProxyHandler] (default I/O-5) No proxy target for request to https://192.168.0.122:8443/ > DEBUG [io.undertow] (default task-7) UT005056: Received node load in STATUS message, node jvmRoute: worker-1, load: 80 > DEBUG [io.undertow.request] (default I/O-5) Failed to connect: java.io.IOException: UT000065: SSL must be specified to connect to a https URL > at io.undertow.client.http.HttpClientProvider.connect(HttpClientProvider.java:93) > at io.undertow.client.UndertowClient.connect(UndertowClient.java:158) > at io.undertow.server.handlers.proxy.ProxyConnectionPool.openConnection(ProxyConnectionPool.java:233) > at io.undertow.server.handlers.proxy.ProxyConnectionPool.connect(ProxyConnectionPool.java:446) > at io.undertow.server.handlers.proxy.mod_cluster.NodePingUtil$1.run(NodePingUtil.java:140) > at org.xnio.nio.WorkerThread.safeRun(WorkerThread.java:560) > at org.xnio.nio.WorkerThread.run(WorkerThread.java:462) > {noformat} > The HTTPS communication between Undertow mod_cluster proxy and its workers needs to be bidirectional. > If I'm just missing any obvious configuration option, please, shout, throw rocks and close this JIRA :) > Thank you for your time looking into it. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4740) Move JMS high-level commands to the messaging extension

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4740?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4740. ---------------------------- > Move JMS high-level commands to the messaging extension > ------------------------------------------------------- > > Key: WFLY-4740 > URL: https://issues.jboss.org/browse/WFLY-4740 > Project: WildFly > Issue Type: Enhancement > Components: JMS > Affects Versions: 10.0.0.Alpha2 > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 10.0.0.Alpha3 > > > This is the pending WildFly issue for WFCORE-733 to move the high-level JMS cli commands to the messaging extension instead of having them hard-coded in the wildfly-cli module -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 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 2017