PI14570: The EAR class loader policy is reset to PARENT_FIRST while publishing a second EAR application.

Rational Application Developer for WebSphere Software Fix Pack 1 (9.1.0.1) for 9.1
Rational Application Developer for WebSphere Software Fix Pack 1 (8.5.5.1) for 8.5.5
Rational Application Developer for WebSphere Software 9.1.1
Rational Application Developer for WebSphere Software Fix Pack 2 (8.5.5.2) for 8.5.5
Rational Application Developer for WebSphere Software 9.5
Rational Application Developer for WebSphere Software Fix Pack 1 (9.5.0.1) for 9.5.0
Rational Application Developer for WebSphere Software Fix Pack 3 (8.5.5.3) for 8.5.5
Rational Application Developer for WebSphere Software Fix Pack 2 (9.5.0.2) for 9.5.0
Rational Application Developer for WebSphere Software Fix Pack 3 (9.5.0.3) for 9.5.0

APAR status

• Closed as program error.

Error description

• Abstract:
  
  Attempts to publish a second application to the same WebSphere
  server profile with the same ?AppName? string in the
  application's name results in EAR class loader policy being
  reset to PARENT_FIRST.
  
  Error Description:
  
  1. Create new EAR/WAR projects 'Example' and 'ExampleWeb'.
  2. Create another EAR/WAR pair named 'ExampleServices'.
  3. Create a new WAS 8.5 server profile and start it.
  4. Add the Example EAR to the profile.
  5. Validate that the Example EAR classloader policy is set to
  the default of PARENT_FIRST through WebSphere administrative
  console.
  6. Change the Example EAR classloader order to PARENT_LAST
  through WebSphere Admin Console.
  7. Publish the ExampleServices EAR to the same server.
  8. Validate that the ExampleServices EAR classloader order is
  set to the default of PARENT_FIRST.
  9. At this point the Example EAR classloader order has been
  reset to PARENT_FIRST.
  
  
  
  Local fix:
  
  This issue only happens if the class loader policy is changed
  through WebSphere administrative console. To workaround the
  issue you can change the EAR class loader policy using WebSphere
  Application Server Deployment page:
  
  In the Enterprise Explorer view, right-click your enterprise
  application project folder and select Java EE ? Open WebSphere
  Application Server Deployment.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Attempts to publish a second application to the same
  WebSphere server profile with the same ?AppName? string in
  the application's name results in EAR class loader policy
  being reset to PARENT_FIRST.
  

Problem conclusion

• The fix for this APAR is included in Rational Application
  Developer v8.5.5.1.
  

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

  RATL APP DEV WI

• Fixed component ID

  5724J1901

Applicable component levels

• R851 PSN

     UP