April 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-5403) CLONE - Adding modcluster via the CLI fails.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-5403?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-5403: ---------------------------------------------- Michal Babacek <mbabacek(a)redhat.com> made a comment on [bug 900801|https://bugzilla.redhat.com/show_bug.cgi?id=900801] As I stated in [1] on 2013-04-16, the composite operation mentioned _in that comment_ works. My previous error was in using a malformed command. [1] https://bugzilla.redhat.com/show_bug.cgi?id=900801#c11 > CLONE - Adding modcluster via the CLI fails. > -------------------------------------------- > > Key: AS7-5403 > URL: https://issues.jboss.org/browse/AS7-5403 > Project: Application Server 7 > Issue Type: Bug > Components: CLI, Clustering > Affects Versions: 7.1.2.Final (EAP) > Reporter: Tom Fonteyne > Assignee: Radoslav Husar > Fix For: 8.0.0.Alpha1 > > > Adding modcluster via the CLI fails. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-6946) Redesign web session clustering

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-6946?page=com.atlassian.jira.plugin.s... ] Brian Stansberry commented on AS7-6946: --------------------------------------- Sounds good. Alpha1 is scheduled for May 6. Please reschedule. :) > Redesign web session clustering > ------------------------------- > > Key: AS7-6946 > URL: https://issues.jboss.org/browse/AS7-6946 > Project: Application Server 7 > Issue Type: Task > Components: Clustering > Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final) > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 8.0.0.Alpha1 > > > The current web session replication code has been around for ages and suffers from a number of issues: > * By maintaining a separate local map of sessions in conjunction with the session data stored in the distributed cache, stale data is inevitable - an number of issues have cropped up in EAP testing. > * Extra concurrency measures are required to ensure synchronicity of the local session map with the distributed cache. > * Extra logic/locking is required to invalidate the local session map is required per request > * AtomicMaps, on which the currently implementation relies, have proven buggy > * Session access outside of the scope of the replication valve is possible and problematic > * Maintaining sessions locally means that the clustering code needs to implement passivation and expiration manually - instead of leveraging Infinispan full capabilities. > * The current code base is tightly coupled to JBoss Web. Migrating the code to support Undertow will inevitably introduce issues and code duplication. > The new design will incorporate a proper SPI for the servlet container. Thus the logic to integrate with Undertow vs JBoss Web will be relatively thin. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-6947) Leverage Infinispan async api for clean shutdown

by Paul Ferraro (JIRA)

Paul Ferraro created AS7-6947: --------------------------------- Summary: Leverage Infinispan async api for clean shutdown Key: AS7-6947 URL: https://issues.jboss.org/browse/AS7-6947 Project: Application Server 7 Issue Type: Sub-task Components: Clustering Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final) Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 8.0.0.Alpha1 Leverage the Infinispan async API to ensure that all sessions have replicated (when using REPL/DIST_ASYNC) prior to shutdown/undeploy. https://docs.jboss.org/author/display/ISPN/Asynchronous+API -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-6946) Redesign web session clustering

by Paul Ferraro (JIRA)

Paul Ferraro created AS7-6946: --------------------------------- Summary: Redesign web session clustering Key: AS7-6946 URL: https://issues.jboss.org/browse/AS7-6946 Project: Application Server 7 Issue Type: Task Components: Clustering Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final) Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 8.0.0.Alpha1 The current web session replication code has been around for ages and suffers from a number of issues: * By maintaining a separate local map of sessions in conjunction with the session data stored in the distributed cache, stale data is inevitable - an number of issues have cropped up in EAP testing. * Extra concurrency measures are required to ensure synchronicity of the local session map with the distributed cache. * Extra logic/locking is required to invalidate the local session map is required per request * AtomicMaps, on which the currently implementation relies, have proven buggy * Session access outside of the scope of the replication valve is possible and problematic * Maintaining sessions locally means that the clustering code needs to implement passivation and expiration manually - instead of leveraging Infinispan full capabilities. * The current code base is tightly coupled to JBoss Web. Migrating the code to support Undertow will inevitably introduce issues and code duplication. The new design will incorporate a proper SPI for the servlet container. Thus the logic to integrate with Undertow vs JBoss Web will be relatively thin. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-6945) Replace mod_cluster proxy-list attribute with list of outbound socket bindings

