eFix (APAR): PQ60165

Status:      eFix 

For Release: WebSphere 4.0.2

For Edition: WebSphere AE, AEs

For ContainerTypes: AEServer, AEsServer, ThinClient, J2EE

For Operating System: All

Supersedes eFixes: None; but this efix also come with efixes features from PQ57696 and PQ60580. By installing this efix,
all 3 efixes, PQ57696, PQ60580, and PQ60615, will be installed on customer's system.
                                                                                                  
CMVC defect: PQ60615 

Byte size of APAR: 864,557

Date: 4/29/2002

Abstract: classloader is unable to load a class because servant is not of the expected type

Description/symptom of problem: 

org.omg.CORBA.BAD_PARAM: Servant is not of the expected type.  minor code: 0  completed: No
	at com.ibm.rmi.corba.ClientDelegate.servant_preinvoke(ClientDelegate.java:745)
	at org.omg.CORBA.portable.ObjectImpl._servant_preinvoke(ObjectImpl.java:213)
	at pftest.ejb._PFSessBeanHome_Stub.create(_PFSessBeanHome_Stub.java:225)




Directions to apply efix:

1) Create temporary "efix" directory to store the zip/tar file:
             AIX: /tmp/WebSphere/efix
   Solaris/Linux: /tmp/WebSphere/efix
         Windows: c:\temp\WebSphere\efix

2) Copy zip/tar file to the directory
   (The zip/tar file will be created by WebSphere L2 Support.  It will contain the
    the efix jar file, the readme.txt file, and any other standard information required
    by IBM)

3) Unzip/untar the file

4) Shutdown WebSphere

5) Run the jar file with the following command answering questions/prompts as they appear:
   java -jar <jarfile name>

6) Start AdminServer then bring up AdminConsole

7) Select your application server

8) Select JVM Settings tab and press "Advanced JVM Settings" button to bring up a new window

9) Add the following to Command Line Arguments text field 
   -Djavax.rmi.CORBA.UtilClass=com.ibm.CORBA.iiop.Util  -Dcom.ibm.CORBA.notLocal=true
   
10) Press Ok, then Press Apply

11) Recycle application server

12) Run your testcases.

13) The temp directory may be removed but the zip/tar file should be saved.  Do not remove 
   any files created and stored in the <WASHOME>/WebSphere/AppServer/efix/<APAR#> directories.
   These files are required if an efix is to be removed.



Directions to remove an efix:

NOTE:  EFIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED.  DO NOT REMOVE AN EFIX UNLESS
       ALL EFIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED.  YOU MAY REAPPLY ANY REMOVED EFIX.

Example:  If your system has efix1, efix2, and efix3 applied in that order and efix2 is to be
          removed, efix3 must be removed first, efix2 removed, and efix3 re-applied.


1) Change directory to the efix location (<WASHOME>/WebSphere/AppServer/efix/<APAR#>).

2) Shutdown WebSphere

3) Run the backup jar file with the following command:
   java -jar <backup_APAR#>

4) Restart WebSphere



Directions to re-apply an efix:

Follow the instructions for applying an efix.  If the backup files still exist (from the 
previous efix application), you will be prompted to overwrite.  Answer "yes" at the overwrite 
prompts.


Trouble shooting
--------------------------------------------------------------------------------------
o  If an efix complains about the container type and you are sure it should match, contact
   WebSphere L2 Support for assistance with the -SkipContainerCheck option to the efix jar.

o  If the efix complains about the version of XML parser, move the file 
   $WASROOT/jre/lib/ext/xerces.jar to a temporary location (such as c:\temp), load the efix 
   and move the file back to it's original location.


Additional Information:
-----------------------

This efix PQ60615 is a workaround for symptom, "Servant is not of the expected type". If you wish to use 
"pass-by-reference" for a better system performance, you will not be able to experince any performance  
optimization/enhancement of your system because of using this efix.