Hi @tahir.manzoor,
Just wondering if there is any update on this issue? I have a similar issue with this class “defaultrandomconfig” while running Aspose words in Oracle.
I tried to grant access to this class using the dbms_java.grant_permissions using the command below
exec dbms_java.grant_permission( ‘ASPOSE’, ‘ASPOSE:com.aspose.words.internal.zzZOP’, ‘defaultRandomConfig’, ‘[defaultRandomConfig]’ );
however I am getting the following error message.
ORA-29532: Java call terminated by uncaught Java exception: java.lang.SecurityException: policy table update ASPOSE:com.aspose.words.internal.zzZOP, defaultRandomConfig
ORA-06512: at "SYS.DBMS_JAVA", line 705
ORA-06512: at line 1
29532. 00000 - "Java call terminated by uncaught Java exception: %s"
*Cause: A Java exception or error was signaled and could not be
resolved by the Java code.
*Action: Modify Java code, if this behavior is not intended.
Thanks
@Sean.dalton
We have linked this forum thread to the same issue (WORDSJAVA-1895). You will be notified via this forum thread once this issue is resolved.
We apologize for your inconvenience.
Are there any updates available on this? We’re running into the same issue using tomcat.
@dandien Сould you please provide more information: what version of the Aspose.Words for Java library are you using, version of Tomcat, sample project source code, and sample document for which the error occurs.
We’re using Aspose.Words 21.12 in Tomcat 9 on oracle-jdk 11.
Providing some source code is not so easy because the security manager ist only activated in our customers integration environment. There the engineer added a permission to the catalina.policy to circumvent the error:
permission com.aspose.words.internal.zzZkK "defaultRandomConfig";
It seems very strange to us, that aspose needs to set a default Secured Random Configuration for bouncycastle.
Is this intended?
Best regards
Daniel
@dandien
The permission:
permission com.aspose.words.internal.zzZkK "defaultRandomConfig";
can be used as a temporary solution to this problem.
We are working on this issue (WORDSJAVA-1895). We will inform you via this forum thread once there is an update available on this issue. We apologize for your inconvenience.
The issues you have found earlier (filed as WORDSJAVA-1895) have been fixed in this Aspose.Words for Java 22.9 update also available on Maven.