December 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-5066) InstanceInterceptors need to set SecurityContext on EnterpriseContext from Threadlocal

by Anil Saldhana (JIRA)

InstanceInterceptors need to set SecurityContext on EnterpriseContext from Threadlocal -------------------------------------------------------------------------------------- Key: JBAS-5066 URL: http://jira.jboss.com/jira/browse/JBAS-5066 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB2, Security Affects Versions: JBossAS-5.0.0.Beta2 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: JBossAS-5.0.0.Beta3 Currently, the StatelessInstanceInterceptor is doing ctx.setSecurityContext(mi.getSecurityContext()); which leads to an error in the audit log (Note: CLIENT_PROXY) as: -------------------------------------------- 2007-12-09 08:06:25,734 TRACE [org.jboss.security.audit.providers.LogAuditProvid er] (WorkerThread#0[127.0.0.1:1180]:) [Error]roleRefPermissionCheck=true;authori zationManager=[AuthorizationManager:class=org.jboss.security.plugins.JBossAuthor izationManager:CLIENT_PROXY:];roleName=InternalRole;Resource:=[org.jboss.securit y.authorization.resources.EJBResource:contextMap={roleRefPermissionCheck=true, r oleName=InternalRole, authorizationManager=[AuthorizationManager:class=org.jboss .security.plugins.JBossAuthorizationManager:CLIENT_PROXY:]}:method=null:ejbMetho dInterface=null:ejbName=Entity:ejbPrincipal=scott:methodRoles=null:securityRoleR eferences=[]];Source=org.jboss.security.integration.ejb.EJBAuthorizationHelper;E xception:=Authorization Failed: ; ------------------------------------------------------------ what needs to be done is: ctx.setSecurityContext(SecurityActions.getSecurityContext()); For StatefulInstanceInterceptor which gets invoked before SecurityInterceptor, create a new sec ctx based on the container settings. -- 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

16 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1775) Let a user define multiple display-name for a portlet-instance in the admin portlet

by Thomas Heute (JIRA)

Let a user define multiple display-name for a portlet-instance in the admin portlet ----------------------------------------------------------------------------------- Key: JBPORTAL-1775 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1775 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal Core Admin Reporter: Thomas Heute Assigned To: Wesley Hales Fix For: 2.6.3 Final When an administrator creates a new portlet-instance, he should be able to define (and edit) different display-names for a single instance. -- 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

16 years, 11 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-5101) Re-enable JGroups message bundling

by Brian Stansberry (JIRA)

Re-enable JGroups message bundling ---------------------------------- Key: JBAS-5101 URL: http://jira.jboss.com/jira/browse/JBAS-5101 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Minor Fix For: JBossAS-5.0.0.CR1, JBossAS-4.2.3.GA For 4.2.0 JGroups message bundling was disabled pending investigation of JGRP-497. That is fixed in JGroups 2.4.1.SP4. Message bundling improves performance, so we should re-enable 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

16 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBCACHE-1165) Endless loop in PessimisticLockInterceptor

by Jacek Halat (JIRA)

Endless loop in PessimisticLockInterceptor ------------------------------------------ Key: JBCACHE-1165 URL: http://jira.jboss.com/jira/browse/JBCACHE-1165 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.4.1.SP4 Environment: Windows XP, Sun jdk150_06 Solaris 10 Reporter: Jacek Halat Assigned To: Manik Surtani When 2 Threads are simulatanous putting/removing values from this same node TreeCache hang's up and goes into endless loop. Main loop looks like: for (int x = 0; x < 1000; x++) { tm.begin(); System.out.println("R" + Thread.currentThread().getName()); //inside transaction cache.remove("/a"); System.out.println("AR" + Thread.currentThread().getName()); tm.commit(); //outside transaction System.out.println("P" + Thread.currentThread().getName()); cache.put("/a/b/c/d", "text"+x,"b"); System.out.println("AP" + Thread.currentThread().getName()); } -- 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

16 years, 11 months

5
19
0 / 0

[JBoss JIRA] Created: (JBAS-4997) Package StatefulPassivationActivationUnitTestCase with its own HAPartition

by Brian Stansberry (JIRA)

