0
346
Question Roberto Cahanap · Jun 14, 2018

Cache Zen Report renderserver

#Caché

We are updating from 2015.1.1 to  2017.2. I am testing the Hot JVM functionality to see if our current functionality is working in the new version of 2017.

I am having a problem trying to make it "fail".

Generally if I put in an invalid renderport then I usually get an error. Now if I put in an invalid renderport it generates the PDF anyway (FOP).

Was there a change where if it fails using the renderserver then it will create a new instance of Java to produce the PDF?

Discussion (3)0
Log in or sign up to continue

Comments

Eduard Lebedyuk · Jun 14, 2018

Not a solution but as a workaround you can probably check the size of the generated PDF. It should probably be the same and fairly small (as it's an empty report).

0
Roberto Cahanap  Jun 14, 2018 to Eduard Lebedyuk

The problem is that it is generating the correct PDF. I am puzzled.

This works:

//68000 is the correct render server port

Set st=obj.GenerateReport(filename,2,0,68000)

This works too:

Set st=obj.GenerateReport(filename,2,0,"ABCDEFG")

0
Vitaliy Serdtsev · Jun 15, 2018

Add the RenderDirectlyOnTimeout property in the report:

Property RenderDirectlyOnTimeout As %ZEN.Datatype.boolean(ZENURL = "$RENDERDIRECTLYONTIMEOUT") [ InitialExpression = {$$$NO} ];

Then you will get the following error:

ERROR #5001: Cannot contact server on port %1.
or
ERROR #5001: Received Control-C or there was a fatal error.
0