Java app running on Windows - 3 bugs 1 feature add

Please don't bid until you have read through this entire post. I need a programmer who will focus on these issues and provide results quickly. We have a Java application that is used to monitor table states in a restaurant. The application is running fairly well but needs three bugs fixed and one feature added. The application has extra code for features we want in the future, but is not completely debugged right now. The extra features are commented out for now. We have one application that is configurable through a .cfg file to be a client and/or a server. There can be only one server in the system but many clients. At anytime, a client can be converted to a server and the old server will become a client. Bug 1: Client network disconnects. After a couple of days a client will disconnect from the server. The client will ping both ways with the server but needs to be restarted to resume application communicates with the server. The requirement is the client should not disconnect for less then two weeks. The problem seems to be that after 8 retries, the client code stops trying to reconnect. But the issue is deeper then the reties running out, it should have reconnected during 8 retries. Right now there are 10 clients on the system and only two clients have disconnected and will not reconnect. Bug 2: Code from a previous programmer saves the IP of the server in the .cfg file. This was done because the programmer refused to broadcast messages from the server and had the code polling for the client to find the server. The most recent programmer fixed the code so it will broadcast making connecting to the server almost immediately. The server IP no longer needs to be saved. The most recent programmer did not understand that the writes to the .cfg file are once in a while corrupting it. He did shut off all writes to the .cfg file and the corruption issue went away, but then when the client was switched to a server, that change was not being saved in the .cfg file so that programmer turned all writes back on bringing back the corruption issue. Bug 3: The switching between server and client, when the writes are working to the .cfg file, sometimes do not get saved to the ,cfg file. When make the switch, the system can be left without a functioning server. Newly needed feature: to update the SSID and network password from the application. I have the server and one client connected to a router that can be accessed from the Internet. The server system and one client has Team Viewer. To do this project, you need to either understand how to use Team Viewer to access the the systems over the Internet OR have two Windows 10 systems to run both applications to debug the code. I will provide the application code so it can be ran on your hardware. This project is to solve three bugs and add one feature to our application. Any additional bugs that are introduced while solving this bug will become part of this project and need to be resolved before the milestone is released. The code you provide should be tested and verified before it is released to my test team. Just throwing code at my test team that does not work and waste their time is not acceptable. You will be given three chances to provide code that function correctly. If the third patch from you does not fix the three bugs and provides the new feature or introduces other bugs, then the milestone will be contested and I will find another programmer to fix the bugs. Before a milestone is released, the source code will be provided to me. The code will have to run error free for two weeks before the milestone is released. You will also select the amount of time it will take you to fix this bug. The amount of time it takes you is part of the programmer selection process. If you do not complete by your end date, then the milestone will be contested and I will find another programmer to fix these bugs. Source code will be provide back to us before the milestone is released.