March 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMX-11) Create an MBeanServerBuilder that reproduces JBossMX behaviour with the JDK MBeanServer

by Adrian Brock (JIRA)

Create an MBeanServerBuilder that reproduces JBossMX behaviour with the JDK MBeanServer --------------------------------------------------------------------------------------- Key: JBMX-11 URL: https://jira.jboss.org/jira/browse/JBMX-11 Project: JBossMX Issue Type: Feature Request Components: mbeanserver Reporter: Adrian Brock Assignee: Adrian Brock Fix For: JBossMX.6.0.0.GA To be able to use the JDK MBeanServer with JBoss we need to wrap it with something that reproduces JBossMX features. * Remembering the classloader used to create/register an MBean and setting that as the TCL for invocations * Returning that classloader from getClassLoaderFor() * Simulating the JBossMX MBeanRegistry -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JGRP-943) FC: set ignore_synchronous_response to true by default

by Bela Ban (JIRA)

FC: set ignore_synchronous_response to true by default ------------------------------------------------------ Key: JGRP-943 URL: https://jira.jboss.org/jira/browse/JGRP-943 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Priority: Minor Fix For: 2.6.9, 2.8 This changes the default from false to true -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
2
0 / 0

[JBoss JIRA] Commented: (JBAS-1602) Can't use container level taglibs

by C?dric Chantepie (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-1602?page=com.atlassian.jira.plug... ] C?dric Chantepie commented on JBAS-1602: ---------------------------------------- Is it possible to have taglib jar in ear/lib ? I've struts jar in ear/lib, its classes can be found in war, but not struts tlds . It seems that other people have the same problem (http://lists.jboss.org/pipermail/jboss-user/2009-February/147299.html) > Can't use container level taglibs > --------------------------------- > > Key: JBAS-1602 > URL: https://jira.jboss.org/jira/browse/JBAS-1602 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web (Tomcat) service > Reporter: Stan Silvert > Assignee: Scott M Stark > Priority: Critical > Fix For: JBossAS-4.0.2 Final > > Attachments: EmbeddedServletOptions.java, TldLocationsCache.java > > > JBoss/Tomcat needs a way to install tag libraries globally so they are available to all web applications. This functionality is mentioned in the JSP 2.0 spec section 7.3.5. In Tomcat standalone, you can do this, but it doesn?t work in JBoss/Tomcat. > The way this works is that the Jasper TldLocationsCache ?Scans all JARs accessible to the webapp's classloader and its parent classloaders for TLDs.? > If I put my jar into Tomcat standalone?s common/lib directory then the tag library will be shared across all web apps. I?ve tried putting the jar in several ?well known? locations in JBoss/Tomcat and nothing seems to work. > For Reference, I?ve attached the TldLocationsCache source code from Tomcat 5.5.8. > Concerning TldLocationsCache, Scott Stark says: > "This class is useless for non-URLClassLoaders and URLClassLoaders that do not expose their classpath via getURLs which is what we currently do because of an old bad behavior with annotated codebases of rmi classes. " > Remy Maucherat offered this as a possible solution: > Would it be possible to have the ENCLoader facade return more interesting things ? > /** > * A trival extension of URLClassLoader that uses an empty URL[] as its > * classpath so that all work is delegated to its parent. > */ > static class ENCLoader extends URLClassLoader > { > private URL[] urllist = new URL[0]; > ENCLoader(ClassLoader parent) > { > super(new URL[0], parent); > } > void addURLInternal(URL url) > { > URL[] result = new URL[urllist.length + 1]; > for (int i = 0; i < urllist.length; i++) > result[i] = urllist[i]; > result[urllist.length] = url; > urllist = result; > } > public URL[] getURLs() > { > return urllist; > } > } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2363) Documentation says Spec version 2.0, but contents are still 1.0

by Magesh Kumar B (JIRA)

Documentation says Spec version 2.0, but contents are still 1.0 --------------------------------------------------------------- Key: JBPORTAL-2363 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2363 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Portlet Affects Versions: 2.7.0 Final Reporter: Magesh Kumar B The JavaDoc documentation pointed at this place: http://docs.jboss.com/jbportal/v2.7.0/javadoc-bundle/portlet/ says "javax.portlet The javax.portlet package defines the API for Java Portlet Specification V2.0.", but whereas the contents are not 2.0, but rather version 1.0. For eg., in http://docs.jboss.com/jbportal/v2.7.0/javadoc-bundle/portlet/javax/portle... the method addProperty(javax.servlet.http.Cookie) is missing. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1795) Fix the ChangeXMLUnitTestCase to be more robust

by jaikiran pai (JIRA)

