November 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Resolved: (JBCACHE-181) Validate and set up a test case for PojoCache using cache loader

by Ben Wang (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-181?page=all ] Ben Wang resolved JBCACHE-181. ------------------------------ Resolution: Out of Date In 2.x release, we reply on cache node-level passivation so this is a non-issue anymore. > Validate and set up a test case for PojoCache using cache loader > ---------------------------------------------------------------- > > Key: JBCACHE-181 > URL: http://jira.jboss.com/jira/browse/JBCACHE-181 > Project: JBoss Cache > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: PojoCache > Affects Versions: PojoCache > Reporter: Ben Wang > Assigned To: Ben Wang > Priority: Minor > Fix For: PojoCache > > Original Estimate: 1 week > Remaining Estimate: 1 week > > We will need to validate and setup a junit test case for JBossCacheAop using cache loader. We have done manually testing before. But we need more extensive testing to validate it. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (EJBTHREE-733) Run-As Semantics Container Task

by Anil Saldhana (JIRA)

Run-As Semantics Container Task ------------------------------- Key: EJBTHREE-733 URL: http://jira.jboss.com/jira/browse/EJBTHREE-733 Project: EJB 3.0 Issue Type: Task Components: Security Affects Versions: EJB 3.0 RC9 - FD Reporter: Anil Saldhana Fix For: EJB 3.0 RC10 - FD This will be the container task for the Run-As semantics validation for the ejb3 layer. -- 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, 6 months

1
2
0 / 0

[JBoss JIRA] Created: (SECURITY-19) Authorization Decision can be affected by deployment level roles

by Anil Saldhana (JIRA)

Authorization Decision can be affected by deployment level roles ---------------------------------------------------------------- Key: SECURITY-19 URL: http://jira.jboss.com/jira/browse/SECURITY-19 Project: JBoss Security Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JBossSX Affects Versions: 2.0 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0 If the user configures roles with principals in the JBoss DD (jboss.xml, jboss-web.xml and jboss-app.xml), these can affect the authorization decision. The Authorization Manager should be aware of these deployment level roles to be passed to the mapping framework (such that if there is an explicit mapping provider that takes into consideration, these deployment level roles), then the overall authorization decision can be affected. -- 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, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-775) Consider deployment level Role-Principals mapping in jboss-app.xml

by Anil Saldhana (JIRA)

Consider deployment level Role-Principals mapping in jboss-app.xml ------------------------------------------------------------------ Key: EJBTHREE-775 URL: http://jira.jboss.com/jira/browse/EJBTHREE-775 Project: EJB 3.0 Issue Type: Task Components: Security Affects Versions: EJB 3.0 RC9 - FD Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: EJB 3.0 RC10 - FD The user may have customized rolename to set of principals mapping in jboss-app.xml, which basically denotes that these role mappings should apply across the application (EAR). Basically the ejb21 and web deployments merge these role mappings with their custom mappings in jboss.xml or jboss-web.xml The ejb3 deployments need to do the same. -- 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, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-776) EJB3 JACC Layer: Consider RunAsIdentity of the Caller Bean

by Anil Saldhana (JIRA)

EJB3 JACC Layer: Consider RunAsIdentity of the Caller Bean ---------------------------------------------------------- Key: EJBTHREE-776 URL: http://jira.jboss.com/jira/browse/EJBTHREE-776 Project: EJB 3.0 Issue Type: Bug Components: Security Affects Versions: EJB 3.0 RC9 - FD Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: EJB 3.0 RC10 - FD If the caller bean has been configured with a RunAsIdentity settings, then the call on the current ejb3 bean needs to consider the run as roles of the caller. -- 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, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (SECURITY-18) Role Mapping Provider to pick up deployment roles

by Anil Saldhana (JIRA)

Role Mapping Provider to pick up deployment roles ------------------------------------------------- Key: SECURITY-18 URL: http://jira.jboss.com/jira/browse/SECURITY-18 Project: JBoss Security Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JBossSX Affects Versions: 2.0 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0 Deployment roles can be configured in any of the JBoss DD (jboss-app.xml,jboss.xml and jboss-web.xml). The ejb21,ejb3 and web layer metamodels all are aware of this. The role mapping provider can pick these role map and map the roles such that the authorization decision can be based on the deployment roles. -- 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, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBREM-625) MicroSocketClientInvoker should decrement count of used sockets when a socket is discarded.

by Ron Sigal (JIRA)

MicroSocketClientInvoker should decrement count of used sockets when a socket is discarded. ------------------------------------------------------------------------------------------- Key: JBREM-625 URL: http://jira.jboss.com/jira/browse/JBREM-625 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.2.0.Alpha3 (Bluto) Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 2.2.0.Alpha3 (Bluto) MicroSocketClientInvoker keeps a counter, usedPooled, of sockets currently in use. When a new socket is created, or when a socket is taken from the socket pool for reuse, usedPooled is incremented, and when the socket is returned to the pool, usedPooled is decremented. However, if a socket experiences a failure (e.g., timeout), the socket is discarded but usedPooled is not decremented. Eventually, usedPooled can reach its maximum value with no working sockets and no possibility of creating new ones. -- 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, 6 months

1
1
0 / 0

[JBoss JIRA] Closed: (JBAS-2570) Ensure JGroups thread is not affected by synchronization issues in DRM.

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2570?page=all ] Brian Stansberry closed JBAS-2570. ---------------------------------- Fix Version/s: JBossAS-4.0.4RC1 (was: JBossAS-5.0.0.Beta) Resolution: Done > Ensure JGroups thread is not affected by synchronization issues in DRM. > ----------------------------------------------------------------------- > > Key: JBAS-2570 > URL: http://jira.jboss.com/jira/browse/JBAS-2570 > Project: JBoss Application Server > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Clustering > Reporter: Brian Stansberry > Assigned To: Brian Stansberry > Fix For: JBossAS-4.0.4RC1 > > > Don't allow the JGroups up-handler thread to call into any methods that may block for extended periods. Make sure all calls from the JGroups thread to DRM.notifyKeyListeners() are handled asynchronously. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBAS-2570) Ensure JGroups thread is not affected by synchronization issues in DRM.

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2570?page=all ] Brian Stansberry reopened JBAS-2570: ------------------------------------ Reopening to correct the Fix Version -- should be 4.0.4.CR1. > Ensure JGroups thread is not affected by synchronization issues in DRM. > ----------------------------------------------------------------------- > > Key: JBAS-2570 > URL: http://jira.jboss.com/jira/browse/JBAS-2570 > Project: JBoss Application Server > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Clustering > Reporter: Brian Stansberry > Assigned To: Brian Stansberry > Fix For: JBossAS-4.0.4RC1 > > > Don't allow the JGroups up-handler thread to call into any methods that may block for extended periods. Make sure all calls from the JGroups thread to DRM.notifyKeyListeners() are handled asynchronously. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1100) ASP support

by Alex Pinkin (JIRA)

ASP support ----------- Key: JBPORTAL-1100 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1100 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Alex Pinkin Fix For: 3.0 Final Portal needs to support ASP environment. In 2.4/2.6 all the roles are global (shared across all Portal instances). -- 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, 6 months

2
1
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 November 2006