PI14586: RDz client gets RSEG1056 and can not connect to RDz host on VIPA Backup LPAR

9.0.1.3: UI20613 PTF for Rational Developer for System z Host Options
Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Rational Developer for System z client gets message RSEG1056 and
  can not connect to RDz host on VIPA Backup LPAR
  
  client .log shows RSEG1056
  
  LPAR1 is the primary SD stack with the following defs:
  VIPADEFINE     MOVEABLE IMMEDIATE
          255.255.255.255 10.01.01.2
  VIPADISTRIBUTE DEFINE SYSPLEXPORTS
          DISTMETHOD BASEWLM
          10.01.01.2
          PORT  14035
          DESTIP ALL
  
  LPAR2 is the backup SD stack with the following defs:
  VIPABACKUP 100   10.01.01.2
  
  rseserver.log shows
  ConnectionMonitor: USER1: java.net.SocketTimeoutException:
  Accept timed out
  
  USER:RSED2 INFO: acceptSocket:New Logon Request arrived in
     socket=124: Peer IP address: 10.01.02.3
     port=8959
  USER:RSED2 INFO: getServerPort:port(18216-18231) ticket(6935647)
     userid(USER1) displayId(1832486) NONE
  USER:RSED2 INFO: RseDaemon:selectThreadPoolProcess():
     process=16843597: check PID result=0
  USER:RSED2 INFO: ConnectionMonitor: USER1:
   >>>>>>>> java.net.SocketTimeoutException:
   >>>>>>>> Accept timed out
  USER:RSED2 INFO: acceptSocket:New Logon Request arrived in
     socket=133: Peer IP address: 10.02.04.5
     port=54459
  USER:RSED2 INFO: getServerPort:port(18216-18231) ticket(6925894)
     userid(USER1) displayId(2384199) NONE
  USER:RSED2 INFO: RseDaemon:selectThreadPoolProcess():
     process=16843597: check PID result=0
  USER:USER1 INFO: ServerThread: LOGON Request: userid(USER1)
     ticket(6925894) port(18216-18231)
     displayId(2384199)
  USER:USER1 INFO: port 18216 assigned to USER1
      INFO: ProcessId=16843597, Memory_Usage=4%,
     Used_Memory=21111KB, MemoryUsage_HighValue=4%,
     threads=6, TCBs=2
  
  Notes
  Telnet to LPAR2 VIPA IP port 18216 can make connection, no error
  is received and this telnet connection times out as expected
  
  RDz Client can connect to RDz on LPAR2 using LPAR2 native IP
  address
  
  LOCAL FIX:
  Specify _RSE_JAVAOPTS -Dserver.bind0=true in the rsed.envvars as
  temporary circumvention
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: 01.system admin                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: 01.improve distributed Dynamic VIPA     *
  *                         support                              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  01.improve distributed Dynamic VIPA support, which can be
     enabled with the _RSE_JAVAOPTS -Denable.dDVIPA=true option
     in rsed.envvars
  

Problem conclusion

• 01.improve distributed Dynamic VIPA support, which can be
     enabled with the _RSE_JAVAOPTS -Denable.dDVIPA=true option
     in rsed.envvars
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Modules/Macros

• FEKFENVR FEKFZOS
  

Fix information

• Fixed component name

  RD/Z HOST

• Fixed component ID

  5724T0723

Applicable component levels

• R900 PSY UI20613

     UP14/08/25 I 1000

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.