Fix the ChangeXMLUnitTestCase to be more robust ----------------------------------------------- Key: EJBTHREE-1795 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1795 Project: EJB 3.0 Issue Type: Bug Components: testsuite Affects Versions: 1.1.3 Reporter: jaikiran pai Assignee: jaikiran pai During the current EJB3 1.1.3 release, it was observed that org.jboss.ejb3.test.changexml.ChangeXMLUnitTestCase fails when run with other tests (particularly involving a security/security domain test). Running only this specific testcase gets it passing. The testcase is not very robust, the way it currently is: -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAOP-711) Add support to annotations on a pointcut's args list

by Flavia Rainone (JIRA)

Add support to annotations on a pointcut's args list ---------------------------------------------------- Key: JBAOP-711 URL: https://jira.jboss.org/jira/browse/JBAOP-711 Project: JBoss AOP Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 2.1.0.CR1 Reporter: Flavia Rainone There are currently no support to annotations on a pointcut's arguments list. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1546) ERROR [util.JMSFactory] Could not lookup connection factory

by devarshi pathak (JIRA)

ERROR [util.JMSFactory] Could not lookup connection factory ----------------------------------------------------------- Key: JBMESSAGING-1546 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1546 Project: JBoss Messaging Issue Type: Task Components: JMS Clustering Affects Versions: 1.4.3.GA Environment: RedHat Linux Reporter: devarshi pathak Assignee: Tim Fox Fix For: 1.4.3.GA Getting this error after upgrade from 4.0.3 to 4.3.0 in JMS Cluster environment. 2009-03-12 13:27:45,304 ERROR [com.xxx.util.JMSFactory] Could not lookup connection factory javax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

2
10
0 / 0

[JBoss JIRA] Created: (JBAS-6699) EJB verification error message should contain the EJB spec version number

by jaikiran pai (JIRA)

EJB verification error message should contain the EJB spec version number ------------------------------------------------------------------------- Key: JBAS-6699 URL: https://jira.jboss.org/jira/browse/JBAS-6699 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB2 Affects Versions: JBossAS-5.1.0.Beta1 Reporter: jaikiran pai Assignee: Alexey Loubyansky When a EJB2 bean is being deployed, the deployer passes it through a verification stage. When the verification fails, the bean deployment is failed and a message is shown in the logs. Currently, the message does not include the EJB spec version. For example, when the bean remote interface and the bean impl class methods don't have a matching throws clause, the following error message is thrown: 12:59:20,209 WARN [verifier] EJB spec violation: Bean : ejb_Test2 Method : public abstract void testAccess() throws RemoteException Section: 7.10.5 Warning: All the exceptions defined in the throws clause of the matching method of the session bean class must be defined in the throws clause of the method of the remote interface. Note the EJB section referred in this message. This section exists in EJB2.0 spec but not in EJB2.1 spec. So it's important to include the EJB spec version too. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBBOOT-19) ServerLoader causes deployment errors in AS

by Andrew Lee Rubinger (JIRA)

ServerLoader causes deployment errors in AS ------------------------------------------- Key: JBBOOT-19 URL: https://jira.jboss.org/jira/browse/JBBOOT-19 Project: JBoss Bootstrap Issue Type: Bug Affects Versions: 1.0.0-Beta-2 Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger jboss-bootstrap ServerLoader adds all under $JBOSS_HOME/lib to the boot CP, resulting in extra scanning/deployment errors (below). ServerLoader in AS presently takes advantage of an explicit boot set. Until all under $JBOSS_HOME/lib may be loaded, switch up to the explicit boot set for AS. Failed to boot JBoss: java.lang.RuntimeException: Error creating annotation for @org.jboss.aop.microcontainer.aspects.jmx.JMX(name="jboss.system:service=ServiceBindingManager", exposedInterface=org.jboss.services.binding.ServiceBindingManagerMBean.class, registerDirectly=true) at org.jboss.beans.metadata.plugins.AbstractAnnotationMetaData.getAnnotationInstance(AbstractAnnotationMetaData.java:128) at org.jboss.beans.metadata.plugins.AbstractAnnotationMetaData.getAnnotationInstance(AbstractAnnotationMetaData.java:100) at org.jboss.deployers.plugins.managed.BeanMetaDataICF.getManagedObjectClass(BeanMetaDataICF.java:119) at org.jboss.deployers.plugins.managed.BeanMetaDataICF.getManagedObjectClass(BeanMetaDataICF.java:50) at org.jboss.managed.plugins.factory.AbstractManagedObjectFactory.initManagedObject(AbstractManagedObjectFactory.java:342) at org.jboss.managed.api.factory.ManagedObjectFactory.initManagedObject(ManagedObjectFactory.java:77) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.initBootstrapMDs(ProfileServiceBootstrap.java:439) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:242) at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461) at org.jboss.Main.boot(Main.java:216) at org.jboss.Main$1.run(Main.java:546) at java.lang.Thread.run(Thread.java:595) Caused by: java.lang.RuntimeException: java.lang.ClassNotFoundException: org.jboss.services.binding.ServiceBindingManagerMBean at org.jboss.annotation.factory.AnnotationCreator.visit(AnnotationCreator.java:241) at org.jboss.annotation.factory.ast.ASTIdentifier.jjtAccept(ASTIdentifier.java:37) at org.jboss.annotation.factory.AnnotationCreator.visit(AnnotationCreator.java:116) at org.jboss.annotation.factory.ast.ASTMemberValuePair.jjtAccept(ASTMemberValuePair.java:37) at org.jboss.annotation.factory.AnnotationCreator.createAnnotation(AnnotationCreator.java:403) at org.jboss.annotation.factory.AnnotationCreator.createAnnotation(AnnotationCreator.java:449) at org.jboss.beans.metadata.plugins.AbstractAnnotationMetaData.getAnnotationInstance(AbstractAnnotationMetaData.java:119) ... 11 more Caused by: java.lang.ClassNotFoundException: org.jboss.services.binding.ServiceBindingManagerMBean at java.net.URLClassLoader$1.run(URLClassLoader.java:200) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:242) at org.jboss.annotation.factory.AnnotationCreator.visit(AnnotationCreator.java:175) ... 17 mor -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JASSIST-74) modifying a method containing a switch statement using IBM JVM throws ArrayIndexOutOfBoundsException

