March 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-952) Any events send to an AuditEndpoint after it is closed need to raise an error.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-952?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-952: --------------------------------- Fix Version/s: 1.1.0.Beta31 (was: 1.1.0.Beta30) > Any events send to an AuditEndpoint after it is closed need to raise an error. > ------------------------------------------------------------------------------ > > Key: ELY-952 > URL: https://issues.jboss.org/browse/ELY-952 > Project: WildFly Elytron > Issue Type: Bug > Components: Audit > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta31 > > > Presently events could be dropped. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-950) Add local audit log rotation

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-950?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-950: --------------------------------- Fix Version/s: 1.1.0.Beta31 (was: 1.1.0.Beta30) > Add local audit log rotation > ---------------------------- > > Key: ELY-950 > URL: https://issues.jboss.org/browse/ELY-950 > Project: WildFly Elytron > Issue Type: Task > Components: Audit > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta31 > > > Could be by time, size, rotate on start-up or a combination. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-949) Add a mechanism to assign priorities to audit events

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-949?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-949: --------------------------------- Fix Version/s: 1.1.0.Beta31 (was: 1.1.0.Beta30) > Add a mechanism to assign priorities to audit events > ---------------------------------------------------- > > Key: ELY-949 > URL: https://issues.jboss.org/browse/ELY-949 > Project: WildFly Elytron > Issue Type: Task > Components: Audit > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta31 > > > We probably want something like MatchRule but also need to think about how it will be configured. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1001) Release WildFly Elytron 1.1.0.Beta30

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1001?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse resolved ELY-1001. ----------------------------------- Resolution: Done > Release WildFly Elytron 1.1.0.Beta30 > ------------------------------------ > > Key: ELY-1001 > URL: https://issues.jboss.org/browse/ELY-1001 > Project: WildFly Elytron > Issue Type: Release > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta30 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2526) Domain mode passed unwanted sys props to spawned servers

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2526?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2526: ------------------------------------- Issue Type: Enhancement (was: Task) > Domain mode passed unwanted sys props to spawned servers > -------------------------------------------------------- > > Key: WFCORE-2526 > URL: https://issues.jboss.org/browse/WFCORE-2526 > Project: WildFly Core > Issue Type: Enhancement > Reporter: John Mazzitelli > > This is related to WFCORE-350, except the solution to that only involves filtering out some but not all unwanted sys props. > I would say the solution should involve any properties, not just jboss.server.xxx properties. > In my case, I'm trying to inject a javaagent into the host controller but I do NOT want the javaagent in the spawned servers. Because my javaagent uses JBoss Logging (JUL) I'm forced to pass in "-Djboss.modules.system.pkgs=org.jboss.byteman,org.jboss.logmanager" and > "-Djava.util.logging.manager=org.jboss.logmanager.LogManager" so the host controller can start up. > But these gets passed to the spawned servers and causes them to fail to boot up (because while my -javaagent command line argument isn't passed to their JVM, the -D sys props are and those combination of sys props are deadly without a JUL-enabled javaagent). > See: http://lists.jboss.org/pipermail/wildfly-dev/2017-March/005810.html -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2526) Domain mode passed unwanted sys props to spawned servers

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2526?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-2526: ------------------------------------------ I doubt we can just not pass through any properties as that would likely be a breaking change for lots of people. Passing properties to domain.sh is a simple way to parameterize a host/server set whose config is otherwise consistent across a set of machines. Perhaps an exclusion list in the jvm config would work. > Domain mode passed unwanted sys props to spawned servers > -------------------------------------------------------- > > Key: WFCORE-2526 > URL: https://issues.jboss.org/browse/WFCORE-2526 > Project: WildFly Core > Issue Type: Enhancement > Reporter: John Mazzitelli > > This is related to WFCORE-350, except the solution to that only involves filtering out some but not all unwanted sys props. > I would say the solution should involve any properties, not just jboss.server.xxx properties. > In my case, I'm trying to inject a javaagent into the host controller but I do NOT want the javaagent in the spawned servers. Because my javaagent uses JBoss Logging (JUL) I'm forced to pass in "-Djboss.modules.system.pkgs=org.jboss.byteman,org.jboss.logmanager" and > "-Djava.util.logging.manager=org.jboss.logmanager.LogManager" so the host controller can start up. > But these gets passed to the spawned servers and causes them to fail to boot up (because while my -javaagent command line argument isn't passed to their JVM, the -D sys props are and those combination of sys props are deadly without a JUL-enabled javaagent). > See: http://lists.jboss.org/pipermail/wildfly-dev/2017-March/005810.html -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2522) Upgrade to WildFly Elytron 1.1.0.Beta30

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2522?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFCORE-2522: ------------------------------------- Summary: Upgrade to WildFly Elytron 1.1.0.Beta30 (was: Upgrade to WildFly Elytron 1.1.0.Beta29) > Upgrade to WildFly Elytron 1.1.0.Beta30 > --------------------------------------- > > Key: WFCORE-2522 > URL: https://issues.jboss.org/browse/WFCORE-2522 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 3.0.0.Beta8 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1001) Release WildFly Elytron 1.1.0.Beta30

