I have been seeing a lot of PingTimeout disconnects in my logs lately on a couple of my servers. I was looking here Ping Timeout and found reasons for what PingTimeout officially is and why it is necessary, but then I just stumbled on an application that doesn’t exhibit the PingTimeout no matter how long you are connected. I’ve been connected for almost 24 hours without issue. Both servers/applications I am looking into are 4.2.0, so just a tad behind. Regardless, the default application PingTimeout in my VHost.xml file is set for 12000 and the application causing the messages has it set for 0 at the bottom of the Application.xml. The application that I have been connected to for almost 24 hours doesn’t even have the PingTimeout defined in its Application.xml. This is most likely because this one was upgraded several times starting way back with version 1.5. The file has been maintained outside of the WSE Manager and it probably started working with the newer versions before getting to the bottom where the PingTimeout directive exists.
Anyway, my question here is…for the server/application that I’ve been connected to for almost 24 hours…does not having the PingTimeout in the Application.xml file in essence turn off or disable the PingTimeout from even happening? If so, I obviously want to correct this, but then does setting it to 0 tell it to use the setting from the VHost.xml file?
I apologize if this was documented somewhere…I couldn’t find it, nor could I find a place in WSE Manager to change the setting in either file.