Topic
2 replies Latest Post - ‏2013-03-17T13:08:12Z by JavaPoet
SystemAdmin
SystemAdmin
253 Posts
ACCEPTED ANSWER

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

‏2013-03-14T23:34:12Z |
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.
Updated on 2013-03-17T13:08:12Z at 2013-03-17T13:08:12Z by JavaPoet
  • RDzJohn
    RDzJohn
    229 Posts
    ACCEPTED ANSWER

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

    ‏2013-03-15T11:45:09Z  in response to SystemAdmin
    Please ask this question in the RDz forum. All of the RDz experts are there and should be able to help you.

    RDzJohn
  • JavaPoet
    JavaPoet
    11 Posts
    ACCEPTED ANSWER

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

    ‏2013-03-17T13:08:12Z  in response to SystemAdmin
    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