Customer moved to 1.5.0_24-rev-b07 from 5u19. They now report an intermittent crash with the following trace.

----------------- lwp# 5086 / thread# 5086 --------------------
 ff2cc8d0 _lwp_kill (6, 0, ff335008, ff2ac158, ffffffff, 6) + 8
 ff241a4c abort (7400, 1, 7c00, eea74, ff333418, 0) + 110
 fee869e0 __1cCosFabort6Fi_v_ (1, 0, ff01d54c, fefe8000, 7d64, 7c00) + 58
 fef1721c __1cHVMErrorOreport_and_die6M_v_ (0, ff045fc8, ff03f59c, 1, fee8adbc, ff03f59c) + c84
 fea793fc JVM_handle_solaris_signal (b, 82fddd00, 82fdda48, 8000, ff03e548, 4275038) + ab4
 ff2c8d08 __sighndlr (b, 82fddd00, 82fdda48, fea78910, 0, 1) + c
 ff2bd3a0 call_user_handler (b, ffbffeff, c, 0, 95510200, 82fdda48) + 3b8
 ff2bd588 sigacthandler (b, 82fddd00, 82fdda48, 47eebf8, 0, 0) + 60
 --- called from signal handler with signal 11 (SIGSEGV) ---
 96bb53c8 soft_des_encrypt_common (47eebf0, 82fddecc, 18, 82fddecc, 82fdeecc, 18) + cc
 96bb64b0 C_EncryptUpdate (3, 82fddecc, 18, 82fddecc, 82fdeecc, 7) + 10c
 971651c0 Java_sun_security_pkcs11_wrapper_PKCS11_C_1EncryptUpdate (42750f4, fe997988, 0, 96ef6a80, 1000, 82fdeecc) + 138
 f8c0c280 * sun/security/pkcs11/wrapper/PKCS11.C_EncryptUpdate(JJ[BIIJ[BII)I+0
 f8c0c224 * sun/security/pkcs11/wrapper/PKCS11.C_EncryptUpdate(JJ[BIIJ[BII)I+0
 f8c058b8 * sun/security/pkcs11/P11Cipher.implUpdate([BII[BII)I+54 (line 461)
 f8c058b8 * sun/security/pkcs11/P11Cipher.engineUpdate([BII[BI)I+18 (line 402)
 f8c058b8 * javax/crypto/Cipher.update([BII[BI)I+60
 
They claim this is a pkcsll bug, one they want fixed.