[JBoss JIRA] (WFCORE-3210) Wildfly module isolation not working consistently
by Nuno Godinho de Matos (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3210?page=com.atlassian.jira.plugi... ]
Nuno Godinho de Matos edited comment on WFCORE-3210 at 8/31/17 5:14 AM:
------------------------------------------------------------------------
Hi James,
I would like to share with you the following google drive reference:
[#https://drive.google.com/drive/folders/0B_dEiNBGUsxqRW1oQkg2LXUyZms?usp=sharing]
In this driver folder you will have two artifacts.
01_wildfly_module_company.zip
02_standalone-WFCORE3210.zip
The first zip file contains a wildfly module, text logs from me switching around starting a wildfly domain via script and via eclipse. And illustrating that when i do the switch between how I startup wildfly the issue with class loading sneaks in. then when I keep starting wildfly with the same apporach either batch file or eclipse the issue stops manifesting.
This module is identical to what you have on a previous entry on this jira.
The difference is that the module stops referring to the Appenders jar file and just holds the pure log4j implementation and the JulToLog4j1 router jar code.
You also have the source code for the router jar in there, in case it may help you.
To install this module, go to you WILDFLY_HOME/modules/ and simply dump the module in there.
You should have in your file system a path of the form:
C:\dev\appserver\wildfly\wildfly-10.1.0.Final\modules\company\logginglog4j1\main
The second artifact is a domain.
On this domain you have an additional bin/ folder with scripts that you can use to start the wildfly domain.
Just make sure that when you copy the domain, you do not put it in WILDFLY_HOME.
Instead you need to make a deeper folder hierarchy as illustrated by this path:
C:\dev\appserver\wildfly\wildfly-10.1.0.Final\user_projects\domains\standalone-WFCORE3210
In the link above, the path part:
C:\dev\appserver\wildfly\wildfly-10.1.0.Final would be a match to your WILDFLY_HOME env var.
That is it!
On my environment:
- Windows 7.
- jdk 8 update144
The phenomena I experience is that normally, when I start the domain for a first time with an approach A.
The starting up has problems with the logging classes.
When I stop the domain and keep using the approach A to start the domain I am fine and the:
C:\dev\appserver\wildfly\wildfly-10.1.0.Final\user_projects\domains\standalone-WFCORE3210\log
WFCORE3210_rollingFileAppender.log
Is getting pumped up with all the application server events.
Which is the ideal thing.
Then, If I swtich my startup approach form A to B, e.g. from bat to eclpse.
The issue manifests once, and then I am fine again.
Last note.
You will want to fix the file:
C:\dev\appserver\wildfly\wildfly-10.1.0.Final\user_projects\domains\standalone-WFCORE3210\configuration\log4jwildfly.properties
The rolling file appender configured in there has a destination directory that is ok for my folder structure, but which will not be ok for your folder structure, since I doubt you are either using widows or putting your wildfly home where I put mine.
Many thanks for your help,
I hope this package allows you to reproduce the issue,
Kindest regards.
was (Author: nuno.godinhomatos):
Hi James,
I would like to share with you the following google drive reference:
[#https://drive.google.com/drive/folders/0B_dEiNBGUsxqRW1oQkg2LXUyZms?usp=sharing]
In this driver folder you will have two artifacts.
01_wildfly_module_company.zip
02_standalone-WFCORE3210.zip
The first zip file contains a wildfly module, text logs from me switching around starting a wildfly domain via script and via eclipse. And illustrating that when i do the switch between how I startup wildfly the issue with class loading sneaks in. then when I keep starting wildfly with the same apporach either batch file or eclipse the issue stops manifesting.
This module is identical to what you have on a previous entry on this jira.
The difference is that the module stops referring to the Appenders jar file and just holds the pure log4j implementation and the router module.
You also have the source code for the router module in there.
To install this module, go to you WILDFLY_HOME/modules/ and simply dump the module in there.
You should have in your file system a path of the form:
C:\dev\appserver\wildfly\wildfly-10.1.0.Final\modules\company\logginglog4j1\main
The second artifact is a domain.
On this domain you have an additional bin/ folder with scripts that you can use to start the wildfly domain.
Just make sure that when you copy the doman, you do not put it in WILDFLY_HOME.
Instead you need to make a deeper folder hiearchy as illustrated by this path:
C:\dev\appserver\wildfly\wildfly-10.1.0.Final\user_projects\domains\standalone-WFCORE3210
That is it.
On my environment: Windows 7.
The phenomena I experience is that normally, when I start the domain for a first time with an approach A.
The starting up has problems with the logging classes.
When I stop the domain and keep using the approach A to start the domain I am fine and the:
C:\dev\appserver\wildfly\wildfly-10.1.0.Final\user_projects\domains\standalone-WFCORE3210\log
WFCORE3210_rollingFileAppender.log
Is getting pumped up with all the application server events.
Which is the ideal thing.
Then, If I swtich my startup approach form A to B, e.g. from bat to eclpse.
The issue manifests once, and then I am fine again.
Last note.
You will want to fix the file:
C:\dev\appserver\wildfly\wildfly-10.1.0.Final\user_projects\domains\standalone-WFCORE3210\configuration\log4jwildfly.properties
The rolling file appender configured in there has a destination directory that is ok for my folder structure, but which will not be ok for your folder structure, since I doubt you are either using widows or putting your wildfly home where I put mine.
Many thanks for your help,
I hope this package allows you to reproduce the issue,
Kindest regards.
> Wildfly module isolation not working consistently
> -------------------------------------------------
>
> Key: WFCORE-3210
> URL: https://issues.jboss.org/browse/WFCORE-3210
> Project: WildFly Core
> Issue Type: Bug
> Components: Logging, Modules
> Affects Versions: 2.2.0.Final
> Reporter: Nuno Godinho de Matos
>
> There is an underministic bug on the module layer of wildfly, whereby the boot logic of the application server is not ensured to give the appropriate module isolation - which can lead to unexpected boot classpath problems.
> An example of this phenomena is given on the wildfly forum thread:
> https://developer.jboss.org/thread/275839
> In this example, we have the logging subsystem setup to use a custome handler.
> The custom handler wishes to have acces to the JUL extension classes on the org.jboss.logmanger module, but wishes to do have no relationship with the org.apache.log4j packages associated to the wildfly org.jboss.log4j module.
> What we see in this example is that an application gets from wildfly mixed behavior.
> Most of the time, during boot, the processes works without problem, where the custom handler runs isolated from the undersired log4j libraries within wildfly.
> But other times the application boot procedure will not go smoothly with the custom handler having processes routing JUL LogRecords events into the bundled log4j because the application server has loaded some of the classes that exist the org.jboss.log4j module.
> And as we know when the same class is loaded by different class loaders, then that class that orinates from class loader A cannot be assigned to the corresponding class of class loader B, even if the classes are exactly the same.
> This is not an isolated issue.
> There are also open issues on the wildfly forum reporting on startup problems on the logging subsystme where sometimes the LogManager class had not yet been loaded, and sometimes this issue goes away.
> This is an indication of some deep issue engrained into the module loading, where the module isolation behavior is not ensured to work all the time and that the boot procedure is not deterministically reliable.
> It should not be that the application server some time starts successfully and others not.
> Booting wildfly should always result in the same outcode.
> Problems of this nature with class loading problems should either always happen if the configuration is not done properly or never happen if the configuration is proper.
> In the case of thread:
> https://developer.jboss.org/thread/275839
> Our belief is that the configuration is doing all it possible can to request the necessary module isolation from base packages and the outcome where log4j class load problems take place should never be allowed to happen.
> Many thanks.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 8 months
[JBoss JIRA] (WFCORE-3210) Wildfly module isolation not working consistently
by Nuno Godinho de Matos (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3210?page=com.atlassian.jira.plugi... ]
Nuno Godinho de Matos commented on WFCORE-3210:
-----------------------------------------------
Hi James,
I would like to share with you the following google drive reference:
[#https://drive.google.com/drive/folders/0B_dEiNBGUsxqRW1oQkg2LXUyZms?usp=sharing]
In this driver folder you will have two artifacts.
01_wildfly_module_company.zip
02_standalone-WFCORE3210.zip
The first zip file contains a wildfly module, text logs from me switching around starting a wildfly domain via script and via eclipse. And illustrating that when i do the switch between how I startup wildfly the issue with class loading sneaks in. then when I keep starting wildfly with the same apporach either batch file or eclipse the issue stops manifesting.
This module is identical to what you have on a previous entry on this jira.
The difference is that the module stops referring to the Appenders jar file and just holds the pure log4j implementation and the router module.
You also have the source code for the router module in there.
To install this module, go to you WILDFLY_HOME/modules/ and simply dump the module in there.
You should have in your file system a path of the form:
C:\dev\appserver\wildfly\wildfly-10.1.0.Final\modules\company\logginglog4j1\main
The second artifact is a domain.
On this domain you have an additional bin/ folder with scripts that you can use to start the wildfly domain.
Just make sure that when you copy the doman, you do not put it in WILDFLY_HOME.
Instead you need to make a deeper folder hiearchy as illustrated by this path:
C:\dev\appserver\wildfly\wildfly-10.1.0.Final\user_projects\domains\standalone-WFCORE3210
That is it.
On my environment: Windows 7.
The phenomena I experience is that normally, when I start the domain for a first time with an approach A.
The starting up has problems with the logging classes.
When I stop the domain and keep using the approach A to start the domain I am fine and the:
C:\dev\appserver\wildfly\wildfly-10.1.0.Final\user_projects\domains\standalone-WFCORE3210\log
WFCORE3210_rollingFileAppender.log
Is getting pumped up with all the application server events.
Which is the ideal thing.
Then, If I swtich my startup approach form A to B, e.g. from bat to eclpse.
The issue manifests once, and then I am fine again.
Last note.
You will want to fix the file:
C:\dev\appserver\wildfly\wildfly-10.1.0.Final\user_projects\domains\standalone-WFCORE3210\configuration\log4jwildfly.properties
The rolling file appender configured in there has a destination directory that is ok for my folder structure, but which will not be ok for your folder structure, since I doubt you are either using widows or putting your wildfly home where I put mine.
Many thanks for your help,
I hope this package allows you to reproduce the issue,
Kindest regards.
> Wildfly module isolation not working consistently
> -------------------------------------------------
>
> Key: WFCORE-3210
> URL: https://issues.jboss.org/browse/WFCORE-3210
> Project: WildFly Core
> Issue Type: Bug
> Components: Logging, Modules
> Affects Versions: 2.2.0.Final
> Reporter: Nuno Godinho de Matos
>
> There is an underministic bug on the module layer of wildfly, whereby the boot logic of the application server is not ensured to give the appropriate module isolation - which can lead to unexpected boot classpath problems.
> An example of this phenomena is given on the wildfly forum thread:
> https://developer.jboss.org/thread/275839
> In this example, we have the logging subsystem setup to use a custome handler.
> The custom handler wishes to have acces to the JUL extension classes on the org.jboss.logmanger module, but wishes to do have no relationship with the org.apache.log4j packages associated to the wildfly org.jboss.log4j module.
> What we see in this example is that an application gets from wildfly mixed behavior.
> Most of the time, during boot, the processes works without problem, where the custom handler runs isolated from the undersired log4j libraries within wildfly.
> But other times the application boot procedure will not go smoothly with the custom handler having processes routing JUL LogRecords events into the bundled log4j because the application server has loaded some of the classes that exist the org.jboss.log4j module.
> And as we know when the same class is loaded by different class loaders, then that class that orinates from class loader A cannot be assigned to the corresponding class of class loader B, even if the classes are exactly the same.
> This is not an isolated issue.
> There are also open issues on the wildfly forum reporting on startup problems on the logging subsystme where sometimes the LogManager class had not yet been loaded, and sometimes this issue goes away.
> This is an indication of some deep issue engrained into the module loading, where the module isolation behavior is not ensured to work all the time and that the boot procedure is not deterministically reliable.
> It should not be that the application server some time starts successfully and others not.
> Booting wildfly should always result in the same outcode.
> Problems of this nature with class loading problems should either always happen if the configuration is not done properly or never happen if the configuration is proper.
> In the case of thread:
> https://developer.jboss.org/thread/275839
> Our belief is that the configuration is doing all it possible can to request the necessary module isolation from base packages and the outcome where log4j class load problems take place should never be allowed to happen.
> Many thanks.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 8 months
[JBoss JIRA] (ELY-1350) Wildfly Elytron Tool, Powershell script elytron-tool.ps1 doesn't work with custom credential store implementation.
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/ELY-1350?page=com.atlassian.jira.plugin.s... ]
Tomaz Cerar commented on ELY-1350:
----------------------------------
btw, you don't need the extensive syntax [Environment]::SetEnvironmentVariable.... for setting env variables that one is only useful for setting them permanently (with optional 3rd parameter)
for script use best is to just use
{{$env:ELYTRON_TOOL_ADDONS="C:\custom.jar"}}
it does the same.
> Wildfly Elytron Tool, Powershell script elytron-tool.ps1 doesn't work with custom credential store implementation.
> ------------------------------------------------------------------------------------------------------------------
>
> Key: ELY-1350
> URL: https://issues.jboss.org/browse/ELY-1350
> Project: WildFly Elytron
> Issue Type: Bug
> Reporter: Hynek Švábek
> Assignee: Darran Lofthouse
>
> Powershell script elytron-tool.ps1 doesn't work with custom credential store implementation.
> There is problem with getting value of environment variable ELYTRON_TOOL_ADDONS.
> *How to reproduce:*
> * run powershell and set work directory JBOSS_HOME/bin
> * set env variable for custom credential store implementation jar like this:
> {code}
> [Environment]::SetEnvironmentVariable("ELYTRON_TOOL_ADDONS", "C:\custom.jar", "
> Process")
> {code}
> * run this command
> {code}
> PowerShell -ExecutionPolicy Bypass -File elytron-tool.ps1 credential-store --add secret_alias --password pass123 --create -x secret_password -l 001.jceks --type CustomTestCredentialStore --debug
> Exception encountered executing the command:
> java.security.NoSuchAlgorithmException
> at org.wildfly.security.credential.store.CredentialStore.getInstance(CredentialStore.java:80)
> at
> org.wildfly.security.tool.CredentialStoreCommand.execute(CredentialStoreCommand.java:188
> at org.wildfly.security.tool.ElytronTool.main(ElytronTool.java:81)
> {code}
> *Suggestion to improve:*
> For me works one of these changes in elytron-tool.ps1 script
> # if (Test-Path env:ELYTRON_TOOL_ADDONS) { $ELYTRON_TOOL_ADDONS=(Get-ChildItem Env:ELYTRON_TOOL_ADDONS).value }
> # $ELYTRON_TOOL_ADDONS=$env:ELYTRON_TOOL_ADDONS
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 8 months
[JBoss JIRA] (WFCORE-3210) Wildfly module isolation not working consistently
by Nuno Godinho de Matos (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3210?page=com.atlassian.jira.plugi... ]
Nuno Godinho de Matos edited comment on WFCORE-3210 at 8/31/17 4:57 AM:
------------------------------------------------------------------------
Understood.
I Hope it is now clear what we want to achieve.
I would also mention that on the topic of what we are trying to achieve, there is a reference to an online blog entry where a person has done exactly the same thing that we want to do here except the JUL logging is routed to Log4j2... This reference was added on the Wildfly forum discussion, where I initially asked for help on how to achieve this goal but using log4j1.
As for Stack traces.
There are none. Otherwise they would have naturally been added to the issue - as well as on the Wildfly Forum - where I originally started a discussion on trying to understand how to resolve this problem.
There are no stack traces because you have at logging Level something exploding, and the logging Implantation log4j1 is handling this log explosion situation by doing a STDERR println to report on the issue encountered with the class loader.
As for the Module configuration.
Yes, the module configuration looks like a patch work indeed.
And yes, some of the comments are a bit out dated - because I did make several experiments, including trying to not bundle log4j1.17 and trying to use the org.jboss.log4j instead - which yielded me the infinite recursive logging issue.
The reason why the module looks this complicated is none-other then the result of multiple Experiments to try to ultimately ban org jboss log4j classes from sneaking into this handler module. That is why you also see all of those excludes with wild card paths...
You can be certain, I did not start by writing a module as complicated looking as you see in the reference panel. That is where i ended up.
Thanks.
was (Author: nuno.godinhomatos):
Understood.
I Hope it is now clear what we want to achieve.
I would also mention that on the topic of what we are trying to achieve, there is a reference to an online blog entry where a person has done exactly the same thing that we want to do here except the JUL logging is routed to Log4j2...
As for Stack traces.
There are none. Otherwise they would have naturally been added to the issue - as well as on the Wildfly Forum - where I originally started a discussion on trying to understand how to resolve this problem.
There are no stack traces because you have at logging Level something exploding, and the logging Implantation log4j1 is handling this log explosion situation by doing a STDERR println to report on the issue encountered with the class loader.
As for the Module configuration.
Yes, the module configuration looks like a patch work indeed.
And yes, some of the comments are a bit out dated - because I did make several experiments, including trying to not bundle log4j1.17 and trying to use the org.jboss.log4j instead - which yielded me the infinite recursive logging issue.
The reason why the module looks this complicated is none-other then the result of multiple Experiments to try to ultimately ban org jboss log4j classes from sneaking into this handler module. That is why you also see all of those excludes with wild card paths...
You can be certain, I did not start by writing a module as complicated looking as you see in the reference panel. That is where i ended up.
Thanks.
> Wildfly module isolation not working consistently
> -------------------------------------------------
>
> Key: WFCORE-3210
> URL: https://issues.jboss.org/browse/WFCORE-3210
> Project: WildFly Core
> Issue Type: Bug
> Components: Logging, Modules
> Affects Versions: 2.2.0.Final
> Reporter: Nuno Godinho de Matos
>
> There is an underministic bug on the module layer of wildfly, whereby the boot logic of the application server is not ensured to give the appropriate module isolation - which can lead to unexpected boot classpath problems.
> An example of this phenomena is given on the wildfly forum thread:
> https://developer.jboss.org/thread/275839
> In this example, we have the logging subsystem setup to use a custome handler.
> The custom handler wishes to have acces to the JUL extension classes on the org.jboss.logmanger module, but wishes to do have no relationship with the org.apache.log4j packages associated to the wildfly org.jboss.log4j module.
> What we see in this example is that an application gets from wildfly mixed behavior.
> Most of the time, during boot, the processes works without problem, where the custom handler runs isolated from the undersired log4j libraries within wildfly.
> But other times the application boot procedure will not go smoothly with the custom handler having processes routing JUL LogRecords events into the bundled log4j because the application server has loaded some of the classes that exist the org.jboss.log4j module.
> And as we know when the same class is loaded by different class loaders, then that class that orinates from class loader A cannot be assigned to the corresponding class of class loader B, even if the classes are exactly the same.
> This is not an isolated issue.
> There are also open issues on the wildfly forum reporting on startup problems on the logging subsystme where sometimes the LogManager class had not yet been loaded, and sometimes this issue goes away.
> This is an indication of some deep issue engrained into the module loading, where the module isolation behavior is not ensured to work all the time and that the boot procedure is not deterministically reliable.
> It should not be that the application server some time starts successfully and others not.
> Booting wildfly should always result in the same outcode.
> Problems of this nature with class loading problems should either always happen if the configuration is not done properly or never happen if the configuration is proper.
> In the case of thread:
> https://developer.jboss.org/thread/275839
> Our belief is that the configuration is doing all it possible can to request the necessary module isolation from base packages and the outcome where log4j class load problems take place should never be allowed to happen.
> Many thanks.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 8 months
[JBoss JIRA] (WFCORE-3210) Wildfly module isolation not working consistently
by Nuno Godinho de Matos (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3210?page=com.atlassian.jira.plugi... ]
Nuno Godinho de Matos edited comment on WFCORE-3210 at 8/31/17 4:56 AM:
------------------------------------------------------------------------
Understood.
I Hope it is now clear what we want to achieve.
I would also mention that on the topic of what we are trying to achieve, there is a reference to an online blog entry where a person has done exactly the same thing that we want to do here except the JUL logging is routed to Log4j2...
As for Stack traces.
There are none. Otherwise they would have naturally been added to the issue - as well as on the Wildfly Forum - where I originally started a discussion on trying to understand how to resolve this problem.
There are no stack traces because you have at logging Level something exploding, and the logging Implantation log4j1 is handling this log explosion situation by doing a STDERR println to report on the issue encountered with the class loader.
As for the Module configuration.
Yes, the module configuration looks like a patch work indeed.
And yes, some of the comments are a bit out dated - because I did make several experiments, including trying to not bundle log4j1.17 and trying to use the org.jboss.log4j instead - which yielded me the infinite recursive logging issue.
The reason why the module looks this complicated is none-other then the result of multiple Experiments to try to ultimately ban org jboss log4j classes from sneaking into this handler module. That is why you also see all of those excludes with wild card paths...
You can be certain, I did not start by writing a module as complicated looking as you see in the reference panel. That is where i ended up.
Thanks.
was (Author: nuno.godinhomatos):
Understood.
Nur now i Hope it is clear what we want to achieve.
Das for Stack traced there are none.
Because you have at logging Level something exploding and the logging Implantation seems to Default to Log to Standard Error the Problem.
As for the Module configuration.
It Looks complucated as a result of multiple Experiments to try to ban org jboss log4j from sneaking in.
I for sure die Not star With a Module Kopplung linke a Patch Work. That is where i ended up.
Thanks.
> Wildfly module isolation not working consistently
> -------------------------------------------------
>
> Key: WFCORE-3210
> URL: https://issues.jboss.org/browse/WFCORE-3210
> Project: WildFly Core
> Issue Type: Bug
> Components: Logging, Modules
> Affects Versions: 2.2.0.Final
> Reporter: Nuno Godinho de Matos
>
> There is an underministic bug on the module layer of wildfly, whereby the boot logic of the application server is not ensured to give the appropriate module isolation - which can lead to unexpected boot classpath problems.
> An example of this phenomena is given on the wildfly forum thread:
> https://developer.jboss.org/thread/275839
> In this example, we have the logging subsystem setup to use a custome handler.
> The custom handler wishes to have acces to the JUL extension classes on the org.jboss.logmanger module, but wishes to do have no relationship with the org.apache.log4j packages associated to the wildfly org.jboss.log4j module.
> What we see in this example is that an application gets from wildfly mixed behavior.
> Most of the time, during boot, the processes works without problem, where the custom handler runs isolated from the undersired log4j libraries within wildfly.
> But other times the application boot procedure will not go smoothly with the custom handler having processes routing JUL LogRecords events into the bundled log4j because the application server has loaded some of the classes that exist the org.jboss.log4j module.
> And as we know when the same class is loaded by different class loaders, then that class that orinates from class loader A cannot be assigned to the corresponding class of class loader B, even if the classes are exactly the same.
> This is not an isolated issue.
> There are also open issues on the wildfly forum reporting on startup problems on the logging subsystme where sometimes the LogManager class had not yet been loaded, and sometimes this issue goes away.
> This is an indication of some deep issue engrained into the module loading, where the module isolation behavior is not ensured to work all the time and that the boot procedure is not deterministically reliable.
> It should not be that the application server some time starts successfully and others not.
> Booting wildfly should always result in the same outcode.
> Problems of this nature with class loading problems should either always happen if the configuration is not done properly or never happen if the configuration is proper.
> In the case of thread:
> https://developer.jboss.org/thread/275839
> Our belief is that the configuration is doing all it possible can to request the necessary module isolation from base packages and the outcome where log4j class load problems take place should never be allowed to happen.
> Many thanks.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 8 months
[JBoss JIRA] (ELY-1350) Wildfly Elytron Tool, Powershell script elytron-tool.ps1 doesn't work with custom credential store implementation.
by Hynek Švábek (JIRA)
Hynek Švábek created ELY-1350:
---------------------------------
Summary: Wildfly Elytron Tool, Powershell script elytron-tool.ps1 doesn't work with custom credential store implementation.
Key: ELY-1350
URL: https://issues.jboss.org/browse/ELY-1350
Project: WildFly Elytron
Issue Type: Bug
Reporter: Hynek Švábek
Assignee: Darran Lofthouse
Powershell script elytron-tool.ps1 doesn't work with custom credential store implementation.
There is problem with getting value of environment variable ELYTRON_TOOL_ADDONS.
*How to reproduce:*
* run powershell and set work directory JBOSS_HOME/bin
* set env variable for custom credential store implementation jar like this:
{code}
[Environment]::SetEnvironmentVariable("ELYTRON_TOOL_ADDONS", "C:\custom.jar", "
Process")
{code}
* run this command
{code}
PowerShell -ExecutionPolicy Bypass -File elytron-tool.ps1 credential-store --add secret_alias --password pass123 --create -x secret_password -l 001.jceks --type CustomTestCredentialStore --debug
Exception encountered executing the command:
java.security.NoSuchAlgorithmException
at org.wildfly.security.credential.store.CredentialStore.getInstance(CredentialStore.java:80)
at
org.wildfly.security.tool.CredentialStoreCommand.execute(CredentialStoreCommand.java:188
at org.wildfly.security.tool.ElytronTool.main(ElytronTool.java:81)
{code}
*Suggestion to improve:*
For me works one of these changes in elytron-tool.ps1 script
# if (Test-Path env:ELYTRON_TOOL_ADDONS) { $ELYTRON_TOOL_ADDONS=(Get-ChildItem Env:ELYTRON_TOOL_ADDONS).value }
# $ELYTRON_TOOL_ADDONS=$env:ELYTRON_TOOL_ADDONS
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 8 months
[JBoss JIRA] (JGRP-2061) TYPE_STRING does not handle unicode
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-2061?page=com.atlassian.jira.plugin.... ]
Bela Ban resolved JGRP-2061.
----------------------------
Resolution: Done
> TYPE_STRING does not handle unicode
> -----------------------------------
>
> Key: JGRP-2061
> URL: https://issues.jboss.org/browse/JGRP-2061
> Project: JGroups
> Issue Type: Bug
> Reporter: Cody Ebberson
> Assignee: Bela Ban
> Fix For: 4.0.6
>
>
> In several places throughout the org.jgroups.util.Util class, it is assumed that Strings are one byte per character.
> For example, see objectToByteBuffer lines 561-567:
> https://github.com/belaban/JGroups/blob/master/src/org/jgroups/util/Util....
> {code:java}
> case TYPE_STRING:
> String str=(String)obj;
> int len=str.length();
> ByteBuffer retval=ByteBuffer.allocate(Global.BYTE_SIZE + len).put(TYPE_STRING);
> for(int i=0; i < len; i++)
> retval.put((byte)str.charAt(i));
> return retval.array();
> {code}
> This code will incorrectly encode any String with non ASCII encoding.
> There are several options to fix. You could use str.getBytes(StandardCharsets.UTF_8) to get a proper byte encoding, or you could use the existing TYPE_SERIALIZABLE code path.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 8 months
[JBoss JIRA] (WFLY-9275) unable to invoke server1 EJB via server2
by Loren Chang (JIRA)
[ https://issues.jboss.org/browse/WFLY-9275?page=com.atlassian.jira.plugin.... ]
Loren Chang updated WFLY-9275:
------------------------------
Description:
I want to invoke server2's EJB via server1, but still received by server 1.
Look at my cliet code & screenshot
test1 & test2 is ok
test3 is fail
was:
This test code on "public static void main" is ok, but fail on war/ear
EJB client API Version:wildfly-naming-client-1.0.0.Beta13.jar、jboss-remote-naming-2.0.4.Final.jar
> unable to invoke server1 EJB via server2
> ----------------------------------------
>
> Key: WFLY-9275
> URL: https://issues.jboss.org/browse/WFLY-9275
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 10.0.0.Final
> Reporter: Loren Chang
> Attachments: EJBTest.png, EJBTest.zip, WildFlyBug.png
>
>
> I want to invoke server2's EJB via server1, but still received by server 1.
> Look at my cliet code & screenshot
> test1 & test2 is ok
> test3 is fail
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 8 months