[JBoss JIRA] (WFCORE-491) Improve ManagedAuditLoggerImpl.log() performance when disabled
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-491?page=com.atlassian.jira.plugin... ]
Brian Stansberry reassigned WFCORE-491:
---------------------------------------
Assignee: (was: Brian Stansberry)
> Improve ManagedAuditLoggerImpl.log() performance when disabled
> --------------------------------------------------------------
>
> Key: WFCORE-491
> URL: https://issues.jboss.org/browse/WFCORE-491
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Domain Management
> Affects Versions: 1.0.0.Alpha15
> Reporter: James Livingston
> Priority: Minor
>
> org.jboss.as.controller.audit.ManagedAuditLoggerImpl.log/logJmxMethodAccess() does some work such as creating the log item which will just be thrown away if getLoggerStatus()==DISABLED.
> It may be worth checking if that is the case and skipping the work that will not be needed. If it was not for the applyHandlerUpdates() call, I think an "isDisabled" volatile flag could be used to avoid taking the lock at all there, which can be expensive due to it being a fair lock.
> This does not appear to show up as a issue unless you are performing a lot (thousands) of management operations in quick succession.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 12 months
[JBoss JIRA] (ELY-20) Where does OTP fit into realms?
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/ELY-20?page=com.atlassian.jira.plugin.sys... ]
David Lloyd commented on ELY-20:
--------------------------------
This may tie in to adding verification-only support for realms.
> Where does OTP fit into realms?
> -------------------------------
>
> Key: ELY-20
> URL: https://issues.jboss.org/browse/ELY-20
> Project: WildFly Elytron
> Issue Type: Sub-task
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Fix For: 1.0.0.Beta1
>
>
> Will investigate further once we have a pure LDAP impl in.
> We could have an architecture where we have an LDAP server that is then referenced by an OTP server or we could have the two somehow combined into one.
> There are also requirements related to marking a token as used or token invalidation after too many bad attempts - this may be handled within the OTP server but for stronger authentication mechanisms may need to be more involved otherwise this becomes another case of falling back to PLAIN / BASIC auth.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 12 months
[JBoss JIRA] (WFCORE-415) Pressing up-arrow crashed CLI on windows
by Alexey Loubyansky (JIRA)
[ https://issues.jboss.org/browse/WFCORE-415?page=com.atlassian.jira.plugin... ]
Alexey Loubyansky resolved WFCORE-415.
--------------------------------------
Fix Version/s: 1.0.0.Alpha15
Resolution: Done
This issues was fixed with the inclusion of Aesh 0.33.14, which contains the fix for AESH-96.
> Pressing up-arrow crashed CLI on windows
> ----------------------------------------
>
> Key: WFCORE-415
> URL: https://issues.jboss.org/browse/WFCORE-415
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Reporter: Nicklas Karlsson
> Assignee: Alexey Loubyansky
> Fix For: 1.0.0.Alpha15
>
>
> Pressing the up-arrow in the CLI on windows crashes it with
> {code}
> [standalone@localhost:9990 /] java.lang.NumberFormatException: For input string:
> "1B"
> at java.lang.NumberFormatException.forInputString(NumberFormatException.
> java:65)
> at java.lang.Integer.parseInt(Integer.java:492)
> at java.lang.Integer.<init>(Integer.java:677)
> at org.fusesource.jansi.AnsiOutputStream.write(AnsiOutputStream.java:120
> )
> at java.io.FilterOutputStream.write(FilterOutputStream.java:125)
> at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221)
> at sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:291)
> at sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:295)
> at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:141)
> at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:229)
> at java.io.PrintWriter.flush(PrintWriter.java:320)
> at org.jboss.aesh.terminal.WindowsTerminal.writeToStdOut(WindowsTerminal
> .java:88)
> at org.jboss.aesh.console.Console.drawLine(Console.java:1011)
> at org.jboss.aesh.console.Console.redrawLine(Console.java:990)
> at org.jboss.aesh.console.Console.getHistoryElement(Console.java:753)
> at org.jboss.aesh.console.Console.parseOperation(Console.java:556)
> at org.jboss.aesh.console.Console.read(Console.java:446)
> at org.jboss.aesh.console.Console.read(Console.java:346)
> at org.jboss.as.cli.impl.Console$Factory$1.readLine(Console.java:177)
> at org.jboss.as.cli.impl.CommandContextImpl.interact(CommandContextImpl.
> java:1198)
> at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:270)
> at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:34)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> sorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.jboss.modules.Module.run(Module.java:270)
> at org.jboss.modules.Main.main(Main.java:411)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 12 months
[JBoss JIRA] (WFLY-3740) standalone.sh does not compute correct module path in Cygwin
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-3740?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar commented on WFLY-3740:
-----------------------------------
any chance you can try with latest wildfly-core? https://github.com/wildfly/wildfly-core/
> standalone.sh does not compute correct module path in Cygwin
> ------------------------------------------------------------
>
> Key: WFLY-3740
> URL: https://issues.jboss.org/browse/WFLY-3740
> Project: WildFly
> Issue Type: Bug
> Components: Scripts
> Affects Versions: 8.1.0.Final
> Environment: Windows with Cygwin
> Reporter: David Del Vecchio
> Assignee: Tomaz Cerar
> Priority: Minor
>
> standalone.sh does not seem to compute the correct JBOSS_MODULEPATH on Cygwin as a result, starting up the server gives the following error:
> {noformat}
> org.jboss.modules.ModuleNotFoundException: org.jboss.as.standalone:main
> at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:240)
> at org.jboss.modules.Main.main(Main.java:385)}}
> {noformat}
> The problem seems to be somewhat related to this issue in that a mix of Windows and Unix style paths are being computed:
> https://issues.jboss.org/browse/WFLY-2523
> Since {{JBOSS_MODULEPATH}} is not set until after all the paths (such as {{JBOSS_HOME}}) have been converted to Windows style, {{JBOSS_MODULEPATH}} ends up with a Unix style forward slash at the end of what is otherwise a Windows style path.
> The fix for me was to move the code which sets the {{JBOSS_MODULEPATH}} to earlier in the script. I moved it to right after the {{export JBOSS_HOME}} line:
> {code:title=standalone.sh|borderStyle=solid}
> ...
> export JBOSS_HOME
> if [ "x$JBOSS_MODULEPATH" = "x" ]; then
> JBOSS_MODULEPATH="$JBOSS_HOME/modules"
> fi
> ...
> {code}
> Probably the key thing is just that the {{JBOSS_MODULEPATH}} gets set before everything is switched to Windows paths in this section of the script:
> {code:title=standalone.sh|borderStyle=solid}
> # For Cygwin, switch paths to Windows format before running java
> if $cygwin; then
> JBOSS_HOME=`cygpath --path --windows "$JBOSS_HOME"`
> JAVA_HOME=`cygpath --path --windows "$JAVA_HOME"`
> JBOSS_MODULEPATH=`cygpath --path --windows "$JBOSS_MODULEPATH"`
> JBOSS_BASE_DIR=`cygpath --path --windows "$JBOSS_BASE_DIR"`
> JBOSS_LOG_DIR=`cygpath --path --windows "$JBOSS_LOG_DIR"`
> JBOSS_CONFIG_DIR=`cygpath --path --windows "$JBOSS_CONFIG_DIR"`
> fi
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 12 months