July 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-5471) Deploying EJB3 service throws "java.lang.RuntimeException: No MBeanServer has been injected"

by Galder Zamarreno (JIRA)

Deploying EJB3 service throws "java.lang.RuntimeException: No MBeanServer has been injected" -------------------------------------------------------------------------------------------- Key: JBAS-5471 URL: http://jira.jboss.com/jira/browse/JBAS-5471 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB3 Affects Versions: JBossAS-5.0.0.Beta4 Reporter: Galder Zamarreno Assigned To: Galder Zamarreno Fix For: JBossAS-5.0.0.CR1 I'm trying to deploy an EJB3 service but I'm unable to do so as the following is thrown: 2008-04-22 17:21:20,640 ERROR [STDERR] (main) Caused by: java.lang.RuntimeException: No MBeanServer has been injected 2008-04-22 17:21:20,641 ERROR [STDERR] (main) at org.jboss.ejb3.deployers.JBossASKernel.installMBean(JBossASKernel.java:135) 2008-04-22 17:21:20,641 ERROR [STDERR] (main) at org.jboss.ejb3.service.ServiceContainer.registerManagementInterface(ServiceContainer.java:587) Please find attached: - source code for EJB3 service - deployment archive - server.log with TRACE on org.jboss.ejb3 I suspect Ejb3JBoss5Deployment should be injecting mbeanServer in the kernelAbstraction but it doesn't: public Ejb3JBoss5Deployment(DeploymentUnit ejb3Unit, Kernel kernel, MBeanServer mbeanServer, org.jboss.deployers.structure.spi.DeploymentUnit jbossUnit, DeploymentScope deploymentScope, JBossMetaData metaData, PersistenceUnitsMetaData persistenceUnitsMetaData) { super(ejb3Unit, deploymentScope, metaData, persistenceUnitsMetaData); this.jbossUnit = jbossUnit; kernelAbstraction = new JBossASKernel(kernel); // todo maybe mbeanServer should be injected? this.mbeanServer = mbeanServer; } I'll have a go at passing the mbeanServer to the kernelAbstraction and see if that fixes 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, 2 months

4
12
0 / 0

[JBoss JIRA] Created: (JBAS-5600) Security Context is remote if it comes as part of invocation

by Anil Saldhana (JIRA)

Security Context is remote if it comes as part of invocation ------------------------------------------------------------ Key: JBAS-5600 URL: http://jira.jboss.com/jira/browse/JBAS-5600 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: EJB2, Security Affects Versions: JBossAS-5.0.0.Beta4 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: JBossAS-5.0.0.CR2 I need to look further into the logic used in PreSecurityInterceptor. I may be doing way too much to derive whether the call was remote or local and accordingly set the security context on the association. The simplest may be to just assume that if there is a security context in the invocation, then it can be inter-vm. Both PresecurityInterceptor and SecurityInterceptor are affected by this change. -- 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, 2 months

3
6
0 / 0

[JBoss JIRA] Created: (JBAS-5520) EJBModule->addMissingMethodPermissions need to be moved to EJBPermissionMapping

by Anil Saldhana (JIRA)

EJBModule->addMissingMethodPermissions need to be moved to EJBPermissionMapping ------------------------------------------------------------------------------- Key: JBAS-5520 URL: http://jira.jboss.com/jira/browse/JBAS-5520 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: EJB2, Security Affects Versions: JBossAS-5.0.0.Beta4 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: JBossAS-5.0.0.CR1 -- 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, 2 months

3
6
0 / 0

[JBoss JIRA] Created: (JBAS-5540) Add test in SecurityContextUnitTestCase to test custom SubjectFactory injection

by Anil Saldhana (JIRA)

Add test in SecurityContextUnitTestCase to test custom SubjectFactory injection -------------------------------------------------------------------------------- Key: JBAS-5540 URL: http://jira.jboss.com/jira/browse/JBAS-5540 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: JCA service, Test Suite Affects Versions: JBossAS-5.0.0.Beta4 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: JBossAS-5.0.0.CR1 Currently we have default JBossSecuritySubjectFactory name used in the ConnectionManagerBuilder. Test addition of a custom subject factory. -- 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, 2 months

3
6
0 / 0

[JBoss JIRA] Created: (JBAS-5513) JBossWebRealm: refactor the three authenticate methods to use a common method

by Anil Saldhana (JIRA)

JBossWebRealm: refactor the three authenticate methods to use a common method ----------------------------------------------------------------------------- Key: JBAS-5513 URL: http://jira.jboss.com/jira/browse/JBAS-5513 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Security, Web (Tomcat) service Affects Versions: JBossAS-5.0.0.Beta4 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: JBossAS-5.0.0.GA The JBossWebRealm has been derived from the legacy JBossSecurityMgrRealm. The 3 authenticate methods have redundant lines of code. So as a first pass cleanup, the three authenticate methods should use a common method that refactors the redundant code. -- 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, 2 months

3
5
0 / 0

