March 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-1003) GssApiServer missing ServerCredentialCallback to obtain GSSCredential

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1003?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse resolved ELY-1003. ----------------------------------- Resolution: Done > GssApiServer missing ServerCredentialCallback to obtain GSSCredential > --------------------------------------------------------------------- > > Key: ELY-1003 > URL: https://issues.jboss.org/browse/ELY-1003 > Project: WildFly Elytron > Issue Type: Enhancement > Components: SASL > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 1.1.0.Beta31 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1004) Release WildFly Elytron 1.1.0.Beta31

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-1004: ------------------------------------- Summary: Release WildFly Elytron 1.1.0.Beta31 Key: ELY-1004 URL: https://issues.jboss.org/browse/ELY-1004 Project: WildFly Elytron Issue Type: Release Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.1.0.Beta31 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-928) CLI is not terminated correctly with invalid address on HPUX

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-928?page=com.atlassian.jira.plugin... ] Jean-Francois Denise commented on WFCORE-928: --------------------------------------------- Hi [~mkopecky], I can see that this upstream bug is open but the JBEAP is closed. Do we still have the issue? If yes, how could I have access to an HPUX to investigate it? Thanks. > CLI is not terminated correctly with invalid address on HPUX > ------------------------------------------------------------ > > Key: WFCORE-928 > URL: https://issues.jboss.org/browse/WFCORE-928 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 2.0.0.Beta4 > Reporter: Marek Kopecký > Assignee: Jean-Francois Denise > Priority: Minor > > *Description of problem:* > CLI is not terminated correctly with invalid address on HPUX. > *How reproducible:* > Always on HPUX > *Steps to Reproduce:* > # ./jboss-cli.sh -c --controller=nonsence > *Actual results:* > CLI is terminated after input on stdin. > *Expected results:* > CLI is terminated correctly. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-695) OutOfMemoryErrors when adding large deployment with audit logging enabled

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-695?page=com.atlassian.jira.plugin... ] Jean-Francois Denise commented on WFCORE-695: --------------------------------------------- The command "deployment deploy-file ..." that will come in CLI.next supports streams in batch mode. As a matter of fact legacy bridge for command deploy ... supports it too. > OutOfMemoryErrors when adding large deployment with audit logging enabled > ------------------------------------------------------------------------- > > Key: WFCORE-695 > URL: https://issues.jboss.org/browse/WFCORE-695 > Project: WildFly Core > Issue Type: Bug > Components: CLI, Domain Management > Affects Versions: 1.0.0.CR4 > Reporter: James Livingston > Assignee: Jean-Francois Denise > > When performing a deployment operation, audit logging will include the deployment content in the audit record (serialised as text). Since JsonAuditLogItemFormatter.createRecordText() creates the string in memory, large deployment will lead to an OutOfMemoryError such as > java.lang.OutOfMemoryError: Java heap space > at java.util.Arrays.copyOf(Arrays.java:2367) [rt.jar:1.7.0_71] > at java.lang.AbstractStringBuilder.expandCapacity(AbstractStringBuilder.java:130) [rt.jar:1.7.0_71] > at java.lang.AbstractStringBuilder.ensureCapacityInternal(AbstractStringBuilder.java:114) [rt.jar:1.7.0_71] > at java.lang.AbstractStringBuilder.appendCodePoint(AbstractStringBuilder.java:730) [rt.jar:1.7.0_71] > at java.lang.StringBuilder.appendCodePoint(StringBuilder.java:242) [rt.jar:1.7.0_71] > at org.jboss.dmr.ModelValue.jsonEscape(ModelValue.java:212) [jboss-dmr-1.2.0.Final-redhat-1.jar:1.2.0.Final-redhat-1] > at org.jboss.dmr.BytesModelValue.formatAsJSON(BytesModelValue.java:144) [jboss-dmr-1.2.0.Final-redhat-1.jar:1.2.0.Final-redhat-1] > at org.jboss.dmr.ModelNode.formatAsJSON(ModelNode.java:1520) [jboss-dmr-1.2.0.Final-redhat-1.jar:1.2.0.Final-redhat-1] > at org.jboss.dmr.ObjectModelValue.formatAsJSON(ObjectModelValue.java:247) [jboss-dmr-1.2.0.Final-redhat-1.jar:1.2.0.Final-redhat-1] > at org.jboss.dmr.ModelNode.formatAsJSON(ModelNode.java:1520) [jboss-dmr-1.2.0.Final-redhat-1.jar:1.2.0.Final-redhat-1] > at org.jboss.dmr.ListModelValue.formatAsJSON(ListModelValue.java:251) [jboss-dmr-1.2.0.Final-redhat-1.jar:1.2.0.Final-redhat-1] > at org.jboss.dmr.ModelNode.formatAsJSON(ModelNode.java:1520) [jboss-dmr-1.2.0.Final-redhat-1.jar:1.2.0.Final-redhat-1] > at org.jboss.dmr.ObjectModelValue.formatAsJSON(ObjectModelValue.java:247) [jboss-dmr-1.2.0.Final-redhat-1.jar:1.2.0.Final-redhat-1] > at org.jboss.dmr.ModelNode.formatAsJSON(ModelNode.java:1520) [jboss-dmr-1.2.0.Final-redhat-1.jar:1.2.0.Final-redhat-1] > at org.jboss.dmr.ListModelValue.formatAsJSON(ListModelValue.java:251) [jboss-dmr-1.2.0.Final-redhat-1.jar:1.2.0.Final-redhat-1] > at org.jboss.dmr.ModelNode.formatAsJSON(ModelNode.java:1520) [jboss-dmr-1.2.0.Final-redhat-1.jar:1.2.0.Final-redhat-1] > at org.jboss.dmr.ObjectModelValue.formatAsJSON(ObjectModelValue.java:247) [jboss-dmr-1.2.0.Final-redhat-1.jar:1.2.0.Final-redhat-1] > at org.jboss.dmr.ModelNode.formatAsJSON(ModelNode.java:1520) [jboss-dmr-1.2.0.Final-redhat-1.jar:1.2.0.Final-redhat-1] > at org.jboss.dmr.ListModelValue.formatAsJSON(ListModelValue.java:251) [jboss-dmr-1.2.0.Final-redhat-1.jar:1.2.0.Final-redhat-1] > at org.jboss.dmr.ModelNode.formatAsJSON(ModelNode.java:1520) [jboss-dmr-1.2.0.Final-redhat-1.jar:1.2.0.Final-redhat-1] > at org.jboss.dmr.ObjectModelValue.formatAsJSON(ObjectModelValue.java:247) [jboss-dmr-1.2.0.Final-redhat-1.jar:1.2.0.Final-redhat-1] > at org.jboss.dmr.ModelValue.writeJSONString(ModelValue.java:351) [jboss-dmr-1.2.0.Final-redhat-1.jar:1.2.0.Final-redhat-1] > at org.jboss.dmr.ModelValue.toJSONString(ModelValue.java:340) [jboss-dmr-1.2.0.Final-redhat-1.jar:1.2.0.Final-redhat-1] > at org.jboss.dmr.ModelNode.toJSONString(ModelNode.java:1350) [jboss-dmr-1.2.0.Final-redhat-1.jar:1.2.0.Final-redhat-1] > at org.jboss.as.controller.audit.JsonAuditLogItemFormatter.createRecordText(JsonAuditLogItemFormatter.java:135) [jboss-as-controller-7.4.2.Final-redhat-2.jar:7.4.2.Final-redhat-2] > A work-around is increasing the controller heap size, but it would be good if that was not required. If including the deployment content in the record is desired, perhaps there is a way to make it stream the record rather than building the entire string in memory at once. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2463) Configuring more password types should be allowed for Elytron filesystem-realm identity in management model

