January 2008 - jboss-jira - Jboss List Archives

[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

18 years, 3 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

18 years, 3 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

18 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-225) Attachment should not be part of ManagedObject serialization contract

by Scott M Stark (JIRA)

Attachment should not be part of ManagedObject serialization contract --------------------------------------------------------------------- Key: JBMICROCONT-225 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-225 Project: JBoss MicroContainer Issue Type: Bug Reporter: Scott M Stark Fix For: JBossMC-2.0.0.Beta10 The serialization of the metadata attachment from ManagedObject/ManagedProperty implementations leaks server side types to clients. This requires the clients have server side jars in their classpath even though they types are not used. -- 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

18 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JGRP-667) Occasionally, messages get too large for the UDP transport

by Bela Ban (JIRA)

Occasionally, messages get too large for the UDP transport ---------------------------------------------------------- Key: JGRP-667 URL: http://jira.jboss.com/jira/browse/JGRP-667 Project: JGroups Issue Type: Bug Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.6.2, 2.7 When message bundling is enabled (say max_bytes=60K), every now and then we get a larger message (say 70K), and then the msg is dropped because UDP has a size limit of 65K. This can happen as follows: - Either magic-map.xml is not found or some headers are not in magic-map - Say we accumulated 100 messages in the message bundler. Before adding a new message, the bundler checks its size (Message.size()), which calls size() on all headers - A header just assumes it has a magic number and returns its size, including 2 bytes for the magic number (a short) - If magic-number.xml is not found, or some headers have no magic number, then we write the fully qualified classname of the class into the stream. So let's assume that's 30 bytes versus the 2 size() returned. - If we have 3 headers/msg which have the additional 28 bytes, and 100 messages, then the serialized message is 8400 bytes larger than what Message.size() returned - So the marshalled message is now 68400 bytes and it will get discarded by UDP ! -- 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

18 years, 3 months

1
3
0 / 0

[JBoss JIRA] Created: (JGRP-672) jg-magic-map.xml: simplification

by Bela Ban (JIRA)

jg-magic-map.xml: simplification -------------------------------- Key: JGRP-672 URL: http://jira.jboss.com/jira/browse/JGRP-672 Project: JGroups Issue Type: Task Reporter: Bela Ban Assigned To: Bela Ban Priority: Minor Fix For: 2.7 Also remove the DTD -- 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

18 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBWEB-99) PHP servlet and context path

by Thomas Heute (JIRA)

PHP servlet and context path ---------------------------- Key: JBWEB-99 URL: http://jira.jboss.com/jira/browse/JBWEB-99 Project: JBoss Web Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBoss Web Server 1.0.1 GA Reporter: Thomas Heute Assigned To: Jean-Frederic Clere By testing an existing app, i realized that $_SERVER['PHP_SELF'] was not set correctly. By definition: http://ch2.php.net/reserved.variables =================== 'PHP_SELF' The filename of the currently executing script, relative to the document root. For instance, $_SERVER['PHP_SELF'] in a script at the address http://example.com/test.php/foo.bar would be /test.php/foo.bar. =================== Unfortunately in the JBossWeb environement we have the context path in between. So getting that variable on http://www.example.com/myContextPath/foo/test.php returns "/foo/test.php" when it should return "/myContextPath/foo/test.php" In order to have existing PHP application working with no modification, $_SERVER['PHP_SELF'] should start with the context path. In general, other SERVER properties should be checked to see their meaning in JBossWeb. It would also be convenient to have access to the context path from a PHP script. -- 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

18 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1185) When the super class of an EJB3 MDB implements the same business interface a second time an "unable to determine messagingType interface for MDB" exception is thrown

by Roland Räz (JIRA)

When the super class of an EJB3 MDB implements the same business interface a second time an "unable to determine messagingType interface for MDB" exception is thrown --------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: EJBTHREE-1185 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1185 Project: EJB 3.0 Issue Type: Bug Affects Versions: AS 4.2.2.GA Reporter: Roland Räz The class org.jboss.ejb3.mdb.MDB.getMessagingType() throws a RuntimeException("unable to determine messagingType interface for MDB") when a s super class of an MDB implements the business interface. To fix this bug the org.jboss.ejb3.ProxyFactoryHelper.getBusinessInterfaces(clazz) method could use internally a Set instead of a list, this would be preferred and least surprising semantic in my opinion. Caused by: java.lang.RuntimeException: unable to determine messagingType interface for MDB at org.jboss.ejb3.mdb.MDB.getMessagingType(MDB.java:88) at org.jboss.ejb3.interceptor.EJB3InterceptorsFactory.getBusinessInterfaces(EJB3InterceptorsFactory.java:167) at org.jboss.ejb3.interceptor.EJB3InterceptorsFactory.isBusinessMethod(EJB3InterceptorsFactory.java:122) at org.jboss.ejb3.interceptor.EJB3InterceptorsFactory.createPerJoinpoint(EJB3InterceptorsFactory.java:98) ... 154 more -- 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

18 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JGRP-671) JMX: ReceivedBytes and ReceivedMessages are not updated correctly

by Bela Ban (JIRA)

JMX: ReceivedBytes and ReceivedMessages are not updated correctly ----------------------------------------------------------------- Key: JGRP-671 URL: http://jira.jboss.com/jira/browse/JGRP-671 Project: JGroups Issue Type: Bug Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.4.2, 2.6.2, 2.7 I'm currently looking at the JMx implementation in jGroups 2.6.1. It seems that using a Receiver on a Channel does not update the number and size of received messages: the dumpStats operation and the attributes ReceivedBytes and ReceivedMessages return a false result. The deprecated method receive in the class JChannel increments the variables received_msgs and received_bytes. I think the method up(Event) in the class JChannel should also update the counters. Do you agree? -- 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

18 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-228) Add support for excluded packages to VFSClassLoaderPolicy

by Scott M Stark (JIRA)

Add support for excluded packages to VFSClassLoaderPolicy --------------------------------------------------------- Key: JBMICROCONT-228 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-228 Project: JBoss MicroContainer Issue Type: Feature Request Reporter: Scott M Stark Assigned To: Scott M Stark Fix For: JBossMC-2.0.0.Beta10 Right now one has to specify all the packages to export if not all should be exported. Typically one only knows what should not be exported, for example, java.*, javax.servlet.*. VFSClassLoaderPolicy would need to support a Set<String> of package prefixes that should not be included in the package determination visitation. -- 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

18 years, 3 months

1
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 January 2008