May 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1528) EAP 7 with secured management become unavailable after ~8 days

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1528?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1528: ------------------------------------- Priority: Critical (was: Major) > EAP 7 with secured management become unavailable after ~8 days > -------------------------------------------------------------- > > Key: WFCORE-1528 > URL: https://issues.jboss.org/browse/WFCORE-1528 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management, Security > Affects Versions: 2.1.0.Final > Environment: EAP 7.0.0.CR01 2-way ssl over remote https communication > Reporter: Simeon Pinder > Assignee: Brian Stansberry > Priority: Critical > Fix For: 3.0.0.Alpha1 > > > Appears there may be an EAP 7.0.0.CR01 2-way ssl issue in domain mode. > Issue discovered by JON QE after testing for 8 days with SSL. > JON QE did not see the same issue when running identical test against EAP 6. > Restarting the remote client(JON Agent) did not repair/fix the issue, and only was repaired after EAP instance restarted. > See BZ https://bugzilla.redhat.com/show_bug.cgi?id=1330180#c0 for more details. > JON team would like some evaluation done to determine: > i)if this is EAP 7 issue or > ii)somehow just a JON issue > iii)suggestions on what to do when we try to reproduce properly or ways to shorten reproduce cycle. > This issue could affect GA release schedules. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1528) EAP 7 with secured management become unavailable after ~8 days

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1528?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1528: ------------------------------------- Fix Version/s: 3.0.0.Alpha1 > EAP 7 with secured management become unavailable after ~8 days > -------------------------------------------------------------- > > Key: WFCORE-1528 > URL: https://issues.jboss.org/browse/WFCORE-1528 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management, Security > Affects Versions: 2.1.0.Final > Environment: EAP 7.0.0.CR01 2-way ssl over remote https communication > Reporter: Simeon Pinder > Assignee: Brian Stansberry > Priority: Critical > Fix For: 3.0.0.Alpha1 > > > Appears there may be an EAP 7.0.0.CR01 2-way ssl issue in domain mode. > Issue discovered by JON QE after testing for 8 days with SSL. > JON QE did not see the same issue when running identical test against EAP 6. > Restarting the remote client(JON Agent) did not repair/fix the issue, and only was repaired after EAP instance restarted. > See BZ https://bugzilla.redhat.com/show_bug.cgi?id=1330180#c0 for more details. > JON team would like some evaluation done to determine: > i)if this is EAP 7 issue or > ii)somehow just a JON issue > iii)suggestions on what to do when we try to reproduce properly or ways to shorten reproduce cycle. > This issue could affect GA release schedules. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1528) EAP 7 with secured management become unavailable after ~8 days

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1528?page=com.atlassian.jira.plugi... ] Brian Stansberry moved JBEAP-4545 to WFCORE-1528: ------------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-1528 (was: JBEAP-4545) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Domain Management Security (was: Domain Management) (was: Security) Target Release: (was: 7.backlog.GA) Affects Version/s: 2.1.0.Final (was: 7.0.0.CR1) > EAP 7 with secured management become unavailable after ~8 days > -------------------------------------------------------------- > > Key: WFCORE-1528 > URL: https://issues.jboss.org/browse/WFCORE-1528 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management, Security > Affects Versions: 2.1.0.Final > Environment: EAP 7.0.0.CR01 2-way ssl over remote https communication > Reporter: Simeon Pinder > Assignee: Brian Stansberry > > Appears there may be an EAP 7.0.0.CR01 2-way ssl issue in domain mode. > Issue discovered by JON QE after testing for 8 days with SSL. > JON QE did not see the same issue when running identical test against EAP 6. > Restarting the remote client(JON Agent) did not repair/fix the issue, and only was repaired after EAP instance restarted. > See BZ https://bugzilla.redhat.com/show_bug.cgi?id=1330180#c0 for more details. > JON team would like some evaluation done to determine: > i)if this is EAP 7 issue or > ii)somehow just a JON issue > iii)suggestions on what to do when we try to reproduce properly or ways to shorten reproduce cycle. > This issue could affect GA release schedules. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ELY-528) Add support for the ASN.1 integer type to DEREncoder and DERDecoder

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/ELY-528?page=com.atlassian.jira.plugin.sy... ] Farah Juma reassigned ELY-528: ------------------------------ Assignee: Darran Lofthouse (was: Farah Juma) > Add support for the ASN.1 integer type to DEREncoder and DERDecoder > ------------------------------------------------------------------- > > Key: ELY-528 > URL: https://issues.jboss.org/browse/ELY-528 > Project: WildFly Elytron > Issue Type: Feature Request > Components: Utils > Reporter: Farah Juma > Assignee: Darran Lofthouse > > Add support for the ASN.1 integer type, as described in Section 5.7 here: > http://luca.ntop.org/Teaching/Appunti/asn1.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ELY-528) Add support for the ASN.1 integer type to DEREncoder and DERDecoder

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/ELY-528?page=com.atlassian.jira.plugin.sy... ] Farah Juma reassigned ELY-528: ------------------------------ Assignee: Farah Juma (was: Darran Lofthouse) > Add support for the ASN.1 integer type to DEREncoder and DERDecoder > ------------------------------------------------------------------- > > Key: ELY-528 > URL: https://issues.jboss.org/browse/ELY-528 > Project: WildFly Elytron > Issue Type: Feature Request > Components: Utils > Reporter: Farah Juma > Assignee: Farah Juma > > Add support for the ASN.1 integer type, as described in Section 5.7 here: > http://luca.ntop.org/Teaching/Appunti/asn1.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1527) Server group / JVM composite add op and minssing parent

