MID Server timeout when testing JDBCProbes

[Kevin50]

Good morning,

I'm having issues with our SCCM integration with the CMDB. I'm testing the jdbc connection and getting a timeout error. I can't find where I might increase the timeout value or if that would even resolved the issue.

Any suggestions would be greatly appreciated.

Kevin

a

[Chris M3]

First thing to check is that the mid server did actually respond, at some point.  The instance stops waiting for the midserver to respond, but that doesn't mean the midserver just stopped at that point.

Go into your ECC Queue, and check for JDBCProbe Result records.  You can find the OUTPUT JDBCProbe entry, which is the instance telling the midserver to do the work, and then look at the related list for the response to the current entry.  See how long it took for the first one to get back.

What I've found, but I'm not sure if this is consistent, is if the midserver eventually responds, the data does get transformed normally, even if it's an hour later.

[tompowe]

This might be what you need:

https://hi.service-now.com/kb_view.do?sysparm_article=KB0684496

If not....

Looking at documentation for default timeout settings, I see this is set at 300:

mid.windows.probe_timeout

Sets the timeout interval for all Windows probes on a specific MID Server. This value is overridden by the values configured for individual probes with the wmi_timeout probe parameter.

• Type: Integer
• Default value: 300

Also found this, but I doubt this is it:

mid.em.metric_binding_timeout_seconds

Specifies the number of seconds to wait before resending unhandled events Type: Integer Default value: 300

This could also be it, but not sure:

https://hi.service-now.com/kb_view.do?sysparm_article=KB0647585

[tim_broberg]

Try probe parameters query_timeout and connection_timeout in units of seconds.

See also the timeout options when setting up a jdbc connection.