Page 1 of 1

DataStage Designer Connection Issues (81002)

Posted: Wed Aug 06, 2014 8:27 am
by kinu008
Hi all,
We are repeatedly getting "The connection is broken (81002)" error messages when the designer client is left idle for 2 or 3 minutes. There is no issue with director client.

Timeout settings in administrator and global timeout settings (web) seems to be fine and nothing has changed...

We are having above issue ever since our servers hosting DataStage are renamed. Prior to that there were no issues.

Is there a log file or a place where I can see why the connections are breaking? Also, my understanding is that designer and director both operate on same ports - so why is the issue happening with only designer, not director? I already checked activity.log, systemout.log, native_stderr.log files but no luck.

We are working with our data center folks but I want to reach out dsxchange community members to see if any one experienced similar issues?

Our DataStage environment is 8.1 on UNIX.

Please let me know if you need additional details.

Thank you,
Kiran

Re: DataStage Designer Connection Issues (81002)

Posted: Wed Aug 06, 2014 8:37 am
by chulett
kinu008 wrote:so why is the issue happening with only designer, not director?
Because the Directory is never truly idle unless you've disabled the refresh.

Re: DataStage Designer Connection Issues (81002)

Posted: Wed Aug 06, 2014 9:16 am
by kinu008
That makes sense why director isn't disconnecting... but I am still perplexed about the designer client...

Thanks..

Posted: Wed Aug 06, 2014 11:13 am
by qt_ky
Try reaching out to Support. They can probably tell you what got missed when your hosts were renamed.

Posted: Wed Aug 06, 2014 2:14 pm
by rkashyap
Have you tried restarting the server?

Posted: Thu Aug 07, 2014 9:07 am
by kinu008
Increasing the firewall timeouts on port 9080 resolved the issue.

Thanks

Posted: Thu Aug 07, 2014 9:39 am
by chulett
Good. Figured it would be something like that, just recently went through something similar with a different set of idle timeouts which involved a fight with the security folks. :wink:

Posted: Thu Aug 07, 2014 10:25 am
by qt_ky
Pesky firewalls!