April 2008 - jboss-dev-forums - Jboss List Archives

[Design of Messaging on JBoss (Messaging/JBoss)] - ClassLoader behaviour on remote clustering tests

by flavia.rainone＠jboss.com

We are seeing an unexpected class loader behaviour in the remote clustering tests, which is resulting in a RuntimeException thrown by JBoss AOP, when aop is run in classical instrumentation mode. The cause of this exception is that JBoss AOP is trying to create a class that has already been created and loaded... JBoss AOP tries to create such a class because the class loader that defined the class is not able of loading the same class, which is totally unexpected. Look at the pseudocode below: ClassLoader myLoader = ....; | Class class = myLoader.defineClass(....); | System.out.println("Same class loader: " + (myLoader == class.getClassLoader())); | System.out.println("I wanted to use this loader: " + loader); | System.out.println("I got a class with this loader: " + loadedClass.getClassLoader()); | myLoader.load(class.getName()); | The call you can see at the second line is actually made by Javassist, through reflection... the code above is a simplification. The result of the code above, when run by JBoss AOP during class generation. is a ClassNotFoundException preceeded by the messages: | Same class loader: false | I wanted to use this loader: sun.misc.Launcher$AppClassLoader@1a5ab41 | I got a class with this loader: org.jboss.test.messaging.tools.container.ClassLoaderJMXWrapper@6fa9fc | Since the call defineClass has been made to sun.misc.Launcher$AppClassLoader@1a5ab41, we need this class to be able of loading the class later, instead of throwing a ClassNotFoundException. Does anybody know why we are seeing this behaviour? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4142731#4142731 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4142731

18 years

1
0
0 / 0

[Design of JBossCache] - Re: Design of JBCACHE-1316

by manik.surtani＠jboss.com

Agreed. No issues with putting this in branch 1.4.X, 2.1.X and trunk. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4142720#4142720 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4142720

18 years

1
0
0 / 0

[Design of JCA on JBoss] - Re: JBPAPP-750 - Integration between AS and JBossMessaging 1

by vickyk

"adrian(a)jboss.org" wrote : | Why? What's the use case? | I am considering the following jsp as the use case , it contains the similar code what was present in the testcase that failed ;) <%@page import="javax.naming.*,javax.jms.*,org.jboss.tm.TransactionManagerLocator,javax.transaction.*,org.jboss.tm.TxUtils"%> | <% | Queue queue = (Queue) new InitialContext().lookup("queue/testQueue"); | ConnectionFactory cf = (ConnectionFactory) new InitialContext().lookup("java:TestJmsLocal"); | TransactionManager tm = TransactionManagerLocator.getInstance().locate(); | tm.begin(); | | try | { | out.println(tm.getTransaction()+"Transaction status --->"+TxUtils.getStatusAsString(tm.getTransaction().getStatus())+" "); | Connection c = cf.createConnection(); | out.println(tm.getTransaction()+"Transaction status --->"+TxUtils.getStatusAsString(tm.getTransaction().getStatus())+" "); | try | { | c.start(); | out.println(tm.getTransaction()+"Transaction status --->>>>>>>>"+TxUtils.getStatusAsString(tm.getTransaction().getStatus())+" "); | Session s = c.createSession(true, Session.SESSION_TRANSACTED); | | out.println(tm.getTransaction()+"Transaction status -------->"+TxUtils.getStatusAsString(tm.getTransaction().getStatus())+" "); | } | finally | { | try | { | c.close(); | } | catch (Exception ignored) | { | } | } | } | finally | { | out.println(tm.getTransaction()+"Transaction status --->"+TxUtils.getStatusAsString(tm.getTransaction().getStatus())+" "); | try{ | tm.commit(); | } | catch(Exception exp) | { | out.println("EXP is "+exp+"caused by: "+exp.getCause()); | exp.printStackTrace(); | } | out.println(tm.getTransaction()); | } | %> Should the above jsp work for the following CF definition ? <tx-connection-factory> | <jndi-name>TestJmsLocal</jndi-name> | <rar-name>jms-ra.rar</rar-name> | <connection-definition>org.jboss.resource.adapter.jms.JmsConnectionFactory</connection-definition> | <config-property name="SessionDefaultType" type="java.lang.String">javax.jms.Topic</config-property> | <config-property name="JmsProviderAdapterJNDI" type="java.lang.String">java:/TestJMSLocalProvider</config-property> | <max-pool-size>20</max-pool-size> | <application-managed-security/> | </tx-connection-factory> View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4142718#4142718 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4142718

18 years

1
0
0 / 0

[Design of JBossCache] - Re: Design of JBCACHE-1316

by galder.zamarreno＠jboss.com

"manik.surtani(a)jboss.com" wrote : In 1.4.X, shouldn't the bounded buffer also be initialised with something a bit bigger than the default 1024? +1. One step at the time. I wanted to get solution on trunk agreed and then move on to other branches. The default value is trunk is 500000, so maybe we should use this one as well for 1.4.x? I can't see any reason why it should be different. 1024 is certainly too small. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4142715#4142715 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4142715

18 years

1
0
0 / 0

[Design of JBoss Remoting, Unified Invokers] - Re: Checking in Eclipse project files into Remoting 3 reposi

by trustin

Another option I'd like to suggest to is the migration to Maven 2. As you know JBossAS 5 is also in course of Mavenization, and we will eventually pull dependencies from the Maven repository. Maven still provides ant-task plugin, so we should be able to run any custom tasks we did in Ant. Moreover, IntelliJ and NetBeans have good Maven integration and the plugin for Eclipse is working pretty well now although it's not that comparable to that of NetBeans or IntelliJ. I think it's really good time to mavenize Remoting 3 considering it's in the early stage of development. The build.xml also looks pretty easy for Mavenization. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4142708#4142708 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4142708

18 years

1
0
0 / 0

[Design of JBoss Web Services] - Re: jbossws-common vs. jbossws-framework

by heiko.braun＠jboss.com

Let's put it another way: It's depency issue. Currently stacks do have a dependency on SPI and Common, but not on framework. And that's the way it needs to be. If we throw common and framework together, stacks (container as well) start having a dependency on the framework.jar which would leak SPI implementation details to the dependee. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4142707#4142707 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4142707

18 years

1
0
0 / 0

[Design of JBoss Web Services] - Re: jbossws-common vs. jbossws-framework

by heiko.braun＠jboss.com

anonymous wrote : | yada yada | common is 'common'. framework is an implementation of the SPI. You can live without the later by providing your own, but you cannot live without common. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4142702#4142702 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4142702

18 years

1
0
0 / 0

[Design of JBossCache] - Re: Design of JBCACHE-1316

by manik.surtani＠jboss.com

In 1.4.X, shouldn't the bounded buffer also be initialised with something a bit bigger than the default 1024? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4142694#4142694 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4142694

18 years

1
0
0 / 0

[Design of JBoss Profiler] - Re: JBoss Profiler 2

by jesper.pedersen

Did you remember to Include the following in JAVA_OPTS: -javaagent:jboss-profiler.jar -Djboss-profiler.properties=jboss-profiler.properties (see README.txt) ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4142693#4142693 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4142693

18 years

1
0
0 / 0

[Design of JCA on JBoss] - Re: JBPAPP-750 - Integration between AS and JBossMessaging 1

by adrian＠jboss.org

"vickyk" wrote : | Rather than having these changes being a part of testsuite I think they should be part of jms/jca as this would eventually make jms/jca as generic resource adapter. | Why? What's the use case? The testsuite use case is to emulate a jms server that doesn't support XA using JBoss Messaging that does. :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4142684#4142684 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4142684

18 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums April 2008