PI76834: Unable to use DB2 XML data type with EclipseLink JPA; Null pointer produced

Fixes are available

APAR status

Closed as program error.

Error description

An application on WebSphere Application Server Liberty
v16.0.0.3 is unable to use a JPA object that maps a column
to a
DB2 xml data type.

The application tries to save and retrieve a database row
using
JPA in Liberty. The database engine is DB2 11 LUW.  The
table
has a XML data type column and this column is mapped as a
String in JPA. This worked well using OpenJPA on previous
Liberty and WAS versions, but moving to EclipseLink (JPA
2.1)
causes a null String to be retrieved.  Note that the save
operation works well.  The problem only exists during read
operation.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server Liberty - Java Persistence API       *
*                  (EclipseLink, JPA 2.1)                      *
****************************************************************
* PROBLEM DESCRIPTION: EclipseLink returns a null result when  *
*                      trying to use XML column types for      *
*                      entities. Occurs only when running on   *
*                      JDK > 1.6                               *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
EclipseLink was improperly detecting the JDK platform level. For
JDK  > 1.6, EclipseLink was defaulting to a JDK level of 1.5.
Since java.sql.SQLXML was first introduced in Java 1.6,
EclipseLink and was not able to return the java.sql.SQLXML data
type when running on Java 7+.

Problem conclusion

The fix for this APAR changes the EclipseLink implementation and
involves an update to the EclipseLink thirdparty bundle. See
https://bugs.eclipse.org/bugs/show_bug.cgi?id=462377

The fix for this APAR is currently targeted for inclusion in
Service Level (Fix Pack) 9.0.0.4 of WebSphere Application Server
version 9.0.0 and in fix pack 17.0.0.2 for WebSphere Application
Server Liberty.  Please refer to the Recommended Updates page
for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PI76834
Reported component name
WAS LIBERTY COR
Reported component ID
5725L2900
Reported release
855
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-02-17
Closed date
2017-03-28
Last modified date
2017-03-28

APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name
WAS LIBERTY COR
Fixed component ID
5725L2900

Applicable component levels

R855 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSD28V","label":"WebSphere Application Server Liberty Core"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"855","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
04 May 2022

Tips

PI76834: Unable to use DB2 XML data type with EclipseLink JPA; Null pointer produced

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R855 PSY

Document Information

Share your feedback

Need support?