How to track the import to module log in RRC 402?
Yesterday I install RRC 402 in our test environment and I upload the requirement doc to module successfully.
But today I import again, the progress is always in 99% and cannot completed.
I want somebody can tell me what's wrong, but I think the import log may helpful. So can anyone tell me where or how to enable the import log so that I can track problems.
Thanks very much!
I add the exception information in rm.log to provide more information:
the error occurred at 14:21, but when I left in 18:00, the import progress did not complete stay in 99%.
2013-05-23 14:21:57,258 [ http-bio-9443-exec-72] ERROR serPreferences.internal.UserPreferencesRestService - Server Error: Entry [8e8e3e4108789a9]
com.ibm.rdm.fronting.server.exception.ConflictException: com.ibm.rdm.fronting.server.exception.ConflictException
at com.ibm.rdm.fronting.server.exception.RRSException.newException(RRSException.java:166)
......
Request
PUT https://localhost:9443/jts/storage/com.ibm.rdm.userPreferences/a99532506fa16c9a2485874598fde756 HTTP/1.1
If-Match: *
Content-Type: application/rdf+xml
Authorization: OAuth oauth_token_secret="Al8Tl1O6SD1SvqvtLMOhTZwPdrCLJX4p5nJQWH2lw", oauth_nonce="-7105227939098229666", oauth_token="112acac43c23428d862cae231b3cb232", oauth_consumer_key="3c4bd6ee9b1746b59a59d3f697ef0e47", oauth_signature_method="HMAC-SHA1", oauth_timestamp="1369290117", oauth_version="1.0", oauth_signature="Qn3b8WCWcDuoKi54od9xp0HTvEI%3D"
--Start entity---
--End entity-----
Response:
HTTP/1.1 409
Server: Apache-Coyote/1.1
Cache-Control: private
Expires: Thu, 01 Jan 1970 08:00:00 CST
Content-Type: text/html;charset=utf-8
Content-Length: 1173
Date: Thu, 23 May 2013 06:21:56 GMT
Content-Length: 1173
---Start entity---
<html><head><title>Apache Tomcat/7.0.32 - Error report</title><style><!--H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}HR {color : #525D76;}--></style> </head><body><h1>HTTP Status 409 - CRJZS0213E 由于与资源的当前状态发生冲突，因此未能完成此请求。</h1><HR size="1" noshade="noshade"><p><b>type</b> Status report</p><p><b>message</b> <u>CRJZS0213E 由于与资源的当前状态发生冲突，因此未能完成此请求。</u></p><p><b>description</b> <u>The request could not be completed due to a conflict with the current state of the resource.</u></p><HR size="1" noshade="noshade"><h3>Apache Tomcat/7.0.32</h3></body></html>
--End entity------
Comments
Stef van Dijk
FORUM MODERATOR / JAZZ DEVELOPER May 23 '13, 4:20 p.m.There is no specific import log that I'm aware of, though there are some low level options that you can enable to get more detail than just the typical error logging that may occur.
But before we get into all that detail, I would start by just checking the rm.log and jts.log for any clues from around the time you attempted the import.
I have seen cases where the status doesn't update because the tracker resource used to monitor the progress cannot for some reason be updated by the server and thus the web client is under the impression that it has still not completed. I am not sure what causes that to occur, just saying I have seen it.
Jia Jia Li
May 24 '13, 10:13 a.m.Thanks Stef, as your suggestion, I attached the rm.log error information in the question, sorry for the Chinese error msg, and I searched the IBM technotes said the error CRJZS0213E can be ignored.
So what's the problem for import not completed? Could you please help to look out it? Thanks very much!
Stef van Dijk
FORUM MODERATOR / JAZZ DEVELOPER May 24 '13, 3:46 p.m.That exception seems unlikely to be related to your problem. It's a conflict exception trying to save user preferences and not the artifact you are creating as part of the import. This type of error would happen if the preferences had changed since the time they were fetched and now being saved again. Even in those cases, RRC will often retry, so unless you see an error indicating that it still failed after x retries, then this may have resolved itself.
What about the jts.log? Anything of note in there?
I'll try to check around to see if anyone else has encountered this before.
Jia Jia Li
May 30 '13, 8:08 p.m.Thanks Stef, jts.log has anything note. Maybe Chinese characters?But I tried a small size English doc to import to module, it still in 99% and could not completed.