Getting session timeouts with MSM

book

Article ID: 49691

calendar_today

Updated On:

Products

CA Compress Data Compression for MVS CA Compress Data Compression for Fujitsu CA Datacom - DB CA Datacom CA Datacom - AD CA Datacom - Server CA Mainframe Software Manager (Chorus Software Manager) CA MICS Resource Management CA CIS CA Common Services for z/OS CA 90s Services CA Database Management Solutions for DB2 for z/OS CA Common Product Services Component CA Common Services CA ecoMeter Server Component FOC CA Easytrieve Report Generator for Common Services CA Infocai Maintenance CA IPC Unicenter CA-JCLCheck Common Component CA Mainframe VM Product Manager CA Chorus Software Manager CA On Demand Portal CA Service Desk Manager - Unified Self Service CA PAM Client for Linux for zSeries CA Mainframe Connector for Linux on System z CA Graphical Management Interface CA Web Administrator for Top Secret CA CA- Xpertware CA Datacom/AD

Issue/Introduction

Description:

With MSM, at the SMP/E tab when selecting the maintenance, the popup window 'Reading maintenance packages from Software Catalog' and after some time also the error message 'The call failed on the server; see server log for details' is displayed.

And in the MSM Tomcat Server log you will find the messages:

SEVERE: Exception while dispatching incoming RPC call
Throwable occurred: java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.read(SocketInputStream.java:140)

Solution:

This is caused by the large amount of data the MSM GUI is retrieving from the MSM Datacom database.
If you check the users setting of the 'Number of Table Rows Displayed' (in his Settings tab, User Setting, User Preferences) it will be 250.
If you lower this to 100, or even to 50 the problem disappears.
If you however want to keep the 250 rows display, you will need to change the timeout values.

The place of the timeout parameters in MSM is in the server.xml member.

The parameter involved:

connectionTimeout="20000"

This says how long the tcpip stack waits for incoming packets (for example you can disconnect notebook from network for less than 20000 ms and the tcpip connection will not be dropped. To solve the problem with the rows displayed at 250, you need to change the connectionTimeout value.. And it could be that you need to set at least 2-3 minutes or unlimited timeout.

The server.xml member can be found in the MSM runtime/tomcat/conf directory.

It is stored in ASCII format and can be edited with ISHELL or with ISPF option P.3.17 and the command EA (Edit Ascii).

Environment

Release:
Component: MSM