August 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-8792) System property wildfly.config.url does not work with Windows path to local file without protocol

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-8792?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-8792: ----------------------------- Fix Version/s: 14.0.0.CR1 > System property wildfly.config.url does not work with Windows path to local file without protocol > ------------------------------------------------------------------------------------------------- > > Key: WFLY-8792 > URL: https://issues.jboss.org/browse/WFLY-8792 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Ondrej Lukas > Assignee: Radovan Stancel > Labels: user_experience > Fix For: 11.0.0.Final, 14.0.0.CR1 > > > In case system property {{wildfly.config.url}} (which is used by Elytron client to find out configuration file) includes path to local file without URL protocol ({{file://}}) then linux path is automatically converted to URL started with {{file://}}. However Windows path is not converted to URL, mentioned below exception is thrown. It is caused by part of code which handles just a linux type of path, see [1]. > Using URL (i.e. protocol is explicitly used) in {{wildfly.config.url}} works correctly. It means this is user experience issue - path to local file without protocol {{file}} can be used in linux but cannot be used in Windows. > Thrown exception for Windows: > {code} > org.wildfly.client.config.ConfigXMLParseException: CONF0014: Invalid configuration file URL > at W:/workspace/eap-7x-security-elytron-testsuite-windows-olukas/f43f9016/tests-security/elytron/target/wildfly-config.xml > at org.wildfly.client.config.ClientConfiguration.readConfiguration(ClientConfiguration.java:132) > at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientConfiguration(ElytronXmlParser.java:139) > at com.redhat.eap.qe.elytron.authnctx.WildflyConfigXmlServlet.parseAndCreateAuthenticationClientConfiguration(WildflyConfigXmlServlet.java:116) > ... 41 more > Caused by: java.net.MalformedURLException: unknown protocol: w > at java.net.URL.<init>(URL.java:600) > at java.net.URL.<init>(URL.java:490) > at java.net.URL.<init>(URL.java:439) > at java.net.URI.toURL(URI.java:1089) > at org.wildfly.client.config.ClientConfiguration.streamOpener(ClientConfiguration.java:67) > at org.wildfly.client.config.ClientConfiguration.readConfiguration(ClientConfiguration.java:130) > ... 43 more > {code} > [1] https://github.com/wildfly/wildfly-client-config/blob/7c12683cd29f88261e7... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8792) System property wildfly.config.url does not work with Windows path to local file without protocol

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-8792?page=com.atlassian.jira.plugin.... ] Kabir Khan resolved WFLY-8792. ------------------------------ Resolution: Done > System property wildfly.config.url does not work with Windows path to local file without protocol > ------------------------------------------------------------------------------------------------- > > Key: WFLY-8792 > URL: https://issues.jboss.org/browse/WFLY-8792 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Ondrej Lukas > Assignee: Radovan Stancel > Labels: user_experience > Fix For: 14.0.0.CR1, 11.0.0.Final > > > In case system property {{wildfly.config.url}} (which is used by Elytron client to find out configuration file) includes path to local file without URL protocol ({{file://}}) then linux path is automatically converted to URL started with {{file://}}. However Windows path is not converted to URL, mentioned below exception is thrown. It is caused by part of code which handles just a linux type of path, see [1]. > Using URL (i.e. protocol is explicitly used) in {{wildfly.config.url}} works correctly. It means this is user experience issue - path to local file without protocol {{file}} can be used in linux but cannot be used in Windows. > Thrown exception for Windows: > {code} > org.wildfly.client.config.ConfigXMLParseException: CONF0014: Invalid configuration file URL > at W:/workspace/eap-7x-security-elytron-testsuite-windows-olukas/f43f9016/tests-security/elytron/target/wildfly-config.xml > at org.wildfly.client.config.ClientConfiguration.readConfiguration(ClientConfiguration.java:132) > at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientConfiguration(ElytronXmlParser.java:139) > at com.redhat.eap.qe.elytron.authnctx.WildflyConfigXmlServlet.parseAndCreateAuthenticationClientConfiguration(WildflyConfigXmlServlet.java:116) > ... 41 more > Caused by: java.net.MalformedURLException: unknown protocol: w > at java.net.URL.<init>(URL.java:600) > at java.net.URL.<init>(URL.java:490) > at java.net.URL.<init>(URL.java:439) > at java.net.URI.toURL(URI.java:1089) > at org.wildfly.client.config.ClientConfiguration.streamOpener(ClientConfiguration.java:67) > at org.wildfly.client.config.ClientConfiguration.readConfiguration(ClientConfiguration.java:130) > ... 43 more > {code} > [1] https://github.com/wildfly/wildfly-client-config/blob/7c12683cd29f88261e7... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8792) System property wildfly.config.url does not work with Windows path to local file without protocol

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-8792?page=com.atlassian.jira.plugin.... ] Kabir Khan reopened WFLY-8792: ------------------------------ > System property wildfly.config.url does not work with Windows path to local file without protocol > ------------------------------------------------------------------------------------------------- > > Key: WFLY-8792 > URL: https://issues.jboss.org/browse/WFLY-8792 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Ondrej Lukas > Assignee: Radovan Stancel > Labels: user_experience > Fix For: 11.0.0.Final, 14.0.0.CR1 > > > In case system property {{wildfly.config.url}} (which is used by Elytron client to find out configuration file) includes path to local file without URL protocol ({{file://}}) then linux path is automatically converted to URL started with {{file://}}. However Windows path is not converted to URL, mentioned below exception is thrown. It is caused by part of code which handles just a linux type of path, see [1]. > Using URL (i.e. protocol is explicitly used) in {{wildfly.config.url}} works correctly. It means this is user experience issue - path to local file without protocol {{file}} can be used in linux but cannot be used in Windows. > Thrown exception for Windows: > {code} > org.wildfly.client.config.ConfigXMLParseException: CONF0014: Invalid configuration file URL > at W:/workspace/eap-7x-security-elytron-testsuite-windows-olukas/f43f9016/tests-security/elytron/target/wildfly-config.xml > at org.wildfly.client.config.ClientConfiguration.readConfiguration(ClientConfiguration.java:132) > at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientConfiguration(ElytronXmlParser.java:139) > at com.redhat.eap.qe.elytron.authnctx.WildflyConfigXmlServlet.parseAndCreateAuthenticationClientConfiguration(WildflyConfigXmlServlet.java:116) > ... 41 more > Caused by: java.net.MalformedURLException: unknown protocol: w > at java.net.URL.<init>(URL.java:600) > at java.net.URL.<init>(URL.java:490) > at java.net.URL.<init>(URL.java:439) > at java.net.URI.toURL(URI.java:1089) > at org.wildfly.client.config.ClientConfiguration.streamOpener(ClientConfiguration.java:67) > at org.wildfly.client.config.ClientConfiguration.readConfiguration(ClientConfiguration.java:130) > ... 43 more > {code} > [1] https://github.com/wildfly/wildfly-client-config/blob/7c12683cd29f88261e7... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4071) (7.1.z) Upgrade wildfly-client-config from 1.0.0 to 1.0.1

