Contents: MashupHub User and Administrator Guide : Mashup Center 2.0
When creating mashups in the data mashup builder, server nonfatal errors are displayed in the Preview tab in the Details window.
Server nonfatal errors are displayed in the Preview tab in the Details window for the Source operator as well as other operators. The error message shows errors with the text Content Retriever
or Cannot parse imported data
Nonfatal errors are only displayed in the data mashup builder when building a mashup. The errors are not displayed in the View Feed in Browser
In the data mashup, nonfatal errors can occur that do not prevent the mashup from running. These nonfatal errors are logged in the log file.
When building a mashup if you have one Source operator that results in a nonfatal error, you can see this error when you preview other operators that are in the flow of the mashup after the Source operator. For example, if you have two source operators and one of them points to a server that is unavailable, if you have a combine operation that uses the Source operator, the preview in the Combine operator will also display the error.
Nonfatal errors can have various causes, including:
- The URL is inaccessible because the server is unavailable.
- The URL is invalid because of a typographical error.
- The URL is invalid because there is no host.
- The data returned from the URL cannot be parsed. For example, there is an invalid XML character in the URL.
Diagnosing the problem
When data returned from the URL cannot be parsed, for example, when there is an invalid XML character in the data, the following message is displayed in Preview tab in the Details window of the URL:
CDHEN1380E: Cannot parse imported data. - An invalid XML
character (Unicode: 0x1a) was found in the element content
of the document.
Another example of an error when data returned from the URL cannot be parsed:
Server non-fatal errors:
CDHEN1380E: Cannot parse imported data. - The reference to
entity "S_CMP" must end with the ';' delimiter.
For an invalid URL when the host is not known or for an I/OException, the following is an example of the message that is logged in the log file:
2009-05-22 13:42:19,687 (http-8443-Processor24) ERROR
[com.ibm.damia.DamiaException] CDHEN4000E: Content Retriever error
'Could not access 'http://xyz' because the
host is unknown.'
For a typographical error, for example, the URL is typed incorrectly
instead of correctly
, the result is an I/O error when retrieving the data:
CDHEN4000E: Content Retriever error 'Could not access
Resolving the problem
For Content Retriever errors, check the URL in the Source operator and correct any mistakes in it.Administrator Response
Open a browser window and try to access the URL used in the Source operator.
When data returned from the URL cannot be parsed, ensure that the data that the URL is returning is XML that can be parsed by removing any invalid XML characters.
Check the log file to determine if an error was returned.
Parent topic: Troubleshooting problems : Mashup Center 2.0
No data is returned from the data source : Mashup Center 2.0
Operators : Mashup Center 2.0
Source operator : Mashup Center 2.0