Incompatible JAR files

Document created by thanh_n88 Employee on May 9, 2018Last modified by thanh_n88 Employee on May 11, 2018
Version 9Show Document
  • View in full screen mode

Sometimes other jar files will conflict with the libraries already loaded in the platform, especially as custom jar files get older or are not maintained anymore.

 

Issue

The most common errors are:

  1. Your process starts failing with "org.xml.sax.SAXNotRecognizedException: Property 'http://javax.xml.XMLConstants/property/accessExternalDTD' is not recognized"
  2. Your process starts failing with "org.xml.sax.SAXNotRecognizedException: http://javax.xml.XMLConstants/feature/secure-processing"
  3. Your process starts failing with an XML non-document related error similar to the above
  4. Your installed libraries tab for the atom is not loading even though other tabs might be working

 

Cause

At some point one or some of the following jar files were added directly to the userlib or lib directory in the atom installation directory:

NoteYou should never add any custom jar files directly to the lib directory.

 

xalan.jar and other xalan*.jar
xerces.jar and other xerces*.jar 

xercesImpl.jar and other xercesImpl*.jar 
xml-apis.jar and other xml-apis*.jar

 

We do not advocate adding jar files directly to the userlib directory unless you are a cloud and really want a jar file(s) to be universally available to all of your tenants. On cloud atoms, tenants should be making custom libraries and deploying them to the environment instead.

 

Solution

Remove the jar file(s) from the userlib or lib directory if they are not actually being used anymore or create a custom library with the jar file(s) and deploy to the desired environment. In the case where you have some library that is directly using any of the incompatible jar files and its classes, you will need to contact your vendor. A known example is the JDE database jar directly using xerces.jar and removing it it is not an option since that interferes with the JDE database connection.

 

Note: If you are getting "http://javax.xml.XMLConstants/property/accessExternalDTD is not recognized" errors but do not have any incompatible jar files (or already tried removing the suspected ones without a change in result), make sure you are on at least Java 1.7.0_55 (for Java 7) or 1.8.0_66 (for Java 8). 

 

How to Create and Deploy a Custom Library

You can also follow the help guide here, Creating a Custom Library component

1. Go to your Setup (top right Account name's drop down menu) -> Account Libraries

2. Click "Upload a File"

3. Choose your jar file and click "Upload"

4. Go the Build tab and make a new "Custom Library" component

Note:

If you choose "General" as the Custom Library Type, the jar files will be placed under the userlib folder.

If you choose "Scripting", the jar files will be placed under the userlib/scripting folder.

If you choose "Connector", you will then choose a connector and the jars will be placed under userlib/<<connector_type>> folder, i.e. choosing the database connector will place those jars into the userlib/database folder.

 

5. Click on "Select JAR files to add" and drop down list with all of the jars you have uploaded in the account libraries will be populated. Pick your jars one at a time. Once selected, you will not see it in the list again and it will populate in the list underneath the "Select JAR files to add"

 

6. Save the component and deploy it to the desired environment

7. Once successfully deployed, the jars should show up in the "Installed Libraries" tab in that atom information. Their location will correspond with what you choose as the Custom Library Type and should reflect in the path

 

Note: Atoms and molecules will get physical copies placed in the corresponding locations. Tenants who deploy a custom library will have them placed in the accounts folder of the cloud directory, <<cloud_installation_directory>>/accounts/account_id/userlib. Deploying a custom library directly to a cloud will not place the jar files physically anywhere in the installation directory. 

1 person found this helpful

Attachments

    Outcomes