Search found 4 matches

by soswald123
Fri Dec 15, 2017 7:50 am
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Caught ORCHESTRATE exception error
Replies: 7
Views: 8496

Craig, Thanks for the quick reply. Of course, always appreciate more info on how to troubleshoot a weird abort. That being said, happens so infrequently in our environment not sure worth chasing down... This job executes every 5 minutes, and on restart after these failures completes successfully. Li...
by soswald123
Fri Dec 15, 2017 6:35 am
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Caught ORCHESTRATE exception error
Replies: 7
Views: 8496

Similar error being thrown from one job (very infrequently) in our environment: Fatal Error: Caught ORCHESTRATE exception in parallel process: APT_Archive::BadPointer: From: Loading memory archive: Expected class "APT_SchemaFieldListRep" , got class "APT_DMDescriptor" when loadin...
by soswald123
Fri Feb 10, 2017 9:25 am
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Losing Content-Type header on InfoSphere Info Server call
Replies: 2
Views: 1883

Thanks for your reply, Julio! The InfoSphere Information Server managing the web service handles the web bindings, creates the header info, manages security, etc. So, I'll need to check the IIS logs, which, unfortunately, are not available thru the IIS front end. :evil: I'm almost positive this is a...
by soswald123
Thu Feb 09, 2017 3:09 pm
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Losing Content-Type header on InfoSphere Info Server call
Replies: 2
Views: 1883

Losing Content-Type header on InfoSphere Info Server call

I've developed a multiple instance job that returns a JSON package thru a web service call. The job is instantiated and persisted by InfoSphere Information Server. A different set of MIME header fields are received depending on how large the JSON package retrieved is. My specific issue is Content-Ty...