Sometimes, when you create a JDBC Connection in your Designer, or when you configure a JDBC Connection in your EAR, You might end up with an error like this :-
java.sql.SQLRecoverableException: IO Error: Connection reset
(In your trace file)
This happens because of urandom
/dev/random is a random number generator often used to seed cryptography functions for better security. /dev/urandom likewise is a (pseudo) random number generator. Both are good at generating random numbers. The key difference is that /dev/random has a blocking function that waits until entropy reaches a certain level before providing its result. From a practical standpoint, this means that programs using /dev/random will generally take longer to complete than /dev/urandom.
With regards to why /dev/urandom vs /dev/./urandom. That is something unique to Java versions 5 and following that resulted from problems with /dev/urandom on Linux systems back in 2004. The easy fix was to force /dev/urandom to use /dev/random. However, it doesn’t appear that Java will be updated to let /dev/urandom use /dev/urandom. So, the workaround is to fake Java out by obscuring /dev/urandom to /dev/./urandom which is functionally the same thing but looks different.
Therefore, Add the following Field to bwengine.tra and designer.tra OR your Individual track’s tra file and restart the bwengine or designer and it works like Magic Johnson’s Dunk.