Client/Serrver application -- we are having a problem with records failing to upload. It appears that the method I am using in my communication plug-in is that it is trying to open too many connections (one for each Action to be uploaded) and the gateway is refusing them after about 300 connection attempts. During my testing The problem only occurred after about 300 connection attempts. However, I believe that the upper limit is based on total connections used by Apache. I think that Apache is only allowing a total of 500 connection. When there are more actions to be uploaded than there are available connections from Apache then our problem appears.
Need advice/suggestions/solutions, etc..... Linux Server w/ 8GB
One suggestion we looked at wa to implement involves caching the records to be uploaded to a special folder on each client machine ([APP_DATA]/SCI/CACHED_UPLOADS ) Once cached the records will remain in the folder until it is successfully uploaded to the server. It will then be removed from the folder. There will also be an 'attempts' counter. If after a certain number of attempts the records still cannot be uploaded it will be moved to a 'Failed' folder. We can later modify our app to look at this folder for reporting purposes. This method will use a single connection to upload all of the cached files.
I don't like this solution because we need to push script to thousands of client computers. I'd prefer to have solution on the Linux server.