When the BC engine starts, The follow exception occurs after the first DB connection:

2025 Nov 08 10:05:08:540 GMT -0500 BW.BusinessConnect-Interior_Server-3 Debug [Level] BW-EXT-LOG-300002 Update check failed: java.net.SocketTimeoutException: connect timed out
at java.net.PlainSocketImpl.socketConnect(Native Method) ~[?:?]
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:412) ~[?:?]
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:255) ~[?:?]
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:237) ~[?:?]
at java.net.Socket.connect(Socket.java:608) ~[?:?]
at sun.net.NetworkClient.doConnect(NetworkClient.java:177) ~[?:?]

The BC engine eventually starts up normally, and handles transactions normally.

all platforms

1. When the TIBCO BusinessConnect (or another BW-based engine) starts up, it initializes a third party library, Ehcache. This library is used for internal caching.

2. Ehcache’s internal update checker thread runs automatically and tries to connect to the default update site: http://www.terracotta.org/download/ehcache-update-check

3. If the customers's environment (customer network or container) has restricted outbound Internet access — likely due to firewalls, proxies, or security monitoring from Dynatrace or corporate policy — the outgoing connection may time out.

4. The result is that the exception:

java.net.SocketTimeoutException: connect timed out

is logged, and then ignored. After that, everything continues normally.

You can eliminate this issue by either:

1.  In the startup JVM options (in your domain script or BW engine launcher), set the java property to see whether the issue can be resolved.

-Dnet.sf.ehcache.skipUpdateCheck=true

or:

2.  Add the following property into deployed BC .tra file:

java.property.net.sf.ehcache.skipUpdateCheck=true

A socket timeout occurs in the BC engine on startup even though the BC engine eventually starts and processes transactions normally.