Package StatefulPassivationActivationUnitTestCase with its own HAPartition -------------------------------------------------------------------------- Key: JBAS-4997 URL: http://jira.jboss.com/jira/browse/JBAS-4997 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering, Test Suite Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Minor This test does thousands of invocations from a single thread. This makes it prone to timeout if nagling or JGroups message bundling are enabled on the HAPartition channel, since the single thread doesn't generate enough *concurrent* load to trigger prompt message transmission. We should deploy the test with a partition with its own channel so we don't have to factor this test into whether or not we want nagling/bundling on the standard channel. -- 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

16 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBCACHE-1231) Implicit use of MarshalledValues in the cache

by Manik Surtani (JIRA)

Implicit use of MarshalledValues in the cache --------------------------------------------- Key: JBCACHE-1231 URL: http://jira.jboss.com/jira/browse/JBCACHE-1231 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.0.0.GA, 2.1.0.CR2 Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.1.0.GA Do not use region-based marshalling in the CacheMarshaller; instead, allow for implicit MarshalledValues in the cache which capture the thread's context class loader when an object is inserted into the cache. -- 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

16 years, 11 months

1
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-853) Partial StringProperty replacement in ejb 3 container

by Roland R?z (JIRA)

Partial StringProperty replacement in ejb 3 container ----------------------------------------------------- Key: EJBTHREE-853 URL: http://jira.jboss.com/jira/browse/EJBTHREE-853 Project: EJB 3.0 Issue Type: Feature Request Affects Versions: EJB 3.0 RC9 - FD Reporter: Roland R?z I tried to change the messageSelector in an EJB 3.0 MDB in the ejb.jar.xml containing partial System Property references (aaa${xyz}bbb). Sadly this didn't work as with ejb 2.1. I think fully supporting system property replacement as with ejb 2.x in EJB 3.0 would be a nice feature. The method org.jboss.ejb3.metamodel.EjbJarDDObjectFactory.getValue(String name, String value) could be changed to { value = org.jboss.util.StringPropertyReplacer.replaceProperties(value); } I would suggest, to implement the string property replacement even better in the class org.jboss.metamodel.descriptor.DDObjectFactory.getValue() and remove the getValue method from JBossDDObjectFactory and EjbJarDDObjectFactory. The idea of using an MBean abstraction to replace system properties is fine but the nice syntax of the StringPropertyReplacer should be still supported (${v1,v2:default}). Returning always the replaced property is one possibility (currently it is not done this way) but probably a new method "getReplaced" would be less surprising. -- 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

16 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (JBCACHE-1230) Node.toString() should not print entire contents of a node if it exceeds a certain size

by Manik Surtani (JIRA)

Node.toString() should not print entire contents of a node if it exceeds a certain size --------------------------------------------------------------------------------------- Key: JBCACHE-1230 URL: http://jira.jboss.com/jira/browse/JBCACHE-1230 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.1.0.CR2 Reporter: Manik Surtani Assigned To: Manik Surtani Priority: Minor Fix For: 2.1.0.GA Can be very noisy in the logs -- 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

16 years, 11 months

1
5
0 / 0

[JBoss JIRA] Created: (JBCACHE-1241) Buddy replication, add data to a node and delete root will cause a exception to be thrown

by Mircea Markus (JIRA)

Buddy replication, add data to a node and delete root will cause a exception to be thrown ----------------------------------------------------------------------------------------- Key: JBCACHE-1241 URL: http://jira.jboss.com/jira/browse/JBCACHE-1241 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.1.0.BETA1 Reporter: Mircea Markus Assigned To: Manik Surtani Fix For: 2.1.0.GA, 1.4.X BuddyReplicationTestsBase on trunk was added to reproduce the issue -- 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

16 years, 11 months

2
6
0 / 0

[JBoss JIRA] Created: (JGRP-375) Paralellize discovery phase

by Bela Ban (JIRA)

Paralellize discovery phase --------------------------- Key: JGRP-375 URL: http://jira.jboss.com/jira/browse/JGRP-375 Project: JGroups Issue Type: Feature Request Affects Versions: 2.4 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.6 With TCPPING, if we have 10 servers defined in the list, we sequentially send a GET_MBRS_REQ to each. However, if that server is not reachable, we will timeout out on the socket connect call. Also, DNS lookup might take some time, so we might time out if we cannot contact all servers. Example: servers 1 - 10. 1-9 are down or not reachable, plus we have a slow DNS, 10 is running. So before we get to 10, the discovery will timeout and we will become a singleton node. SOLUTION: use threads from the common (global) thread pool in JGroups to parallelize the sending of requests to all 10 servers. -- 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

16 years, 11 months

3
5
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2007