Failed to connect to JobMonApp on port 13401

Manfred Hagedorn · Post by **Manfred Hagedorn** » Mon Dec 14, 2009 4:11 am

Since Today i get the warning:
Failed to connect to JobMonApp on port 13401

I know, that there are alredy many posts on this issue. I think, i have read most of them.

I stopped and re-started the JobMonitor several times.
I stopped and re-started Datastage several times.
I used "ipcrm" and "clearsockets".
Nothing helped.

Does anybody have any further idea, what could solve the problem?

Best regards
Manfred

chulett · Post by **chulett** » Mon Dec 14, 2009 7:25 am

'ipcrm' is used to clear shared memory segments, not sockets. What does "netstat -a |grep 13401" show when DataStage is running and when shutdown? How long did you wait after stopping before starting?

Manfred Hagedorn · Post by **Manfred Hagedorn** » Mon Dec 14, 2009 8:01 am

Hello Chulett,

First "netstat -a |grep 13401" showed nothing.
After restarting Datastage again, it shows:
tcp 0 0 *.13401 *.* LISTEN
But Warning still is in the log.

Beside the message mentioned in the header, there is in the log:
Contents of phantom output file =>
DataStage Job 1204 Phantom 14406
OpenSocket() returned 16
DataStage Phantom Finished.

For restarting Datastage i have a small job, using a sleep of 60 between stop and start.
Best regards
Manfred

lstsaur · Post by **lstsaur** » Mon Dec 14, 2009 11:37 am

Set your $APT_ORCHHOME first, then go to your /home/dsadm/Ascential/DataStage/PXEngine/java directory, then issue sh jobmoninit start $APT_ORCHHOME.

chulett · Post by **chulett** » Mon Dec 14, 2009 11:56 am

Manfred Hagedorn wrote:For restarting Datastage i have a small job, using a sleep of 60 between stop and start.

You really shouldn't do this on a timer, but rather after a check for open ports returns zero in that state:

Code: Select all

netstat -a |grep dsrpc | wc -l

Manfred Hagedorn · Post by **Manfred Hagedorn** » Wed Dec 16, 2009 2:26 am

Hello,
thanks for your replay.
1. APT_ORCHHOME: how should i set this? You really think, this parameter is related to JobMonitor?
2. netstat -a |grep dsrpc | wc -l shows: 1
So, i still don't really know, how to get the JobMonitor runing.

Just to mention again, JobMonitor was runing in the past, and i have re-started him in the past several times ... something must have changed or be different now, but what ???

As a workaround, it would help me, just to remove "Failed to connect to JobMonApp on port 13401" from the log and get a return code without warnings. But i tried to do this with the Message Handler in the Director, but this warning doesn't have a message id and i can't suppress it from log ???

Best regards
Manfred