unit testing DRb server

[Joe Van Dyk]

Hi,

I'm trying to test a class that starts a DRb server. I have a stop
method in the class that does a @drb_thread.kill. But when I try to
start the DRb server up again, it's throwing an exception:=20
#<Errno::EADDRINUSE: Address already in use - bind(2)>

Any way around that? Do I need to wait a couple seconds between each
run for the port to clear up?

 

[Eric Hodel]

Hi,

I'm trying to test a class that starts a DRb server. I have a stop
method in the class that does a @drb_thread.kill. But when I try to
start the DRb server up again, it's throwing an exception:
#<Errno::EADDRINUSE: Address already in use - bind(2)>

Any way around that? Do I need to wait a couple seconds between each
run for the port to clear up?

Do you really need to test it via DRb? Why not just call the methods
on the front object the regular way and have a single separate test
that makes sure the DRb service gets started correctly?

 

[Joe Van Dyk]

=20
On 29 Aug 2005, at 17:35, Joe Van Dyk wrote:
=20
=20
Do you really need to test it via DRb? Why not just call the methods
on the front object the regular way and have a single separate test
that makes sure the DRb service gets started correctly?

I guess I could do that.

What I'm trying to do is have have DRb servers running on multiple
computers that will start and kill applications, and have another
application that is able to ask that manages all the other computers.