The custom-rmi-invoker has not been associated with any container (certainly not the "Sniffer Stateless SessionBean" shown here. See the invoker-proxy-binding-name in the jboss_4_0.dtd:
| <!ELEMENT container-configuration (container-name , call-logging?, | invoker-proxy-binding-name?, sync-on-commit-only?, | insert-after-ejb-post-create?, call-ejb-store-on-clean?, container-interceptors? , | instance-pool? , instance-cache? , persistence-manager? , web-class-loader? , | locking-policy? , container-cache-conf? , container-pool-conf? , | commit-option? , optiond-refresh-rate? , security-domain?, cluster-config?, | depends*)> | | <!-- The invoker-proxy-binding-name elements maps to the name element of | an invoker-proxy-binding definition. | | Used in: container-configuration, invoker | --> | <!ELEMENT invoker-proxy-binding-name (#PCDATA)> | | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3910471#3910471 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3910471 ------------------------------------------------------- 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
