Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Join us in NYC Sept 4th for Qlik's AI Reality Tour! Register Now
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

tBufferOutput from subjob is not loaded in Mainjob..

Hi all,

 

I have a mainjob running, in which a subjob is started to get a DigestKey from a webservice. This value is retreived (I checked it with tLogRow in the subjob) , and then stored in a tBufferOutput. However, in the mainjob when I want to set it as variable immediately, it is null.

This problem showed up as soon as I incorporated logging with tStatCatcher in my jobs, because before that, the job was running fine.


Any idea what can be the problem here? Is the buffered output emptied because of the logging running afterwards? Or is something else the problem?

 

I get this message as error when I run it: "Error on line 1 of document : Content is not allowed in prolog. Nested exception: Content is not allowed in prolog."

While, as stated before, without the logging I never got this message.

 

Any ideas? I hope you can help me!

Labels (2)
1 Solution

Accepted Solutions
Anonymous
Not applicable
Author

Hi all,

 

I found the error that caused this issue.

In the main job, I used as contenttype and accept for the webservice Json, while in the Digestkey subjob I used atom+xml.

So, when I changed the subjob to JSON as well, and consequently also the tConvert and tXMLMap to a tJSONExtract, then this wasn't an issue anymore (now there is another problem again.. but okay.. baby steps 0683p000009MA9p.png )  .

 

Thanks for the help anyway!

View solution in original post

13 Replies
Anonymous
Not applicable
Author

This is the subjob in which the digestkey is stored in tBufferOutput.. But then not returned in the mainjob..

 

0683p000009Lv7A.png

Anonymous
Not applicable
Author

Hi,

Can you output your digestkey to see if it has been stored in tBufferOutput?

Best regards

Sabrina

Anonymous
Not applicable
Author

Hi,

 

I put tLogRow behind the tBufferOutput, and then it shows the digestkey in the output. So it is stored there..

Anonymous
Not applicable
Author

On second thought..

Now I run the whole job, and the tlogrow was still connected to the digest key, and then it shows up empty in the log of the main job..

 

Anonymous
Not applicable
Author

Hi,

What does your main job look like? Is the attached screenshot your whole work flow?

Best regards

Sabrina

Anonymous
Not applicable
Author

Yes, the attached job in my first post is the whole job.

Anonymous
Not applicable
Author

Hi,

 

I've run the mainjob while in the subjob GetDigestKey I put several tLogRows, and it seems that in the first 2 tLogRows (4 and 5) the DigestKey is printed, but after the tConvert and tMap the Digestkey disappeared and leaves empty logs.. (tLogRow 3,2 and 1).

While, when I run this subjob alone, the DigestKey is visible in all the tLogRows... so somehow the incorporation in the mainjob causes a problem.
Does this give you any new ideas? Also in combination with the error about content not allowed in Prolog?

 

Kind regards,

Annewieke

 

 

 

 

 

0683p000009Lv3a.png

Anonymous
Not applicable
Author

Hi all,

 

I found the error that caused this issue.

In the main job, I used as contenttype and accept for the webservice Json, while in the Digestkey subjob I used atom+xml.

So, when I changed the subjob to JSON as well, and consequently also the tConvert and tXMLMap to a tJSONExtract, then this wasn't an issue anymore (now there is another problem again.. but okay.. baby steps 0683p000009MA9p.png )  .

 

Thanks for the help anyway!

Anonymous
Not applicable
Author

Hi,

Thanks for posting your solution here. Don't hesitate to post your issue here.

Best regards

Sabrina