Deadlock occurs when starting an OracleAS application.

Document ID : KB000020383
Last Modified Date : 14/02/2018
Show Technical Document Details

 Introduction:

 The introscope Agent tries to get a crypto provider to generate a random number.  It requests an IBM crypto provider. So, it seems to lock the class "com.ibm.crypto.provider.SecureRandom".

 During this lock, it requests the lock on "sun.security.provider.Sun" and it seems that the deadlock is on these resources.  Introscope does not directly lock on any of  these resources, but looks like the security setting does.

 

 Environment:  

 Introscope Agent 9.1x, 9.5x and 9.6x

 

 Instructions: 

 Change the "java.security" file of the IBM JDK to reorder the JCE providers so that IBM JCE is the first choice.