PM67160: APPLICATION UPDATE OPERATION FAILS WHEN USING THE DEPLOY OPTION "-UPDATE.IGNORE.NEW" ADMA0014E failed validating application.xml

8.5.0.1: WebSphere Application Server V8.5 Fix Pack 1
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2
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

• Application update operation fails when using the deploy option
  -update.ignore.new ; Without this option, application update
  operation succeeds but they lose their existing application
  resources.
  
  ADMA0014E Deployment failed while validating the
  application.xml file
  In a trace that contains "admin=all" you can find the following:
  [6/7/12 8:33:42:249 CEST] 00000000 MapJaspiHelpe 3   taskData
  row [xxxxxxx, META-INF/application.xml, xxxxxx, ] is invalid
  The specifics here are that MAPJASPIHELPER found null value
  If this JaspiRefBindings is null, security code adds default
  provider
  
  (which is an empty string)
  
  If this JaspiRefBindings is non-null, security
  code calls JaspiRefBindings.getProvider() and set the provider
  returned by this api.
  
  Looking at the MapJaspiHelper prepareTask() in the trace,
  providerName is empty or null when it gets passed in.
  

Local fix

• A workaround would be to ensure a non-null value for
  jaspi provider ; this APAR will resolve the issue with
  the deployment when no provider is specified.
  .
  Alternative workaround is to not use the -update.ignore.new
  deploy option
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: Application update task might fail,     *
  *                      if locale setting on a client           *
  *                      is different from a server.             *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Upon composing an object which is used for application
  deployment MBean call, a translated word was used for one of
  parameters. As a result, if a client and a server are
  configured with different locale, the server does not
  recognize the parameter due to inconsistent translated word.
  

Problem conclusion

• With this fix, locale neutral string is used as a parameter.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.0.0.5 and 8.5.0.1.  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:

• 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

• R800 PSY

     UP

• R850 PSY

     UP