by Pedro Igor (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2463?page=com.atlassian.jira.plugi... ] Pedro Igor reassigned WFCORE-2463: ---------------------------------- Assignee: Pedro Igor (was: Darran Lofthouse) > Configuring more password types should be allowed for Elytron filesystem-realm identity in management model > ----------------------------------------------------------------------------------------------------------- > > Key: WFCORE-2463 > URL: https://issues.jboss.org/browse/WFCORE-2463 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 3.0.0.Beta7 > Reporter: Ondrej Lukas > Assignee: Pedro Igor > Labels: user_experience > > In case when two password type are part of {{set-password}} operation for identity of Elytron filesystem-realm then only first of them is used and others are discarded. Configuring multiple credentials for one identity should be supported [1]. > [1] https://issues.jboss.org/browse/WFLY-7584?focusedCommentId=13322919&page=... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-55) CFME Tests: Adjust environment and smoke tests to JMAN4-111

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-55?page=com.atlassian.jira.plu... ] Hayk Hovsepyan commented on HAWKULARQE-55: ------------------------------------------ PR sent to fix failing tests https://github.com/ManageIQ/integration_tests/pull/4370 > CFME Tests: Adjust environment and smoke tests to JMAN4-111 > ----------------------------------------------------------- > > Key: HAWKULARQE-55 > URL: https://issues.jboss.org/browse/HAWKULARQE-55 > Project: Hawkular QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Blocker > > Once [JMAN4-111|https://issues.jboss.org/browse/JMAN4-111] feature is done, EAP servers on Containers will become immutable, but our CFME Testing environment runs on Containers. > * switch EAP7 Containers to VMs > * and for container EAP7 make smoke tests -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8359) Upgrade jboss-javaee-spec to 1.1.0.Final

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-8359?page=com.atlassian.jira.plugin.... ] Tomaz Cerar deleted WFLY-8359: ------------------------------ > Upgrade jboss-javaee-spec to 1.1.0.Final > ---------------------------------------- > > Key: WFLY-8359 > URL: https://issues.jboss.org/browse/WFLY-8359 > Project: WildFly > Issue Type: Task > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8360) Upgrade jboss-javaee-spec to 1.1.0.Final

