Problems with Toplink Essentials on OracleAS 10.1.3.1 / OC4J 10.1.3.2

Question

Hi, all.
I successfully installed OracleAS 10.1.3.0 and applied patch 5906151 to update do OAS 10.1.3.1 and OC4J 10.1.3.2, running on both Windows and AIX.
I deployed a j2ee app (ejb-jar and ear/war separatelly) on both. My application runs very well on Windows platform, but fails on AIX.
In order to get my app running with EJB 3.0, JPA and Toplink, I had to copy toplink-essentials.jar to $ORACLE_HOME/j2ee/home/applib/ directory.
On AIX I was getting the following error:
exception occurred during method invocation: javax.ejb.EJBException:
   java.lang.RuntimeException: javax.ejb.EJBException: oracle.toplink.essentials.exceptions.ValidationException
          Exception Description: Error encountered when building the @NamedQuery [MyClass.findAll]
             from entity class [class oracle.toplink.essentials.internal.ejb.cmp3.metadata.queries.MetadataNamedQuery].
         Internal Exception: java.lang.IllegalStateException: ClassLoader "myApp.root:0.0.1"
           (from  in /oracle/product/10.1.3.0/j2ee/OC4J_1/applications/myApp/):
  This loader has been closed and should not be in use.;
But I found a known issue on Metalink [Note:427650.1] (bug 5928776) - https://metalink.oracle.com/metalink/plsql/f?p=130:14:11405609768040641618::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,427650.1,1,1,1,helvetica
I replaced the toplink-essentials.jar and toplink-essentials-agent.jar as stated on the metalink for the version build 41, and tested. And later for the latest build 58.
But I am getting another error message:
Exception [TOPLINK-46] (Oracle TopLink Essentials - 2.0 (Build b58-rc1 (08/05/2007))): oracle.toplink.essentials.exceptions.DescriptorException
Exception Description: There should be one non-read-only mapping defined for the primary key field [MY_TABLE.MY_FIELD].
Descriptor: RelationalDescriptor(xyz.MyClass --> [DatabaseTable(MY_TABLE)])
Runtime Exceptions:
; nested exception is: javax.persistence.PersistenceException: Exception [TOPLINK-0] (Oracle TopLink Essentials - 2.0 (Build b58-rc1 (08/05/2007))): oracle.toplink.essentials.exceptions.IntegrityException
Descriptor Exceptions:
---------------------------------------------------------Does anyone have any idea about this issue?

Answer 1

Seems to be a bug. That was the response from Oracle support (Metalink)
Response:
Your issue seems to be related to bug 5594702 - Abstract: EJB30 ENTITY BEAN WITH @ID AND @COLUMN ANNOTATION FAILS TO DEPLOY ON AIX.
There is an issue with the IBM JDK/JRE 1.5's processing of annotations.
Links:
http://www.theserverside.com/discussions/thread.tss?thread_id=37764
http://www-128.ibm.com/developerworks/forums/dw_thread.jsp?forum=367&thread=112543&cat=10
When processing annotations it returns boolean values as false.
Work-around:
Fully specify the @Column annotation's boolean values. If insertable and updatable are set to false (which will happen due to this bug) then TopLink sets the PK
mapping to read-only and the exception seen is expected.
Note: nullable attribute of the @Colmun is not used in the EJB3/JPA preview of 10.1.3.0 If the customer MUST override the default column name then they should use:
@Column(name="column-name", insertable=true, updatable=true)
If they do not wish to override the default column name then simply do not use an @Column annotation.
It can be deleted or commented out in the JDev generated code.
There are two reported annotation processing issues with the AIX JVM. One was fixed in SR1 and the other is fixed
in SR3 (due out Oc 11 - today). Upgrading to these more recent JVM releases may also address this issue.
RECOMMENDED SOLUTIONS:
1. Upgrade the IBM AIX JVM to SR3.
OR
2. Fix all generated @Column annotations as described above