Open GoogleCodeExporter opened 9 years ago
Unable to reproduce.
I see behaviour outwardly similar to "expected results" - when you start
ostinato the second time, it starts drone (without checking that it is already
running), but this instance of drone fails to bind to port 7878 so exits with
an error, but Ostinato connects to the original drone already running.
Original comment by pstav...@gmail.com
on 3 Nov 2014 at 3:23
The expected result is that Ostinato will check that drone is running before
connecting to it and no errors occur.
Original comment by developers@plvision.eu
on 6 Nov 2014 at 3:28
Do you see any error now? I don't.
Given that, I don't see what practical difference it would make to check for a
running Drone at Ostinato startup.
Original comment by pstav...@gmail.com
on 12 Nov 2014 at 3:44
Please refer attached screen-shoots of Ostinato application.
Error is shown for second drone.exe and OS tries to process this exception.
To avoid excessive error messages I'm suggesting to add validation "is drone
running" during application start.
Regards,
Hanna
Original comment by developers@plvision.eu
on 13 Nov 2014 at 2:17
Attachments:
Are you sure you are using version 0.6 and not an earlier version? You should
not be seeing the error message on 0.6.
Original comment by pstav...@gmail.com
on 13 Nov 2014 at 4:57
My bad, last Ostinato version on Win XP we have used is 0.5.1.
I'll try to verify this issue on version 0.6.
Original comment by developers@plvision.eu
on 13 Nov 2014 at 5:49
Original issue reported on code.google.com by
developers@plvision.eu
on 24 Oct 2014 at 3:22