IV21267: GSR0089E IS REPORTED WHEN VIEWING A BUSINESS MODEL THAT HAS A REVERSE RELATIONSHIP SHOWING FROM A MODEL CLASS.

8.0.0.3-WS-WSRR-ZOS-IFIV65487_IV79085_IV87422_IV87429_IV89477
8.0.0.3-WS-WSRR-MultiOS-IFIV65487_IV79085_IV87422_IV87429_IV89477
WebSphere Service Registry and Repository V8.0 Fix Pack 1

APAR status

• Closed as program error.

Error description

• The issue happens when viewing an instance of a business
  model B, which has a reverse relationship showing in the detail
  view,
  where the relationship is from model class A. When any business
  model
  definition loaded into WSRR has multiple super classes, and more
  than one of those super classes has a subclass that is class A.
  

Local fix

• NA
  

Problem summary

• An XPATH query is trying to find any objects related to the
  currently displayed object via a modelled relationship "rel".
  When executing this XPATH, the code finds which specific
  business model this relationship "rel" is defined on. It does
  this by looking through all defined models in the system, and
  all their super classes. The code also checks the subclasses of
  each class when that class is being considered.
  
  For complex inheritance with multiple super classes, the code
  was finding that for a single class, it has many super classes
  and more than one of these super classes appeared to have the
  relationship "rel" defined upon them. The following error was
  put into the WebSphere Application Server console:
  
  Caused by:
  com.ibm.serviceregistry.exception.xpath.XPathInternalException:
  GSR4519E: Ambiguous mapping
   at
  com.ibm.sr.xpath.athene_triplequery.RendererHelper.getBestRelati
  on(RendererHelper.java:164)
   at
  com.ibm.sr.xpath.athene_triplequery.TQContext._step(TQContext.ja
  va:493)
   at
  com.ibm.sr.xpath.athene_triplequery.TQContext.step(TQContext.jav
  a:473)
   at
  com.ibm.sr.xpath.athene_triplequery.Renderer.doPath(Renderer.jav
  a:516)
   at
  com.ibm.sr.xpath.athene_triplequery.Renderer.doPred(Renderer.jav
  a:683)
   at
  com.ibm.sr.xpath.athene_triplequery.Renderer.doPredicate(Rendere
  r.java:596)
   at
  com.ibm.sr.xpath.athene_triplequery.Renderer.doPred(Renderer.jav
  a:628)
   at
  com.ibm.sr.xpath.athene_triplequery.Renderer.doPredicate(Rendere
  r.java:592)
   at
  com.ibm.sr.xpath.athene_triplequery.Renderer.popPred(Renderer.ja
  va:227)
   at
  com.ibm.sr.xpath.athene_triplequery.Renderer.doExistenceChecksFo
  r(Renderer.java:562)
   at
  com.ibm.sr.xpath.athene_triplequery.Renderer.doPredicates(Render
  er.java:547)
   at
  com.ibm.sr.xpath.athene_triplequery.Renderer.doInitialPath(Rende
  rer.java:436)
   at
  com.ibm.sr.xpath.athene_triplequery.Renderer.render(Renderer.jav
  a:274)
   at
  com.ibm.sr.xpath.athene_triplequery.Renderer.transformPropertyQu
  ery(Renderer.java:145)
   at
  com.ibm.sr.athene.persistence.impl.QueryManagerImpl.query(QueryM
  anagerImpl.java:330)
   at
  com.ibm.sr.athene.persistence.impl.QueryManagerImpl.query(QueryM
  anagerImpl.java:160)
   at
  com.ibm.sr.api.ServiceRegistryImpl.executeQuery(ServiceRegistryI
  mpl.java:1811)
  
  The reason that "rel" was thought to be defined on multiple
  super classes was that the code checked each sub-class of the
  super classes, and several of these super-classes had the same
  sub class which had "rel" defined upon it. Thus the code found
  that these super-classes had "rel" defined upon several of them,
  which is an error condition because a relationship can only be
  defined upon one class.
  

Problem conclusion

• The code was removed which checks the sub-classes of every
  class, when it is being examined to see if the class has a
  specific relationship on it.
  

Temporary fix

Comments

APAR Information

• 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

  SERVICE REGISTR

• Fixed component ID

  5724N7200

Applicable component levels

• R750 PSY

     UP

• R800 PSY

     UP