Hi,

I trying to run Integration Server using IBM JDK in order to configure EJB adapter to connect to IBM websphere. I have changed the JAVA_DIR in the server.sh file. I have intalled integration server on Sun platform.

I am getting the following error after the State Manager is started… Did anybody come across this problem… please let me know how you resolved… Thanks in advance.

./server.sh -debug 6 -log none

2003-05-08 14:21:31 BST [ISS.0025.0001C] Integration Server 6.0.1 Build 425
2003-05-08 14:21:31 BST [ISS.0025.0006C] License Manager started
2003-05-08 14:21:32 BST [BAS.0123.0001C] FSData full consistency check is beingD
2003-05-08 14:21:35 BST [ISS.0025.0017C] Repository Manager started
2003-05-08 14:21:36 BST [ISS.0025.0024C] JDBC Connection Manager started
2003-05-08 14:21:37 BST [BAS.0123.0001C] FSData full consistency check is being.
2003-05-08 14:21:43 BST [ISS.0025.0023C] Audit Log Manager started
2003-05-08 14:21:43 BST [ISS.0025.0021C] ACL Manager started
2003-05-08 14:21:43 BST [ISS.0025.0008C] State Manager started
java.lang.ExceptionInInitializerError: java.lang.SecurityException: Cannot set s
at javax.crypto.a.(Unknown Source)
at javax.crypto.Cipher.getInstance(Unknown Source)
at com.entrust.toolkit.security.provider.AnsiRandom1.engineSetSeed(Ansi)
at java.security.SecureRandom.(SecureRandom.java:166)
at iaik.security.random.SecRandom.(SecRandom.java)
at com.entrust.toolkit.security.provider.AnsiRandom.(AnsiRandom.j)
at java.lang.Class.newInstance0(Native Method)
at java.lang.Class.newInstance(Class.java:232)
at iaik.security.random.SecRandom.a(SecRandom.java)
at iaik.security.random.SecRandom.getDefault(SecRandom.java)
at com.wm.app.b2b.server.StateManager.init(StateManager.java:63)
at com.wm.app.b2b.server.Server.run(Server.java:215)

What is the exact version of the IBM JDK you switched to? Is it one of the IS supported JVMs?

IS embeds 3rd party cryto libraries that aren’t compatible with changes to Sun jce implementation of Sun 1.4. I think IBM may have bundled their jce implementation based on these changes into their 1.3.1 release also.

I have been able to get IS to run with Sun 1.4.1 by deleting the jce.jar and sunjce_provider.jar, so I assume something similar with get everything to work on IBM.

Maybe someone else can elaborate and confirm the workaround.

IS on Mac OS 10.2.5 and jdk 1.4.1 exhibits the same problem. Removing only the jce.jar file allows IS to start under jdk 1.4.1. Sun’s forums seem to indicate the following three files must be in the same location as the jce.jar file:

local_policy.jar
US_export_policy.jar
sunjce_provider.jar

The 1.4.1 configuration has them dispersed as follows:
1.4.1/Classes/jce.jar
1.4.1/Home/lib/security/local_policy.jar
1.4.1/Home/lib/security/US_export_policy.jar
1.4.1/Home/lib/ext