by Paul Ferraro (JIRA)

Paul Ferraro created AS7-6945: --------------------------------- Summary: Replace mod_cluster proxy-list attribute with list of outbound socket bindings Key: AS7-6945 URL: https://issues.jboss.org/browse/AS7-6945 Project: Application Server 7 Issue Type: Task Components: Clustering Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final) Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 8.0.0.Beta1 Currently, the mod_cluster subsystem defines proxies using a comma separated string of address:port. This attribute needs to be deprecated in favor of an attribute, call it "proxies" that defines an xs:list of outbound socket binding names. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-6345) <vault> does not have module option

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-6345?page=com.atlassian.jira.plugin.s... ] Brian Stansberry commented on AS7-6345: --------------------------------------- It's a borderline bug, since providing a plugin point that requires the user to modify the module.xml for an internal module in order to allow the plugin to be loaded is basically broken. The coding magic is pretty simple; you read the name of the module from the new "module" attribute and if defined get the module and use its classloader to load the class specified by the "code" attribute. See, for example: https://github.com/jbossas/jboss-as/blob/master/logging/src/main/java/org... https://github.com/jbossas/jboss-as/blob/master/logging/src/main/java/org... > <vault> does not have module option > ----------------------------------- > > Key: AS7-6345 > URL: https://issues.jboss.org/browse/AS7-6345 > Project: Application Server 7 > Issue Type: Bug > Components: Security > Affects Versions: 7.1.3.Final (EAP) > Reporter: James Livingston > Assignee: Peter Skopek > > The <vault> element in standalone/domain.xml takes a 'code' attribute specifying the class to use as the implementation. It does not let you specify a 'module' option like most similar elements have, and instead always loads the class from the org.picketbox module. > The <vault> element should take a module option too. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-6944) Cannot update OSGi WebApp

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-6944: ----------------------------------- Summary: Cannot update OSGi WebApp Key: AS7-6944 URL: https://issues.jboss.org/browse/AS7-6944 Project: Application Server 7 Issue Type: Bug Components: OSGi Reporter: Thomas Diesler Assignee: Thomas Diesler -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-733) Session replication broken by NegotiationAuthenticator valve

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-733?page=com.atlassian.jira.plug... ] RH Bugzilla Integration updated SECURITY-733: --------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=949737 > Session replication broken by NegotiationAuthenticator valve > ------------------------------------------------------------ > > Key: SECURITY-733 > URL: https://issues.jboss.org/browse/SECURITY-733 > Project: PicketBox > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Negotiation > Affects Versions: Negotiation_2_2_2 > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: Negotiation_2_2_3 > > > From an initial review of the code I believe this is because the ClusterSessionValve implements the Listener interface - however the wrapper class does not. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-733) Session replication broken by NegotiationAuthenticator valve

by Darran Lofthouse (JIRA)

Darran Lofthouse created SECURITY-733: ----------------------------------------- Summary: Session replication broken by NegotiationAuthenticator valve Key: SECURITY-733 URL: https://issues.jboss.org/browse/SECURITY-733 Project: PicketBox Issue Type: Bug Security Level: Public (Everyone can see) Components: Negotiation Affects Versions: Negotiation_2_2_2 Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: Negotiation_2_2_3 >From an initial review of the code I believe this is because the ClusterSessionValve implements the Listener interface - however the wrapper class does not. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-6943) Cannot reliably uninstall bundles

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-6943: ----------------------------------- Summary: Cannot reliably uninstall bundles Key: AS7-6943 URL: https://issues.jboss.org/browse/AS7-6943 Project: Application Server 7 Issue Type: Bug Components: OSGi Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 8.0.0.Alpha1 There is race condition when #1 Bundle.uninstall() invokes Bundle.unresolve() #2 Bundle.unresolve() takes Module service down #3 INSTALL Phase has a dependency on Module service #4 BundleUninstallProcessor calls Bundle.uninstall() again -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2013