We are having some potential performance related issues with the layout package. We deploy our code to several different sites and there is only one site that utilizes the layout package. For this site we call layout:apply in order to insert the atipl:startpage and atipl:endpage tags, which are used later in the code to count the number of pages in the document. Our call to the apply function looks like
local layoutResults = layout::apply(", 0x40, docID); # docID is the obtained earlier in the code
myDebug("(PPRP) layout::apply Results - " . layoutResults );
if ( layoutResults == 0 )
{
myDebug("(markPages) Unable to apply layout tags ")
doc_close(docID);
myDebug(get_last_errors());
return -1;
}
Ultimately, our calls into E3 come from Cocoon via f=acl and the what is happening is we are getting a 500 Error on the Cocoon side with the additional error that the connection was reset. On the E3 side, the myDebug statement simply puts the text parameter into a log. At about the same time we get the 500 Error we also see entries in our custom E3 log that seem to stop at the layout::apply call because we see "(PPRP) layout::apply Results - " . layoutResults" in the log. It seems to hang within the layout:apply function call.
Has anyone experienced this issue? Is this a matter of not having enough resources? Is the layout manager a resource intensive process? Any thoughts would be helpful.
Thanks,
Craig
This email may contain material that is confidential, privileged and/or attorney work product for the sole use of the intended recipient. Any review, reliance or distribution by others or forwarding without express permission is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.
