Symptoms may include one or more of the following:
Jan 17 13:02:22:478 FATAL [main, udm_manager] java.lang.RuntimeException: java.sql.SQLRecoverableException: IO Error: Connection reset
An unknown error has occurred.
Refreshing your browser may resolve the issue.
com.firehunter.ump.exceptions.DataFactoryException : null
SELECT DISTINCT aa.nimid, aa.alarmSource FROM umpAlarmAnnotations aa
java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist
head -n1 /dev/random
The JDBC 11g needs about 40 bytes of secure random numbers, gathered from /dev/random, to encrypt its connect string. In systems where there are no keyboard or mouse inputs, it is possible that the OS is unable to generate enough entropy noise to fulfill this encryption request.
This fix involves forcing the JVM to utilize a non-blocking random number generator (/dev/urandom) vs the blocking random number generator (/dev/random). To do this, perform the following steps:
There are numerous topics related to the the security concerns of random vs urandom. Testing has shown that urandom is still very secure and that in most environments, hundreds of megabytes of randomness must be generated before numbers became predictable enough to fail a FIPS-140 test. For most environments, utilizing urandom will result in acceptable levels of cryptography and performance.
Please see the following page for detailed information on random vs urandom:
If additional levels of security are required, then there are no options within the UIM product that can resolve this issue. It must be dealt with on the operating system level and involve creating additional sources for entropy. Please see the following Wikipedia page for options on ways to accomplish this goal: