PM35515: XS CONSOLE MAY DISPLAY "CONNECTION ERROR" WHEN CONNECTING TO CATALOG SERVERS HOSTED IN WEBSPHERE APPLICATION SERVER ND

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • For a valid domain chosen on the WebSphere eXtreme Scale
    Monitoring Console, consisting of catalog servers hosted
    within the WebSphere Application Server ND environment, the
    connection status may appear as "Connection Error," with grid
    statistics failing to appear for the domain.
    
    The following exceptions may also appear in connection with
    the above symptoms:
    STDERR  テ    テ  info ツ ᄄUpdate connection info
    for /storage/current/domain 2011-01-11 13:52:48
    zero.core.context.zones.JavaGCSerializer::deserialize Thread-1
    SEVERE  &#65411;   CWPZC0029E: Unable to serialize key < &#65411;  B@45cb45cb>
    the ser zone.  &#65410; &#65448;
    java.io.EOFException
    at
    java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInpu
    tStream.java:2292)
    at
    java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectI
    nputStream.java:2761)
    at
    java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.jav
    a:791)
    at
    java.io.ObjectInputStream.<init>(ObjectInputStream.java:291)
    at
    zero.core.context.zones.JavaGCSerializer.deserialize(JavaGCSeria
    lizer.java:71)
    at
    zero.core.context.zones.GCFileStore.read(GCFileStore.java:432)
    at
    zero.core.context.zones.GCFileStore.load(GCFileStore.java:384)
    at
    zero.core.context.zones.PersistentZoneHandler.get(PersistentZone
    Handler.java:139)
    at
    zero.core.context.zones.support.ZoneHandler2Wrapper.get(ZoneHand
    ler2Wrapper.java:101)
    at zero.core.context.Context.zput(Context.java:351)
    at
    zero.core.context.zones.support.ZoneHandler2Wrapper.zput(ZoneHan
    dler2Wrapper.java:53)
    at zero.core.context.Context.zput(Context.java:337)
    at zero.core.context.GlobalContext.zput(GlobalContext.java)
    at
    com.ibm.ws.xs.app.DomainConnectionUpdater.setConnectionInfo(Do
    mainConnectionUpdater.java:135)
    at
    com.ibm.ws.xs.app.DomainConnectionUpdater.run(DomainConnection
    Updater.java:78)
    at java.lang.Thread.run(Thread.java:735)
    ...
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of the monitoring console in      *
    *                  WebSphere eXtreme Scale Version 7.1.0 or    *
    *                  later.                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: A connection error displays as the      *
    *                      connection status to a valid catalog    *
    *                      service domain. Grid statistics do      *
    *                      not display.                            *
    ****************************************************************
    * RECOMMENDATION:  Install a fix pack that contains this APAR. *
    ****************************************************************
    When you add  catalog servers that are hosted in a WebSphere
    Application Server Network Deployment environment to a
    catalog service domain that was created in the eXtreme Scale
    monitoring console, the following exceptions related to
    deserialization might display in logs after
    a period of time:
    
    STDERR     nfo pdate connection info
    for /storage/current/domain 2011-01-11 13:52:48
    zero.core.context.zones.JavaGCSerializer::deserialize Thread-1
    SEVERE   CWPZC0029E: Unable to serialize key <  @45cb45c
    the ser zone.
    java.io.EOFException
    at
    java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInpu
    tStream.java:2292)
    at
    java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectI
    nputStream.java:2761)
    at
    java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.jav
    a:791)
    at
    java.io.ObjectInputStream.<init>(ObjectInputStream.java:291)
    at
    zero.core.context.zones.JavaGCSerializer.deserialize(JavaGCSeria
    lizer.java:71)
    at
    zero.core.context.zones.GCFileStore.read(GCFileStore.java:432)
    at
    zero.core.context.zones.GCFileStore.load(GCFileStore.java:384)
    at
    zero.core.context.zones.PersistentZoneHandler.get(PersistentZone
    Handler.java:139)
    at
    zero.core.context.zones.support.ZoneHandler2Wrapper.get(ZoneHand
    ler2Wrapper.java:101)
    at zero.core.context.Context.zput(Context.java:351)
    at
    zero.core.context.zones.support.ZoneHandler2Wrapper.zput(ZoneHan
    dler2Wrapper.java:53)
    at zero.core.context.Context.zput(Context.java:337)
    at zero.core.context.GlobalContext.zput(GlobalContext.java)
    at
    com.ibm.ws.xs.app.DomainConnectionUpdater.setConnectionInfo(Do
    mainConnectionUpdater.java:135)
    at
    com.ibm.ws.xs.app.DomainConnectionUpdater.run(DomainConnection
    Updater.java:78)
    at java.lang.Thread.run(Thread.java:735)
    ...
    
    The exceptions occur when the runtime attempts to deserialize
    information about catalog servers for the chosen catalog
    service domain
    that
    is
    persisted to the following files in the file system:
    
    <eXtreme_Scale_Install_root>/ObjectGrid/console/xs.app/.zero/app
    liancezoneStore/catalogServers.ser
    
    <eXtreme_Scale_Install_root>/ObjectGrid/console/xs.app/.zero/sto
    ragezoneStore/wxs/catalogServers.ser
    
    The file contents might be corrupted.
    
    As a result, the connection status to a selected, valid
    catalog service
    domain might erroneously diplay as: "Connection Error". Data
    grid
    statistics also might not display for the catalog service
    domain.
    

Problem conclusion

  • The runtime was corrected to store the catalog server
    information in a temporary storage location instead persisting
    it to a file. This APAR is anticipated to be included in
    WebSphere eXtreme Scale Version 7.1.0.3.
    

Temporary fix

  • As a temporary workaround, you can stop the console,
    delete the .ser files, and restart the console.
    

Comments

APAR Information

  • APAR number

    PM35515

  • Reported component name

    XD EXTREME SCAL

  • Reported component ID

    5724J3402

  • Reported release

    710

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-03-23

  • Closed date

    2011-04-28

  • Last modified date

    2011-05-05

  • 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

    XD EXTREME SCAL

  • Fixed component ID

    5724J3402

Applicable component levels

  • R710 PSY

       UP



Rate this page:

(0 users)Average rating

Document information


More support for:

WebSphere eXtreme Scale
General

Software version:

710

Reference #:

PM35515

Modified date:

2011-05-05

Translate my page

Machine Translation

Content navigation