Beacon causes excessive Seach

[mdavidsaver]

I observe the search retry time being reset after each beacon even at a 15 sec interval (c++ servers later switch to a 3 min. interval). This is with pvAccessJava 4.1.3 (cs-studio 4.3.3b).

The test setup is a PVA client trying to connect to a non-existent PV, and PVA server.

[shroffk]

I tried to recreate your test using the master branch of the java PVAccess library. I adding a print statement to print out the timestamp of when the search request message was being broadcast.

I noticed that the exponential backoff is reset after about 30s.

2018-10-02T09:34:07.563 Local multicast enabled on /224.0.0.128:5076:5076 using Software Loopback Interface 1. 
2018-10-02T09:34:07.599 Channel 'nonExistant' created with status: StatusImpl [type=OK]. 
generating search request message at 2018-10-02T09:34:07.609-0400 for channel nonExistant
generating search request message at 2018-10-02T09:34:07.792-0400 for channel nonExistant
generating search request message at 2018-10-02T09:34:08.227-0400 for channel nonExistant
generating search request message at 2018-10-02T09:34:09.092-0400 for channel nonExistant
generating search request message at 2018-10-02T09:34:10.822-0400 for channel nonExistant
generating search request message at 2018-10-02T09:34:14.280-0400 for channel nonExistant
generating search request message at 2018-10-02T09:34:21.198-0400 for channel nonExistant
generating search request message at 2018-10-02T09:34:35.028-0400 for channel nonExistant
generating search request message at 2018-10-02T09:35:02.683-0400 for channel nonExistant
generating search request message at 2018-10-02T09:35:08.453-0400 for channel nonExistant
generating search request message at 2018-10-02T09:35:08.732-0400 for channel nonExistant
generating search request message at 2018-10-02T09:35:09.166-0400 for channel nonExistant
generating search request message at 2018-10-02T09:35:10.032-0400 for channel nonExistant
generating search request message at 2018-10-02T09:35:11.762-0400 for channel nonExistant
generating search request message at 2018-10-02T09:35:15.220-0400 for channel nonExistant
generating search request message at 2018-10-02T09:35:22.135-0400 for channel nonExistant
generating search request message at 2018-10-02T09:35:35.964-0400 for channel nonExistant
generating search request message at 2018-10-02T09:36:03.619-0400 for channel nonExistant

In the implementation I cannot find an obvious property or setting being used to govern the beacon reset time.