[JBoss JIRA] (WFLY-10987) Performance issue in audit endpoints
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFLY-10987?page=com.atlassian.jira.plugin... ]
Darran Lofthouse updated WFLY-10987:
------------------------------------
Fix Version/s: 15.0.0.Alpha1
> Performance issue in audit endpoints
> ------------------------------------
>
> Key: WFLY-10987
> URL: https://issues.jboss.org/browse/WFLY-10987
> Project: WildFly
> Issue Type: Task
> Components: Documentation, Security
> Affects Versions: 14.0.0.Final
> Reporter: Jan Kalina
> Assignee: Jan Kalina
> Priority: Critical
> Fix For: 15.0.0.Alpha1
>
>
> Synchronization in audit endpoint implementations leads to a great performance drop.
> We see the issue in {{FileAuditEndpoint.accept(EventPriority, String)}}, but similar code is also in the {{SyslogAuditEndpoint}}.
> Check the attached recording (FlightRecorder) in jmc (Java Mission Control).
> It can be seen in these tabs
> - Threads > Contention
> - Threads > Thread Dumps
> - Threads > Lock Instances
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months
[JBoss JIRA] (WFLY-10987) Performance issue in audit endpoints
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFLY-10987?page=com.atlassian.jira.plugin... ]
Darran Lofthouse reassigned WFLY-10987:
---------------------------------------
Assignee: Darran Lofthouse (was: Jan Kalina)
> Performance issue in audit endpoints
> ------------------------------------
>
> Key: WFLY-10987
> URL: https://issues.jboss.org/browse/WFLY-10987
> Project: WildFly
> Issue Type: Task
> Components: Documentation, Security
> Affects Versions: 14.0.0.Final
> Reporter: Jan Kalina
> Assignee: Darran Lofthouse
> Priority: Critical
> Fix For: 15.0.0.Alpha1
>
>
> Synchronization in audit endpoint implementations leads to a great performance drop.
> We see the issue in {{FileAuditEndpoint.accept(EventPriority, String)}}, but similar code is also in the {{SyslogAuditEndpoint}}.
> Check the attached recording (FlightRecorder) in jmc (Java Mission Control).
> It can be seen in these tabs
> - Threads > Contention
> - Threads > Thread Dumps
> - Threads > Lock Instances
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months
[JBoss JIRA] (WFLY-11073) Support hex encoding in jdbc-realm for elytron
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFLY-11073?page=com.atlassian.jira.plugin... ]
Darran Lofthouse reassigned WFLY-11073:
---------------------------------------
Assignee: (was: Jan Kalina)
> Support hex encoding in jdbc-realm for elytron
> ----------------------------------------------
>
> Key: WFLY-11073
> URL: https://issues.jboss.org/browse/WFLY-11073
> Project: WildFly
> Issue Type: Feature Request
> Components: Documentation, Security
> Reporter: Jan Kalina
> Labels: elytron
> Fix For: 15.0.0.Alpha1
>
>
> Old database login-module can be configured passing the attribute {{hashEncoding}}, for example:
> {code:xml}
> <login-module code="Database" flag="required">
> <module-option name="dsJndiName" value="java:jboss/datasources/ExampleDS"/>
> <module-option name="principalsQuery" value="SELECT password FROM User WHERE username = ?"/>
> <module-option name="rolesQuery" value="SELECT role, 'Roles' FROM User WHERE username = ?"/>
> <module-option name="hashAlgorithm" value="SHA-1"/>
> <module-option name="hashEncoding" value="hex"/>
> <module-option name="hashCharset" value="UTF-8"/>
> </login-module>
> {code}
> Currently jdbc-realm in elytron only uses base64 encoding if hash is stored in a text column. This way the migration is more complicated cos the password hash is not valid changing from old security system to elytron.
> Think also about the charset attribute.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months
[JBoss JIRA] (WFLY-10072) Stale session data on failover
by tommaso borgato (JIRA)
[ https://issues.jboss.org/browse/WFLY-10072?page=com.atlassian.jira.plugin... ]
tommaso borgato updated WFLY-10072:
-----------------------------------
Affects Version/s: 14.0.1.Final
15.0.0.Alpha1
> Stale session data on failover
> ------------------------------
>
> Key: WFLY-10072
> URL: https://issues.jboss.org/browse/WFLY-10072
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 14.0.1.Final, 15.0.0.Alpha1
> Reporter: Daniel Čihák
> Assignee: Paul Ferraro
> Priority: Minor
>
> Occured on client. Affected scenarios:
> eap-7x-failover-ejb-ejbservlet-shutdown-dist-async
> eap-7x-failover-http-granular-shutdown-repl-sync
> eap-7x-failover-http-session-jvmkill-dist-sync
> eap-7x-failover-http-session-jvmkill-repl-sync
> eap-7x-failover-http-session-shutdown-repl-sync-haproxy
> eap-7x-failover-http-session-undeploy-dist-sync
> Client log stacktrace:
> {code}
> 2016/09/21 17:28:51:294 EDT [WARN ][Runner - 134] HOST dev220.mw.lab.eng.bos.redhat.com:rootProcess:c - Error sampling data: <org.jboss.smartfrog.loaddriver.RequestProcessingException: Stale session data received. Expected 42, received 41, Runner: 134>
> org.jboss.smartfrog.loaddriver.RequestProcessingException: Stale session data received. Expected 42, received 41, Runner: 134
> at org.jboss.smartfrog.loaddriver.http.AbstractSerialNumberValidatorFactoryImpl$SerialNumberValidator.processRequest(AbstractSerialNumberValidatorFactoryImpl.java:133)
> at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:52)
> at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:103)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> Link to client log:
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-failover-http-...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months