[JBoss JIRA] Created: (JBAS-4070) Generalize naming factory and remoting lookup

by Scott M Stark (JIRA)

Generalize naming factory and remoting lookup --------------------------------------------- Key: JBAS-4070 URL: http://jira.jboss.com/jira/browse/JBAS-4070 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.0.0.Beta2 Reporter: Scott M Stark Fix For: JBossAS-5.0.0.CR1 -- 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, 2 months

3
7
0 / 0

[JBoss JIRA] Created: (JGRP-278) Externalization of socket creation in TCP/TCP_NIO (BasicTCP)

by Bela Ban (JIRA)

Externalization of socket creation in TCP/TCP_NIO (BasicTCP) ------------------------------------------------------------ Key: JGRP-278 URL: http://jira.jboss.com/jira/browse/JGRP-278 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.6 User configures a socket factory which creates client and server sockets. There is always 1 default factory configured. This allows developers to override socket creation, e.g. for use with SSL sockets. This way, TCP and TCP_NIO can be used with SSL. -- 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, 2 months

3
11
0 / 0

[JBoss JIRA] Created: (JBAS-4591) Create a generic way to createDestinations on MDB Container

by Clebert Suconic (JIRA)

Create a generic way to createDestinations on MDB Container ----------------------------------------------------------- Key: JBAS-4591 URL: http://jira.jboss.com/jira/browse/JBAS-4591 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JB5-Messaging Reporter: Clebert Suconic Assigned To: Clebert Suconic Fix For: JBossAS-5.0.0.Beta3, JBossAS-4.4.0.CR1 We should provide a generic way to configure the MDB container to create destinations in other providers besidess JBossMQ. The Implementation I'm going to do will use a Property Name for the MBean responsible to create destinations and method names for the create methods. Also... we will support two signatures... one (createTopic(String Topicname) or createQueue(String queueName)) or createTopic(String TopicName, String jndti) or createQueue(String queueName, String jndi) -- 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, 3 months

3
4
0 / 0

[JBoss JIRA] Created: (JASSIST-58) Complie error on autoboxing

by Guy Korland (JIRA)

Complie error on autoboxing --------------------------- Key: JASSIST-58 URL: http://jira.jboss.com/jira/browse/JASSIST-58 Project: Javassist Issue Type: Bug Reporter: Guy Korland Assigned To: Shigeru Chiba e.g. 1. call the following method: void foo(Object obj) as foo(1) causes compile error. 2. casting a primitive to Object causes a compile error e.g.: (Object )1. The first error is caused by the MemberResolver.compareSignature() line 220: if (j < 0 || argTypes[n] != CLASS) return NO; Should be changed to if (j < 0) return NO; The second error caused by CodeGen line 1395: if (type == CLASS) Should be removed -- 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, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JASSIST-43) ConstPool.getItem(int) returns unexpected item, causes exceptions in calling methods; e.g. in getFieldrefClassName(...) and getInterfaceMethodrefClassName(...)

by Martin Burger (JIRA)

ConstPool.getItem(int) returns unexpected item, causes exceptions in calling methods; e.g. in getFieldrefClassName(...) and getInterfaceMethodrefClassName(...) --------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JASSIST-43 URL: http://jira.jboss.com/jira/browse/JASSIST-43 Project: Javassist Issue Type: Bug Environment: $ uname -a Darwin [...] 8.11.1 Darwin Kernel Version 8.11.1: Wed Oct 10 18:23:28 PDT 2007; root:xnu-792.25.20~1/RELEASE_I386 i386 i386 $ java -version java version "1.5.0_13" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_13-b05-241) Java HotSpot(TM) Client VM (build 1.5.0_13-121, mixed mode, sharing) Javassist 3.6.0 Reporter: Martin Burger Assigned To: Shigeru Chiba I am using subclasses of javassist.expr.ExprEditor to heavily instrument classes. On some large (in terms of amount of code) classes I get various exceptions in ConstPool, for example: Caused by: java.lang.ClassCastException: javassist.bytecode.ClassInfo at javassist.bytecode.ConstPool.getFieldrefClassName(ConstPool.java:254) at javassist.expr.FieldAccess.getClassName(FieldAccess.java:97) at javassist.expr.FieldAccess.getCtClass(FieldAccess.java:89) at javassist.expr.FieldAccess.getField(FieldAccess.java:112) And: Caused by: java.lang.NullPointerException at javassist.bytecode.ConstPool.getInterfaceMethodrefClassName(ConstPool.java:413) at javassist.expr.MethodCall.getClassName(MethodCall.java:91) at javassist.expr.MethodCall.getCtClass(MethodCall.java:75) at javassist.expr.MethodCall.getMethod(MethodCall.java:114) It seems that ConstPool.getItem(int) returns an "unexpected" item, so (1) the cast to FieldrefInfo fails and (2) the returned item is null instead of an instance of InterfaceMethodrefInfo, respectively. -- 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, 3 months

2
6
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 July 2008