Re: Connection reuse, WAS: Remove Command Fails Myseriously

Jeff Cantin wrote:
> If it is generally true that connections can't be reused, maybe we
> should put a notification or exception-by-default on the connection
> if it's used more than once. This could be turned off with a system
> property, but it would prevent so many people from seeing mysterious
> behavior from what looks like the library. 
> 

good idea. anyone volunteers to submit the patch?

Milos

> 
> 
> --- Milos Kleint <[email protected]> wrote:
> 
>>As I replied to Robbie Gibson yesterday, the probable cause is that
>>you don't create a new 
>>connection each time. yes, it's weird, I assume the cvs server
>>doesn't do proper cleanup after the 
>>add command is initiated. The library was initially designed (or at
>>least allows it) to shere the 
>>connection among the commands, however the server doesn't like it.
>>
>>
>>Matt Small wrote:
>>
>>>Hi all, I've been fighting this problem for the last 6 hours or
>>
>>so, and I
>>
>>>just cannot figure out what might be going wrong. Whenever I add
>>
>>a new file
>>
>>>with the add command (and commit), and then immediately remove
>>
>>it, the
>>
>>>command fails. However, if I do the add then restart my VM, or
>>
>>get a new CVS
>>
>>>connection between the execution of the Add and the Remove
>>
>>everything seems
>>
>>>to work fine. What is really confusing me though is that when I
>>
>>trace the
>>
>>>Output Stream, everything I send to the server (on the remove
>>
>>command) is
>>
>>>exactly the same in both cases:
>>>
>>>Directory cmsRoot/WNN/includes
>>>/usr/local/src/clickability/cmsRoot/WNN/includes
>>>Entry /m6/1.1///
>>>Directory .
>>>/usr/local/src/clickability
>>>Argument cmsRoot/WNN/includes/m6
>>>remove
>>>
>>
>>Well, there are also the header requests that can play a role. IMHO
>>the cause is unproper cleanup at 
>>the server side.
>>
>>Milos
>>
>>
>>>The successful response to this request is as follows:
>>>
>>>E cvs server: scheduling `cmsRoot/WNN/includes/m6' for removal
>>>Checked-in cmsRoot/WNN/includes/
>>>/usr/local/src/clickability/cmsRoot/WNN/includes/m6
>>>/m6/-1.1///
>>>E cvs server: use 'cvs commit' to remove this file permanently
>>>ok
>>>
>>>But when I do the remove immediately after adding, I get the
>>
>>following
>>
>>>response from the server:
>>>
>>>E cvs server: file `cmsRoot/WNN/includes/m6' still in working
>>
>>directory
>>
>>>E cvs server: 1 file exists; remove it first
>>>ok
>>>
>>>It just doesn't make sense to me how the same request can
>>
>>consistently
>>
>>>behave differently under different conditions. I am using the
>>>setDeleteBeforeRemove(true) method and the file is actually being
>>
>>deleted
>>
>>>properly. 
>>>
>>>Any advice would be greatly appreciated. I am using a very recent
>>
>>version of
>>
>>>the HEAD of the javacvs lib.
>>>
>>>Thanks
>>>
>>>Matt
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
> ---------------------------------------------------------------------
> 
>>>To unsubscribe, e-mail: [email protected]
>>>For additional commands, e-mail: [email protected]
>>>
>>
>>
>>
>>
>>
> ---------------------------------------------------------------------
> 
>>To unsubscribe, e-mail: [email protected]
>>For additional commands, e-mail: [email protected]
>>
> 
> 
> 
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Health - Feel better, live better
> http://health.yahoo.com
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>