Looks like problem is with the sending of the client which is actually LocalClientInvoker. When create a client that points to a server within the same vm, remoting will internally use a local client invoker (by reference calling) instead of remote client invoker (this is done automatically by default). Since the local client invoker has a dirrect reference on the server invoker, can't send it over the wire to another server.
A quick work around for this would be to force the use of the remote client invoker (via 'byvalue' for 1.4.x or 'force_remote' for 2.0.0 property - see http://labs.jboss.com/portal/jbossremoting/docs/guide/ch05.html#section-configuration for detals). However, this should be something that the local client invoker does internally (basically switch itself to remote when being serialized). Have created a jira issue for this - http://jira.jboss.com/jira/browse/JBREM-575. BTW, there has been a good bit of work around transporters done for 2.0.0 release. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3964675#3964675 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3964675 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
