Issue/144 Timeout while trying to contact RemoteTestNG

[missedone]

this is to fix issue #144 by polling the connection with several retries (default as 360, aka. the total wait time is 5 sec (timeout) * 360 = 1800 sec = 30 min)

max retries is configurable on the man launch tab:
max retries

this also fix the issue #155
for example, add breakpoint at java.util.Properties, you can see the job is running wait for connection, rather than report timeout error and exit:
job

here is the log we can see it's polling (in eclipse log):

!ENTRY org.testng.eclipse 1 0 2015-08-16 04:19:28.968
!MESSAGE TestNG viewer connect timeout, will retry 3, max retries 360

!ENTRY org.testng.eclipse 1 0 2015-08-16 04:19:33.969
!MESSAGE TestNG viewer connect timeout, will retry 4, max retries 360

!ENTRY org.testng.eclipse 1 0 2015-08-16 04:19:38.975
!MESSAGE TestNG viewer connect timeout, will retry 5, max retries 360

!ENTRY org.testng.eclipse 1 0 2015-08-16 04:19:43.977
!MESSAGE TestNG viewer connect timeout, will retry 6, max retries 360

!ENTRY org.testng.eclipse 1 0 2015-08-16 04:19:48.981
!MESSAGE TestNG viewer connect timeout, will retry 7, max retries 360

!ENTRY org.testng.eclipse 1 0 2015-08-16 04:19:53.984
!MESSAGE TestNG viewer connect timeout, will retry 8, max retries 360

[missedone]

default max retries as 360, so that the total wait time is 5 sec * 360 = 1800 sec (where 5 sec is the default socket timeout)

[missedone]

i'd like to close this pr as it's based on my wrong understanding of how messafesender work. (though it works so far so good)
will try other option later