Re: The XML response contains invalid XML

[OlePinto]

We have finally fixed it, although we sadly do not really know what the
problem was.
The magic medicine has been: run /netsh int ip reset c:\filename.log/,
reset, reconfigure the network, and done!
So it seems it was a client problem, but I don't really know even what kind
of problem it was.
Did it help anyone else?




--
View this message in context: 
http://subversion.1072662.n5.nabble.com/The-XML-response-contains-invalid-XML-tp186929p193059.html
Sent from the Subversion Users mailing list archive at Nabble.com.

Re: The XML response contains invalid XML

[OlePinto]

Hello, I am having the same problem (more or less). We have thoroughly
investigated it in-house, but have no more clues about what to look for.
I'll begin saying the server is running under Glassfish + SCM, in case it
switches a light before going on reading.
We can reproduce the problem doing a merge from trunk into a branch. Most of
the files are about 100Kb or smaller; there is a big binary (about 37 Mb)
which can not be merged.
The merge starts, the filenames go up the screen. It pauses while processing
the big-file and after a while it gives the error "E130003 the xml response
contains invalid xml". About 10s later, the svn command ends.
It happened with 1.8.10 and still happens with 1.8.13, both under WinXp (so
32 bits).
It doesn't happen to my colleagues, all with Win7. We have reproduced it in
a virtual machine running WinXp, but it happens randomly there (in my
machine it happens every time). (hint: a client problem?)
We have made a copy of the production repo (PROD) into a VM (COPY).
Let's say the structure of the repo goes like
'/produccion/juegos/Mex/trunk'. In order to discard WC problems, we checkout
a fresh one.
I run the following:
 and then

Then, after cd'ing into COPY/branches/arcoiris and PROD/branches/arcoiris,
we do

Under COPY it works flawlessly, but it fails under PROD. (hint: a server
problem?).
The whole merge takes 22s under COPY, and 1,5m under PROD.
We have captured the comms, I think they look good. The client is the one
closing the connection, so we don't think the server is the one deciding to
finish the transaction.
 
We have enabled debug logging in glassfish and svn, we can't find any
difference between successful and failed transactions.
I randomly get also "E125012: Invalid character in hex checksum"; maybe it
has any relation to the former, maybe not.
Any idea? Any other test or information that could be useful?



--
View this message in context: 
http://subversion.1072662.n5.nabble.com/The-XML-response-contains-invalid-XML-tp186929p193058.html
Sent from the Subversion Users mailing list archive at Nabble.com.

RE: The XML response contains invalid XML

[Bert Huijben]

> -Original Message-
> From: OlePinto [mailto:olepinto+...@gmail.com]
> Sent: dinsdag 21 april 2015 12:20
> To: users@subversion.apache.org
> Subject: Re: The XML response contains invalid XML
> 
> We have finally fixed it, although we sadly do not really know what the
> problem was.
> The magic medicine has been: run /netsh int ip reset c:\filename.log/,
> reset, reconfigure the network, and done!
> So it seems it was a client problem, but I don't really know even what
kind
> of problem it was.
> Did it help anyone else?

What kind of virusscanner / firewall do/did you run on this machine?

This command removes custom settings on the IP stack, which may include
third party hooks. Adding this information to this thread may help resolve
the problem in the future.

There might be valuable information in the 'c:\filename.log' file created by
running this command. Did you check that file?

Bert

RE: The XML response contains invalid XML

[OlePinto]

I did, but we haven't found anything worthy. The file follows.
resetlog.txt
  
The client's machine is running a McAffee, before and after the fix. The
server is running some antivirus, which we even switched off to test (no
change).



--
View this message in context: 
http://subversion.1072662.n5.nabble.com/The-XML-response-contains-invalid-XML-tp186929p193061.html
Sent from the Subversion Users mailing list archive at Nabble.com.

Merge from a branch of a branch to trunk, losing files

[Robert Voliva]

Hello,

I created a branch off of trunk.  Files were added to that branch.  A
branch was created off of that branch.  Files were added/changed in that
branch.  The second branch was merged back to trunk.  The files added in
the first branch, before the second branch was cut from it, were not
included in the merge.

Slightly more visual:

trunk
project1
file1
(make branch)
branches
branch1
file1
branchfile1
(make branch of branch1)
branch2
file1
branchfile1
branchfile2
branchfile3

When you go to merge branch2 into trunk, branchfile1 is not merged.  Can
someone explain this to me as to what is going on?  Bug in svn?
Documentation to why you can't do this?

Thanks,
Robert Voliva

Re: svndumptool and svn:externals

[Ryan Schmidt]

On Apr 20, 2015, at 6:56 AM, MOKRANI Rachid wrote:

> I moved my SVN server, and now I need to change our svn:externals path.
> 
> I saw that svndumptool can help me to do that, but I don't know exactly the 
> syntax command to run.
> 
> 
> My old SVN server is:
> http://my_old_server/
> 
> I can access to my SVN project with the URL : 
> http://my_old_server/R11/MY_PROJECT
> 
> 
> Name Value
> svn:externals AA http://my_old_server/R11/MY_PROJECT/AA
>   BB http://my_old_server/R11/MY_PROJECT/BB
> 
> 
> 
> 
> New server :
> https://my_new_server/
> Now I can access to my SVN project with the URL : 
> http://my_new_server/svn/MY_PROJECT
> 
> Need to change my svn:externals path to:
> Name Value svn:externals  AA http://my_new_server/svn/MY_PROJECT/AA
>   BB http://my_new_server/svn/MY_PROJECT/BB
> 
> 
> 
> 
> 
> Is the following command is correct ? Or what is exactly the good syntax.
> 
> svndumptool.py transform-prop svn:externals '^(\S+) 
> http://my_old_server/R11(\S+)' '^\1 https://my_new_server/svn/\2'  SVN.dump   
> SVN_ext.dump
> 
> and/or 
> 
> svndumptool.py transform-prop svn:externals "(\S*) (|-r ?\d* 
> ?)http://my_old_server/R11(/\S*)" "\2\3 \1"   SVN.dump   SVN_ext.dump
> 
> other ?

If you have externals that refer to your own repository by its absolute URL, 
then I recommend you switch those to the "new" (as of Subversion 1.5) relative 
URL externals syntax so that you never have to do this again even if you change 
repository locations again in the future.