October 2018 - jboss-jira - Jboss List Archives

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

5 years, 10 months

1
0
0 / 0

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

5 years, 10 months

1
0
0 / 0

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

5 years, 10 months

1
0
0 / 0

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

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3542) Elytron JDBC realm password mapping is not consistent with underlying implementation

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3542?page=com.atlassian.jira.plugi... ] Darran Lofthouse reassigned WFCORE-3542: ---------------------------------------- Assignee: (was: Jan Kalina) > Elytron JDBC realm password mapping is not consistent with underlying implementation > ------------------------------------------------------------------------------------ > > Key: WFCORE-3542 > URL: https://issues.jboss.org/browse/WFCORE-3542 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: David Lloyd > > There is no way to configure the JDBC realm to use modular crypt in WildFly, even though the underlying realm does support it. > The problem is that the *{{salt-index}} and {{itereration-count-index}} attributes should be optional*, and if they not given, a value of {{-1}} should be passed to the mapper. By omitting both of these values, the database column values will then be recognized as modular-crypt strings. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3832) Support hex encoding in jdbc-realm for elytron

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3832?page=com.atlassian.jira.plugi... ] Darran Lofthouse reassigned WFCORE-3832: ---------------------------------------- Assignee: (was: Jan Kalina) > Support hex encoding in jdbc-realm for elytron > ---------------------------------------------- > > Key: WFCORE-3832 > URL: https://issues.jboss.org/browse/WFCORE-3832 > Project: WildFly Core > Issue Type: Feature Request > Components: Security > Affects Versions: 5.0.0.Alpha7 > Reporter: Jan Kalina > Labels: elytron > > 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)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBMETA-414) Add tests to cover iiop configuration paarsing

by ehsavoie Hugonnet (JIRA)

ehsavoie Hugonnet created JBMETA-414: ---------------------------------------- Summary: Add tests to cover iiop configuration paarsing Key: JBMETA-414 URL: https://issues.jboss.org/browse/JBMETA-414 Project: JBoss Metadata Issue Type: Enhancement Components: ejb Affects Versions: 12.0.0.Final Reporter: ehsavoie Hugonnet Assignee: ehsavoie Hugonnet Priority: Minor Add test to cover the old way of parsing iiop configuration (even if this doesn't follow the schemas) @see https://github.com/wildfly/wildfly/pull/11408 and https://github.com/wildfly/wildfly/pull/11700 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3947) Support SSL Certificate revocation using OCSP

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3947?page=com.atlassian.jira.plugi... ] Darran Lofthouse reassigned WFCORE-3947: ---------------------------------------- Assignee: (was: Jan Kalina) > Support SSL Certificate revocation using OCSP > --------------------------------------------- > > Key: WFCORE-3947 > URL: https://issues.jboss.org/browse/WFCORE-3947 > Project: WildFly Core > Issue Type: Task > Components: Security > Affects Versions: 6.0.0.Alpha2 > Reporter: Jan Kalina > Priority: Critical > > - Provide undertow's client certificate revocation capability when undertow is used as a load balancer using OCSP. > (CRL capability is provided in the earlier release as part of Elytron SSL Consolidation effort that this JIRA is cloned from) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3969) ALIAS_FILTER in Elytron trustmanager ignored when crl used

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3969?page=com.atlassian.jira.plugi... ] Darran Lofthouse reassigned WFCORE-3969: ---------------------------------------- Assignee: (was: Jan Kalina) > ALIAS_FILTER in Elytron trustmanager ignored when crl used > ---------------------------------------------------------- > > Key: WFCORE-3969 > URL: https://issues.jboss.org/browse/WFCORE-3969 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 6.0.0.Alpha2 > Reporter: Jan Kalina > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10531) Wildfly leaks ActiveMQ connections

by Jan-Willem Gmelig Meyling (JIRA)

[ https://issues.jboss.org/browse/WFLY-10531?page=com.atlassian.jira.plugin... ] Jan-Willem Gmelig Meyling commented on WFLY-10531: -------------------------------------------------- I seem to suffer from this issue in WF14.0.1 too... > Wildfly leaks ActiveMQ connections > ---------------------------------- > > Key: WFLY-10531 > URL: https://issues.jboss.org/browse/WFLY-10531 > Project: WildFly > Issue Type: Bug > Affects Versions: 13.0.0.Final > Environment: openjdk 8 / openjdk 9, Linux > Reporter: Marcel Šebek > Assignee: Jeff Mesnil > Attachments: WFLY-10531-ear-1.0.ear, WFLY10531.zip > > > After upgrading our application from wildfly 12 to 13, the app started to crash after a while (hours, days, depending on circumstances). It crashes on > IJ000453: Unable to get managed connection for java:/JmsXA > and other errors (it simply cannot perform all the jobs it contains). I found that when shutting down the server which has been running for a while, I can see a bunch of these messages in the log: > WARN [org.jboss.jca.core.connectionmanager.pool.strategy.PoolByCri] (ServerService Thread Pool -- 117) [:::] IJ000615: Destroying active connection in pool: ActiveMQConnectionDefinition (org.apache.activemq.artemis.ra.ActiveMQRAManagedConnection@2f37f69) > Bascially, the longer the server was running, more of these messages are shown. I cannot find a way how to reproduce the issue. When the server runs for short time but with some load, no connection is leaked (or just one, rarely). On the other side, it leaks connections even without any particularly high load (just a few requests and @Schedule jobs) when running for longer time. > It may also be a bug in our application, which just happen to have more serious impact with the new wildfly version. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2018