January 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JGRP-639) UDP: bind MulticastSocket to multicast address

by Bela Ban (JIRA)

UDP: bind MulticastSocket to multicast address ---------------------------------------------- Key: JGRP-639 URL: http://jira.jboss.com/jira/browse/JGRP-639 Project: JGroups Issue Type: Task Reporter: Bela Ban Assigned To: Bela Ban Priority: Minor Fix For: 2.6.2, 2.7 This doesn't work on Windows, so try-catch it and create new MulticastSocket with a wildcard bind address. -- 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
14
0 / 0

[JBoss JIRA] Created: (JGRP-674) ChannelFactory#createMultiplexerChannel bundled state transfer is not symmetric

by Vladimir Blagojevic (JIRA)

ChannelFactory#createMultiplexerChannel bundled state transfer is not symmetric -------------------------------------------------------------------------------- Key: JGRP-674 URL: http://jira.jboss.com/jira/browse/JGRP-674 Project: JGroups Issue Type: Bug Reporter: Vladimir Blagojevic Assigned To: Bela Ban Channel createMultiplexerChannel(String stack_name, String id, boolean register_for_state_transfer, String substate_id) throws Exception method should be invoked on each cluster node. We have previously assumed that a user will invoke createMultiplexerChannel with two parameters on a first cluster node and use 4 parameter invocation on all other nodes. However, this approach is highly non-practical. -- 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
4
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-230) When we have a specific classloader for a bean use it as the context classloader

by Adrian Brock (JIRA)

When we have a specific classloader for a bean use it as the context classloader -------------------------------------------------------------------------------- Key: JBMICROCONT-230 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-230 Project: JBoss MicroContainer Issue Type: Feature Request Components: Dependency Reporter: Adrian Brock Assigned To: Adrian Brock Fix For: JBossMC-2.0.0.CR1 See forum thread for requirements. -- 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] Updated: (JBAS-2614) Add a stress test of region activation/inactivation under load

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2614?page=all ] Brian Stansberry updated JBAS-2614: ----------------------------------- Fix Version/s: JBossAS-5.0.1.CR1 (was: JBossAS-5.0.0.Beta4) > Add a stress test of region activation/inactivation under load > -------------------------------------------------------------- > > Key: JBAS-2614 > URL: http://jira.jboss.com/jira/browse/JBAS-2614 > Project: JBoss Application Server > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Test Suite > Reporter: Brian Stansberry > Assigned To: Brian Stansberry > Priority: Minor > Fix For: JBossAS-5.0.1.CR1 > > Original Estimate: 6 hours > Remaining Estimate: 6 hours > > There are already tests of this in the JBossCache testsuite, but a test that involves the JBossCacheManager layer as well would be good. -- 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
0
0 / 0

[JBoss JIRA] Created: (JBAS-5155) DistributedReplicantManager - Add lookup method to that given a replicant name, returns a List of ClusterNode

by Galder Zamarreno (JIRA)

DistributedReplicantManager - Add lookup method to that given a replicant name, returns a List of ClusterNode ------------------------------------------------------------------------------------------------------------- Key: JBAS-5155 URL: http://jira.jboss.com/jira/browse/JBAS-5155 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering Affects Versions: JBossAS-5.0.0.Beta3 Reporter: Galder Zamarreno Assigned To: Galder Zamarreno Fix For: JBossAS-5.0.0.Beta4 I could do with having a method in DRM like this: public List<ClusterNode> lookupReplicantsNodes(String key); and deprecate lookupReplicantsNodeNames() as it returns a List of String names, which could still be accessible via ClusterNode.getName(). Otherwise, building a List of ClusterNode from, for example. the singleton service name is inefficient. I have to take the singleton name, look up the List of Cluster Node names, and with that list, take ClusterNode list from the partition and match them to create a brand new ClusterNode list with the nodes where the singleton are running. ugh -- 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: (JBAS-5131) Update JBoss Messaging (from 1.4.0.SP3)

by Dimitris Andreadis (JIRA)

Update JBoss Messaging (from 1.4.0.SP3) --------------------------------------- Key: JBAS-5131 URL: http://jira.jboss.com/jira/browse/JBAS-5131 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: JB5-Messaging Reporter: Dimitris Andreadis Assigned To: Tim Fox Fix For: JBossAS-5.0.0.Beta4 Need to bring in the changes Scott has made for: JBMESSAGING-1189 -- 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
4
0 / 0

[JBoss JIRA] Created: (JBAS-5168) Deployers conflict on .sar extension

by jean deruelle (JIRA)

Deployers conflict on .sar extension ------------------------------------ Key: JBAS-5168 URL: http://jira.jboss.com/jira/browse/JBAS-5168 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Deployment services Affects Versions: JBossAS-4.2.2.GA Reporter: jean deruelle Assigned To: Dimitris Andreadis We are currently building a sip servlets (JSR 289) implementation that aims to be able to run both on top of Tomcat and Jboss. (available at https://sip-servlets.dev.java.net/) Unfortunately for us, the specs mandates that compliant containers should be able to deploy sip servlets bundled as a sar archive (.sar extension, same as jboss service archive extension). A valid sar file should contain a sip.xml in its WEB-INF directory. This requirement made me look into Jboss AS 4.2.2.GA code and I found that the current SARDeployer will accept any file with .sar extension (in its accepts method, actually through the SubDeployerSupport accepts method). However if the sar file deployed doesn't contain a META-INF/jboss-service.xml it will fail to deploy. This prevents us to provide our custom Tomcat Deployer to deploy sip servlet archive file (sar file with a sip.xml) We have a proposition to correct the situation so that we can use Jboss as a sip servlets converged container : Provide an accepts method in SARDeployer that enforce checks to see if the sar file contains a META-INF/jboss-service.xml. If not the method would return false and won't accept the deployment, leaving it for our sip servlets deployer to process and accept since it will contain a sip.xml. -- 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
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1223) Make SecurityStore Configurable

by Clebert Suconic (JIRA)

Make SecurityStore Configurable ------------------------------- Key: JBMESSAGING-1223 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1223 Project: JBoss Messaging Issue Type: Feature Request Reporter: Clebert Suconic Assigned To: Scott M Stark Fix For: 1.4.1.GA JBAS 5 needs to generalize SecurityStore as a configurable option. -- 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: (JBAS-5167) Support injection of JGroups Channel into ClusterPartition

by Brian Stansberry (JIRA)

Support injection of JGroups Channel into ClusterPartition ---------------------------------------------------------- Key: JBAS-5167 URL: http://jira.jboss.com/jira/browse/JBAS-5167 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.Beta4 ClusterPartition currently gets its channel by calling JChannelFactory.createMultiplexerChannel(). We need to support direct injection of the channel. This will allow users of the class to move away from the multiplexer and to shared transport channels simply by configuring cluster-beans.xml to inject a shared transport 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
3
0 / 0

[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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2008