IBM Support

IC99046: THE BASEPORT FOR THE CONTAINER JVM ON THE SECOND NODE OF EACH CLUSTER SHOWS THE UI BASEPORT

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • Customer has two production clusters which are separate from
    each other.
    After upgrading the clusters to patch 5104 from 5102 he can see
    that the baseport for the Container JVM on the second node of
    each cluster shows the same baseport (37000) as the cluster
    node when displaying "Node Status" in the UI, instead of
    the baseport defined in
    <SI_ROOT>/properties/node2AC1/node2AC1.properties.
    However in the system.log for the Container JVM I can see it
    does select the correct baseport from the properties on startup
    and all the properties files seem to be defined correctly.
    
    
    [2013-10-31 14:14:19.796] ALL 000000000000 GLOBAL_SCOPE Get
    Baseport 30071 for node2AC1 node from propFile
    /product/SEE/integrator/install/properties/node2AC1/node2AC1.pro
    perties
    
    The cluster looks to have started correctly and I can see the
    members all joined in noapp.log :-
    
    [2013-10-31 14:14:19.789] ALL 000000000000 GLOBAL_SCOPE **
    Member joined: 153.239.84.110:30061
    [2013-10-31 14:14:19.789] ALL 000000000000 GLOBAL_SCOPE **
    Member joined: 153.239.84.110:30073
    [2013-10-31 14:14:19.789] ALL 000000000000 GLOBAL_SCOPE **
    Member joined: 153.239.84.112:30061
    [2013-10-31 14:14:19.789] ALL 000000000000 GLOBAL_SCOPE **
    Member joined: 153.239.84.112:30073
    
    Note they have switched from UDP to TCP in jgroups_cluster and
    made the changes for node and JVM Container in the
    customer_override.properties.
    
    We tried this but it did not work on
    production nodes. This did however work on their QA system:
    
        * stopped the node1AC1 container
        * erased the line in OPS_NODE_INFO table
        * restarted the node1AC1
    

Local fix

  • STRRTC - 402249
    AC / AC
    Circumvention: None
    

Problem summary

  • Users Affected:
    All
    
    Problem Description:
    The baseport for the Container JVM on the second node of each
    cluster shows the UI baseport.
    
    Platforms Affected:
    All
    

Problem conclusion

  • Resolution Summary:
    A code fix has been provided.
    
    Delivered In:
    5020500_6
    5105
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC99046

  • Reported component name

    STR B2B INTEGRA

  • Reported component ID

    5725D0600

  • Reported release

    510

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-01-29

  • Closed date

    2015-06-11

  • Last modified date

    2016-03-22

  • 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

    STR B2B INTEGRA

  • Fixed component ID

    5725D0600

Applicable component levels

  • R525 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS3JSW","label":"IBM Sterling B2B Integrator"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.1","Edition":"","Line of Business":{"code":"LOB02","label":"AI Applications"}}]

Document Information

Modified date:
22 March 2016