PM62133: Universal Test Client lookup on remote server may result in an IWAD0401E error code

Interim fix 1 - Rational Application Developer for WebSphere Software, v7.5.5.5

APAR status

• Closed as program error.

Error description

• Abstract:
  
  Attempts to instantiate an EJB on a remote server using the
  Universal Test Client (UTC) result in error IWAD0401E Unknown
  type of JNDI object
  
  Problem:
  
  You want to use the Universal Test Client to test Enterprise
  Java Beans on a remote IBM WebSphere Application Server.
  
  You have verified that:
  
  1. The local and remote WebSphere Application Server have the
  same version, including the same version of the Java Virtual
  Machine.
  
  2. The EJB Project containing the EJBs to be tested is deployed
  to both servers, so that the UTC has access to the EJB Classes
  on its classpath
  
  3. You can use the JNDI Explorer in UTC to browse the remote
  JNDI tree.
  
  4. You are attempting to test an EJB that exposes a Remote
  interface.
  
  Results:
  
  When you try to instantiate the EJB Home, the Universal Test
  Client shows the error:
  
  IWAD0401E Unknown type of JNDI object
  
  If you enable UTC debug traces by launching:
  http://[host]:[port]/UTC/debug
  you see the following in the SystemOut.log file of Websphere
  Application Server:
  
  SystemOut     O UTC: EJB Object: IOR:[IOR_value]
  SystemOut     O UTC: Object cl: null
  
  If you parse the [IOR_value], you can see that it refers to the
  remote server.
  
  Local fix:
  
  There is no known workaround at this time.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The problem was not reproducible by the development team;
  however, a workaround has been delivered for successfully
  loading EJB's in UTC.
  

Problem conclusion

• The fix for this APAR is included in Rational Application
  Developer v7.5.5.5 iFix1.
  

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

• R755 PSN

     UP