[Design of Messaging on JBoss (Messaging/JBoss)] - Re: ClassLoader behaviour on remote clustering tests
by clebert.suconic@jboss.com
This is interesting:
If I changed ClassLoaderJMSWrapper to look on itself besides the delegate, everything works (even with the latest AOP):
public Class<?> loadClass(String name) throws ClassNotFoundException
| {
| try
| {
| if (name.endsWith("[]"))
| {
| name = name.substring(0, name.length() - 2);
|
| //The classloader of an array type is the classloader of it's element (if non primitive)
|
| Class cl = delegate.loadClass(name);
|
| Object arr = Array.newInstance(cl, 0);
|
| return arr.getClass();
| }
| else
| {
| return delegate.loadClass(name);
| }
| }
| catch (ClassNotFoundException e)
| {
| return super.loadClass(name);
| }
| }
|
Now I have a few question:
Is there any hacks from javassist involved on calling the classLoader (direct calls to internal methods)?
Can you check if you are aways using the correct classloader? This might turn a bug on ClassLoaderJMXWrapper only. We just need to double check.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4142760#4142760
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4142760
18 years
[Design of JBoss Profiler] - Re: JBoss Profiler 2
by lretief
Why would I get this when attempting to stop the profiler?
2008-04-09 15:47:01,783 ERROR [org.jboss.profiler.client.cmd.Client]
java.lang.NullPointerException
at org.jboss.profiler.agent.ClassUtil.getClasses(ClassUtil.java:80)
at org.jboss.profiler.agent.Profiler.stopProfiler(Profiler.java:146)
at org.jboss.profiler.connectors.AbstractHandler.handleCommand(AbstractHandler.java:51)
at org.jboss.profiler.connectors.SocketHandler.invoke(SocketHandler.java:50)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:734)
at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:560)
at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:369)
at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:165)
at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:163)
at org.jboss.remoting.Client.invoke(Client.java:1550)
at org.jboss.remoting.Client.invoke(Client.java:530)
at org.jboss.remoting.Client.invoke(Client.java:518)
at org.jboss.profiler.client.cmd.Client.main(Client.java:252)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4142742#4142742
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4142742
18 years
[Design of JCA on JBoss] - Re: JBPAPP-750 - Integration between AS and JBossMessaging 1
by adrian@jboss.org
"vickyk" wrote :
| 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>
|
Only if TestJMSLocalProvider points at a plain ConnectionFactory, i.e.
one that doesn't implement XAConnectionFactory.
If the jms provider implements XA then don't use a local connection manager
to manage transactions. You end up with the weaker Last Resource Gambit
(i.e. the transaction observer pattern rather than the transaction participant pattern).
But I'm just repeating what I've already said.
I want a real use case not trying to support some broken/stupid configuration.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4142737#4142737
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4142737
18 years