by Ingo Weiss (JIRA)

[ https://issues.jboss.org/browse/WFCORE-4071?page=com.atlassian.jira.plugi... ] Ingo Weiss moved JBEAP-15318 to WFCORE-4071: -------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-4071 (was: JBEAP-15318) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Build System (was: Build System) Affects Version/s: 1.0.0.Final (was: 7.1.2.GA) Fix Version/s: 1.0.1.Final (was: 7.1.5.GA) > (7.1.z) Upgrade wildfly-client-config from 1.0.0 to 1.0.1 > --------------------------------------------------------- > > Key: WFCORE-4071 > URL: https://issues.jboss.org/browse/WFCORE-4071 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Build System > Affects Versions: 1.0.0.Final > Reporter: Ingo Weiss > Assignee: Vladimir Dosoudil > Fix For: 1.0.1.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-120) [Artemis 2.x upgrade] Undelivered/Lost messages in remote JCA scenario with killing remote servers

by Miroslav Novak (JIRA)

Miroslav Novak created WFWIP-120: ------------------------------------ Summary: [Artemis 2.x upgrade] Undelivered/Lost messages in remote JCA scenario with killing remote servers Key: WFWIP-120 URL: https://issues.jboss.org/browse/WFWIP-120 Project: WildFly WIP Issue Type: Bug Components: Artemis Reporter: Miroslav Novak Assignee: Martyn Taylor Priority: Critical There undelivered/lost messages in sceario where MDB is connected to remote Artemis cluster in which nodes are killed and restarted. Issue is intermittent. Test Scenario: * start cluster containing node 1 and 3 with deployed inQueue and outQueue ** JDBC store with Oracle 12c is used * start node 2 and 4 * producer sends 5000 small and large messages to inQueue to node-1 * wait for producer to finish * deploy MDBs to node-2 and node-4 which read messages from inQueue and sends them to outQueue in XA transactions * kill and start following nodes in this sequence: 1,3,1,3,1 * wait until all messages are processed * start Consumer which consumes messages form outQueue * Check that number of messages sent to InQueue and received from OutQueue is the same Result: 7 messages were missing in OutQueue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4070) Upgrade jboss-vfs to 3.2.14.Final

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-4070?page=com.atlassian.jira.plugi... ] Kabir Khan resolved WFCORE-4070. -------------------------------- Fix Version/s: 6.0.0.CR5 Resolution: Done > Upgrade jboss-vfs to 3.2.14.Final > --------------------------------- > > Key: WFCORE-4070 > URL: https://issues.jboss.org/browse/WFCORE-4070 > Project: WildFly Core > Issue Type: Component Upgrade > Components: VFS > Reporter: Tomas Hofman > Fix For: 6.0.0.CR5 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4070) Upgrade jboss-vfs to 3.2.14.Final

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-4070?page=com.atlassian.jira.plugi... ] Kabir Khan moved WFLY-10707 to WFCORE-4070: ------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-4070 (was: WFLY-10707) Component/s: VFS (was: VFS) > Upgrade jboss-vfs to 3.2.14.Final > --------------------------------- > > Key: WFCORE-4070 > URL: https://issues.jboss.org/browse/WFCORE-4070 > Project: WildFly Core > Issue Type: Component Upgrade > Components: VFS > Reporter: Tomas Hofman > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3310) mechanism-configuration in http/sasl authentication factory in server configuration should fail when includes some attribute

