March 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-8160) Webservice response File Descriptor leak

by Mahesh Reddy (JIRA)

[ https://issues.jboss.org/browse/WFLY-8160?page=com.atlassian.jira.plugin.... ] Mahesh Reddy updated WFLY-8160: ------------------------------- Attachment: file-leak-detector_output.txt > Webservice response File Descriptor leak > ---------------------------------------- > > Key: WFLY-8160 > URL: https://issues.jboss.org/browse/WFLY-8160 > Project: WildFly > Issue Type: Bug > Components: Web Services > Affects Versions: 9.0.0.Final, 9.0.2.Final, 10.1.0.Final > Environment: JDK: jdk1.8.0_121, jdk1.8.0_66 > WilfFly : wildfly-10.1.0.Final, wildfly-9.0.2.Final , wildfly-9.0.0.Final > OS: Red Hat Enterprise Linux Server release 7.1 (Maipo) > Hardware: 64 bit 4 core > Reporter: Mahesh Reddy > Assignee: Alessio Soldano > Attachments: BioMatcherWebserviceImpl.java, SOAP_REQUEST.txt, SOAP_RESPONSE.txt, file-leak-detector_output.txt > > > We are getting File descriptor leak when wildfly responds to webservice call. > I think this happens if the webresvice response is huge complex structure, > I confirmed by adding the sleep just before the returning from the webservice method and checking lsof -p <pid>, And again checking it after client receives the response,. > I notice for each webservice call, 2 file descriptors are open and never closed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8441) Stack containing encrypt-protocol throws IllegalStateException at runtime

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-8441?page=com.atlassian.jira.plugin.... ] Paul Ferraro moved JBEAP-9868 to WFLY-8441: ------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-8441 (was: JBEAP-9868) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Clustering (was: Clustering) Affects Version/s: No Release (was: 7.1.0.DR15) > Stack containing encrypt-protocol throws IllegalStateException at runtime > -------------------------------------------------------------------------- > > Key: WFLY-8441 > URL: https://issues.jboss.org/browse/WFLY-8441 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: No Release > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Critical > > Looks to be the result of a botched merge/rebase. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8426) EJBClientDescriptorTestCase doesn't do a proper clean-up

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-8426?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-8426: ----------------------------------- Fix Version/s: 11.0.0.Alpha1 > EJBClientDescriptorTestCase doesn't do a proper clean-up > -------------------------------------------------------- > > Key: WFLY-8426 > URL: https://issues.jboss.org/browse/WFLY-8426 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Josef Cacek > Assignee: Josef Cacek > Fix For: 11.0.0.Alpha1 > > > The ServerSetupTask instance {{EJBClientDescriptorTestCase.EJBClientDescriptorTestCaseSetup}} has a wrong order of operations in {{tearDown}} method, so already the first operation fails. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8421) Upgrade jboss-ejb-client to 4.0.0.Beta22

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-8421?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-8421: ----------------------------------- Fix Version/s: 11.0.0.Alpha1 > Upgrade jboss-ejb-client to 4.0.0.Beta22 > ---------------------------------------- > > Key: WFLY-8421 > URL: https://issues.jboss.org/browse/WFLY-8421 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Farah Juma > Assignee: Farah Juma > Fix For: 11.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8423) Transaction client does not have access to EJB client

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-8423?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-8423: ----------------------------------- Fix Version/s: 11.0.0.Alpha1 > Transaction client does not have access to EJB client > ----------------------------------------------------- > > Key: WFLY-8423 > URL: https://issues.jboss.org/browse/WFLY-8423 > Project: WildFly > Issue Type: Bug > Components: Build System > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: 11.0.0.Alpha1 > > > Missing import in the module.xml for the tx client. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8429) Pooled connection factory with default discovery group is not able to connect to cluster

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-8429?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-8429: ----------------------------------- Fix Version/s: 11.0.0.Alpha1 > Pooled connection factory with default discovery group is not able to connect to cluster > ---------------------------------------------------------------------------------------- > > Key: WFLY-8429 > URL: https://issues.jboss.org/browse/WFLY-8429 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 11.0.0.Alpha1 > > > Test Scenario: > * Start 1st EAP 7.1 server with deployed queues InQueue and OutQueue > * Start 2nd EAP 7.1 server with MDB which consumes messages from InQueue and resends to OutQueue > ** pooled-connection-factory is using default {{discovery-group="dg-group1"}} to get connectors to 1st EAP 7.1 server > * Send messages to InQueue and consume from OutQueue > Pass Criteria: Number of send and received messages is the same. > Actual Result: > MDB does not start to consume messages from InQueue. > Expected Result: > MDB will resend messages from InQueue to OutQueue. > Attaching configuration and trace logs from test. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8397) Create test cases for Elytron Principal Transformers

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-8397?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-8397: ----------------------------------- Fix Version/s: 11.0.0.Alpha1 > Create test cases for Elytron Principal Transformers > ---------------------------------------------------- > > Key: WFLY-8397 > URL: https://issues.jboss.org/browse/WFLY-8397 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Ondrej Lukas > Assignee: Ondrej Lukas > Fix For: 11.0.0.Alpha1 > > > Create test cases for following Elytron Principal Transformers: > * constant-principal-transformer > * regex-principal-transformer > * regex-validating-principal-transformer > * chained-principal-transformer > Test case for aggregate-principal-transformer cannot developed due to WFCORE-2547. Once meaning of aggregate-principal-transformer will be revisited then appropriate test case will be added. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2570) Explain the meaning of maximum-session-cache-size and session-timeout default values.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2570?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFCORE-2570: ------------------------------------- Fix Version/s: 3.0.0.Beta11 > Explain the meaning of maximum-session-cache-size and session-timeout default values. > ------------------------------------------------------------------------------------- > > Key: WFCORE-2570 > URL: https://issues.jboss.org/browse/WFCORE-2570 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 3.0.0.Beta9 > Reporter: Ilia Vassilev > Assignee: Ilia Vassilev > Fix For: 3.0.0.Beta11 > > > The default values 0 of maximum-session-cache-size and session-timeout of Elytron will not override the JVM defaults. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2409) Review elytron kerberos-security-factory resource

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2409?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFCORE-2409: ------------------------------------- Fix Version/s: 3.0.0.Beta11 (was: 4.0.0.Alpha1) > Review elytron kerberos-security-factory resource > ------------------------------------------------- > > Key: WFCORE-2409 > URL: https://issues.jboss.org/browse/WFCORE-2409 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 3.0.0.Beta7 > Reporter: Martin Choma > Assignee: Darran Lofthouse > Priority: Critical > Labels: user_experience > Fix For: 3.0.0.Beta11 > > > * {{mechanism-oids}} > ** Minimal command for kerberos security factory creation is {code}/subsystem=elytron/kerberos-security-factory=kerberos:add(principal=mchoma, path=/path/to/keytab, mechanism-oids=[1.2.840.113554.1.2.2]){code} > ** I don't think it is user-friendly to require user to specify mechanism-oids. I think some reasonable default value should be used here. > * {{minimum-remaining-lifetime}} > ** please, specify units in documentation, e.g. seconds/minutes > * {{relative-to}} > ** as just path reference can be used here, probably should be just "expressions-allowed" => false > ** In legacy settings it is documented better: "The name of another previously named path, or of one of the standard paths provided by the system. If 'relative-to' is provided, the value of the 'path' attribute is treated as relative to the path specified by this attribute." > * {{server}} > ** I assume based on {{server}} attribute INITIATE_ONLY or ACCEPT_ONLY is configured on GSSCredential [1]. Wouldn't it be useful to have also possibility to set INITIATE_AND_ACCEPT? Couldn't that be useful for example in case of identity propagation. > * {{for-hosts}} > ** comparing to legacy security {{kerberosIdentityType}} I am missing for-hosts. Elytron won't provide such feature? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2399) Removing and re-adding alias to credential store leads to Duplicate resource failure

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2399?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFCORE-2399: ------------------------------------- Fix Version/s: 3.0.0.Beta11 > Removing and re-adding alias to credential store leads to Duplicate resource failure > ------------------------------------------------------------------------------------ > > Key: WFCORE-2399 > URL: https://issues.jboss.org/browse/WFCORE-2399 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Josef Cacek > Assignee: ehsavoie Hugonnet > Priority: Critical > Labels: credential-store > Fix For: 3.0.0.Beta11 > > > When an alias is removed from a credential store and added once more, the {{add}} operation fails with Duplicate resource message. > *Unignore tests* > When this issue is fixed, unignore (and fix if needed) related tests in {{testsuite/elytron/src/test/java/org/wildfly/test/integration/elytron/application/}}. Thanks. > {code} > git grep WFLY-8144 > {code} -- 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