July 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1180) Migrate QE tests upstream.

by Tibor Zimányi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1180?page=com.atlassian.jira.plugi... ] Tibor Zimányi closed DROOLS-1180. --------------------------------- > Migrate QE tests upstream. > --------------------------- > > Key: DROOLS-1180 > URL: https://issues.jboss.org/browse/DROOLS-1180 > Project: Drools > Issue Type: Enhancement > Reporter: Tibor Zimányi > Assignee: Tibor Zimányi > Priority: Minor > > We have some regression tests in QE that could be migrated upstream. This is a tracking issue for this migration. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3108) Upgrade commons-logging-jboss-logmanager from 1.0.1.Final to 1.0.2.Final

by Kabir Khan (JIRA)

Kabir Khan created WFCORE-3108: ---------------------------------- Summary: Upgrade commons-logging-jboss-logmanager from 1.0.1.Final to 1.0.2.Final Key: WFCORE-3108 URL: https://issues.jboss.org/browse/WFCORE-3108 Project: WildFly Core Issue Type: Component Upgrade Components: Logging Reporter: James Perkins Assignee: James Perkins Upgrade commons-logging-jboss-logmanager from 1.0.1.Final to 1.0.2.Final. Only contains two commits. One is just a license fix and the other fixes an issue with reporting the correct caller for the log message. https://github.com/jboss-logging/commons-logging-jboss-logmanager/compare... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9138) Warning message mistake

by Baturman Şen (JIRA)

Baturman Şen created WFLY-9138: ---------------------------------- Summary: Warning message mistake Key: WFLY-9138 URL: https://issues.jboss.org/browse/WFLY-9138 Project: WildFly Issue Type: Bug Components: CDI / Weld Affects Versions: 10.1.0.Final Reporter: Baturman Şen Assignee: Stuart Douglas Priority: Trivial I am not native english speaker but, following warning message should be fixed. {panel:title=Original Message} 09:52:31,242 WARN [org.jboss.weld.deployer] (MSC service thread 1-5) WFLYWELD0013: Deployment deployment "xxxx" contains CDI annotations but no bean archive was not found. (No beans.xml nor class with bean defining annotations) {panel} {panel:title=Fixed Message} 09:52:31,242 WARN [org.jboss.weld.deployer] (MSC service thread 1-5) WFLYWELD0013: Deployment "xxxx" contains CDI annotations but no bean archive was found. (No beans.xml nor class with bean defining annotations) {panel} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9137) SSL tests in ElytronRemoteOutboundConnectionTestCase fails on IBM JDK

by Michal Jurc (JIRA)

