ISD Jobs to Finished status

Dedicated to DataStage and DataStage TX editions featuring IBM<sup>®</sup> Service-Oriented Architectures.

Moderators: chulett, rschirm

Post Reply
dj
Participant
Posts: 78
Joined: Thu Aug 24, 2006 5:03 am
Location: india

ISD Jobs to Finished status

Post by dj »

Hi All,

When we deploy the Service,one of the ISD jobs goes to finished status and then it tries to invokes a new instance which again goes to finished status and it iterates the same for multiple instances until it stabilize for "Running" state.

These jobs are running for years and in other environment there are no issues.

1) Why does it goes to finished status ? and it creates numerous instances and we have to undeploy as it brings the system down.

2) when i try to hit a soap request ,the response does'nt display as multiple tags instead they display in single line which causes issues to the downstreams.
I have checked for all the properties and groups arguments remains the same as other environments.

Code: Select all

<SoapHeader><SoapBody><arg1><column1>123</column1><column2>......
actual result should be

Code: Select all

<SoapHeader>
<SoapBody>
<arg1>
<column1>123</column1>
<column2>jjj</column2>
</arg1>
Thanks,
Dj
qt_ky
Premium Member
Premium Member
Posts: 2895
Joined: Wed Aug 03, 2011 6:16 am
Location: USA

Post by qt_ky »

The pretty XML formatting should not normally be a concern. If you test using SoapUI, you normally see a response that is nicely formatted (by SoapUI). But if you click the tab to view the "Raw" response, it tends to come as a single line, which is normal.

Why your ISD deployment going crazy and cycling the job so much is a big concern. I have only seen once over the years where one of ours got possessed like that and could not be repaired. In our case we assumed corruption and we rebuilt the ISD app, service, and operation from scratch, then it was all good again.
Choose a job you love, and you will never have to work a day in your life. - Confucius
dj
Participant
Posts: 78
Joined: Thu Aug 24, 2006 5:03 am
Location: india

Post by dj »

Thanks for your reply.

It brings the system down ,that's the issue. It try to creates 100+instances immediately and we have got 3 jobs doing the same.

This test box server is limited here and it increases the cpu utilization and finally crashes .It happens for every deployment.

will start to create from scratch and give a try. Thanks
Post Reply