InterceptorChain

[mmarcuci]

How are Interceptors determined for the JBossConnectionFactory on the messaging client? I'm trying to create regular JBoss Messaging connections, and have two setups one which works and one that doesn't. When I step through the code, I end up in createConnectionDelegate. The difference I'm finding is that within a MethodInfo reference, the setup that works has a StateCreationAspect0 in the interceptorChain, while the one that doesn't have an empty chain.

[gaohoward]

I think you can have a look at the aop configuration file and get an idea about it. It in the source :
integration/EAP4/etc/aop-messaging-client.xml

[mmarcuci]

I don't think that file is anywhere in my path. I looked inside all the jars I'm using and didn't see it anywhere. Is it on the server side? The -client part of the file leads me to think no.

[clebert.suconic]

It's on the server side.

org.jboss.jms.client.ClientAOPStackLoader will download it and install it on the client side.

[mmarcuci]

That's what's strange to me. Basically, I have two clients one running as a standalone process and one running inside a second jboss instance. The standalone one seems to get the correct AOP stack to create connections, but the client running inside jboss does not. Could it possibly be loading from the wrong file?

[clebert.suconic]

"mmarcuci" wrote:
That's what's strange to me. Basically, I have two clients one running as a standalone process and one running inside a second jboss instance. The standalone one seems to get the correct AOP stack to create connections, but the client running inside jboss does not. Could it possibly be loading from the wrong file?

I think it will be something else (not related to AOP), but It's impossible to tell without more information. (Stack traces.. logs.. etc.)

You will have to investigate, and ping us with more information if you can't figure out.

Probably there's a classpath issue at one of your clients.

[clebert.suconic]

Probably there's a classpath issue at one of your clients.

I mean...but the classpath issue wouldn't be related to the AOP file. Probably some class missing.

[mmarcuci]

The details of my setups and a stack trace are in this post.
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=151709

Digging through the code I essentially came up with the fact that on the client running within the JBoss appserver the interceptor chain is empty when creating the connection delegate, but within the working client it contains a StateCreationAspect0 object. So basically what I'm trying to determine is why the interceptor chains are different in these two situations.

Thanks for your help thus far.