Google Analytics

Tuesday, November 17, 2015

The loading of OPSS java security policy provider failed due to exception

ADF development mode "weblogic.security.SecurityInitializationException: The loading of OPSS java security policy provider failed due to exception" is a common issue that most of the ADF developers face.

Solutions:

1) Disable the virus guard and try. Still issue exists, consider point 2.

2) Close Jdeveloper. Rename the existing DefaultDomain. Open the Jdeveloper. Don't get previous Domain settings to new Domain. Still issue exist, consider point 3.

3) Close Jdeveloper. Find cwallet.sso file under MDW_H\DefaultDomain\config\fmwconfig and give the Admin rights to the file. Open the Jdeveloper. Still issue exists, consider point 4.

4) Close Jdeveloper. Find system-jazn-data.xml corrupted file under MDW_H\DefaultDomain\config\fmwconfig. Replace with newest system-jazn-data.xml file.

>Point 4 is worked for me. In my case jazn-data.xml file size is over 3.5 Mb and seems too big.       Jdeveloper try to merge the Application jazn-data.xml with integrated weblogic system-jazn-data.xml file. 

>If the file application jazn-data.xml file is too big  "java.io.IOException: The process cannot access the file because another process has locked a portion of the file" error occurred and after long time application deploy and run.

>Delete existing application roles to reduce the size. Then remove the application large jazn-data.xml and replace small jazn-data.xml file.

5) Every application deployment jazn-data.xml file overwrite/merge with system-jazn-data.xml file. This error can be stop by avoiding above merging process. Keep setting as below image.





More Details:
https://community.oracle.com/thread/2268436
http://fortunefusionminds.blogspot.com/2014/05/xmlstreamexception-end-document-reached.html

No comments:

Post a Comment