Article - CS404068
Jasper errors result in hung methodcontexts that might use up all DB connections in Windchill PDMLink 12.0
Modified: 14-Nov-2025
Applies To
- Windchill PDMLink 12.0 to 13.1
Description
- Jasper errors result in zombie MethodContexts that never end
- These zombie MethodContext do not show up in thread dumps as they do not have a thread
- Each zombie MethodContext might hold on to a database connection
- MethodServer might run out of database connections, due to the db connection leak
- Method Server stop working
- All queues stop working
- Workflow process stopped working
- When the MethodServer runs out of database connections, operations hang waiting for a database connection to become available
- Example Jasper error found in MethodServer log or MiscLogEvents table:
[Thread-116] com.ptc.wbr.client.ReportClientHelper - generateJasperPrint(): Deleteing SYNC execution request for savedReportOID=com.ptc.wbr.core.WBRReportCriteria:15419704 [Thread-116] com.ptc.wbr.client.ReportClientHelper - generateJasperPrint(): Jasper Report execution failed for savedReportOID=com.ptc.wbr.core.WBRReportCriteria:15419704. Aborting the heat-beat to notify failure. [Thread-116] com.ptc.wbr.core.execution.JasperReportExecutor - getJasperPrint(): Error While executing Jasper report - net.sf.jasperreports.engine.fill.JRExpressionEvalException
This is a printer-friendly version of Article 404068 and may be out of date. For the latest version click CS404068