| his technote explains why an IBM® Rational® ClearCase® Remote Client (CCRC) on Microsoft® Windows® may fail during a load and the debug trace output reports the error, ccweb: Error: Unable to commit item. | | | | Symptom | - When attempting a load from a CCRC Windows machine when the VOB and RWP server are hosted on a UNIX® or Linux® host, the load hangs.
- When a CCRC client side trace is performed, errors like these are seen for many files:
Apr 14, 2008 4:50:45 PM GMT::TRACE::HTTP_CLIENT::content::log::[DEBUG] << ".ccweb: Error: INTERNAL ERROR detected and logged in "/var/adm/rational/clearcase/log/error_log".[\n]"
Apr 14, 2008 4:50:45 PM GMT::TRACE::HTTP_CLIENT::content::log::[DEBUG] << "ccweb: Error: Unable to commit item "src/" "file.txt"[\n]"
- The error log reports errors like:
ccweb: Error: Mon Apr 14 09:00:00 EDT 2008. host "vob_server", pid 762036, user "jdoe" Internal Error detected in "../ccw_ws.cxx" line 4122
Refer to technote 1234118 How to setup up debug tracing for the ClearCase Remote Client for further information about CCRC tracing.
- When an attempt is made to load the view through CCWeb, an error like this is generated:
Error: "java.io.FileNotFoundException: C:\ccwebviews\web_view\vob\src\con.loading.1.2.3.4.5... ...6751.6752.6753 (The system cannot find the path specified)"
Note: If the same load is attempted on a UNIX/Linux machine, the load finishes successfully. | | |
|
 |
|
| Cause |
A file or folder being loaded into the view has a Windows' reserved word as its name.
The CCWeb error actually shows the problem file. In the example above the file is named 'con'.
The load is not completing because 'con' is a reserved word on Windows, but it is not a reserved word on UNIX or Linux; hence, there is no problem on either OS.
When the attempt is made to create the file or folder, the OS changes the name to something else without throwing an error, which results in the path not being found and the CCRC load hangs at that point. |
| |
|
| Resolving the problem |
To resolve this issue, the file must be renamed to an allowable name on both Windows as well as UNIX and Linux.
To prevent this problem, you must avoid using names that are reserved by the operating system, especially in a mixed environment, refer to technote 1131223 for more details About naming conventions and characters used to create ClearCase objects. |
No comments:
Post a Comment