[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
[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
[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