[jboss-user] [JBoss Messaging] - Re: Client Connection Delegate has Null state

2009-03-11 Thread clebert.suco...@jboss.com
"ataylor" wrote : i would suggest migrating to jboss 4.2.3.

+1

If you really have to use JBAS 4.0.X at your client, you will have to play with 
classLoader isolations, and have all the JBAS 4.2 libraries on that isolated 
classLoader, in a way that your WEB/EAR application would behave as any other 
standalone application.

That's a sour procedure and error prone... it's probably easier to migrate to 
4.2.3.

View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4216966#4216966

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4216966
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [JBoss Messaging] - Re: Client Connection Delegate has Null state

2009-03-11 Thread ataylor
i would suggest migrating to jboss 4.2.3.

View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4216878#4216878

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4216878
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [JBoss Messaging] - Re: Client Connection Delegate has Null state

2009-03-10 Thread mmarcuci
I've updated the aop jar to the recommended version and now get this error

Caused by: java.lang.AbstractMethodError: getLoaderRepository
at org.jboss.aop.AspectManager.instance(AspectManager.java:340)
at org.jboss.aop.AspectManager.instance(AspectManager.java:255)
at 
org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.(ClientConnectionFactoryDelegate.java)
at sun.misc.Unsafe.ensureClassInitialized(Native Method)
at 
sun.reflect.UnsafeFieldAccessorFactory.newFieldAccessor(UnsafeFieldAccessorFactory.java:25)
at 
sun.reflect.ReflectionFactory.newFieldAccessor(ReflectionFactory.java:122)
at java.lang.reflect.Field.acquireFieldAccessor(Field.java:918)
at java.lang.reflect.Field.getFieldAccessor(Field.java:899)
at java.lang.reflect.Field.getLong(Field.java:528)
at 
java.io.ObjectStreamClass.getDeclaredSUID(ObjectStreamClass.java:1614)
at java.io.ObjectStreamClass.access$700(ObjectStreamClass.java:52)
at java.io.ObjectStreamClass$2.run(ObjectStreamClass.java:425)
at java.io.ObjectStreamClass.(ObjectStreamClass.java:413)
at java.io.ObjectStreamClass.lookup0(ObjectStreamClass.java:310)
at java.io.ObjectStreamClass.lookup(ObjectStreamClass.java)
at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:547)
at 
java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1583)
at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1496)
at 
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1732)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
at 
java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1947)
at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1871)
at 
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
at java.rmi.MarshalledObject.get(MarshalledObject.java:142)
at 
org.jnp.interfaces.MarshalledValuePair.get(MarshalledValuePair.java:72)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:652)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587)
at javax.naming.InitialContext.lookup(InitialContext.java:392)


It looks as thought the implementation of AOPScopedClassLoaderHelper that is 
used within AspectManager does not implement this method.  The only 
implementation in my classpath is JBossScopedClassLoaderHelper, and the class 
signature doesn't have this method.  The class is defined in 
jboss-aspect-library-jdk50.jar, version jboss-aspect-library-1.5.

View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4216800#4216800

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4216800
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [JBoss Messaging] - Re: Client Connection Delegate has Null state

2009-03-10 Thread clebert.suco...@jboss.com
We used AOP 1.5.5.GA on JBossMessaging 1.4.0.SP3.

There's probably some inconsistency around AOP and JBAS 4.0.3?

Look at the JBM Documentation at the specific version you are using, to verify 
about these dependencies.


BTW: I believe JBM has been set to run on JBAS 4.2+. I know you're talking 
about the client, but maybe you will need to play with classLoader isolations 
to get that working.



View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4216743#4216743

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4216743
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user