March 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1432) PersistentResourceXMLDescription#marshallAttributes does not marshall defined values if they match default values

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1432?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1432: ------------------------------------- Fix Version/s: 2.1.0.Final (was: 2.1.0.CR2) > PersistentResourceXMLDescription#marshallAttributes does not marshall defined values if they match default values > ----------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-1432 > URL: https://issues.jboss.org/browse/WFCORE-1432 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 2.1.0.CR1 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 2.1.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-1410) XNIO 3.3.5.Final

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1410?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFCORE-1410: ---------------------------------------- Fix Version/s: 2.1.0.Final Assignee: Stuart Douglas Resolution: Done > XNIO 3.3.5.Final > ---------------- > > Key: WFCORE-1410 > URL: https://issues.jboss.org/browse/WFCORE-1410 > Project: WildFly Core > Issue Type: Component Upgrade > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Fix For: 2.1.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-1406) CLI client freezes for undefined security realm

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1406?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1406: ------------------------------------- Fix Version/s: 2.1.0.Final (was: 2.1.0.CR2) > CLI client freezes for undefined security realm > ----------------------------------------------- > > Key: WFCORE-1406 > URL: https://issues.jboss.org/browse/WFCORE-1406 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 2.1.0.CR1 > Environment: Fedora 23, Ubuntu 14.04 > Reporter: Alexey Loubyansky > Assignee: Alexey Loubyansky > Priority: Blocker > Fix For: 2.1.0.Final > > > During work, CLI freezes randomly. See attached thread dump which was taken on Fedora 23. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-1418) Reloading host-controller via http-api puts the HC into unresponsive state

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1418?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1418: ------------------------------------- Fix Version/s: 2.1.0.Final (was: 2.1.0.CR2) > Reloading host-controller via http-api puts the HC into unresponsive state > -------------------------------------------------------------------------- > > Key: WFCORE-1418 > URL: https://issues.jboss.org/browse/WFCORE-1418 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 2.0.10.Final > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > Priority: Blocker > Fix For: 2.1.0.Final > > > Reloading host-controller via http-api puts the HC into unresponsive state. > *reproduce* > \- create an administrative user admin:asdasd@2 > \- start a domain > \- reload a server via http api > {noformat} > curl --digest -L -D - http://localhost:9990/management --header "Content-Type: application/json" -d '{"operation":"reload","name":"", "address":{"host" : "master"},"json.pretty":1}' -u admin:asdasd@2 > {noformat} > *actual* > Default server instances are stopped, HC is left in unresponsive state. > Keeping the domain alive, following message will appear in 5 minutes, domain will become responsive again after that. > {noformat} > [Host Controller] 04:47:23,966 ERROR [org.jboss.as.controller.management-operation] (management task-7) WFLYCTL0349: Timeout after [300] seconds waiting for service container stability while finalizing an operation. Process must be restarted. Step that first updated the service container was 'reload' at address '[("host" => "master")]' > {noformat} > *expected* > Domain is reloaded > *additional info* > The issue was introduced by fix for JBEAP-2751 - https://github.com/jbossas/wildfly-core-eap/commit/4986773a51fbf43ad911ae... > thread dump of unresponsive HC > http://pastebin.test.redhat.com/348732 > I am unable to reproduce locally, but issue can be easily reproduced on slower servers in MWQE lab. SSLMasterSlave*WayTestCase using reload via http-api cousing failures in domain modules of wf-core testsuite (e.g. [eap-7x-as-testsuite-test-core-rhel|https://url.corp.redhat.com/9f1f544] ) > Regression against 7.0.0.ER4. I was able to reproduce with the latest wildfly-core bits as well (1be598e) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-1394) default maxPermgen is added when jvm isn't configured

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1394?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1394: ------------------------------------- Fix Version/s: 2.1.0.Final (was: 2.1.0.CR2) > default maxPermgen is added when jvm isn't configured > ------------------------------------------------------ > > Key: WFCORE-1394 > URL: https://issues.jboss.org/browse/WFCORE-1394 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 2.1.0.CR1 > Reporter: Martin Simka > Assignee: Ken Wills > Fix For: 2.1.0.Final > > > Default maxPermgen size is added when {{jvm}} element isn't specified in domain.xml/host.xml and warning is logged. > {code:xml} > <server-group name="main-server-group" profile="default"> >  > <socket-binding-group ref="standard-sockets"/> > </server-group> > {code} > {noformat} > WFLYHC0011: Ignoring <permgen> for jvm 'SUN' type jvm: null > {noformat} > It happens because default is defined in [JvmElement.java#L76|https://github.com/wildfly/wildfly-core/blob/master/h...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-1369) Audit logging to TCP syslog is stopped after syslog restart

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1369?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1369: ------------------------------------- Fix Version/s: 2.1.0.Final (was: 2.1.0.CR2) > Audit logging to TCP syslog is stopped after syslog restart > ----------------------------------------------------------- > > Key: WFCORE-1369 > URL: https://issues.jboss.org/browse/WFCORE-1369 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 2.0.10.Final > Reporter: Ondrej Lukas > Assignee: James Perkins > Fix For: 2.1.0.Final > > > In case when audit logging to TCP syslog is enabled and syslog server is restarted then audit logging to syslog is stopped. UDP works correctly. It can be related to issue [1]. > [1] https://issues.jboss.org/browse/LOGMGR-123 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-1378) Forward port the version 1.8 management schema

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1378?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1378: ------------------------------------- Fix Version/s: 2.1.0.Final (was: 2.1.0.CR2) > Forward port the version 1.8 management schema > ---------------------------------------------- > > Key: WFCORE-1378 > URL: https://issues.jboss.org/browse/WFCORE-1378 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 2.1.0.Final > > > JBoss EAP 6 is introducing a new version 1.8 of the management schema, this task is to forward port it upstream. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-1390) upgrade PicketBox to 4.9.5.Final

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1390?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFCORE-1390: ---------------------------------------- Fix Version/s: 2.1.0.Final Assignee: Peter Skopek (was: Darran Lofthouse) Resolution: Done > upgrade PicketBox to 4.9.5.Final > -------------------------------- > > Key: WFCORE-1390 > URL: https://issues.jboss.org/browse/WFCORE-1390 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Security > Reporter: Peter Skopek > Assignee: Peter Skopek > Fix For: 2.1.0.Final > > > upgrade PicketLink to 4.9.5.Final due to: https://issues.jboss.org/browse/JBEAP-364 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-1404) Upgrade Undertow to 1.3.18.Final

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1404?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1404: ------------------------------------- Fix Version/s: 2.1.0.Final (was: 2.1.0.CR2) > Upgrade Undertow to 1.3.18.Final > -------------------------------- > > Key: WFCORE-1404 > URL: https://issues.jboss.org/browse/WFCORE-1404 > Project: WildFly Core > Issue Type: Component Upgrade > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Priority: Blocker > Fix For: 2.1.0.Final > > > Changelog https://issues.jboss.org/projects/UNDERTOW/versions/12329565 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-1365) Undertow 1.3.17.Final

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1365?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1365: ------------------------------------- Fix Version/s: 2.1.0.Final (was: 2.1.0.CR2) > Undertow 1.3.17.Final > --------------------- > > Key: WFCORE-1365 > URL: https://issues.jboss.org/browse/WFCORE-1365 > Project: WildFly Core > Issue Type: Component Upgrade > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Fix For: 2.1.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 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 2016