PM55510: INSUFFICIENT DIAGNOSTIC INFO FOR BLUEPRINT.XML INVALIDSYNTAXEXCEPTIONS.

8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15

APAR status

• Closed as program error.

Error description

• Insufficient Diagnostic Info for blueprint.xml
  InvalidSyntaxExceptions.
  
  If a blueprint.xml file has a syntax error, WSAS correctly fails
  to deploy the EBA, but does not provide any diagnostic
  information about where the error was found.  This is a critical
  for developers, as finding the problem requires looking
  through potentially every blueprint.xml file hoping to visually
  find what WSAS has already found programmatically.
  
  For example, the below reference has a syntax error:
  
  -
  filter=?osgi.jndi.service.name=myJndiResource?/>
  -
  
  The filter is missing parenthesis, so the above should have been
  -
  filter=?(osgi.jndi.service.name=myJndiResource)?/>
  --
  
  
  WSAS console reports the following error:
  
  -----------------------------------------------------------
  The exception
  "com.ibm.ws.eba.admin.application.modeller.ModellerException:
  ..
  org.osgi.framework.InvalidSyntaxException: Missing ( at
  characeter 2" occured.
  
  Check log for detail.
  ----------------------------------------------------------
  
  As we can see above WSAS does not say what particular bundle has
  the error nor the line number of the problem. The log file
  reports the same error message, with no additional detail.
  

Local fix

• Finding the problem looking through potentially every
  blueprint.xml file
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server deploying OSGi applications.         *
  ****************************************************************
  * PROBLEM DESCRIPTION: Insufficient diagnostic information.    *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  If a syntax error is detected whilst parsing an OSGi filter
  string, the error reported by the application server is not
  clear about the nature of the failure.
  

Problem conclusion

• The code has been altered so that a relevant error message is
  output in the event that the application server fails to parse
  an OSGi filter string successfully.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.0.0.4.  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 is sysrouted FROM one or more of the following:

  PM55366

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

Fix information

• Fixed component name

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R800 PSY

     UP