PK58455: RAD 7 LOOSECONFIG PROBLEM CAUSES FILENOTFOUNDEXCEPTION

Rational Application Developer for WebSphere Software, Version 7.0.0.6
Rational Software Architect, Version 7.0.0.6
6.1.1.6: WebSphere Application Server Toolkit Version 6.1.1 Fix Pack 6

APAR status

• Closed as program error.

Error description

• This problem happens in RAD v7, when using a WAS v6.1 server
  and Publishing is set to "Run server with resources within the
  workspace".
  
  The problem happens when one project is trying to reference JAR
  files from another project.  For example, an EAR project is
  referencing JAR files from a separate Web or Java project.
  
  The error looks like this in the SystemErr.log file:
  ----------------------------------------------------------------
  [14/12/07 09:40:57:987 GMT] 0000000a SystemErr     R
  *** ERROR ***: Fri Dec 14 09:40:57 GMT 2007
  org.eclipse.jst.j2ee.commonarchivecore.internal.exception.OpenFa
  ilureException: IWAE0034E Could not open the nested archive
  "jt400.jar" in
  "D:\workspaces\rad7wrk_head\GEAC_enCompass_Enterprise"
      Stack trace of nested exception:
      java.io.FileNotFoundException: IWAE0036E URI Name:
  D:\workspaces\rad7wrk_head\GEAC_enCompass_Enterprise\jt400.jar;
  File name:
  D:\workspaces\rad7wrk_head\GEAC_enCompass_Enterprise\jt400.jar
  ----------------------------------------------------------------
  
  The server is looking for the jar file in the root of the EAR
  project called "GEAC_enCompass_Enterprise".  This is because of
  an incorrect entry in the looseconfig.xmi file such as:
  
  <looseArchives
  xsi:type="org.eclipse.jst.j2ee.commonarchivecore.looseconfig:Loo
  seLibrary" uri="jt400.jar"
  binariesPath="D:\workspaces\rad7wrk_head\GEAC_enCompass_Enterpri
  se\jt400.jar"
  resourcesPath="D:\workspaces\rad7wrk_head\GEAC_enCompass_Enterpr
  ise\jt400.jar"/>
  
  However, the org.eclipse.common.component file shows that the
  jar file is actually located in another project IBM_JDBC_AS400.
  
          <dependent-module deploy-path="/"
  handle="module:/classpath/lib/IBM_JDBC_AS400/jt400.jar">
              <dependency-type>uses</dependency-type>
          </dependent-module>
  

Local fix

• As a temporary work-around, the customer can change Publishing
  to "Run server with resources on the server".  This option does
  NOT use looseconfig.xmi and therefore does not have the problem.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of Rational Application            *
  *                 Developer v7.0 or WebSphere Application      *
  *                 Server Toolkit v6.1.1.                       *
  ****************************************************************
  * PROBLEM DESCRIPTION: JAR files that reside in projects       *
  *                      other than the EAR project are not      *
  *                      properly added to the looseconfig.xmi   *
  *                      file                                    *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  JAR files that reside in projects other than the EAR project
  but are dependencies for the EAR project are not properly
  added to the looseconfig.xmi file.  This causes errors in the
  WebSphere Application Server console window as the runtime is
  unable to properly locate the location of the JAR file and
  therefore causes the application to fail to start.
  

Problem conclusion

• The correct binary URL in the looseconfig will now be used in
  this scenario to ensure that the WebSphere Application Server
  runtime is able to locate the necessary JAR files for the
  application being published to the server.  The fix for this
  APAR is currently targeted for inclusion in the Rational
  Application Developer v7.0.0.6 and WebSphere Application
  Server Toolkit v6.1.1.6 fixapcks.  Please refer to the
  Recommended Updates page for WebSphere Application Server
  Toolkit delivery information:
  http://www.ibm.com/support/docview.wss?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

  WEBAPP SERVER A

• Fixed component ID

  5724J0820

Applicable component levels

• R610 PSY

     UP