[resolved] SAXParseException when uploading DSC Tasks

[Anonymous]

Hi
When I want to upload DSC tasks I get the following error:

java.net.SocketTimeoutException: Read timed out
	at java.net.SocketInputStream.socketRead0(Native Method)
	at java.net.SocketInputStream.read(Unknown Source)
	at java.net.SocketInputStream.read(Unknown Source)
	at java.io.BufferedInputStream.fill(Unknown Source)
	at java.io.BufferedInputStream.read1(Unknown Source)
	at java.io.BufferedInputStream.read(Unknown Source)
	at sun.net.www.http.HttpClient.parseHTTPHeader(Unknown Source)
	at sun.net.www.http.HttpClient.parseHTTP(Unknown Source)
	at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
	at java.net.HttpURLConnection.getResponseCode(Unknown Source)
	at org.talend.datastewardship.server.task.creation.TaskLoadClient.doLoad(TaskLoadClient.java:100)
	at helios.j004_dedup_create_person_tasks_dsc_0_1.j004_DEDUP_create_person_tasks_DSC.tFileInputDelimited_1Process(j004_DEDUP

To see the whole post, download it here

[Anonymous]

Hi,
The lines:

2014-12-11 11:30:52,047 ERROR  Failed to validate XML file through 'D:\app\talend\Talend-MDMServer-r118616-V5.5.1\jboss-4.2.2.GA\server\default\deploy\org.talend.datastewardship.war\WEB-INF\classes\org\talend\datastewardship\server\task\creation\inputTask.xsd
org.dom4j.DocumentException: Error on line 1 of document  : Content is not allowed in prolog. Nested exception: Content is not allowed in prolog.

... are rather strange. It looks like you send malformed DSC tasks to the DSC. Changing the database vendor should not be the cause of the error (issue occurs before store to database). Could you check the DSC task contents you're sending?

[Anonymous]

Hi
Here's an example of a DSC task which should be uploaded:

.--------------------------------------.
|            #1. tLogRow_1             |
+------------------+-------------------+
| key              | value             |
+------------------+-------------------+
| Id               | 775231            |
| FIRST_NAME       | Erik              |
| LAST_NAME        | Verlaet           |
| FULL_NAME        | Erik Verlaet      |
| GENDER_CD        | Male              |
| LANGUAGE_CD      | nl                |
| WORK_STREET_NAME | Koekoekstraat     |
| WORK_HOUSE_NR    | 121               |
| WORK_STREET_CD   | 6601              |
| WORK_POSTAL_CD   | 2627              |
| WORK_CITY        | Schelle           |
| WORK_COUNTRY     | BE                |
| FAX              |                   |
| WORK_PHONE       |                   |
| EMAIL            | admin@bel-east.be |
| SOURCE_CD        | CP3               |
| matchingGroup    | Ud37              |
| score            | 0.0               |
| groupQuality     | 0.0               |
| staticTag        | DuplicatePerson   |
| weights          | 0                 |
| isTarget         | false             |
+------------------+-------------------+
.-------------------------------------------.
|               #2. tLogRow_1               |
+------------------+------------------------+
| key              | value                  |
+------------------+------------------------+
| Id               | 203131                 |
| FIRST_NAME       | Erik                   |
| LAST_NAME        | Verlaet                |
| FULL_NAME        | Erik Verlaet           |
| GENDER_CD        | Male                   |
| LANGUAGE_CD      | nl                     |
| WORK_STREET_NAME | Koekoekstraat          |
| WORK_HOUSE_NR    | 121A                   |
| WORK_STREET_CD   | 6601                   |
| WORK_POSTAL_CD   | 2627                   |
| WORK_CITY        | Schelle                |
| WORK_COUNTRY     | BE                     |
| FAX              |                        |
| WORK_PHONE       |                        |
| EMAIL            | erik.verlaet@skynet.be |
| SOURCE_CD        | CP3                    |
| matchingGroup    | Ud37                   |
| score            | 0.0                    |
| groupQuality     | 0.0                    |
| staticTag        | DuplicatePerson        |
| weights          | 0                      |
| isTarget         | false                  |
+------------------+------------------------+

Kind regards
Dries

[Anonymous]

It seems the tStewardshipTaskOutput component is sending an invalid XML to the DSC. You could check if XML sent over http is correct by sniffing the traffic. I suggest you also to contact Support team to help you on that issue.