tracker issue : CF-4198761

select a category, or use search below
(searches all categories and all time range)
Title:

cfdocument does not generate chart in a pdf after CF11 update 12.

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/BugVerified

Reporter/Name(from Bugbase): / ()

Created: 05/24/2017

Components: Document Management, PDF generation

Versions: 2016,11.0

Failure Type: Non Functioning

Found In Build/Fixed In Build: 11,0,12,302575 / 303586

Priority/Frequency: Normal / Some users will encounter

Locale/System: /

Vote Count: 4

Listed in the version 2016.0.05.303689 Issues Fixed doc 
Problem: cfdocument does not generate a chart in a pdf after CF11 update 12.

Method: After update 12, pdf created using cfdocument doesn't have a chart. 

Repro code: 

<cfdocument format="PDF" filename="test.pdf" overwrite="true">
<cfoutput>
<table>
<tr>
<td>This is a test page</td>
<td>Chart print test case</td>
</tr>
	<tr><td>
	<cfchart format="png" type="bar" showlegend="false" chartHeight="600" chartWidth="400" title="Basic Chart">
		<cfchartseries>
        <cfchartdata item="2015" value=20>
        <cfchartdata item="2016" value=40>
        <cfchartdata item="2017" value=60>
		</cfchartseries>
	</cfchart>
	
	</tr></td>	
		</table>
		
		</cfoutput>
</cfdocument>

Result: It is giving red X in a generated PDF.

Expected: It should generate PDF with a chart on it.

Workaround: Revert to CF11 update 11.

Note: Working fine in CF2016 update 4.

Attachments:

  1. September 14, 2017 00:00:00: 4198761.zip

Comments:

Possibly related to the behavior documented above, we are seeing similar behavior for CFIMAGE-generated images within CFDOCUMENT-generated PDF's in CF11 + Hotfix 12 + Java 8b144 (Oracle's current release level) on Windows servers. The following test case fails with red X's instead of images in CF11 + Hotfix 11 or 12 + Java 8b144 (even with Hotfix 12 + the patch for CF-4198761 provided to me privately by Anit Kumar): <cfdocument format="pdf"> <p>Image: <cfimage action="writetobrowser" source="#imageNew('', 250, 50, 'rgb', '##ff0000')#" format="png" /></p> </cfdocument> Breakage appears to be specific to Windows for both the original issue and this new aspect (all test cases and combinations of CF hotfixes, special patches, and Java versions work as expected on macOS and Linux). The following combinations work as expected: CFCHART in PDF: CF11 + Hotfix 11 + Java 8b131 (the current Java version when the original issue was logged) CFCHART in PDF: CF11 + Hotfix 12 + special patch + Java 8b131 CFIMAGE in PDF: CF11 + Hotfix 11 + Java 8b131 CFIMAGE in PDF: CF11 + Hotfix 12 + Java 8b131 CFIMAGE in PDF: CF11 + Hotfix 12 + special patch + Java 8b131 The following combinations fail: CFCHART in PDF: CF11 + Hotfix 12 + Java 8b131 (per the original issue) CFCHART in PDF: CF11 + Hotfix 11 + Java 8b144 (current Java version) CFCHART in PDF: CF11 + Hotfix 12 + Java 8b144 CFCHART in PDF: CF11 + Hotfix 12 + special patch + Java 8b144 CFIMAGE in PDF: CF11 + Hotfix 11 + Java 8b144 CFIMAGE in PDF: CF11 + Hotfix 12 + Java 8b144 CFIMAGE in PDF: CF11 + Hotfix 12 + special patch + Java 8b144
Comment by RONALD S.
682 | September 11, 2017 03:29:10 PM GMT
We have tested and confirmed that Windows + CF11 + Hotfix 13 + Java 8b131 works as expected for both the CFCHART-in-PDF test case in the original bug report and the CFIMAGE-in-PDF test case above, but both test cases fail with red X’s for Windows + CF11 + Hotfix 13 + Java 8b144.
Comment by RONALD S.
683 | September 13, 2017 07:28:01 PM GMT
Hi Ronald, I tried the same with the latest version of java which is 1.8 144, and both the cases are passing for me My configuration: ColdFusion 11 + HF 13 + Java 1.8 144 I have attached my test cases along with the result PDF. I have also attached my settings summary snapshot. The attachments are in a zip format with the name 4198761.zip Can you please share your settings summary snapshot? Also, what is the build number you are on? Thanks, Kailash
Comment by Kailash B.
684 | September 14, 2017 08:47:24 AM GMT
Kailash, Thanks for your off-line help with this. We have confirmed that the patch functions as expected in our environment. We tracked the problems I described above in my follow-up comment to an SSL certificate issue related to the Java update, and have resolved it.
Comment by RONALD S.
685 | September 20, 2017 09:20:15 PM GMT