Home | Contact Us | Submit Troubleshooting Info | Search | Help


    Output | Software Solutions | Proofing | Color, Screening and Calibration | Scanning | Digital Photography | Consumables | POS


Multi-page PDF vector output fails on very large or complicated jobs


Product

  Prinergy Connect 2.0 ; Prinergy Connect 2.1

Platform

 

Server: Dell all; Client: PC or Macintosh

Operating system

 

Server: Windows 2000; Client: Windows or Macintosh


Error

 

History Log error message:

Message from Extreme: Vector-Output:Vector-Output failed processing: ..[1080007]

DIAG error message:

E 25Mar02 11:37:46.191-PST [4284.3648] PIG

Pig PVectorOutputJTP DCSV_SupportMethods.cpp(337): DCSV_JTP::CreatePDFOutput: CORBA system exception while publishing SPES -

System exception `NO_RESPONSE'

Locality: exception has been generated locally

Completed: maybe

Minor code: 0x0

E 25Mar02 11:37:46.191-PST [4284.3648] PIG

Pig PVectorOutputJTP DCSV_JTP.cpp(709): DCSV_JTP::ProcessJT: Caught an unknown exception in ProcessJT.


Symptoms

 

Vector JTP fails to output a job with many pages to a single PDF file.

This only applies to PDF output to a single file. No other vector JTP output is affected by this problem.


Cause

  Version 2.0.7

The default timeout period for server calls is 2 minutes. If a single file PDF output job has many pages, or some complicated pages, it may take more than 2 minutes for the server to generate the file. So the call can timeout before the PDF is finished, and the job will fail.

Version 2.1 and later

For v2.1, the timeout for single file PDF output is set individually, each time a job is created. The timeout is based on the number of pages in the job, so large jobs should no longer trigger a timeout error. Font outlining can severely slow the PDF generation process, so if it's enabled, the timeout period is increased even more significantly. These changes should prevent most premature timeout errors in version 2.1 or later, but they are still possible.


Solution

 

Version 2.0.7

Increase the default timeout period for server calls in the registry (See reg key HKEY_LOCAL_MACHINE\SOFTWARE\Creo\Araxi\<version.build>\Default\APPL\DefaultCORBAInvocationTimeout). This value is in milliseconds, and the default is 120,000 (2 minutes). The output vector JTP must be stopped and restarted for this change to take effect.

NOTE: Changing this setting will increase the timeout for ALL client/server calls, not just those for the vector output JTP. This may cause some processes to remain hung for a longer period before they restart or fail.

Versions 2.1 and later

Increase the timeout period for vector output server calls (See reg key HKEY_LOCAL_MACHINE\SOFTWARE\Creo\Araxi\<version.build>\Default\DCSV\<JTP name>\CorbaTimeoutPerPage). This value is the timeout PER PAGE, in milliseconds. The default setting is 400 ms per page. Note that each vector output JTP has it's own timeout setting. The JTP must be stopped and restarted for this change to take effect.

There is a separate timeout reg key used when font outlining is enabled (see reg key CorbaTimeoutPerFontOutlinedPage under the above path). This is because font outlining can significantly increase processing time. The default timeout when font outlining is enabled is 2500 ms per page.

Permanent fix:


See also

 


Keywords

 

JTP, PDF, proofing, vector output


Technical contact(s)
 

James Bredenhof

Submitted by
 

Ed Bradshaw

Date submitted
 

25 Mar 2002


    Copyright © 2005 Creo Inc. All rights reserved. Confidential. Back to top.