Invalid Java Classes and crash in Libj9jit23.so When Configuring and using Database Webservice Callouts ( dbws ) on Aix POWER7 Based Hardware
(Doc ID 1446614.1)
Last updated on MAY 16, 2022
Applies to:Web Services - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
Following Document 469588.1 to perform the setup steps for web services callouts (DBWS) on Oracle database version 18.104.22.168 running on IBM AIX 6.1
Before installing the DBWS utility a check of the database JVM has been performed to determine if invalid classes exist. No invalid classes were found.
Step 11 of the above document asks that the following command be run at the command line:
assuming that the name of the schema created to hold the callout classes is DBWS. The -u value should be altered to reflect the actual schema created in the actual environment.
DBWS will be used as the user created schema reference for the remainder of this note.
The following exception is shown:
Type=Segmentation error vmState=0x0005ff05
J9Generic_Signal_Number=00000004 Signal_Number=0000000b Error_Value=00000000 Signal_Code=00000033
R0=0000000000000000 R1=00000001112F4220 R2=09001000A043A5E0 R3=00000001120EB198
After performing another check for invalid objects, the following is observed:
SQL> select owner, status, count(*) from dba_objects where object_type='JAVA CLASS' group by owner, status;
OWNER STATUS COUNT(*)
------------------------------ ------- ----------
DBWS INVALID 342
Here, DBWS shows 342 invalid objects
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document