Job run statistics not displaying in DS Director/Designer

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
arvind_ds
Participant
Posts: 428
Joined: Thu Aug 16, 2007 11:38 pm
Location: Manali

Job run statistics not displaying in DS Director/Designer

Post by arvind_ds »

Hello Experts,

I am facing problems in one of the parallel job(9.1.2 version). I am not able to see the job run statistics (i.e. rows per second processed) do not update in DataStage Designer or Director clients for one particular parallel job only. I checked the JobMonApp service on the backend(Linux server) and found that JobMonApp service is running perfectly fine with both the ports(13400 & 13401 listenning properly). In addition to this, the Job run statistics is working fine for all other jobs except the one which I mentioned above. Strangely, when I run this job again on the next day(without making any changes in the environment), the job run statistics works fine and then again same problem appears with this job only after 1 month or so).The problematic job extracts data from DB2 database and write it to sequential files subjected to certain ETL transformations.

I followed the below IBM technote as well.

http://www-01.ibm.com/support/docview.w ... wg21392483

Everythig mentioned in the above technote seems fine in our datastage environment. I just found the below information in /ibm/InformationServer/Server/PXEngine/java/JobMonApp.log file.

Fatal Parsing Error Occurred:Premature end of file.
Received malformed xml syntax... Closing Connection to Conductor...Premature end of file.
Exception in thread "ProducerInputReader" java.lang.NullPointerException
at ProducerInputReaderThread.run(ProducerInputReaderThread.java:145)
Tue Nov 25 22:22:03 EST 2014 RequestParseHandler created.

Fatal Parsing Error Occurred:Premature end of file.
Could not write to subscriber socket.
SAXParseException... Closing Connection to Client...Premature end of file.
org.xml.sax.SAXParseException: Premature end of file.
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at ConsumerRequestReaderThread.run(ConsumerRequestReaderThread.java:210)
Tue Nov 25 22:22:03 EST 2014 ResponseParseHandler created.


Fatal Parsing Error Occurred:Premature end of file.
Received malformed xml syntax... Closing Connection to Conductor...Premature end of file.
Exception in thread "ProducerInputReader" java.lang.NullPointerException
at ProducerInputReaderThread.run(ProducerInputReaderThread.java:145)
Tue Nov 25 22:22:03 EST 2014 RequestParseHandler created.


Fatal Parsing Error Occurred:Premature end of file.
Could not write to subscriber socket.

SAXParseException... Closing Connection to Client...Premature end of file.
org.xml.sax.SAXParseException: Premature end of file.
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at ConsumerRequestReaderThread.run(ConsumerRequestReaderThread.java:21


Any help on the resolution of this problem, is much appreciated. Many thanks.
Arvind
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

For errors of that nature you would need to involve your official support provider.
-craig

"You can never have too many knives" -- Logan Nine Fingers
Post Reply