Intermittent error on x86 chip set: Cannot validate provider JSDP

Question

<p>Hello,</p>
<p>
I am experiencing an intermittant issue on an X86 chip set machine running Solaris 10.
</p>
<p>
I have statically registerd the JSDP provider with the jre used by WLS by adding it to the java.security file:
security.provider.8=com.entegrity.jsdp.security.provider.JSDP
</p>
<p>
I did not copy the jsdp.jar file to the jre ext folder however as this causes class loading issues.
</p>
<p>
This was all that was required to allow the JSDP provider to be trusted by the jvm on sparc solaris 10 machine, however on the X86 machine we get the following error:
</p>
<p>
6/17/08 2:36:29 PM (thread 0 run 0): Aborted run, script threw class java.rmi.RemoteException: Error in ejbCreate:; nested exception is:
javax.ejb.CreateException: java.lang.InstantiationException: java.lang.SecurityException: Cannot validate provider JSDP:java.lang.Securi
tyException: The jar is not signed by a trusted signer
java.rmi.RemoteException: Error in ejbCreate:; nested exception is:
javax.ejb.CreateException: java.lang.InstantiationException: java.lang.SecurityException: Cannot validate provider JSDP:java.lang.Securi
tyException: The jar is not signed by a trusted signer
at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:211)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:338)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:252)
at com.somechumpcomp.at.beans.impl.MadBean_9a7x6e_EOImpl_922_WLStub.getRandom(Unknown Source)
</p>
<p>
I initially appced the ejb on again on the X86 machine and this seemed to resolve the issue however the next day the problem returned, apprantly no one had touched anything..
</p>
<p>
I have asked the ejb vendor to dynamically register the JSDP provider which is used to establish trust of a signed jar file.
</p>
<p>
Does anyone else have any ideas I can try for instance can I register the provider on using environment varibles that I can pass to the WLS managed sercer JVM, or has anyone experienced similar issues on WLS9.2, JDK1.5.11 running on Solaris 10 X86?
</p>
<p>
Hussein Badakhchani
London Middleware
</p>
Edited by hoos at 06/17/2008 7:40 AM

Answer 1

Hello,
What API guide are you looking at? It appears your version of FDM is 9.3.0 and I do not see anything like what you are mentioning in the v9.3.0 API guide.
Keep in mind that newer API guides might not contain all the information from previous releases are are only valid for the release for which they were intended.
On a side note a Permissions Denied - 70 error generally can be traced with ProcessMonitor / ProcessExplorer ... I would start there.
Thank you,