...

The JDBC interface might be configured to read from the file /dev/randomurandom to get random numbers. The difference with the /dev/urandomrandom file is, being that /dev/urandom does not block if no random numbers are are  not immediately available.

Check Entropy Pool Issues (Unix)

...

If the "entropy_avail" result is too small (JDBC needs 40 bytes of secure random numbers) then you have to increase the pool by producing some environmental noise. This could be a hurdle, when you operate a headless server (no console) as the noise is produced by keyboard, mouse, login etc.

Check the entropy pool size (normally 4096) with the command:

...

If this solves your problem then the JDBC interface was not able to get random numbers from the OS in good time. Please note that the effect of the given above commands is reverted on reboot.

...

Java holds the security configuration for example with the ./jre/lib/security/java.security or ./conf/security/java.security files. You can modify this file to point to /dev/urandom instead of /dev/random like this:

...

• for JOC Cockpit: js7_jocw.exe
  
  • Example: C:\Program Files\sos-berlin.com\js7\joc\service\js7_jocw.exe
• This brings up a utility that allows Java options to be specified:
  
  
  
  

For further information see JS7 - How To - Apply Java Options.

Network Issues

A wrong network configuration can cause delays when executing Java and when accessing a database, e.g. if host name resolution takes too long. 

...