RE: Starting JVM from RPGLE through JNI apis with option(java.version 1.4) and having "heap space" messages.

We just upgraded the jdk 1.4 on ISeries box. I used to I start JVM through JNI 
apis from rpgle with option (java.version 1.3). As we upgraded to 1.4, I 
started passing (java.version 1.4) to the JNI api, and all of a sudden The 
following 2 messages started showing up in the joblog. This comes out of 
JNI_CreateJavaVM api. It seems hurmless as,the subsequent programs works as 
usual, but I need to make sure of that.
Anybody encountered this before?
Thanks in advance for any help.
Ali
  

MCH6902    Escape                  40    08/06/03   13:22:37   #hmfremi         
     
  To module . . . . . . . . . :   DLSCTODF37                                    
 
  To procedure  . . . . . . . :   __dl__FPv                                     
 
  Statement . . . . . . . . . :   7            *PRCLT                           
 
  Message . . . . :   The requested heap space operation is invalid.            
 
   Cause . . . . . :   The requested heap space operation is invalid. The heap  
  
  space identifier is 0. The activation group mark is 2. The activation group  
  mark will be zero if the heap space is not associated with an activation     
  group. The error type is 2. The error type indicating why the heap space     
  request is invalid is defined as follows: 0001-Attempt to destroy the        
  default heap space; 0002-Attempt to free or reallocate heap space storage    
  that is not allocated; The heap space identifier and activation group mark   
  may not be valid for this error type; 0003-Access to the heap space is not   
  allowed; 0004-Attempt to mark a heap space that cannot be marked;

C2M1212    Diagnostic              30    08/06/03   13:22:37   QC2UTIL1       
  From module . . . . . . . . :   QC2ALLOC                                  
  From procedure  . . . . . . :   free                                      
  Statement . . . . . . . . . :   1024                                      
  To module . . . . . . . . . :   DLSCTODF37                                
  To procedure  . . . . . . . :   __dl__FPv                                 
  Statement . . . . . . . . . :   7                                         
  Message . . . . :   The pointer parameter passed to free or realloc is not 
valid.  
    Cause . . . . . :   The pointer parameter passed to free or realloc was not 
  valid. This caused your function call to fail. Recovery  . . . :   Correct
  the invalid pointer parameter being passed to free or realloc. Technical  
  description . . . . . . . . :   The value of the pointer passed to free or
  realloc is X'8000000000000000F827EC1301C26540'.