Automated Testing

Automated Testing

Automated Testing

Build an automated testing process to enable continuous integration of your hybrid cloud applications including z/OS

 View Only
Back to discussions
Expand all | Collapse all

RSEG1056 Connection refused. Make sure that the datastore server is runnin

  • 1.  RSEG1056 Connection refused. Make sure that the datastore server is runnin

    Posted Thu March 14, 2013 07:34 PM
    RDz client receives error message 'RSEG1056 Connection refused. Make sure that the datastore server is running on host_name under port port_number.' The RSED and JMON tasks are both running. In the rseserver.log we see the following

    Thu Mar 14 10:26:09 MDT 2013
    INFO acceptSocket: New Logon Request arrived in socket=137: Peer IP address: 206

    Thu Mar 14 10:26:09 MDT 2013
    INFO getServerPort: port(0) ticket(4303933) userid(NUO3405) displayId(36217) NON

    Thu Mar 14 10:26:09 MDT 2013
    INFO RseDaemon: selectThreadPoolProcess(): process=903: check PID result=0

    Thu Mar 14 10:26:09 MDT 2013
    INFO LogHandler: 903:NUO3405:4303933:0:36217

    Thu Mar 14 10:26:09 MDT 2013
    INFO LogHandler: ProcessId=903: port 47634 assigned to XXXXXXX

    Then the client gets the connection refused message. The host_name in the message is correct and the port_number is the one assigned to user XXXXXXX in the above LogHandler message. I can't see any error messages on the z/OS side in SYSLOG, TCPIP, RDz logs, or the RDz tasks. Any idea where or why the connection to the RSE server is getting refused?

    Thank you for any assistance provided.
    SystemAdmin


  • 2.  Re: RSEG1056 Connection refused. Make sure that the datastore server is runnin

    Posted Fri March 15, 2013 07:45 AM
    Please ask this question in the RDz forum. All of the RDz experts are there and should be able to help you.

    RDzJohn
    RDzJohn


  • 3.  Re: RSEG1056 Connection refused. Make sure that the datastore server is runnin

    Posted Sun March 17, 2013 09:08 AM
    Hi Christine,
    When you connect to RSED you will be give a port to a thread pool that will handle your connection. It would appear that you are not able to connect back to the port that you were provided. Make sure that the firewalls, tcp/ip routing, etc. are not blocking you from connecting to the thread pool.

    Mike
    JavaPoet


Related Content