DataStage Designer Connection Issues (81002)

A forum for discussing DataStage<sup>®</sup> basics. If you're not sure where your question goes, start here.

Moderators: chulett, rschirm, roy

Post Reply
kinu008
Premium Member
Premium Member
Posts: 36
Joined: Fri Mar 16, 2007 1:35 pm

DataStage Designer Connection Issues (81002)

Post 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
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Re: DataStage Designer Connection Issues (81002)

Post 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.
-craig

"You can never have too many knives" -- Logan Nine Fingers
kinu008
Premium Member
Premium Member
Posts: 36
Joined: Fri Mar 16, 2007 1:35 pm

Re: DataStage Designer Connection Issues (81002)

Post by kinu008 »

That makes sense why director isn't disconnecting... but I am still perplexed about the designer client...

Thanks..
qt_ky
Premium Member
Premium Member
Posts: 2895
Joined: Wed Aug 03, 2011 6:16 am
Location: USA

Post by qt_ky »

Try reaching out to Support. They can probably tell you what got missed when your hosts were renamed.
Choose a job you love, and you will never have to work a day in your life. - Confucius
rkashyap
Premium Member
Premium Member
Posts: 532
Joined: Fri Dec 02, 2011 12:02 pm
Location: Richmond VA

Post by rkashyap »

Have you tried restarting the server?
kinu008
Premium Member
Premium Member
Posts: 36
Joined: Fri Mar 16, 2007 1:35 pm

Post by kinu008 »

Increasing the firewall timeouts on port 9080 resolved the issue.

Thanks
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post 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:
-craig

"You can never have too many knives" -- Logan Nine Fingers
qt_ky
Premium Member
Premium Member
Posts: 2895
Joined: Wed Aug 03, 2011 6:16 am
Location: USA

Post by qt_ky »

Pesky firewalls!
Choose a job you love, and you will never have to work a day in your life. - Confucius
Post Reply