by Ken Wills (JIRA)

Ken Wills created WFCORE-1527: --------------------------------- Summary: Server group / JVM composite add op and minssing parent Key: WFCORE-1527 URL: https://issues.jboss.org/browse/WFCORE-1527 Project: WildFly Core Issue Type: Bug Components: Domain Management Reporter: Ken Wills Assignee: Ken Wills The test AutoIgnoreDomain tests when adding an ignored server group, like this: https://github.com/luck3y/wildfly-core/blob/6cdd4af55b7723ff943a3743143a6... Also calld the JvmAddHandler. During the JVMH add, the prior add of the server group is not visible in the model and the op fails. Workaround in JVMAddHandler.populateModel, to attempt to RRFR, and fail silently if the parent is not available, but something prior in the chain is violating the readDomainFromRoot contract, as the server element should be a visible, but uncommitted change in the model. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6591) Memory leak of expired session in Infinispan cache with optimistic locking

by Mathieu Lachance (JIRA)

[ https://issues.jboss.org/browse/WFLY-6591?page=com.atlassian.jira.plugin.... ] Mathieu Lachance edited comment on WFLY-6591 at 5/5/16 12:05 PM: ----------------------------------------------------------------- I'd like also to point out to a comment in the top of the class https://github.com/wildfly/wildfly/blob/master/clustering/web/infinispan/...: {code} /** * Session expiration scheduler that eagerly expires sessions as soon as they are eligible. * If/When Infinispan implements expiration notifications (ISPN-694), this will be obsolete. * @author Paul Ferraro */ public class SessionExpirationScheduler implements Scheduler { {code} ISPN-694 has been resolved in Infinispan 8 which is now part of WF10. Is there some remaining TODO's that were 'forgotten' ? Just in case... was (Author: matlach): I'd like also to pointout a comment in the top of the class https://github.com/wildfly/wildfly/blob/master/clustering/web/infinispan/...: {code} /** * Session expiration scheduler that eagerly expires sessions as soon as they are eligible. * If/When Infinispan implements expiration notifications (ISPN-694), this will be obsolete. * @author Paul Ferraro */ public class SessionExpirationScheduler implements Scheduler { {code} ISPN-694 has been resolved in Infinispan 8 which is now part of WF10. Is there some remaining TODO's that were 'forgotten' ? Just in case... > Memory leak of expired session in Infinispan cache with optimistic locking > -------------------------------------------------------------------------- > > Key: WFLY-6591 > URL: https://issues.jboss.org/browse/WFLY-6591 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.0.0.Final, 10.1.0.Final > Reporter: Gabriel Lavoie > Assignee: Paul Ferraro > > When using optimistic locking on the web cache, data from expired sessions is not removed from the web cache by the org.wildfly.clustering.web.infinispan.session.SessionExpirationScheduler and leaks forever. > Session seems to be invalidated correctly and isn't accessible anymore. > After tracing the code, org.wildfly.clustering.web.infinispan.session.InfinispanSessionMetaDataFactory.remove() doesn't remove the metadata entries when "this.properties.isLockOnWrite()" returns false (which is always the case for optimistic locking). Then in org.wildfly.clustering.web.infinispan.session.InfinispanSessionFactory.remove(), the call to attributesFactory.remove(id) also gets skipped. > We've tried to adjust the code of org.wildfly.clustering.web.infinispan.session.InfinispanSessionMetaDataFactory.remove() to the following: > {code} > private boolean remove(String id, Cache<SessionCreationMetaDataKey, SessionCreationMetaDataEntry<L>> creationMetaDataCache) { > SessionCreationMetaDataKey key = new SessionCreationMetaDataKey(id); > if (this.properties.isLockOnWrite()) { > if (creationMetaDataCache.getAdvancedCache().withFlags(Flag.ZERO_LOCK_ACQUISITION_TIMEOUT, Flag.FAIL_SILENTLY).lock(key)) { > creationMetaDataCache.getAdvancedCache().withFlags(Flag.IGNORE_RETURN_VALUES).remove(key); > this.accessMetaDataCache.getAdvancedCache().withFlags(Flag.IGNORE_RETURN_VALUES).remove(new SessionAccessMetaDataKey(id)); > return true; > } > return false; > } else { > creationMetaDataCache.getAdvancedCache().withFlags(Flag.IGNORE_RETURN_VALUES).remove(key); > this.accessMetaDataCache.getAdvancedCache().withFlags(Flag.IGNORE_RETURN_VALUES).remove(new SessionAccessMetaDataKey(id)); > return true; > } > } > {code} > With that change, the memory leaks disappears. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6591) Memory leak of expired session in Infinispan cache with optimistic locking

by Mathieu Lachance (JIRA)

[ https://issues.jboss.org/browse/WFLY-6591?page=com.atlassian.jira.plugin.... ] Mathieu Lachance edited comment on WFLY-6591 at 5/5/16 12:05 PM: ----------------------------------------------------------------- I'd like also to point out a comment in the top of the class https://github.com/wildfly/wildfly/blob/master/clustering/web/infinispan/...: {code} /** * Session expiration scheduler that eagerly expires sessions as soon as they are eligible. * If/When Infinispan implements expiration notifications (ISPN-694), this will be obsolete. * @author Paul Ferraro */ public class SessionExpirationScheduler implements Scheduler { {code} ISPN-694 has been resolved in Infinispan 8 which is now part of WF10. Is there some remaining TODO's that were 'forgotten' ? Just in case... was (Author: matlach): I'd like also to point out to a comment in the top of the class https://github.com/wildfly/wildfly/blob/master/clustering/web/infinispan/...: {code} /** * Session expiration scheduler that eagerly expires sessions as soon as they are eligible. * If/When Infinispan implements expiration notifications (ISPN-694), this will be obsolete. * @author Paul Ferraro */ public class SessionExpirationScheduler implements Scheduler { {code} ISPN-694 has been resolved in Infinispan 8 which is now part of WF10. Is there some remaining TODO's that were 'forgotten' ? Just in case... > Memory leak of expired session in Infinispan cache with optimistic locking > -------------------------------------------------------------------------- > > Key: WFLY-6591 > URL: https://issues.jboss.org/browse/WFLY-6591 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.0.0.Final, 10.1.0.Final > Reporter: Gabriel Lavoie > Assignee: Paul Ferraro > > When using optimistic locking on the web cache, data from expired sessions is not removed from the web cache by the org.wildfly.clustering.web.infinispan.session.SessionExpirationScheduler and leaks forever. > Session seems to be invalidated correctly and isn't accessible anymore. > After tracing the code, org.wildfly.clustering.web.infinispan.session.InfinispanSessionMetaDataFactory.remove() doesn't remove the metadata entries when "this.properties.isLockOnWrite()" returns false (which is always the case for optimistic locking). Then in org.wildfly.clustering.web.infinispan.session.InfinispanSessionFactory.remove(), the call to attributesFactory.remove(id) also gets skipped. > We've tried to adjust the code of org.wildfly.clustering.web.infinispan.session.InfinispanSessionMetaDataFactory.remove() to the following: > {code} > private boolean remove(String id, Cache<SessionCreationMetaDataKey, SessionCreationMetaDataEntry<L>> creationMetaDataCache) { > SessionCreationMetaDataKey key = new SessionCreationMetaDataKey(id); > if (this.properties.isLockOnWrite()) { > if (creationMetaDataCache.getAdvancedCache().withFlags(Flag.ZERO_LOCK_ACQUISITION_TIMEOUT, Flag.FAIL_SILENTLY).lock(key)) { > creationMetaDataCache.getAdvancedCache().withFlags(Flag.IGNORE_RETURN_VALUES).remove(key); > this.accessMetaDataCache.getAdvancedCache().withFlags(Flag.IGNORE_RETURN_VALUES).remove(new SessionAccessMetaDataKey(id)); > return true; > } > return false; > } else { > creationMetaDataCache.getAdvancedCache().withFlags(Flag.IGNORE_RETURN_VALUES).remove(key); > this.accessMetaDataCache.getAdvancedCache().withFlags(Flag.IGNORE_RETURN_VALUES).remove(new SessionAccessMetaDataKey(id)); > return true; > } > } > {code} > With that change, the memory leaks disappears. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6591) Memory leak of expired session in Infinispan cache with optimistic locking

by Mathieu Lachance (JIRA)

[ https://issues.jboss.org/browse/WFLY-6591?page=com.atlassian.jira.plugin.... ] Mathieu Lachance commented on WFLY-6591: ---------------------------------------- I'd like also to pointout a comment in the top of the class https://github.com/wildfly/wildfly/blob/master/clustering/web/infinispan/...: {code} /** * Session expiration scheduler that eagerly expires sessions as soon as they are eligible. * If/When Infinispan implements expiration notifications (ISPN-694), this will be obsolete. * @author Paul Ferraro */ public class SessionExpirationScheduler implements Scheduler { {code} ISPN-694 has been resolved in Infinispan 8 which is now part of WF10. Is there some remaining TODO's that were 'forgotten' ? Just in case... > Memory leak of expired session in Infinispan cache with optimistic locking > -------------------------------------------------------------------------- > > Key: WFLY-6591 > URL: https://issues.jboss.org/browse/WFLY-6591 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.0.0.Final, 10.1.0.Final > Reporter: Gabriel Lavoie > Assignee: Paul Ferraro > > When using optimistic locking on the web cache, data from expired sessions is not removed from the web cache by the org.wildfly.clustering.web.infinispan.session.SessionExpirationScheduler and leaks forever. > Session seems to be invalidated correctly and isn't accessible anymore. > After tracing the code, org.wildfly.clustering.web.infinispan.session.InfinispanSessionMetaDataFactory.remove() doesn't remove the metadata entries when "this.properties.isLockOnWrite()" returns false (which is always the case for optimistic locking). Then in org.wildfly.clustering.web.infinispan.session.InfinispanSessionFactory.remove(), the call to attributesFactory.remove(id) also gets skipped. > We've tried to adjust the code of org.wildfly.clustering.web.infinispan.session.InfinispanSessionMetaDataFactory.remove() to the following: > {code} > private boolean remove(String id, Cache<SessionCreationMetaDataKey, SessionCreationMetaDataEntry<L>> creationMetaDataCache) { > SessionCreationMetaDataKey key = new SessionCreationMetaDataKey(id); > if (this.properties.isLockOnWrite()) { > if (creationMetaDataCache.getAdvancedCache().withFlags(Flag.ZERO_LOCK_ACQUISITION_TIMEOUT, Flag.FAIL_SILENTLY).lock(key)) { > creationMetaDataCache.getAdvancedCache().withFlags(Flag.IGNORE_RETURN_VALUES).remove(key); > this.accessMetaDataCache.getAdvancedCache().withFlags(Flag.IGNORE_RETURN_VALUES).remove(new SessionAccessMetaDataKey(id)); > return true; > } > return false; > } else { > creationMetaDataCache.getAdvancedCache().withFlags(Flag.IGNORE_RETURN_VALUES).remove(key); > this.accessMetaDataCache.getAdvancedCache().withFlags(Flag.IGNORE_RETURN_VALUES).remove(new SessionAccessMetaDataKey(id)); > return true; > } > } > {code} > With that change, the memory leaks disappears. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ELY-528) Add support for the ASN.1 integer type to DEREncoder and DERDecoder

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/ELY-528?page=com.atlassian.jira.plugin.sy... ] Farah Juma updated ELY-528: --------------------------- Description: Add support for the ASN.1 integer type, as described in Section 5.7 here: http://luca.ntop.org/Teaching/Appunti/asn1.html was: Add support for the ASN.1 integer type, as defined in Section 5.7 here: http://luca.ntop.org/Teaching/Appunti/asn1.html > Add support for the ASN.1 integer type to DEREncoder and DERDecoder > ------------------------------------------------------------------- > > Key: ELY-528 > URL: https://issues.jboss.org/browse/ELY-528 > Project: WildFly Elytron > Issue Type: Feature Request > Components: Utils > Reporter: Farah Juma > Assignee: Farah Juma > > Add support for the ASN.1 integer type, as described in Section 5.7 here: > http://luca.ntop.org/Teaching/Appunti/asn1.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2016