February 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-3593) Intermittent failure in EarJBossDeploymentStructureTestCase in WF full

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3593?page=com.atlassian.jira.plugi... ] Stuart Douglas commented on WFCORE-3593: ---------------------------------------- https://ci.wildfly.org/viewLog.html?buildId=88149&buildTypeId=WFPR > Intermittent failure in EarJBossDeploymentStructureTestCase in WF full > ---------------------------------------------------------------------- > > Key: WFCORE-3593 > URL: https://issues.jboss.org/browse/WFCORE-3593 > Project: WildFly Core > Issue Type: Bug > Components: Server > Reporter: Stuart Douglas > Assignee: Stuart Douglas > > Even though the bug manifests in full the problem is in core. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9796) Update Eclipselink module to public

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-9796?page=com.atlassian.jira.plugin.... ] Kabir Khan commented on WFLY-9796: ---------------------------------- [~bmaxwell] [~bilge] > Update Eclipselink module to public > ----------------------------------- > > Key: WFLY-9796 > URL: https://issues.jboss.org/browse/WFLY-9796 > Project: WildFly > Issue Type: Task > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 12.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9796) Update Eclipselink module to public

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-9796?page=com.atlassian.jira.plugin.... ] Kabir Khan edited comment on WFLY-9796 at 2/11/18 3:09 PM: ----------------------------------------------------------- [~bmaxwell] [~bilge] Does this need wider discussion? was (Author: kabirkhan): [~bmaxwell] [~bilge] > Update Eclipselink module to public > ----------------------------------- > > Key: WFLY-9796 > URL: https://issues.jboss.org/browse/WFLY-9796 > Project: WildFly > Issue Type: Task > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 12.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3592) Expose external ServiceTarget to DUP processing

by Stuart Douglas (JIRA)

Stuart Douglas created WFCORE-3592: -------------------------------------- Summary: Expose external ServiceTarget to DUP processing Key: WFCORE-3592 URL: https://issues.jboss.org/browse/WFCORE-3592 Project: WildFly Core Issue Type: Enhancement Reporter: Stuart Douglas Assignee: Stuart Douglas This ServiceTarget can be used to install services outside the scope of a deployment, while still being monitored by the container state monitor. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9796) Update Eclipselink module to public

by Scott Marlow (JIRA)

