It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×7,479
×6,033
×1,230

question asked: Mar 06 '14, 5:55 a.m.
question was seen: 6,364 times
last updated: Apr 22 '14, 9:56 a.m.

Related questions

DOORS and Insight Integration

0
MiYoung Hong (1●3●4) | asked Mar 06 '14, 5:55 a.m.
edited Mar 06 '14, 5:57 a.m.

I 'm trying to extract data from doors using REST services. (DOORS 9.5.2.1 and Insight 1.1.3)

But I got a error like below when I tried to run the CLM4.0.5_all Job in RM_ODS.

This is the context and error message.  Could anybody help me how to solve this problem?
Run context:
JobStream 'RM4.0.5'
 JobStream 'RM_ODS4.0.5_DeltaLoad'
  JobStream 'RM_ODS4.0.5'
   JobStream 'DOORS_PROJECT'
    Build 'DOORSProject'

[PROGRESS   - 19:43:00] Fact Build 'DOORSProject'
[PROGRESS   - 19:43:00] Parsing Reference Definition
[PROGRESS   - 19:43:00] Validating Build Specification
[PROGRESS   - 19:43:02] Checking Fact Data existence

03/06/2014 19:43:02,345 INFO  Thread-5 com.ibm.rational.drivers.jdbc.xml.internal.PageFetcherThread : CRRRE1219I: initial URL request => http://rationaldemo:8080/dwa-rrtranslator/publish/linktypes/*?resetDataset=true&size=1&modifiedsince=1899-12-31T00:00:00.000%2B0900
03/06/2014 19:43:04,628 ERROR Thread-5 com.ibm.rational.drivers.jdbc.xml.internal.PageFetcherThread : An exception occurred when connecting to the remote server:
java.io.IOException: Server returned HTTP response code: 500 for URL: http://rationaldemo:8080/dwa-rrtranslator/publish/linktypes/*?resetDataset=true&size=1&modifiedsince=1899-12-31T00:00:00.000%2B0900
 at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1479)
 at com.ibm.rational.drivers.jdbc.xml.internal.PageFetcherThread.exeFetch(PageFetcherThread.java:423)
 at com.ibm.rational.drivers.jdbc.xml.internal.PageFetcherThread.run(PageFetcherThread.java:136)
03/06/2014 19:45:40,310 ERROR Thread-5 com.ibm.rational.drivers.jdbc.xml.internal.PageFetcherThread : com.ibm.rational.etl.common.exception.ETLException:

5 answers

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Francesco Chiossi (5.7k●1●11●19) | answered Mar 06 '14, 6:04 a.m.
Hello MiYoung,

HTTP error 500 usually means that the source application (DOORS in this case) had an internal error.
To further troubleshoot I would suggest 2 things:
  1. Try to paste the URL in the error message in your browser address bar, logging is as the same DOORS user that is configured in the xdc file, ans see what happens.
  2. Check the DOORS logs at the time the error 500 occurs for error messages.

Best Regards,

Francesco Chiossi

0
permanent link
Maeve OReilly (381●3) | answered Mar 06 '14, 7:36 a.m.
It's the DWA festival logs that are important on DOORS side - server/festival/logs

I would also double check also that you have set <f:property name="disable.oauth" value="true" /> in the festival.xml.

And that working set defined in DOORS is not the entire database (assuming that is large).  Just add a couple of modules to begin with.  
0
permanent link
jean-claude vauthier (226●3●49●57) | answered Mar 17 '14, 7:01 a.m.
I'm not an expert, but I thought that Doors 9.5.2  ifix 1 was compatible with CLM 4.0.6 and Doors 9.5.2 with CLM 4.0.5.  Maybe I'm wrong.
0
permanent link
Kenji Sarai (960●3●9) | answered Mar 27 '14, 12:47 a.m.
Does the target project contain Korean (double-byte characters)? Please try it with single-byte project name to isolate the problem. 
0
permanent link
jean-claude vauthier (226●3●49●57) | answered Apr 22 '14, 9:56 a.m.
Have you tried https://<servername + https port> /dwa-rrtranslator/publish

When setting up the doors_rrc.xdc file with XML Data Configuration tool instead of http.

I have got a similar problem with Insight 1.1.1.3 + Doors 9.5.2.1 + CLM 4.0.6.

Specifying with https has solved my problem

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.