Problems with WEBUTIL_CORE on OAS 10.1.2 (CLIENT_IMAGE.READ_IMAGE_FILE)

Question

Hello,
I get a problem with webutil 106 on Application Server 10.1.2.0.2 (RedHat 4)
Some functions raise errors as :
oracle.forms.net.ConnectionException: Abandon de la session Forms <839> : communication avec le processus runtime impossible.
at oracle.forms.net.ConnectionException.createConnectionException(Unknown Source)
at oracle.forms.net.HTTPNStream.getResponse(Unknown Source)
at oracle.forms.net.HTTPNStream.doFlush(Unknown Source)
at oracle.forms.net.HTTPNStream.flush(Unknown Source)
at java.io.DataOutputStream.flush(Unknown Source)
at oracle.forms.net.StreamMessageWriter.run(Unknown Source)
For testing, I use the demo form WU_TEST_106 and I encounter this problem with :
CLIENT_IMAGE.READ_IMAGE_FILE
I get another problem with SHOWBEANS(FALSE) that doesn't terminate (showbeans(true) works fine)
I've tried others Webutil functions that works fine
I've another platform with same release of Webutil / OAS 10.1.2 / Redhat4 which works fine (the major difference is that OAS was installed with portal in this last platform).
I've made those test with same client and same database (10g)
Any ideas ?

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