It sounds like a JDBC timeout. In the WebLogic console, go to Services-> Data Sources and click the name of the data source to view its settings. Click the Connection Pool tab and expand the Advanced section at the bottom of the page. Locate Report Timeout Job .
From the documentation :
If Runtime is set to -1, (default), no timeout occurs.
The behavior that you see indicates that the timeout is set to 1800 if it turns off after 30 minutes.
However, this will not change on its own, and if it was already installed, it was previously ignored, which would require some kind of investigation - has something else changed?
Another possibility is that your code makes several calls within a 3-4-hour window, and one of them now exceeds the timeout on its own, which can occur if the timeout is below 1800. Without viewing the code or the current value the timeout that Iām just guessing is obvious.
source share