August 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBAS-3205) Backport the latest joesnmp to JBoss 4.0.3SP1 so that the jboss.bind.address can be used.

by Ryan Campbell (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3205?page=all ] Ryan Campbell updated JBAS-3205: -------------------------------- Security: Public (was: JBoss Internal) > Backport the latest joesnmp to JBoss 4.0.3SP1 so that the jboss.bind.address can be used. > ----------------------------------------------------------------------------------------- > > Key: JBAS-3205 > URL: http://jira.jboss.com/jira/browse/JBAS-3205 > Project: JBoss Application Server > Issue Type: Support Patch > Security Level: Public(Everyone can see) > Components: Other > Affects Versions: JBossAS-4.0.3 SP1 > Reporter: Darran Lofthouse > Assigned To: JBN Patch Team > > Backport the upgrade to joesnmp 0.3.4 to JBoss 4.0.3 SP1 so that the jboss.bind.address value can be used by the snmp-adapter service without conflicts. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-3094) PooledInvoker/PooledInvokerHA pooling problems, incomplete fix for JBAS-2500

by Ryan Campbell (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3094?page=all ] Ryan Campbell updated JBAS-3094: -------------------------------- Security: Public (was: JBoss Customer) > PooledInvoker/PooledInvokerHA pooling problems, incomplete fix for JBAS-2500 > ---------------------------------------------------------------------------- > > Key: JBAS-3094 > URL: http://jira.jboss.com/jira/browse/JBAS-3094 > Project: JBoss Application Server > Issue Type: Support Patch > Security Level: Public(Everyone can see) > Components: Remoting > Affects Versions: JBossAS-4.0.3 SP1, JBossAS-4.0.4.CR2, JBossAS-3.2.8.SP1 > Reporter: Scott M Stark > Assigned To: JBN Patch Team > > The previous patch/fix for pooling conflicts when both HA/non-HA pooled invokers were in use done in JBAS-2500 resulted in the connections not being pooled across all pooled invoker proxies. The real problem was not the shared connection pool, it was an invalid equals algorithm in the server address object used as the key into the shared pool. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-3057) JBAS-2500 Patch for JBoss 4.0.3SP1

by Ryan Campbell (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3057?page=all ] Ryan Campbell updated JBAS-3057: -------------------------------- Security: Public (was: JBoss Customer) > JBAS-2500 Patch for JBoss 4.0.3SP1 > ---------------------------------- > > Key: JBAS-3057 > URL: http://jira.jboss.com/jira/browse/JBAS-3057 > Project: JBoss Application Server > Issue Type: Support Patch > Security Level: Public(Everyone can see) > Components: Clustering, EJB2, Remoting > Affects Versions: JBossAS-4.0.3 SP1 > Reporter: Galder Zamarreno > Assigned To: Ryan Campbell > > Port the fix for JBAS-2500 to 4.0.3SP1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 11 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBAS-3057) JBAS-2500 Patch for JBoss 4.0.3SP1

by Ryan Campbell (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3057?page=all ] Ryan Campbell closed JBAS-3057. ------------------------------- > JBAS-2500 Patch for JBoss 4.0.3SP1 > ---------------------------------- > > Key: JBAS-3057 > URL: http://jira.jboss.com/jira/browse/JBAS-3057 > Project: JBoss Application Server > Issue Type: Support Patch > Security Level: Public(Everyone can see) > Components: Clustering, EJB2, Remoting > Affects Versions: JBossAS-4.0.3 SP1 > Reporter: Galder Zamarreno > Assigned To: Ryan Campbell > > Port the fix for JBAS-2500 to 4.0.3SP1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-2818) Patch for JBAS-2813 - client sockets when JMS Singleton leaves the cluster

by Ryan Campbell (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2818?page=all ] Ryan Campbell updated JBAS-2818: -------------------------------- Security: Public (was: JBoss Customer) > Patch for JBAS-2813 - client sockets when JMS Singleton leaves the cluster > -------------------------------------------------------------------------- > > Key: JBAS-2818 > URL: http://jira.jboss.com/jira/browse/JBAS-2818 > Project: JBoss Application Server > Issue Type: Support Patch > Security Level: Public(Everyone can see) > Components: JMS service > Affects Versions: JBossAS-4.0.3 SP1 > Reporter: Adrian Brock > Assigned To: Ryan Campbell > > This is a backport of the fix to "throw off" clients when the JMS Singleton stops > on a server but that server instance process does not terminate. > e.g. it leaves the cluster. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 11 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBAS-2818) Patch for JBAS-2813 - client sockets when JMS Singleton leaves the cluster

