We have a discovery SmartConnector processor that end unsuccessfully. In the SmartConnector log file we see the following error:
The underlying connection was closed: a connection that was expected to be kept alive was closed by the server
Any idea what is causing the server to close the connection?
Are you able to post the log? I would like to see the messages before that led up to this error. It is hard to say without this what caused this message you are seeing.
If your discovery processor is taking 2.5 hours, that of itself (assuming it simply doing discovery) may point to an issue.
The product in this case is the EBO-OPC server. The discovery processor needs to discover ~25,000 value items. The value items are defined in remote controllers. This is why it takes 2.5 hours.
Is there a time limit for a processor to run? If yes, can this limit be increased?
I am unable to get the log file due confidentiality.
Any idea how to proceed?
The default time limit for a processor to run is 10 minutes, but that can be ignored by adding the ILongRunningProcess interface to your processor, which I am sure you did as it is already running for 2.5 hours. On top of that, I have run processors for months and months at a time with no issues, so this is not the problem here.
As far as the log file, this single error message doesn't tell me enough, is the database connection lost? Server connection lost? Does this happen every time you run it, and fail at the same spot? I really do need more info before I can give additional insight.
Thank you for your answer. It happens every time the processor is started. I will send you a picture of the log I got from the customer (via email due confidentiality).