March 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-2451) CS tool, invalid content of --type parameter leads to NPE

by Ilia Vassilev (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2451?page=com.atlassian.jira.plugi... ] Ilia Vassilev commented on WFCORE-2451: --------------------------------------- This issue is resolved by PR [1] for WFCORE-2484 which will display the complete stack trace of the underlying exception. [1] https://github.com/wildfly-security/wildfly-elytron-tool/pull/23 > CS tool, invalid content of --type parameter leads to NPE > --------------------------------------------------------- > > Key: WFCORE-2451 > URL: https://issues.jboss.org/browse/WFCORE-2451 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Martin Choma > Assignee: Ilia Vassilev > Priority: Critical > > If I fill --type option with some invalid value (other then KeyStoreCredentialStore) I get NPE. For example with -t DoesNotExists I get > {code} > [mchoma@localhost bin]$ java -jar wildfly-elytron-tool.jar credential-store --add myalias --secret supersecretpassword --location="/tmp/test.store" --uri "cr-store://test?modifiable=true;create=true;keyStoreType=JCEKS" --password mycspassword --salt 12345678 --iteration 230 --summary -t DoesNotExists > Exception in thread "main" java.lang.NullPointerException > at java.util.regex.Matcher.getTextLength(Matcher.java:1283) > at java.util.regex.Matcher.reset(Matcher.java:309) > at java.util.regex.Matcher.<init>(Matcher.java:229) > at java.util.regex.Pattern.matcher(Pattern.java:1093) > at java.util.Formatter.parse(Formatter.java:2547) > at java.util.Formatter.format(Formatter.java:2501) > at java.io.PrintStream.format(PrintStream.java:970) > at java.io.PrintStream.printf(PrintStream.java:871) > at org.wildfly.security.tool.ElytronTool.main(ElytronTool.java:58) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8467) simple-election-policy is not sufficiently descriptive

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-8467: ---------------------------------- Summary: simple-election-policy is not sufficiently descriptive Key: WFLY-8467 URL: https://issues.jboss.org/browse/WFLY-8467 Project: WildFly Issue Type: Enhancement Components: Clustering Affects Versions: 11.0.0.Alpha1 Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 12.0.0.Alpha1 simple-election-policy was originally a port of http://anonsvn.jboss.org/repos/jbossas/trunk/cluster/src/main/java/org/jb... It's time to revisit this. 1. The term "simple" doesn't at all describe how the policy elects the primary node. 2. "position" isn't intuitive either - until you realize that it is a reference to the underlying data structure. 3. Is the ability to specify the nth youngest or oldest node a realistic requirement? We can generalize this policy as doing 2 things: a. Sorts the candidates based on some criteria (e.g. age, name) b. Select the head of the sorted list This is logically equivalent to: members.stream().sort(comparator).findFirst(); Proposal: <age-election-policy sort="DESCENDING|ASCENDING"/> <name-election-policy sort="ASCENDING|DESCENDING"/> -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2488) Elytron keystore type default value

by Ilia Vassilev (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2488?page=com.atlassian.jira.plugi... ] Ilia Vassilev closed WFCORE-2488. --------------------------------- Release Notes Text: JBEAP-8508 was closed Resolution: Rejected > Elytron keystore type default value > ----------------------------------- > > Key: WFCORE-2488 > URL: https://issues.jboss.org/browse/WFCORE-2488 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Martin Choma > Assignee: Ilia Vassilev > > Make attribute type optional during key-store creation. If not set default value "JKS" can be used. > Basically in this issue is requesting same behaviour as legacy keystore in realms > {code:jsonl|title=ManagementModel} > "keystore-provider" => { > "type" => STRING, > "description" => "The provider for loading the keystore, defaults to JKS.", > "expressions-allowed" => true, > "required" => false, > "nillable" => true, > "default" => "JKS", > "min-length" => 1L, > "max-length" => 2147483647L, > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "resource-services" > }, > {code} > Extracted from WFLY-7125 and tracked as separate issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1041) Add support for PKCS11 in KeyStoreCredentialStore

by Peter Skopek (JIRA)

Peter Skopek created ELY-1041: --------------------------------- Summary: Add support for PKCS11 in KeyStoreCredentialStore Key: ELY-1041 URL: https://issues.jboss.org/browse/ELY-1041 Project: WildFly Elytron Issue Type: Task Components: Credential Store Reporter: Peter Skopek Assignee: Peter Skopek To be able to use KeyStoreCredentialStore in FIPS mode we need to have support for working with SecretKey stored in PKCS11 credential store. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2588) Deprecate optional dependencies in manifests and descriptors

by Richard Opalka (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2588?page=com.atlassian.jira.plugi... ] Richard Opalka closed WFCORE-2588. ---------------------------------- Resolution: Rejected After comments on associated PR from WildFly folks I'm closing this issue. The optional module dependencies will be worked around in DU processing chain. > Deprecate optional dependencies in manifests and descriptors > ------------------------------------------------------------ > > Key: WFCORE-2588 > URL: https://issues.jboss.org/browse/WFCORE-2588 > Project: WildFly Core > Issue Type: Enhancement > Affects Versions: 3.0.0.Beta11 > Reporter: Richard Opalka > Assignee: Richard Opalka > Fix For: 3.0.0.Beta12 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8466) Socket leak when setting HTTP Content-Length and client not reading entire response

by Johannes Ritter (JIRA)