by Ryan Campbell (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2818?page=all ] Ryan Campbell closed JBAS-2818. ------------------------------- > Patch for JBAS-2813 - client sockets when JMS Singleton leaves the cluster > -------------------------------------------------------------------------- > > Key: JBAS-2818 > URL: http://jira.jboss.com/jira/browse/JBAS-2818 > Project: JBoss Application Server > Issue Type: Support Patch > Security Level: Public(Everyone can see) > Components: JMS service > Affects Versions: JBossAS-4.0.3 SP1 > Reporter: Adrian Brock > Assigned To: Ryan Campbell > > This is a backport of the fix to "throw off" clients when the JMS Singleton stops > on a server but that server instance process does not terminate. > e.g. it leaves the cluster. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 11 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBAS-3045) Security patch for isUserInRole(String) for same principal name

by Ryan Campbell (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3045?page=all ] Ryan Campbell closed JBAS-3045. ------------------------------- > Security patch for isUserInRole(String) for same principal name > --------------------------------------------------------------- > > Key: JBAS-3045 > URL: http://jira.jboss.com/jira/browse/JBAS-3045 > Project: JBoss Application Server > Issue Type: Support Patch > Security Level: Public(Everyone can see) > Affects Versions: JBossAS-4.0.3 SP1 > Reporter: Scott M Stark > Assigned To: Ryan Campbell > Priority: Critical > > As described in JBAS-3043, the JBossSecurityMgrRealm mapping of Principal to GenericPrincipal is not using an application level scope and so if there are multiple web apps with the same principal, but different roles, there is a conflict in the principal to role mapping logic. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-3045) Security patch for isUserInRole(String) for same principal name

by Ryan Campbell (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3045?page=all ] Ryan Campbell updated JBAS-3045: -------------------------------- Security: Public (was: JBoss Customer) > Security patch for isUserInRole(String) for same principal name > --------------------------------------------------------------- > > Key: JBAS-3045 > URL: http://jira.jboss.com/jira/browse/JBAS-3045 > Project: JBoss Application Server > Issue Type: Support Patch > Security Level: Public(Everyone can see) > Affects Versions: JBossAS-4.0.3 SP1 > Reporter: Scott M Stark > Assigned To: Ryan Campbell > Priority: Critical > > As described in JBAS-3043, the JBossSecurityMgrRealm mapping of Principal to GenericPrincipal is not using an application level scope and so if there are multiple web apps with the same principal, but different roles, there is a conflict in the principal to role mapping logic. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 11 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBAS-2691) LdapLoginModule role filter leads to extra role or NPE and failed authentication

by Ryan Campbell (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2691?page=all ] Ryan Campbell closed JBAS-2691. ------------------------------- > LdapLoginModule role filter leads to extra role or NPE and failed authentication > -------------------------------------------------------------------------------- > > Key: JBAS-2691 > URL: http://jira.jboss.com/jira/browse/JBAS-2691 > Project: JBoss Application Server > Issue Type: Support Patch > Security Level: Public(Everyone can see) > Affects Versions: JBossAS-4.0.3 SP1 > Reporter: Scott M Stark > Assigned To: Ryan Campbell > > The change to support control over the search depth introduced a faulty role filter query that could return extra roles or fail with an NPE when a match without the expected role attribute was seen. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-2691) LdapLoginModule role filter leads to extra role or NPE and failed authentication

by Ryan Campbell (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2691?page=all ] Ryan Campbell updated JBAS-2691: -------------------------------- Security: Public (was: JBoss Customer) > LdapLoginModule role filter leads to extra role or NPE and failed authentication > -------------------------------------------------------------------------------- > > Key: JBAS-2691 > URL: http://jira.jboss.com/jira/browse/JBAS-2691 > Project: JBoss Application Server > Issue Type: Support Patch > Security Level: Public(Everyone can see) > Affects Versions: JBossAS-4.0.3 SP1 > Reporter: Scott M Stark > Assigned To: Ryan Campbell > > The change to support control over the search depth introduced a faulty role filter query that could return extra roles or fail with an NPE when a match without the expected role attribute was seen. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 11 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 August 2006