We associate the SLSB to the custom-rmi-invoker in our jboss.xml file:
| <session> | <ejb-name>OptimizerPilot</ejb-name> | <jndi-name>OptimizerPilotBean</jndi-name> | <local-jndi-name>OptimizerPilotLocal</local-jndi-name> | <configuration-name>Sniffer Stateless SessionBean</configuration-name> | <invoker-bindings><invoker> | <invoker-proxy-binding-name>custom-rmi-invoker</invoker-proxy-binding-name> | </invoker></invoker-bindings> | <clustered>true</clustered> | | <method-attributes> | </method-attributes> | </session> | | >From looking at the snippet of the server.log in my previous post I can see >that it is calling the ClientInterceptorSniffer class which is listed in the >custom-rmi-invoker client interceptor list. But I do not see any debug >tracing where it is calling any of the classes listed in the >client-interceptors "HOME" section. With the org.jboss.invocation TRACE >turned on I expect to see some TRACE lines when it hits the InvokerInterceptor. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3910674#3910674 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3910674 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
