April 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-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

[JBoss JIRA] Created: (EJBTHREE-1260) Performance issue with EjbLinkDemandMetaData

by Guy Coleman (JIRA)

Performance issue with EjbLinkDemandMetaData -------------------------------------------- Key: EJBTHREE-1260 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1260 Project: EJB 3.0 Issue Type: Bug Components: core Affects Versions: AS 5.0.0.Beta4 Reporter: Guy Coleman We have an application with about 200 EJB3 SLSB and MDBs, 120 EJB2 entity beans and a few web apps. This takes about 1-2 minutes to start up with JBoss 4.2.2.GA. With 5.0.0.Beta4 this jumps to around 20-30 minutes. Some thread dumps show that it's spending most of its time here: "main" prio=6 tid=0x044b7430 nid=0x10b4 runnable [0x049cd000..0x049cf9f8] at java.lang.Throwable.fillInStackTrace(Native Method) at java.lang.Throwable.<init>(Throwable.java:196) at java.lang.Exception.<init>(Exception.java:41) at javax.management.JMException.<init>(JMException.java:35) at javax.management.OperationsException.<init>(OperationsException.java:36) at javax.management.MalformedObjectNameException.<init>(MalformedObjectNameException.java:35) at javax.management.ObjectName.construct(ObjectName.java:393) at javax.management.ObjectName.<init>(ObjectName.java:1304) at org.jboss.ejb3.dependency.EjbLinkDemandMetaData$EjbLinkDemandDependencyItem.resolve(EjbLinkDemandMetaData.java:134) at org.jboss.dependency.plugins.AbstractDependencyInfo.resolveDependencies(AbstractDependencyInfo.java:140) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:901) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:839) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:784) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:622) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:411) at org.jboss.system.ServiceController.doChange(ServiceController.java:659) at org.jboss.system.ServiceController.create(ServiceController.java:393) at org.jboss.system.ServiceController.create(ServiceController.java:358) at sun.reflect.GeneratedMethodAccessor212.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:186) Patching EjbLinkDemandMetaData to avoid creating ObjectNames for names that are obviously invalid speed this up considerably: the startup time is then about 5 minutes, though It still seems to spend a lot of time looping in that EjbLinkDemandDependencyItem .resolve -- 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
4
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-129) Implement support for the generic metadata in the javassist implementation of ClassInfo

by Adrian Brock (JIRA)

Implement support for the generic metadata in the javassist implementation of ClassInfo --------------------------------------------------------------------------------------- Key: JBMICROCONT-129 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-129 Project: JBoss MicroContainer Issue Type: Task Components: BeanInfo Affects Versions: JBossMC_2_0_0 Beta Reporter: Adrian Brock The support for generics has only been implemented in the reflection based ClassInfo implementation. This needs doing also for the Javassist implementation. -- 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

6
9
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1392) WSRP does not submit the from when enctype set to "multipart/form-data"

by Andrey Adamovich (JIRA)

WSRP does not submit the from when enctype set to "multipart/form-data" ----------------------------------------------------------------------- Key: JBPORTAL-1392 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1392 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal WSRP Affects Versions: 2.6.CR2 Environment: All Reporter: Andrey Adamovich Assigned To: Chris Laprun We are developing a portlet on BEA WebLogic Portal that is supposed to be consumed later by JBoss Portal. This portlet is used for file data upload. The thing is that portlet contains a form that has enctype attribute set to multipart/form-data to enable file sending. When the form is submitted on the consumer (JBoss) no form parameters are passed to producer. Looking in the WSRP request sent to BEA Portal by JBoss only action name is seen. If enctype attribute is removed from the form then when form is submitted all parameters are sent to producer except file content. -- 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
6
0 / 0

[JBoss JIRA] Created: (JASSIST-42) Proxy serialization looses inner data objects

by Damien Lecan (JIRA)

Proxy serialization looses inner data objects --------------------------------------------- Key: JASSIST-42 URL: http://jira.jboss.com/jira/browse/JASSIST-42 Project: Javassist Issue Type: Bug Reporter: Damien Lecan Assigned To: Shigeru Chiba Priority: Blocker I working with proxies build with ProxyFactory method. When I want to serialize/deserialize it, everything seems to be ok except that only proxy instance is serialized, not inner objects. Eg. Object "A" contains an instance of "B" After serialization/deserialization of a proxy of A, instance of "B" in "A" is null When I look at this code : public static SerializedProxy makeSerializedProxy(Object proxy) throws java.io.InvalidClassException { Class clazz = proxy.getClass(); return new SerializedProxy(clazz, ProxyFactory.getFilter(clazz), ProxyFactory.getHandler(clazz)); } I don't understand how serialization can keep inner objects ... -- 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
11
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 April 2008