[ https://issues.jboss.org/browse/WFLY-9137?page=com.atlassian.jira.plugin.... ] Michal Jurc moved JBEAP-12357 to WFLY-9137: ------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-9137 (was: JBEAP-12357) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Test Suite (was: Test Suite) Affects Version/s: (was: 7.1.0.ER2) > SSL tests in ElytronRemoteOutboundConnectionTestCase fails on IBM JDK > --------------------------------------------------------------------- > > Key: WFLY-9137 > URL: https://issues.jboss.org/browse/WFLY-9137 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Michal Jurc > Assignee: Michal Jurc > > Setup in SSL tests in {{ElytronRemoteOutboundConnectionTestCase}} fails with the following on IBM JDK: > {code}{ > "outcome" => "failed", > "failure-description" => {"WFLYCTL0080: Failed services" => {"org.wildfly.security.key-manager.ejb-remote-tests-server-key-manager" => "java.security.NoSuchAlgorithmException: SunX509 KeyManagerFactory not available > Caused by: java.security.NoSuchAlgorithmException: SunX509 KeyManagerFactory not available"}}, > "rolled-back" => true > }{code} > The test runs with incorrect configuration then and therefore fails. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9136) Undertow is doubly URLDecoder.decode(ing) auth-method query parameters

by Stuart Douglas (JIRA)

Stuart Douglas created WFLY-9136: ------------------------------------ Summary: Undertow is doubly URLDecoder.decode(ing) auth-method query parameters Key: WFLY-9136 URL: https://issues.jboss.org/browse/WFLY-9136 Project: WildFly Issue Type: Bug Components: Web (Undertow) Affects Versions: 10.1.0.Final Reporter: Scott Stark Assignee: Stuart Douglas I'm testing a custom authentication mechanism that is passing in a PEM encoded public key that has been URL.encoded. I have attached the web.xml I'm using, but I have also created a simple standalone unit test that illustrates the issue. The org.wildfly.extension.undertow.deployment.AuthMethodParser.parse method calls io.undertow.util.QueryParameterUtils.parseQueryString to handle the parsing of the query string passed in with the auth-method name. This detects if there is a need to decode a parameter and does so. The resulting map of query properties is then again unconditionally decodes the values again by this loop in AuthMethodParser: {code:java} for (Map.Entry<String, Deque<String>> entry : props.entrySet()) { Deque<String> val = entry.getValue(); if (val.isEmpty()) { authMethodConfig.getProperties().put(URLDecoder.decode(entry.getKey(), UTF_8), ""); } else { authMethodConfig.getProperties().put(URLDecoder.decode(entry.getKey(), UTF_8), URLDecoder.decode(val.getFirst(), UTF_8)); } } {code} since the original value is a PEM encoded public key, it may contains '+' characters, and these then are incorrectly transformed into space characters. I would suggest that this second decoding step simply be dropped. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9135) Undertow is doubly URLDecoder.decode(ing) auth-method query parameters

by Scott Stark (JIRA)

Scott Stark created WFLY-9135: --------------------------------- Summary: Undertow is doubly URLDecoder.decode(ing) auth-method query parameters Key: WFLY-9135 URL: https://issues.jboss.org/browse/WFLY-9135 Project: WildFly Issue Type: Bug Components: Web (Undertow) Affects Versions: 10.1.0.Final Reporter: Scott Stark Assignee: Stuart Douglas Attachments: AuthMethodParserTest.java, web.xml I'm testing a custom authentication mechanism that is passing in a PEM encoded public key that has been URL.encoded. I have attached the web.xml I'm using, but I have also created a simple standalone unit test that illustrates the issue. The org.wildfly.extension.undertow.deployment.AuthMethodParser.parse method calls io.undertow.util.QueryParameterUtils.parseQueryString to handle the parsing of the query string passed in with the auth-method name. This detects if there is a need to decode a parameter and does so. The resulting map of query properties is then again unconditionally decodes the values again by this loop in AuthMethodParser: {code:java} for (Map.Entry<String, Deque<String>> entry : props.entrySet()) { Deque<String> val = entry.getValue(); if (val.isEmpty()) { authMethodConfig.getProperties().put(URLDecoder.decode(entry.getKey(), UTF_8), ""); } else { authMethodConfig.getProperties().put(URLDecoder.decode(entry.getKey(), UTF_8), URLDecoder.decode(val.getFirst(), UTF_8)); } } {code} since the original value is a PEM encoded public key, it may contains '+' characters, and these then are incorrectly transformed into space characters. I would suggest that this second decoding step simply be dropped. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9132) Applications won't deploy if their persistence.xml have multiple persistence units

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-9132?page=com.atlassian.jira.plugin.... ] Scott Marlow commented on WFLY-9132: ------------------------------------ We did make a change that likely is causing the deployment error that your seeing. Please let us know the deployment error message (include the entire exception stack trace also). [https://docs.jboss.org/author/display/WFLY10/JPA+Reference+Guide#JPARefer...] mentions the "wildfly.jpa.default-unit" persistence unit property, which you could set to true, in the persistence unit that you want to be the default (out of the multiple persistence units that you have in your application). Hope that helps. Scott > Applications won't deploy if their persistence.xml have multiple persistence units > ---------------------------------------------------------------------------------- > > Key: WFLY-9132 > URL: https://issues.jboss.org/browse/WFLY-9132 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: 10.1.0.Final > Environment: Windows 10 64 bit > Wildfly 10.1.0 > Reporter: Bobby Bassman > Assignee: Scott Marlow > > Applications won't deploy if their persistence.xml have multiple persistence units. This was not a problem with EAP. Now, Wildfly requires that each @PersistenceContext have a 'unitName' parameter. WIth EAP 6.4, if a @PersistenceContext did not have a 'unitName' parameter, then the default PU was used. By requiring that @PersistenceUnit have 'unitName', developers are forced to unnecessarily bind Java code to configuration. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3107) Allow slave hosts to ignore missing RBAC config resources

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-3107: ---------------------------------------- Summary: Allow slave hosts to ignore missing RBAC config resources Key: WFCORE-3107 URL: https://issues.jboss.org/browse/WFCORE-3107 Project: WildFly Core Issue Type: Sub-task Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Part of parent issue whereby slaves can ignore missing RBAC constraint resources for write requests coming from the DC. If the DC sent the request, then the address is ok overall. So if it's missing on the slave that means the slave doesn't have that constraint registered and doesn't need to handle the op. This fix could possibly be backported to the 2.1.x and to EAP 6.4.x in lieu of adding transformers as part of the parent issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2961) Server booting with unconfigured https management shows https port as -1

by Ken Wills (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2961?page=com.atlassian.jira.plugi... ] Ken Wills commented on WFCORE-2961: ----------------------------------- Actually comparing this to EAP7: [Host Controller] 19:19:07,947 INFO [org.jboss.as] (MSC service thread 1-7) WFLYSRV0049: JBoss EAP 7.0.0.GA (WildFly Core 2.1.2.Final-redhat-1) starting [Host Controller] 19:19:08,599 INFO [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0003: Creating http management service using network interface (management) port (9990) securePort (-1) We logged -1 too, so unrelated to this change, and I don't think we should change this now. > Server booting with unconfigured https management shows https port as -1 > ------------------------------------------------------------------------ > > Key: WFCORE-2961 > URL: https://issues.jboss.org/browse/WFCORE-2961 > Project: WildFly Core > Issue Type: Task > Reporter: Ken Wills > Assignee: Ken Wills > > See commit: 47984e987dff4cf218fde952a8bc28a75ad71f31 in core, changes from WFCORE-2771. > This may work correctly in full, so its a minor issue in core, but this needs to be checked. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2961) Server booting with unconfigured https management shows https port as -1

by Ken Wills (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2961?page=com.atlassian.jira.plugi... ] Ken Wills closed WFCORE-2961. ----------------------------- Resolution: Won't Fix > Server booting with unconfigured https management shows https port as -1 > ------------------------------------------------------------------------ > > Key: WFCORE-2961 > URL: https://issues.jboss.org/browse/WFCORE-2961 > Project: WildFly Core > Issue Type: Task > Reporter: Ken Wills > Assignee: Ken Wills > > See commit: 47984e987dff4cf218fde952a8bc28a75ad71f31 in core, changes from WFCORE-2771. > This may work correctly in full, so its a minor issue in core, but this needs to be checked. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

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