Menu
▾
▴
[eclipse-ccase-develop] [ eclipse-ccase-Bugs-3036429 ] Timeout problems with long running cleartool process
|
From: SourceForge.net <no...@so...> - 2013-01-15 15:29:54
|
Bugs item #3036429, was opened at 2010-07-29 00:13 Message generated for change (Comment added) made by eraonel You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=460297&aid=3036429&group_id=50595 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: 2.x Status: Open Resolution: Accepted Priority: 2 Private: No Submitted By: Achim Bursian (achim66) Assigned to: Mikael Petterson (eraonel) Summary: Timeout problems with long running cleartool process Initial Comment: ClearCase Java API 2.2.3.v20100527231 Eclipse 3.6.0 My Eclipse projects are associated with ClearCase. Initially all communications with the VOB server while executing commands are successful. If after having remained idle for a period of time (maybe an hour or so) and I attempt a team command such as check out, I will often receive the following message: db_start_trans_get_info_V3: RPC: Unable to send; errno = [WINSOCK] Connection reset by peer Check database log on VOB host "some_host.some_domain.com". --> finished, exit status 1, duration: 109ms cleartool: Error: Trouble communicating with VOB database: "\an_admin_vob". cleartool: Error: Unable to search for process guards cleartool: Error: Unable to create branch requested by -mkbranch option in config spec. cleartool: Error: Unable to check out "C:\path_to_file_in_vob\some_file.java". At this point I can no longer execute commands offered via the ClearCase integration inside Eclipse. ClearCase commands outside of Eclipse continue to function as expected. The only way to regain ClearCase command integration within Eclipse is to restart Eclipse. Then all is well again, at least until this condition comes up again. Does this ring any bells? I would be most pleased if I could regain communictions with ClearCase without restarting Eclipse. Once I restart it seems as though the ClearCase plugin wants to completely refresh my code base with ClearCase and that operation takes a bit of time to complete. Let me know what you think, and thanks for a great piece of software! This variant of the ClearCase plugin is so much better than it's ever been. (by bhoylma on help forum, https://sourceforge.net/projects/eclipse-ccase/forums/forum/167189/topic/3785183) ---------------------------------------------------------------------- >Comment By: Mikael Petterson (eraonel) Date: 2013-01-15 07:29 Message: I guess we could try to rewrite SingleProcessCommand to terminate the ExecutionManagementThread when a certain time limit has passed we can stop the process. //Mike ---------------------------------------------------------------------- Comment By: Mikael Petterson (eraonel) Date: 2013-01-15 06:53 Message: Hi, Is the same commands working and failing as listed in the http://netbeans.org/bugzilla/show_bug.cgi?id=137539 ? br //mike ---------------------------------------------------------------------- Comment By: Boomer (lokimon) Date: 2013-01-10 05:00 Message: Seeing the same thing in 2.2.27. ---------------------------------------------------------------------- Comment By: Mikael Petterson (eraonel) Date: 2012-12-31 00:44 Message: I am not sure if this is solved. Neatbeans cc plugin had similair problem: http://netbeans.org/bugzilla/show_bug.cgi?id=137539 Problem was in the cleartool shell hangs and they fixed it with creating a new process. I will leave this open for a while to see if problem still persists. //mike ---------------------------------------------------------------------- Comment By: https://www.google.com/accounts () Date: 2011-05-23 05:38 Message: Just wandering if you had a chance to implement a 'kill process' operation whenever a cleartool command fails. My system (Windows 7/64, plugin version 2.2.28) continues to lose contact with the cleartool process once in a while (at least once a day) and I need to manually kill the process to continue (or restart eclipse). Thanks ---------------------------------------------------------------------- Comment By: Achim Bursian (achim66) Date: 2010-07-29 00:16 Message: Thanks, Reuben, that helps a lot. This proves that it is not a problem inside the plugin, but really in the cleartool subprocess. The only thing we could do to work around this is to implement an internal timeout, after which the cleartool subprocess gets reaped and respawned. Would be good to know if that happens only after a long idle time, or if it could happen even with ClearCase activity all the time. If the idle time is the important thing, then we could send a regular "pwv" to the cleartool subprocess every 60 seconds or so, maybe that would cure the whole issue, too...? ---------------------------------------------------------------------- Comment By: Achim Bursian (achim66) Date: 2010-07-29 00:16 Message: by rsivan 2010-07-28 12:55:57 CEST Achim, I followed your advice, killed the cleartool process, and right away a new process was spawned and the operation (a check-out) that was failing took place correctly without restarting eclipse. Hope this info is useful. Thanks, Reuben ---------------------------------------------------------------------- Comment By: Achim Bursian (achim66) Date: 2010-07-29 00:15 Message: by achim66 2010-07-27 11:03:21 CEST Also, for testing, if that condition appears: Open the task manager, and look for a running cleartool process (on the task tab). Kill that, without exiting Eclipse, and then try to do a ClearCase operation in Eclipse. Does it work then? We keep one long running cleartool process, and maybe there are internal timeout problems inside the ClearCase subsystem. If the above mentioned process does cure it, there might be a chance to add some special handling to the plugin. ---------------------------------------------------------------------- Comment By: Achim Bursian (achim66) Date: 2010-07-29 00:15 Message: by eraonel 2010-07-27 10:04:09 CEST Hi, Peace are you using windows? What version? I Reuben and you both have windows then it is specific to win platform. Peace can you send the log from Vob server ( when you get this error) if you have access to it? I 'googled' a bit and found that there is known error for windows: http://www-01.ibm.com/support/docview.wss?uid=swg21142584 but I want to be sure since your provided log does not really tell if it is related to this problem. //mike ---------------------------------------------------------------------- Comment By: Achim Bursian (achim66) Date: 2010-07-29 00:14 Message: by rsivan: 2010-07-27 04:55:22 CEST Same problem in my environment, same workaround found. I'm on Windows 7/64, eclipse 64, JVM 64. Have the same problem in both Galileo and Helios. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=460297&aid=3036429&group_id=50595 |