Skip to main content
ExLibris
  • Subscribe by RSS
    • Back
    Aleph
    Ex Libris Knowledge Center

    Unable to Print Large (>20MBs) Reports

    1. Last updated
    2. Save as PDF
    • Article Type: General
    • Product: Aleph
    • Product Version: 16.02

    Description:
    Our PLIF load produces a large report (>20MBs) which we are unable to print. The following message appears during our attempted print: Exception in thread "main" java.lang.OutOfMemoryError: Java heap space. Is there a workaround for this?

    Resolution:
    The problem with large files is a known issue for which there is not currently a fix in the version 16 GUI. We are also working on the PLIF Loader report file size to try and make smaller.
    Meanwhile, there is a workaround so that you can print or view large files outside of the GUI. This works using Internet Explorer to view XML files. It should work on other browsers, but we haven’t tried it.

    WORKAROUND:
    A few small steps will change your problem XMLXSL file into a standard XML file that can be viewed using the standard Aleph XSL stylesheet. Even though the GUI could not display the large file, when you downloaded it and tried to print it from the GUI, Aleph did convert the file just like any other file viewed via the Task Manager.

    The problem XMLXSL file should be located in:
    C:\AL500\ALEPHCOM\files\[LIBRARY]\print\history\[DATE]\[HOUR]
    For example, a file that you tried to print during the hour between 10 am and 11 am on 26 April 2006 from your USM50 library would be located in:
    C:\AL500\ALEPHCOM\files\USM50\print\history\20060426\10
    The file name will be: patron-loader-[NNNN].xmlxsl, for example, patron-loader-1840.xmlxsl

    [1] Copy the problem XMLXSL into the XSL template directory (this directory gets overwritten regularly, so if you want to print the same file in a week or so, you’ll have to perform these changes again). The XSL template directory location is:
    C:\AL500\ALEPHCOM\files\[LIBRARY]\PrintTemplates\[LNG]
    (Your language/“LNG� is probably “eng�):

    [2] Change the XMLXSL file extension from *.xmlxsl to *.xml so that it will behave like a standard XML file.

    [3] Edit the XML file using Notepad (or a similar text editor). The first 4 lines of the file should be:
    ## - XML_XSL
    <?xml version="1.0"?>
    <printout>
    <form-name>patron-loader</form-name>

    [3a] Remove the first line: “## - XML_XSL�.
    The first line in the file is now: “<?xml version="1.0"?>�
    [3b] Add a new 2nd line (between “<?xml version="1.0"?>� and “<printout>�) pointing the XML file to its XSL stylesheet:
    <?xml-stylesheet type='text/xsl' href='[formname].xsl'?>
    Usually you can use the name between the “<form-name>� and “</form-name>� delimiters, but on my machine the name of the patron loader XSL file is “patron-loader-00.xsl�, so on my machine, this is what should be copied between the form-name delimiters. Check in your XSL template directory to be sure about the file name.

    The first 4 lines of the XML file should now be:
    <?xml version="1.0"?>
    <?xml-stylesheet type='text/xsl' href='patron-loader-00.xsl'?>
    <printout>
    <form-name>patron-loader</form-name>

    Save and close the XML file.

    [4] Once these steps are complete, opening the modified XML file in your default Internet Browser (for example, by double-clicking on the file in Windows Explorer) should display the report.

    • Article last edited: 10/8/2013