Scott Marlow created WFLY-9796: ---------------------------------- Summary: Update Eclipselink module to public Key: WFLY-9796 URL: https://issues.jboss.org/browse/WFLY-9796 Project: WildFly Issue Type: Task Components: JPA / Hibernate Reporter: Scott Marlow Assignee: Scott Marlow Fix For: 12.0.0.Alpha1 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-377) The management API should provide a command to restart only all servers that are in state 'reload-required'

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-377?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-377: ------------------------------------ Fix Version/s: 4.0.0.Beta1 (was: 4.0.0.Alpha10) > The management API should provide a command to restart only all servers that are in state 'reload-required' > ----------------------------------------------------------------------------------------------------------- > > Key: WFCORE-377 > URL: https://issues.jboss.org/browse/WFCORE-377 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Wolf-Dieter Fink > Labels: cli, domain, domain-mode, management > Fix For: 4.0.0.Beta1 > > > After configuration changes via CLI batch it might be that different processes needs to be restarted. > It is possible to iterate over all servers and check it. > But I think it would be easier to have a command that restart all controllers and servers conditional to the 'relod required' state > - at domain level > - at host level > - at server level > command example : > :restart(ifRequired=true) > :reload(ifRequired=true) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-185) Api returns internal server error instead of not found for non-existing path

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-185?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-185: ------------------------------------ Fix Version/s: 4.0.0.Beta1 (was: 4.0.0.Alpha10) > Api returns internal server error instead of not found for non-existing path > ---------------------------------------------------------------------------- > > Key: WFCORE-185 > URL: https://issues.jboss.org/browse/WFCORE-185 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Heiko Rupp > Assignee: Brian Stansberry > Labels: domain-mode, rhq > Fix For: 4.0.0.Beta1 > > > When I try to e.g. /subsystem=foo:read-resource the api returns a 500 internal server error. > In http-land, the return code for "not found" is normally 404. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-482) Add log4j2 support for WildFly

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-482?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-482: ------------------------------------ Fix Version/s: 4.0.0.Beta1 (was: 4.0.0.Alpha10) > Add log4j2 support for WildFly > ------------------------------ > > Key: WFCORE-482 > URL: https://issues.jboss.org/browse/WFCORE-482 > Project: WildFly Core > Issue Type: Task > Components: Logging > Environment: Spring 3, Hibernate, Wicket, JBoss AS7 > Reporter: Amarkanth Ranganamayna > Assignee: James Perkins > Priority: Optional > Fix For: 4.0.0.Beta1 > > > I am trying to use Flume Appender which comes with Log4j2 (log4j 1.x doesn't support flume appender) (AND) inorder to acheive this, I am looking at how to configure JBoss AS7 to use log4j2. > Looks like Jboss AS7 by default use log4j 1.x > Are you guys already working on using log4j2 ? > If NOT, can you please suggest how to configure Jboss AS7 such that it picks up "log4j2.xml" file and doesn't use its own logging. > Thanks, > Amar -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-456) Add a content-stream attribute to the root deployment=* resources

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-456?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-456: ------------------------------------ Fix Version/s: 4.0.0.Beta1 (was: 4.0.0.Alpha10) > Add a content-stream attribute to the root deployment=* resources > ----------------------------------------------------------------- > > Key: WFCORE-456 > URL: https://issues.jboss.org/browse/WFCORE-456 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Brian Stansberry > Assignee: ehsavoie Hugonnet > Fix For: 4.0.0.Beta1 > > > Add a new attribute to the deployment resource that allows the user to get a stream with the deployment content attached to the response, a la what we do with the subsystem=logging/log-file=* resource's "stream" attribute. > The attribute must be configured as runtime-only and read-only. > The read handler that handles the attribute should only attach a stream if the following conditions are met, otherwise the value for the attribute should remain as 'undefined'. > 1) The resource's "content" attribute has only a single element in the list. (This is always the case today; adding a check for this is just future proofing) > 2) The first element in the "content" attribute list has a defined value in its "hash" field. (This confirms the content is stored in the content repo. We won't support serving unmanaged content as we have insufficient control over it.) > 3) The first element in the "content" attribute list has a 'true' as value of its "archive" field. (Current this will always be the case; this is future proofing for when we add support for exploded content in the content repo. Trying to assemble a stream from exploded content is currently out of scope for this feature.) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1649) RBAC constraint config modifications will fail in a mixed domain if the modified constraint is not present in the legacy slave

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1649?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1649: ------------------------------------- Fix Version/s: 4.0.0.Beta1 (was: 4.0.0.Alpha10) > RBAC constraint config modifications will fail in a mixed domain if the modified constraint is not present in the legacy slave > ------------------------------------------------------------------------------------------------------------------------------ > > Key: WFCORE-1649 > URL: https://issues.jboss.org/browse/WFCORE-1649 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Critical > Labels: domain-mode > Fix For: 4.0.0.Beta1 > > > The management model for RBAC constraints is maintained using synthetic resources, with resources only existing for those items (SensitivityClassification and ApplicationClassification) that are registered in the current process. Operations that touch classifications unknown to that process will fail due to missing resource problems. > This is a big problem in the following scenarios: > 1) Mixed domain, where legacy slaves do not know about newly introduced classifications. > 2) Slimming scenarios where slaves are ignoring unrelated parts of the domain wide config and also don't have some extension installed, resulting in classifications registered by those extensions not being present. > A partial workaround to 1) is for the kernel to register transformers for newly introduced classifications (e.g. SERVER_SSL added in EAP 6.4.7 and EAP 7). But: > -- that doesn't help with problem 2) > -- only the kernel can register kernel transformers, so if extensions add new classifications there is no way for them to register the transformer. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 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 February 2018