by Jiri Ondrusek (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3310?page=com.atlassian.jira.plugi... ] Jiri Ondrusek reassigned WFCORE-3310: ------------------------------------- Assignee: Jiri Ondrusek (was: Ilia Vassilev) > mechanism-configuration in http/sasl authentication factory in server configuration should fail when includes some attribute > ---------------------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-3310 > URL: https://issues.jboss.org/browse/WFCORE-3310 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 3.0.3.Final > Reporter: Ondrej Lukas > Assignee: Jiri Ondrusek > > Based on wildfly-elytron XSD mechanism-configuration element of http-authentication-factory or sasl-authentication-factory should not contain any attribute. However when some attribute is added for this element in standalone.xml then it does not fail during server start. In correct behavior Validation error should be thrown during starting server. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10707) Upgrade jboss-vfs to 3.2.14.Final

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-10707?page=com.atlassian.jira.plugin... ] Kabir Khan updated WFLY-10707: ------------------------------ Summary: Upgrade jboss-vfs to 3.2.14.Final (was: Upgrade jboss-vfs to 3.2.13.Final) > Upgrade jboss-vfs to 3.2.14.Final > --------------------------------- > > Key: WFLY-10707 > URL: https://issues.jboss.org/browse/WFLY-10707 > Project: WildFly > Issue Type: Component Upgrade > Components: VFS > Reporter: Tomas Hofman > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3310) mechanism-configuration in http/sasl authentication factory in server configuration should fail when includes some attribute

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3310?page=com.atlassian.jira.plugi... ] Darran Lofthouse commented on WFCORE-3310: ------------------------------------------ I suspect this may be largely out of date - at this stage I would suggest the first thing is to verify the current issue. > mechanism-configuration in http/sasl authentication factory in server configuration should fail when includes some attribute > ---------------------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-3310 > URL: https://issues.jboss.org/browse/WFCORE-3310 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 3.0.3.Final > Reporter: Ondrej Lukas > Assignee: Ilia Vassilev > > Based on wildfly-elytron XSD mechanism-configuration element of http-authentication-factory or sasl-authentication-factory should not contain any attribute. However when some attribute is added for this element in standalone.xml then it does not fail during server start. In correct behavior Validation error should be thrown during starting server. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

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