[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: JDeveloper & svn 1.4.0 -- Malformed network data?

From: Mark Phippard <markp_at_softlanding.com>
Date: 2006-09-12 15:43:23 CEST

"Gale, David" <David.Gale@Hypertherm.com> wrote on 09/12/2006 09:23:09 AM:

> I upgraded our svn server yesterday to 1.4.0, and tested through the
> command line and tortoisesvn (both 1.3.2 versions, using 1.3.2 working
> copies). Everything looked good. I have not yet upgraded the
> repositories to 1.4.0 through a dump-load process.
> This morning, one of our Java developers said that they're having
> problems with committing to the repository--every commit results in
> "Malformed Network Data", and the files are marked as having conflicts.
> He said that they'd applied a service pack to their JDeveloper installs
> last Friday, and isn't sure that they tried committing to the repository
> between then and when I upgraded the server. They're now on JDeveloper
> Is anyone else having this issue? Or, does anyone have any idea what we
> could do to fix it?
> The server is redhat, running svnserve. There is no proxy.

I believe that JDeveloper uses JavaSVN to talk to Subversion. I know that
this has not been updated to 1.4 yet, but I would assume that would only
cause problems with working copy formats. I wonder if the server and
client are not property negotiating the use of the new svndiff1 protocol
format? It should fall back to the old format but maybe JavaSVN is not
handling something correctly.

Just speculating. I am not even sure if JDeveloper uses JavaSVN
exclusively or not.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Sep 12 16:04:08 2006

This is an archived mail posted to the Subversion Users mailing list.