[ https://issues.jboss.org/browse/WFLY-8466?page=com.atlassian.jira.plugin.... ] Johannes Ritter commented on WFLY-8466: --------------------------------------- Probably related to this issue. > Socket leak when setting HTTP Content-Length and client not reading entire response > ----------------------------------------------------------------------------------- > > Key: WFLY-8466 > URL: https://issues.jboss.org/browse/WFLY-8466 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 10.1.0.Final > Environment: CentOS 6.7 > Reporter: Johannes Ritter > Assignee: Stuart Douglas > Labels: leak, socket > Attachments: socket_leak.tar.gz > > > Wildfly leaks half-open sockets if the client closes the connection before all data was sent to the client. This only happens when the HTTP header field "Content-Length" was manually set. > The leaked sockets can be determined by "lsof -p <process-id> | grep identify". The relevant sockets are listed with "Can't identify protocol". > The leak occurs if the client connection is closed (on the client side) before the server could send the complete response. > It does not happen every time. I have attached an example application using a web browser as client. One button click sends the request 500 times. The socket does not leak on every button click. > *Another interesting fact is, that the socket will also leak if a Content-Length larger than the actual response data is set.* This is independent from the client's behavior. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8466) Socket leak when setting HTTP Content-Length and client not reading entire response

by Johannes Ritter (JIRA)

Johannes Ritter created WFLY-8466: ------------------------------------- Summary: Socket leak when setting HTTP Content-Length and client not reading entire response Key: WFLY-8466 URL: https://issues.jboss.org/browse/WFLY-8466 Project: WildFly Issue Type: Bug Components: Web (Undertow) Affects Versions: 10.1.0.Final Environment: CentOS 6.7 Reporter: Johannes Ritter Assignee: Stuart Douglas Attachments: socket_leak.tar.gz Wildfly leaks half-open sockets if the client closes the connection before all data was sent to the client. This only happens when the HTTP header field "Content-Length" was manually set. The leaked sockets can be determined by "lsof -p <process-id> | grep identify". The relevant sockets are listed with "Can't identify protocol". The leak occurs if the client connection is closed (on the client side) before the server could send the complete response. It does not happen every time. I have attached an example application using a web browser as client. One button click sends the request 500 times. The socket does not leak on every button click. *Another interesting fact is, that the socket will also leak if a Content-Length larger than the actual response data is set.* This is independent from the client's behavior. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBJCA-1341) Account for additional DB2 FATAL connection errors

by Ingo Weiss (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1341?page=com.atlassian.jira.plugin... ] Ingo Weiss updated JBJCA-1341: ------------------------------ Git Pull Request: https://github.com/ironjacamar/ironjacamar/pull/622, https://github.com/ironjacamar/ironjacamar/pull/621, https://github.com/ironjacamar/ironjacamar/pull/620, https://github.com/ironjacamar/ironjacamar/pull/613, https://github.com/ironjacamar/ironjacamar/pull/612, https://github.com/ironjacamar/ironjacamar/pull/611, https://github.com/ironjacamar/ironjacamar/pull/606, https://github.com/ironjacamar/ironjacamar/pull/607, https://github.com/ironjacamar/ironjacamar/pull/608 (was: https://github.com/ironjacamar/ironjacamar/pull/613, https://github.com/ironjacamar/ironjacamar/pull/612, https://github.com/ironjacamar/ironjacamar/pull/611, https://github.com/ironjacamar/ironjacamar/pull/606, https://github.com/ironjacamar/ironjacamar/pull/607, https://github.com/ironjacamar/ironjacamar/pull/608) > Account for additional DB2 FATAL connection errors > -------------------------------------------------- > > Key: JBJCA-1341 > URL: https://issues.jboss.org/browse/JBJCA-1341 > Project: IronJacamar > Issue Type: Enhancement > Components: Validator > Reporter: Ingo Weiss > Assignee: Ingo Weiss > Original Estimate: 2 days > Time Spent: 2 days > Remaining Estimate: 0 minutes > > Various version of pre 11.x DB2 drivers utilize the -99999 error code for a SQLException. Not all -99999 errors are fatal. For those variations that are known to be fatal, a check should be added to treat as such. > One example would be the -99999 error that indicates "Connection is closed" -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1040) Elytron, incorrect IPv6 address resolution

by Martin Choma (JIRA)

Martin Choma created ELY-1040: --------------------------------- Summary: Elytron, incorrect IPv6 address resolution Key: ELY-1040 URL: https://issues.jboss.org/browse/ELY-1040 Project: WildFly Elytron Issue Type: Bug Reporter: Martin Choma Assignee: Darran Lofthouse Priority: Critical There is code in Elytron {code:java|title=SetMechanismInformationMechanismFactory.java} @Override public void evaluateRequest(HttpServerRequest request) throws HttpAuthenticationException { String host = request.getFirstRequestHeaderValue(HOST); String resolvedHostName = null; if (host != null) { if (host.startsWith("[")) { int close = host.indexOf(']'); if (close > 0) { resolvedHostName = host.substring(0, close); } } {code} I assume intention of this code is to get from e.g. "[::1]:8080" just "[::1]", but now it gets only "[::1". To achieve this my assumption, there should be rather {code} resolvedHostName = host.substring(0, close + 1); {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2023) Log viewer does not show any log file for rpm installation

by Ivo Hrádek (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2023?page=com.atlassian.jira.plugi... ] Ivo Hrádek reassigned WFCORE-2023: ---------------------------------- Assignee: Ivo Hrádek (was: Bartosz Baranowski) > Log viewer does not show any log file for rpm installation > ---------------------------------------------------------- > > Key: WFCORE-2023 > URL: https://issues.jboss.org/browse/WFCORE-2023 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Reporter: Bartosz Baranowski > Assignee: Ivo Hrádek > > I'm running a fresh RHEL7.3 server subscribed to the current jboss eap7 repository [1] using the rpm package. [2] > [1] subscription-manager repos --enable=jb-eap-7-for-rhel-RHEL_VERSION-server-rpms > [2] https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-appli... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

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