IBM Support

PM41934: UNHANDLED EXCEPTION ATTEMPTING RMI CONNECTION WITH RMI CLIENT RUNNING IN A 64-BIT JVM

Fixes are available

7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
Obtain the fix for this APAR.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • In WebSphere Application Server on z/OS, while
    attempting an RMI connection with an RMI client running in a
    64-bit JVM, the client fails with symptoms including:
    
    
    Unhandled exception
    Type=Segmentation error vmState=0x00000000
    J9Generic_Signal_Number=00000004 Signal_Number=0000000b Error_V
    alue=00000000 Signal_Code=00000035
    ...
    
    ----------- Stack Backtrace -----------
    protectedIntrospectBacktraceSymbols+0x84be8ed8 (, 0x00000000000
    00000)
    j9sig_protect+0x84bd51a0 (, 0x0000000000000000)
    j9introspect_backtrace_symbols+0x84be8fb8 (, 0x0000000000000000
    )
    generateDiagnosticFiles+0x8499f930 (, 0x0000000000000000)
    j9sig_protect+0x84bd51a0 (, 0x0000000000000000)
    structuredSignalHandler+0x8499e4d0 (, 0x0000000000000000)
    masterSynchSignalHandler+0x84bd6998 (, 0x0000000000000000)
    (, 0x0000000000000000)
    __zerros+0xceaf9ea8 (, 0x0000000000000000)
    CEEHDSP+0xcef238b8 (, 0x0000000000000000)
    CEEOSIGJ+0xceceeaf0 (, 0x0000000000000000)
    CELQHROD+0xcef10c08 (, 0x0000000000000000)
    CEEOSIGG+0xcecf52a8 (, 0x0000000000000000)
    CELQHROD+0xcef10c08 (, 0x0000000000000000)
    ORB_Request::createStoragePools()+0x836e9e48 (, 0x0000000000000
    000)
    ORB_Request::initializeClass()+0x836ea1d0 (, 0x0000000000000000
    )
    CORBA::ORB::BOA_init(int&,char**,char*)+0x8348c120 (, 0x0000000
    000000000)
    Java_com_ibm_ws390_orb_ORB_BOA_1init+0x8370c7e0 (, 0x0000000000
    000000)
    SIDECARINVOKEREFLECTCONSTRUCTOR+0x849cdcf8 (, 0x000000000000000
    0)
    JVM_NewInstanceFromConstructor+0x848f7170 (, 0x0000000000000000
    )
    Java_sun_reflect_NativeConstructorAccessorImpl_newInstance0+0x8
    4ae3d38 (, 0x0000000000000000)
    SIDECARINVOKEREFLECTMETHOD+0x849ccd68 (, 0x0000000000000000)
    JVM_InvokeMethod+0x848f6230 (, 0x0000000000000000)
    Java_sun_reflect_NativeMethodAccessorImpl_invoke0+0x84ae3d80 (,
     0x0000000000000000)
    SIDECARINVOKEREFLECTMETHOD+0x849ccd68 (, 0x0000000000000000)
    JVM_InvokeMethod+0x848f6230 (, 0x0000000000000000)
    Java_sun_reflect_NativeMethodAccessorImpl_invoke0+0x84ae3d80 (,
     0x0000000000000000)
    RUNCALLINMETHOD+0x849d16a8 (, 0x0000000000000000)
    gpProtectedRunCallInMethod+0x84994838 (, 0x0000000000000000)
    signalProtectAndRunGlue+0x84994a60 (, 0x0000000000000000)
    j9sig_protect+0x84bd51a0 (, 0x0000000000000000)
    gpCheckCallin+0x84991970 (, 0x0000000000000000)
    callStaticVoidMethod+0x8499a630 (, 0x0000000000000000)
    JavaMain+0xcf0f3b08 (, 0x0000000000000000)
    ---------------------------------------
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V7.0                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: While attempting an RMI connection with *
    *                      a client running in a 64-bit JVM, the   *
    *                      client fails.                           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    In WebSphere Application Server on z/OS, while
    attempting an RMI connection with an RMI client running in a
    64-bit JVM, the client fails with symptoms including:
    Unhandled exception
    Type=Segmentation error vmState=0x00000000
    J9Generic_Signal_Number=00000004 Signal_Number=0000000b Error_V
    alue=00000000 Signal_Code=00000035
    ...
    ----------- Stack Backtrace -----------
    protectedIntrospectBacktraceSymbols+0x84be8ed8 (, 0x00000000000
    00000)
    j9sig_protect+0x84bd51a0 (, 0x0000000000000000)
    j9introspect_backtrace_symbols+0x84be8fb8 (, 0x0000000000000000
    )
    generateDiagnosticFiles+0x8499f930 (, 0x0000000000000000)
    j9sig_protect+0x84bd51a0 (, 0x0000000000000000)
    structuredSignalHandler+0x8499e4d0 (, 0x0000000000000000)
    masterSynchSignalHandler+0x84bd6998 (, 0x0000000000000000)
    (, 0x0000000000000000)
    __zerros+0xceaf9ea8 (, 0x0000000000000000)
    CEEHDSP+0xcef238b8 (, 0x0000000000000000)
    CEEOSIGJ+0xceceeaf0 (, 0x0000000000000000)
    CELQHROD+0xcef10c08 (, 0x0000000000000000)
    CEEOSIGG+0xcecf52a8 (, 0x0000000000000000)
    CELQHROD+0xcef10c08 (, 0x0000000000000000)
    ORB_Request::createStoragePools()+0x836e9e48 (, 0x0000000000000
    000)
    ORB_Request::initializeClass()+0x836ea1d0 (, 0x0000000000000000
    )
    CORBA::ORB::BOA_init(int&,char**,char*)+0x8348c120 (, 0x0000000
    000000000)
    Java_com_ibm_ws390_orb_ORB_BOA_1init+0x8370c7e0 (, 0x0000000000
    000000)
    SIDECARINVOKEREFLECTCONSTRUCTOR+0x849cdcf8 (, 0x000000000000000
    0)
    JVM_NewInstanceFromConstructor+0x848f7170 (, 0x0000000000000000
    )
    Java_sun_reflect_NativeConstructorAccessorImpl_newInstance0+0x8
    4ae3d38 (, 0x0000000000000000)
    SIDECARINVOKEREFLECTMETHOD+0x849ccd68 (, 0x0000000000000000)
    JVM_InvokeMethod+0x848f6230 (, 0x0000000000000000)
    Java_sun_reflect_NativeMethodAccessorImpl_invoke0+0x84ae3d80 (,
    0x0000000000000000)
    SIDECARINVOKEREFLECTMETHOD+0x849ccd68 (, 0x0000000000000000)
    JVM_InvokeMethod+0x848f6230 (, 0x0000000000000000)
    Java_sun_reflect_NativeMethodAccessorImpl_invoke0+0x84ae3d80 (,
    0x0000000000000000)
    RUNCALLINMETHOD+0x849d16a8 (, 0x0000000000000000)
    gpProtectedRunCallInMethod+0x84994838 (, 0x0000000000000000)
    signalProtectAndRunGlue+0x84994a60 (, 0x0000000000000000)
    j9sig_protect+0x84bd51a0 (, 0x0000000000000000)
    gpCheckCallin+0x84991970 (, 0x0000000000000000)
    callStaticVoidMethod+0x8499a630 (, 0x0000000000000000)
    JavaMain+0xcf0f3b08 (, 0x0000000000000000)
    ---------------------------------------
    Below is an example call to wsadmin.sh that would trigger this:
    wsadmin.sh -conntype RMI -port 9809 -username usr -password pas
    

Problem conclusion

  • Code was fixed to properly handle a 64-bit client address space.
    
    APAR PM41934 is currently targeted for inclusion in Service
    Level (Fix Pack) 7.0.0.19 of WebSphere Application Server V7.0.
    
    Please refer to URL:
    //www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
    for Fix Pack availability.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM41934

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-06-17

  • Closed date

    2011-08-15

  • Last modified date

    2011-10-04

  • 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

    WEBSPHERE FOR Z

  • Fixed component ID

    5655I3500

Applicable component levels

  • R700 PSY UK71297

       UP11/09/10 P F109

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.



Document information

More support for: WebSphere Application Server for z/OS
General

Software version: 7.0

Reference #: PM41934

Modified date: 04 October 2011