by Darran Lofthouse (JIRA)

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

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2527) There is wrong default *relative-to* path for CredentialStore, is set to folder from which we started EAP server.

by Hynek Švábek (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2527?page=com.atlassian.jira.plugi... ] Hynek Švábek updated WFCORE-2527: --------------------------------- Description: There is set wrong default *relative-to* path for CredentialStore. Default *relative-to* path is set to folder from which we started EAP server. e.g.: * cd EAP_FOLDER * ./bin/standalone.sh * relative-to is se to EAP_FOLDER or * cd EAP_FODER/bin * ./standalone.sh * relative-to is se to EAP_FOLDER/bin *How to reproduce* {code} /subsystem=elytron/credential-store=cs007:add(uri="cr-store://test/keystorecs007.jceks?create=true", credential-reference= {clear-text=pass123}) {code} {code} /subsystem=elytron/credential-store=cs007/alias=newCs007:add(secret-value=Elytron) {code} Now you can see in EAP_FOLDER (it can be different, see above) keystorecs007.jceks file. I would expect this file in data directory of server. was: There is set wrong default *relative-to* path for CredentialStore. Default *relative-to* path is set to folder from which we started EAP server. e.g.: * cd EAP_FOLDER * ./bin/standalone.sh * relative-to is se to EAP_FOLDER or * cd EAP_FODER/bin * ./standalone.sh * relative-to is se to EAP_FOLDER/bin *How to reproduce* {code} /subsystem=elytron/credential-store=cs007:add(uri="cr-store://test/folderNotExist/keystorecs007.jceks?create=true", credential-reference= {clear-text=pass123}) {code} {code} /subsystem=elytron/credential-store=cs007/alias=newCs007:add(secret-value=Elytron) {code} Now you can see in EAP_FOLDER/folderNotExist (it can be different, see above) keystorecs007.jceks file > There is wrong default *relative-to* path for CredentialStore, is set to folder from which we started EAP server. > ----------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-2527 > URL: https://issues.jboss.org/browse/WFCORE-2527 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Hynek Švábek > Assignee: Darran Lofthouse > Priority: Critical > > There is set wrong default *relative-to* path for CredentialStore. > Default *relative-to* path is set to folder from which we started EAP server. > e.g.: > * cd EAP_FOLDER > * ./bin/standalone.sh > * relative-to is se to EAP_FOLDER > or > * cd EAP_FODER/bin > * ./standalone.sh > * relative-to is se to EAP_FOLDER/bin > *How to reproduce* > {code} > /subsystem=elytron/credential-store=cs007:add(uri="cr-store://test/keystorecs007.jceks?create=true", credential-reference= {clear-text=pass123}) > {code} > {code} > /subsystem=elytron/credential-store=cs007/alias=newCs007:add(secret-value=Elytron) > {code} > Now you can see in EAP_FOLDER (it can be different, see above) keystorecs007.jceks file. > I would expect this file in data directory of server. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2513) Wildfly 10.1.0.Final does not start as a linux service

by mohammed hilout (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2513?page=com.atlassian.jira.plugi... ] mohammed hilout edited comment on WFCORE-2513 at 3/13/17 10:12 AM: ------------------------------------------------------------------- Hi [~ctomc], I added the wildfly as service with the command: chkconfig wildfly on --level 12356 but wildfly don't start on boot. I used the same command for Jboss 7.2.0 and it work fine. was (Author: hilout): Hi [~ctomc], I added the wildfly as service with the command: chkconfig wildfly on --level 12356 but wildfly don't start on boot. I user the same command for Jboss 7.2.0 and it work fine. > Wildfly 10.1.0.Final does not start as a linux service > ------------------------------------------------------ > > Key: WFCORE-2513 > URL: https://issues.jboss.org/browse/WFCORE-2513 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Affects Versions: 2.2.0.Final > Environment: Oracle Linux Server release 6.7, Oracle, Java 8 > Reporter: mohammed hilout > Assignee: Tomaz Cerar > > I follow this article to run WildFly as service: "http://developer-should-know.com/post/112230363742/how-to-install-wildfly..." > I can start / stop service, but wildfly don't run on boot -- 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