by Tomaz Cerar (JIRA)

Tomaz Cerar created WFLY-8360: --------------------------------- Summary: Upgrade jboss-javaee-spec to 1.1.0.Final Key: WFLY-8360 URL: https://issues.jboss.org/browse/WFLY-8360 Project: WildFly Issue Type: Task Components: Build System Reporter: Tomaz Cerar Assignee: Tomaz Cerar -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8359) Upgrade jboss-javaee-spec to 1.1.0.Final

by Tomaz Cerar (JIRA)

Tomaz Cerar created WFLY-8359: --------------------------------- Summary: Upgrade jboss-javaee-spec to 1.1.0.Final Key: WFLY-8359 URL: https://issues.jboss.org/browse/WFLY-8359 Project: WildFly Issue Type: Task Components: Build System Reporter: Tomaz Cerar Assignee: Tomaz Cerar -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-36) IPV6

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-36?page=com.atlassian.jira.plu... ] Hayk Hovsepyan commented on HAWKULARQE-36: ------------------------------------------ IPv6 is not supported in 4.5 version. Foreman Hostgroups "Hawkular/Cassandra node" and "Hawkular/Services" are modified to support IPv6 network installation. > IPV6 > ---- > > Key: HAWKULARQE-36 > URL: https://issues.jboss.org/browse/HAWKULARQE-36 > Project: Hawkular QE > Issue Type: Task > Reporter: Matt Mahoney > Assignee: Hayk Hovsepyan > > See: [HAWKULAR-1193|https://issues.jboss.org/browse/HAWKULAR-1193] > Create IPv6 testing environment and run smoke tests on it. > Automate via jenkins job running CFME smoke tests. -- 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