We recently found an issue that i believe closely related to yours. It's still being investigated. You can try to work around it by setting timeout to a non-zero value.
By the way if you are using JBM 1.4.3.GA, I suggest you to update to 1.4.6.GA. There is a good article about how to do it written by a user. Search the forum you will find it.
Thanks for your response.
Setting timeout to a non non-zero value (file remoting-bisocket-service.xml) does not resolve the problem.
I'm going to update to JBM 1.4.6.GA and JBoss Remoting 2.5.2SP1.