by Mooky Grand (JIRA)

modifying a method containing a switch statement using IBM JVM throws ArrayIndexOutOfBoundsException ---------------------------------------------------------------------------------------------------- Key: JASSIST-74 URL: https://jira.jboss.org/jira/browse/JASSIST-74 Project: Javassist Issue Type: Bug Affects Versions: 3.8.1.GA Environment: OS: Probably all. I produced it on Windows JVM: does not happen with Sun JVM (at least the versions I used). Does happen with IBM's JVM. I used the following version: java version "1.5.0" Java(TM) 2 Runtime Environment, Standard Edition (build pwi32dev-20060511 (SR2)) IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 Windows XP x86-32 j9vmwi3223-20060504 (JIT enabled) J9VM - 20060501_06428_lHdSMR JIT - 20060428_1800_r8 GC - 20060501_AA) JCL - 20060511a This version comes bundled with Websphere 6.1 ND. The Exact version that I used is "WebSphere Platform 6.1 [ND 6.1.0.0 b0620.14]" Reporter: Mooky Grand Assignee: Shigeru Chiba First the exception that I see: Exception in thread "main" java.lang.ArrayIndexOutOfBoundsException: -2147483648 at javassist.bytecode.CodeIterator.insertGap2(CodeIterator.java(Compiled Code)) at javassist.bytecode.CodeIterator.insertGap0(CodeIterator.java:656) at javassist.bytecode.CodeIterator.insertGap(CodeIterator.java:640) at javassist.bytecode.CodeIterator.insertGapCore(CodeIterator.java:467) at javassist.bytecode.CodeIterator.insert0(CodeIterator.java:370) at javassist.bytecode.CodeIterator.insertEx(CodeIterator.java:339) at javassist.CtBehavior.insertBefore(CtBehavior.java:671) at javassist.CtBehavior.insertBefore(CtBehavior.java:640) at sample.MyTest2.main(MyTest2.java:26) >From the little analysis I did I discovered the following: 1. The problem is not reproduced using Sun's JVM. 2. The method being modified must be of a certain length 3. The method must have a switch statement. 4. The added code should be containe dinside a try-catch block. All of these are demonstrated in my example. MyTest2.java: package sample; import javassist.*; import javassist.expr.*; public class MyTest2 { public static void main(String[] args) throws Exception { ClassPool pool = ClassPool.getDefault(); final CtClass jdbcCt = pool.get("sample.Bla"); final CtMethod fooMethod = jdbcCt.getDeclaredMethod("foo"); String sourceCode = "{" + "System.out.println(\"Bla!\");" + "}"; String toInsert = " try " + " { " + sourceCode + " } " + " catch(Throwable e) " + " { " + " e.printStackTrace(); " + " } "; fooMethod.insertBefore(toInsert); jdbcCt.writeFile(); // update the class file } } Bla.java: package sample; public class Bla { protected void foo() { int j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; j = 4; switch (1) { default: } } } When I remove some of the repeating statements the exception goes away (BTW, if I remove just one there's no exception but the resulting file is corrupted). Essentially, this prevents me from using Javassist under IBM's JVM for large methods that contain switch statements. I've reproduced this problem using javassist 3.4, 3.8 & 3.9. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

2
22
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2009