You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by theresa merenkov <th...@oracle.com> on 2011/10/13 10:54:29 UTC
Subversion exception svn update
I was using Tortoise SVN 1.6 and began having problems loading a file
that was 1gig up through the high speed internet provider I have Astound
broadband. I think this is a network issue, because I get the same
message, if I'm uploading a large amount of data (could this be Apache
problem?) I get this message:
Command: Commit
Modified: D:\GCDP_Repository\method-pub\installshield
packaging\0_installshield_projects\OUM_5.5.0_Project\OUM_5.5.0\Oracle_OUM_5.5.0_Install.exe
Sending content: D:\GCDP_Repository\method-pub\installshield
packaging\0_installshield_projects\OUM_5.5.0_Project\OUM_5.5.0\Oracle_OUM_5.5.0_Install.exe
Error: Commit failed (details follow):
Error: PUT of
Error:
'/svn/method-pub/!svn/wrk/3883a3a4-badd-1947-aa1f-0e12d0d7f338/trunk/installshield%20packaging/0_installshield_projects/OUM_5.5.0_Project/OUM_5.5.0/Oracle_OUM_5.5.0_Install.exe':
Error: SSL handshake failed: An existing connection was forcibly closed
by the remote host.
Error: (https://gcdpsource.oracle.com)
Finished!:
I decided to go to SVN 1.7, and therefore encountered the requirement to
do a SVN Updgrade working copy on EVERY ONE OF MY checkout project areas.
So I upgraded a working copy in one of my workspaces and then tried to
do an SVN Update of a folder with a large file in it.
Now when I try to execute the svn cleanup command I get this message
repeatedly.
Any ideas? Thanks much for your help.
Subversion Exception!
---------------------------
Subversion encountered a serious problem.
Please take the time to report this on the Subversion mailing list
(users@subversion.apache.org)
with as much information as possible about what
you were trying to do.
But please first search the mailing list archives for the error message
to avoid reporting the same problem repeatedly.
You can find the mailing list archives at
http://subversion.apache.org/mailing-lists.html
Subversion reported the following
(you can copy the content of this dialog
to the clipboard using Ctrl-C):
In file
'D:\Development\SVN\Releases\TortoiseSVN-1.7.0\ext\subversion\subversion\libsvn_wc\workqueue.c'
line 672: assertion failed (checksum != NULL)
I guess my other option is to delete the checkout and checkout the files
again... Why didn't anyone say svn was a total re-checkout of all
repositories BEFORE I upgraded!
--
Oracle <http://www.oracle.com>
Theresa Merenkov, CSM, PMP | Global Methods Senior Director
Phone: +1 925 939-7792 <tel:+1%20925%209397792> | Fax: +1 925 939-8042
<fax:+1%20925%209398042> | Mobile: +1 510 599-2606 <tel:+1%20510%205992606>
Oracle Global Methods
Northern California
http://methods.oraclecorp.com
Join in on the discussion about the Oracle® Unified Method (OUM)
OUM on LinkedIn <http://www.linkedin.com/groups?gid=3774161> l OUM on
Twitter <http://twitter.com/oum_info> l OUM Blog
<http://blogs.oracle.com/oum/>
------------------------------------------------------------------------
Green Oracle <http://www.oracle.com/commitment> Oracle is committed to
developing practices and products that help protect the environment
Re: Subversion exception svn update
Posted by Andy Levy <an...@gmail.com>.
On Thu, Oct 13, 2011 at 04:54, theresa merenkov
<th...@oracle.com> wrote:
>
> I was using Tortoise SVN 1.6 and began having problems loading a file that was 1gig up through the high speed internet provider I have Astound broadband. I think this is a network issue, because I get the same message, if I'm uploading a large amount of data (could this be Apache problem?) I get this message:
> Command: Commit
> Modified: D:\GCDP_Repository\method-pub\installshield packaging\0_installshield_projects\OUM_5.5.0_Project\OUM_5.5.0\Oracle_OUM_5.5.0_Install.exe
> Sending content: D:\GCDP_Repository\method-pub\installshield packaging\0_installshield_projects\OUM_5.5.0_Project\OUM_5.5.0\Oracle_OUM_5.5.0_Install.exe
> Error: Commit failed (details follow):
> Error: PUT of
> Error: '/svn/method-pub/!svn/wrk/3883a3a4-badd-1947-aa1f-0e12d0d7f338/trunk/installshield%20packaging/0_installshield_projects/OUM_5.5.0_Project/OUM_5.5.0/Oracle_OUM_5.5.0_Install.exe':
> Error: SSL handshake failed: An existing connection was forcibly closed by the remote host.
> Error: (https://gcdpsource.oracle.com)
> Finished!:
If you suspect it's an Apache problem (and it's quite possible that it
is), upgrading your client only adds another variable and element of
risk to the situation. Searching Google for that error plus
"Subversion large upload" eventually yields this:
http://osdir.com/ml/version-control.svk.devel/2007-10/msg00003.html
Short version: your server may be configured to disallow a commit of
the size you're attempting.
> I decided to go to SVN 1.7, and therefore encountered the requirement to do a SVN Updgrade working copy on EVERY ONE OF MY checkout project areas.
>
> So I upgraded a working copy in one of my workspaces and then tried to do an SVN Update of a folder with a large file in it.
>
> Now when I try to execute the svn cleanup command I get this message repeatedly.
>
> Any ideas? Thanks much for your help.
>
>
> Subversion Exception!
> ---------------------------
> Subversion encountered a serious problem.
> Please take the time to report this on the Subversion mailing list
> (users@subversion.apache.org)
> with as much information as possible about what
> you were trying to do.
> But please first search the mailing list archives for the error message
> to avoid reporting the same problem repeatedly.
> You can find the mailing list archives at
> http://subversion.apache.org/mailing-lists.html
>
> Subversion reported the following
> (you can copy the content of this dialog
> to the clipboard using Ctrl-C):
>
> In file
> 'D:\Development\SVN\Releases\TortoiseSVN-1.7.0\ext\subversion\subversion\libsvn_wc\workqueue.c'
> line 672: assertion failed (checksum != NULL)
http://svn.haxx.se/users/archive-2011-10/0213.shtml
> I guess my other option is to delete the checkout and checkout the files again... Why didn't anyone say svn was a total re-checkout of all repositories BEFORE I upgraded!
Because in the majority of cases, it isn't required if your pre-1.7
working copies are clean.