We changed every timeout parameter in the SMP cockpit to very high numbers. None affect the socket disconnect timeout. The timeout is happening in the ssl socket connection
javax.net.ssl.SSLException: Connection has been shutdown
The application is not even loaded. This is happening on the initial application load. The process goes through the the CT and DT loads. Then it starts downloading the application definitions. Exactly 5 minutes after the application definitions start the server closes the socket.
In the ATE the application loads completely because it is fast enough to load before the timeout. The windows ce device loads very slowly and only gets through 1/3 of the rules before the socket is closed.
During the initial application load would the stay connected actually be in affect before the transmit config is even loaded? The socket closing seems to be coming from the server side. Why would the client close the socket before the application is loaded?