[JBoss JIRA] (ELY-1323) Performance issue in audit endpoints
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/ELY-1323?page=com.atlassian.jira.plugin.s... ]
Jan Kalina commented on ELY-1323:
---------------------------------
There is intentionally audit-endpoints forced to wait for flush on every log event accept by keeping default *audit-endpoint.synchronized=true*
[~jcacek] would be possible to retest with *synchronized=false*?
> Performance issue in audit endpoints
> ------------------------------------
>
> Key: ELY-1323
> URL: https://issues.jboss.org/browse/ELY-1323
> Project: WildFly Elytron
> Issue Type: Bug
> Components: Audit
> Affects Versions: 1.1.0.CR4
> Reporter: Josef Cacek
> Assignee: Jan Kalina
> Priority: Blocker
> Attachments: elytron-flightrecording.jfr
>
>
> 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.2.3#72005)
8 years, 9 months
[JBoss JIRA] (WFCORE-3281) Upgrade Elytron Web to 1.0.1.Final
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3281?page=com.atlassian.jira.plugi... ]
Darran Lofthouse moved JBEAP-13134 to WFCORE-3281:
--------------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-3281 (was: JBEAP-13134)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Security
(was: Security)
> Upgrade Elytron Web to 1.0.1.Final
> ----------------------------------
>
> Key: WFCORE-3281
> URL: https://issues.jboss.org/browse/WFCORE-3281
> Project: WildFly Core
> Issue Type: Component Upgrade
> Components: Security
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Priority: Blocker
>
> No specific fixes in this tag other than testsuite changes but as this is a candidate release getting all of the Elytron components in sync.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (WFCORE-3280) Upgrade WildFly Elytron Tool to 1.0.1.Final
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3280?page=com.atlassian.jira.plugi... ]
Darran Lofthouse moved JBEAP-13133 to WFCORE-3280:
--------------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-3280 (was: JBEAP-13133)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Security
(was: Security)
> Upgrade WildFly Elytron Tool to 1.0.1.Final
> -------------------------------------------
>
> Key: WFCORE-3280
> URL: https://issues.jboss.org/browse/WFCORE-3280
> Project: WildFly Core
> Issue Type: Component Upgrade
> Components: Security
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Priority: Blocker
> Fix For: 3.0.2.Final
>
>
> There is no specific fix for this upgrade but as the tool is a shaded jar containing the Elytron release it referenced this update is to bring the versions up to date.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (ELY-1323) Performance issue in audit endpoints
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/ELY-1323?page=com.atlassian.jira.plugin.s... ]
Jan Kalina reassigned ELY-1323:
-------------------------------
Assignee: Jan Kalina
> Performance issue in audit endpoints
> ------------------------------------
>
> Key: ELY-1323
> URL: https://issues.jboss.org/browse/ELY-1323
> Project: WildFly Elytron
> Issue Type: Bug
> Components: Audit
> Affects Versions: 1.1.0.CR4
> Reporter: Josef Cacek
> Assignee: Jan Kalina
> Priority: Blocker
> Attachments: elytron-flightrecording.jfr
>
>
> 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.2.3#72005)
8 years, 9 months