Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik Open Lakehouse is Now Generally Available! Discover the key highlights and partner resources here.

'Property 'http://javax.xml.XMLConstants/property/accessExternalDTD' is not recognized' is still being thrown from Camel validator

100% helpful (2/2)
cancel
Showing results for 
Search instead for 
Did you mean: 
TalendSolutionExpert
Contributor II
Contributor II

'Property 'http://javax.xml.XMLConstants/property/accessExternalDTD' is not recognized' is still being thrown from Camel validator

Last Update:

Mar 5, 2024 4:32:47 AM

Updated By:

Sonja_Bauernfeind

Created date:

Apr 14, 2021 5:37:36 PM

As covered in the Talend Community Knowledge Base (KB) article Exception Property 'http://javax.xml.XMLConstants/property/accessExternalDTD' is not recognized, this was fixed in Talend ESB 7.

However, when a route uses the validator feature in Talend ESB 7, the follow error is thrown:

org.xml.sax.SAXNotRecognizedException: Property 'http://javax.xml.XMLConstants/property/accessExternalDTD' is not recognized.
at org.apache.xerces.jaxp.validation.ValidatorImpl.setProperty(Unknown Source) [?:?]
at org.apache.camel.processor.validation.ValidatingProcessor.doProcess(ValidatingProcessor.java:110) [226:org.apache.camel.camel-core:2.21.2]

 

Cause

The validator itself is working in Talend ESB 7. These warnings are harmless and shouldn't affect the functionality of the validator.

 

Resolution

To suppress these warnings so that they don't fill up the tesb.log files, edit the RUNTIME-HOME/etc/org.ops4j.pax.logging.cfg file and add the following lines:

log4j2.logger.validatingProcessor.name=org.apache.camel.processor.validation.ValidatingProcessor
log4j2.logger.validatingProcessor.level=ERROR
log4j2.logger.schemaReader.name=org.apache.camel.processor.validation.SchemaReader
log4j2.logger.schemaReader.level=ERROR
Labels (1)
Comments
mgoedhart
Contributor III
Contributor III

Hi Jamie,

This solution doesn't work in Talend ESB 8.

Still see the warning.

Do I have to add other classes to the org.ops4j.pax.logging.cfg file?

Best regards

Marius

Xiaodi_Shi
Employee
Employee

Hello,

Please make sure that you do restart the karaf.

Could you please let us know if the validator itself is working in your Talend ESB 8? Do these warnings affect the functionality of the validator from your side?

Best regards

Sabrina

mgoedhart
Contributor III
Contributor III

Hi,

The validator itself is working in Talend ESB 8.

The warnings still appear after restarting karaf.

 

Best regards

Marius

mgoedhart
Contributor III
Contributor III

Hi,

I noticed that the bundle name has changed in the camel 3 version. So I changed the following in the configuration file (support is added)

log4j2.logger.validatingProcessor.name = org.apache.camel.support.processor.validation.ValidatingProcessor
log4j2.logger.validatingProcessor.level = ERROR

log4j2.logger.schemaReader.name = org.apache.camel.support.processor.validation.SchemaReader
log4j2.logger.schemaReader.level = ERROR

 

Now the exception warnings are gone.

Thanks for the help

Best regards

Marius

Xiaodi_Shi
Employee
Employee

Hello,

It is a very good solution to add "Support" here and thank for sharing it with us.

Best regards

Sabrina

Version history
Last update:
‎2024-03-05 04:32 AM
Updated by: