Skip to main content
Participant
May 28, 2020
Question

Font Mangement not showing fonts after adding additional instances coldfusion 2016

  • May 28, 2020
  • 1 reply
  • 1001 views

We are trying to use the cfdocument tag on coldfusion 2016 and getting errors on creating the pdf.

I have found that the issue only appears on the coldfusion servers where we have defined multiple instances. 

On the default cfusion instance everything works perfectly.  When running from additional instances it does not.  In the coldfusion administrtor the Font Managment does not show any fonts on the additional instances.  On the cfusion instance I can see all the Adobe installed fonts that were part of the initial install.

On startup of the additional instances I am getting the error 

May 27, 2020 21:45:47 PM Error [Thread-65] - com.lowagie.text.FontFactory.getFontFaces()Ljava/util/Map;
May 27, 2020 21:45:47 PM Error [Thread-65] - com.lowagie.text.FontFactory.getFontFaces()Ljava/util/Map;

 

This is also the same error that appears if I try to define my own font directory.

How can I get the fonts to appear on the Font Management in the additional instances.

 

We are running on RHEL 7.5 and Apache

    This topic has been closed for replies.

    1 reply

    BKBK
    Community Expert
    Community Expert
    May 28, 2020

    Did you upgrade all your instances to the same level? The latest update of ColdFusion 2016 is Update 15.

    Participant
    May 28, 2020

    Yes, I'm running Update 15 on the instances.

    I'm seeing this same thing across multiple servers.  The default cfusion install has no issues with the Fonts and the Font Management showing in the coldfusion administrator.  All the additional instances do not show the Fonts in the Font Managment and are showing this error in the log. 

    May 28, 2020 12:20:42 PM Error [Thread-65] - com.lowagie.text.FontFactory.getFontFaces()Ljava/util/Map;
    May 28, 2020 12:20:42 PM Error [Thread-65] - com.lowagie.text.FontFactory.getFontFaces()Ljava/util/Map;

    BKBK
    Community Expert
    Community Expert
    May 28, 2020

    In which log file do you see this?

    It might help to simply restart the instance concerned.