I agree, the test is wrong in the fact that it serializes a MC bean. Yes there can be multiple kernels within one VM, that still does not preclude a serializable reference to one particular kernel. In actuality I should create a seriailizable object which has both the serializable kernel reference and the name of the service I want to invoke upon. Then after deserialization I can invoke that service via the kernel bus. But I would still need a serializable kernel reference to be able to do that. Maybe a KernelReferenceRegistry which functions similar to the NonSerializableFactory? So I can do KernelReferenceRegistry.getKernelReference(kernel)? But then why not make the Kernel externalizable with it's own lookup map? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4151441#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...