PK97811: ENTITIES WITH RELATIONSHIPS AS PRIMARY KEYS CAN FAIL METADATA INITIALIZATION

Fixes are available

APAR status

Closed as program error.

Error description

Description:
When OpenJPA initializes entity metadata, entities with
relationships as part of their primary keys (that is, a table's
simple or compound primary key contains a foreign key reference
to another table) may fail to initialize if the metadata for the
referenced entity has not already been initialized.

Local fix

```
N/A
```

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server V7.0                                 *
****************************************************************
* PROBLEM DESCRIPTION: OpenJPA may fail initial metadata       *
*                      processing when an entity's identity    *
*                      includes a relationship with another    *
*                      entity                                  *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
With OpenJPA, initial metadata processing may fail when
entities that utilize a relationship with another entity in
its identity (in other words, a foreign key in one of its
primary key fields) when that particular identity field is
also annotated with @JoinColumn.  When the entity with the
identity relationship is being processed, it attempts to
access the mapping data of the entity its primary key field
maps to, assuming that its mapping data has already been
processed.  If the target entity's metadata has not yet been
processed, a NullPointerException is the result; for example:

Caused by: java.lang.NullPointerException
        at
org.apache.openjpa.jdbc.meta.MappingInfo.mergeJoinColumn(Mapping
Info.java:1400)
        at
org.apache.openjpa.jdbc.meta.MappingInfo.createJoins(MappingInfo
.java:1206)
        at
org.apache.openjpa.jdbc.meta.MappingInfo.createForeignKey(Mappin
gInfo.java:968)
        at
org.apache.openjpa.jdbc.meta.ValueMappingInfo.getTypeJoin(ValueM
appingInfo.java:104)
        at
org.apache.openjpa.jdbc.meta.strats.RelationFieldStrategy.map(Re
lationFieldStrategy.java:157)
        at
org.apache.openjpa.jdbc.meta.FieldMapping.setStrategy(FieldMappi
ng.java:121)
        at
org.apache.openjpa.jdbc.meta.RuntimeStrategyInstaller.installStr
ategy(RuntimeStrategyInstaller.java:80)
        at
org.apache.openjpa.jdbc.meta.FieldMapping.resolveMapping(FieldMa
pping.java:454)

Problem conclusion

The solution was to reorder the list of metadata objects to be
processed as necessary, ensuring that entities which have
relationships in its primary key fields are located after the
entities that they are dependent on.

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.9.  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
PK97811
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-10-02
Closed date
2009-11-10
Last modified date
2009-12-11

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
WEBSPHERE APP S
Fixed component ID
5724J0800

Applicable component levels

R700 PSY
UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
24 October 2021

Tips

PK97811: ENTITIES WITH RELATIONSHIPS AS PRIMARY KEYS CAN FAIL METADATA INITIALIZATION

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

R700 PSY

Document Information

Share your feedback

Need support?