Unhandled Content Status SVNException

Hello Jason,

It seems that your ISVNEventHandler throws exception while 
SVNBasicClient calls its handleEvent() method:

try {
   myEventDispatcher.handleEvent(event, progress);
} catch (SVNException e) {
   throw e;
} catch (Throwable th) {
  SVNErrorMessage err =
SVNErrorMessage.create(SVNErrorCode.UNKNOWN, 
"Error while dispatching event: ",
th.getMessage());
                 SVNErrorManager.error(err, th);
}

Alexander Kitaev,
TMate Software,
http://svnkit.com/ - Java
[Sub]Versioning Library!

Jason Winnebeck wrote:
> I am getting the following exception from dry-run
doMerge:
> 
>  
> 
>         conn.getDiffClient().doMerge(
config.getStableURL(), 
> SVNRevision.HEAD,
> 
>                                      
config.getDevURL(), SVNRevision.HEAD,
> 
>                                       root, true,
false, true, true );
> 
>  
> 
> The exception appears to be coming from SVNKit...
> 
>  
> 
> org.tmatesoft.svn.core.SVNException: svn: Error while
dispatching event: 
> Unhandled content status
> 
>  SVNEventAction.UPDATE_UPDATE
SVNStatusType.INAPPLICABLE 
> SVNStatusType.CHANGED
> 
>       at 
>
org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVN
ErrorManager.java:49)
> 
>       at 
>
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.r
equest(HTTPConnection.java:512)
> 
>       at 
>
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.r
equest(HTTPConnection.java:236)
> 
>       at 
>
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.r
equest(HTTPConnection.java:224)
> 
>       at 
>
org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doRepor
t(DAVConnection.java:219)
> 
>       at 
>
org.tmatesoft.svn.core.internal.io.dav.DAVRepository.diff(DA
VRepository.java:675)
> 
>       at 
>
org.tmatesoft.svn.core.wc.SVNDiffClient.doMerge(SVNDiffClien
t.java:1375)
> 
>       at 
>
org.tmatesoft.svn.core.wc.SVNDiffClient.doMerge(SVNDiffClien
t.java:1193)
> 
>       at
edu.rit.cims.Workflow.SVN.SVN.getDifferences(SVN.java:128)
> 
>  
> 
> I’m not sure what this means, or what could have gone
wrong.
> 
>  
> 
> Thanks,
> 
> Jason
> 

------------------------------------------------------------
---------
To unsubscribe, e-mail: svnkit-users-unsubscribesvnkit.com
For additional commands, e-mail: svnkit-users-helpsvnkit.com

You're right. I thought it was in my code. What I couldn't
figure out is when I was trying to trace it to my code there
is no stack trace linking it back to my code. I was able to
put a debug breakpoint on the line that generates that
message and somewhere in the chain the cause gets dropped.
The culprit is a "bug" in the SAXException class.
In endElement in BasicDAVHandler a SAXException is thrown on
line 73 in version 1.1.3 of svnkit. SVNException does not
support "causes" in the normal JDK way, so it
stores it in its own variable, making getCause() return
null.
 
This exception does get caught and "return
((SVNException) e.getException()).getErrorMessage();"
is executed, which seems that it might trim all but the
"top" exception in the stack.
 
Either way, at least the point of the story for me is that
UPDATE + INAPPLICABLE + CHANGED equals a property change on
a directory. I thought I handled this case when I was
testing over svn and file and not https protocols... But now
I can.
 
Thanks for the help,
 
Jason

________________________________

From: Alexander Kitaev [mailto:Alexander.Kitaevsvnkit.com]
Sent: Wed 7/18/2007 5:29 PM
To: svnkit-userssvnkit.com
Subject: Re: Unhandled Content Status SVNException



Hello Jason,

It seems that your ISVNEventHandler throws exception while
SVNBasicClient calls its handleEvent() method:

try {
   myEventDispatcher.handleEvent(event, progress);
} catch (SVNException e) {
   throw e;
} catch (Throwable th) {
  SVNErrorMessage err =
SVNErrorMessage.create(SVNErrorCode.UNKNOWN,
"Error while dispatching event: ",
th.getMessage());
                 SVNErrorManager.error(err, th);
}

Alexander Kitaev,
TMate Software,
http://svnkit.com/ - Java
[Sub]Versioning Library!

Jason Winnebeck wrote:
> I am getting the following exception from dry-run
doMerge:
>
> 
>
>         conn.getDiffClient().doMerge(
config.getStableURL(),
> SVNRevision.HEAD,
>
>                                      
config.getDevURL(), SVNRevision.HEAD,
>
>                                       root, true,
false, true, true );
>
> 
>
> The exception appears to be coming from SVNKit...
>
> 
>
> org.tmatesoft.svn.core.SVNException: svn: Error while
dispatching event:
> Unhandled content status
>
>  SVNEventAction.UPDATE_UPDATE
SVNStatusType.INAPPLICABLE
> SVNStatusType.CHANGED



------------------------------------------------------------
---------
To unsubscribe, e-mail: svnkit-users-unsubscribesvnkit.com
For additional commands, e-mail: svnkit-users-helpsvnkit.com

Hello Jason,

> This exception does get caught and "return
((SVNException) 
> e.getException()).getErrorMessage();" is executed,
which seems that
> it might trim all but the "top" exception in
the stack.
The reason for loosing stack trace is not in SAXException
actually, but 
in the way it is processed. Indeed original stack trace get
lost during 
this processing and only error message remains. I think we
will fix it 
in one of the next versions.

However, stack trace is logged in BasicDAVHandler, so you
may consider 
running your application with debug logging enabled (set log
level to 
FINEST) to get complete information about the error.

Alexander Kitaev,
TMate Software,
http://svnkit.com/ - Java
[Sub]Versioning Library!

Jason Winnebeck wrote:
> You're right. I thought it was in my code. What I
couldn't figure out
>  is when I was trying to trace it to my code there is
no stack trace 
> linking it back to my code. I was able to put a debug
breakpoint on 
> the line that generates that message and somewhere in
the chain the 
> cause gets dropped. The culprit is a "bug" in
the SAXException class.
>  In endElement in BasicDAVHandler a SAXException is
thrown on line 73
>  in version 1.1.3 of svnkit. SVNException does not
support "causes"
> in the normal JDK way, so it stores it in its own
variable, making 
> getCause() return null.
> 
> This exception does get caught and "return
((SVNException) 
> e.getException()).getErrorMessage();" is executed,
which seems that 
> it might trim all but the "top" exception in
the stack.
> 
> Either way, at least the point of the story for me is
that UPDATE + 
> INAPPLICABLE + CHANGED equals a property change on a
directory. I 
> thought I handled this case when I was testing over svn
and file and 
> not https protocols... But now I can.
> 
> Thanks for the help,
> 
> Jason
> 
> ________________________________
> 
> From: Alexander Kitaev [mailto:Alexander.Kitaevsvnkit.com] Sent: Wed
>  7/18/2007 5:29 PM To: svnkit-userssvnkit.com Subject: Re: Unhandled
>  Content Status SVNException
> 
> 
> 
> Hello Jason,
> 
> It seems that your ISVNEventHandler throws exception
while 
> SVNBasicClient calls its handleEvent() method:
> 
> try { myEventDispatcher.handleEvent(event, progress); }
catch 
> (SVNException e) { throw e; } catch (Throwable th) {
SVNErrorMessage 
> err = SVNErrorMessage.create(SVNErrorCode.UNKNOWN,
"Error while 
> dispatching event: ", th.getMessage());
SVNErrorManager.error(err,
>  th); }
> 
> Alexander Kitaev, TMate Software, http://svnkit.com/ - Java 
> [Sub]Versioning Library!
> 
> Jason Winnebeck wrote:
>> I am getting the following exception from dry-run
doMerge:
>> 
>> 
>> 
>> conn.getDiffClient().doMerge(
config.getStableURL(), 
>> SVNRevision.HEAD,
>> 
>> config.getDevURL(), SVNRevision.HEAD,
>> 
>> root, true, false, true, true );
>> 
>> 
>> 
>> The exception appears to be coming from SVNKit...
>> 
>> 
>> 
>> org.tmatesoft.svn.core.SVNException: svn: Error
while dispatching 
>> event: Unhandled content status
>> 
>> SVNEventAction.UPDATE_UPDATE
SVNStatusType.INAPPLICABLE 
>> SVNStatusType.CHANGED
> 
> 
>
------------------------------------------------------------
------------
> 
> 
> 
> 
>
------------------------------------------------------------
---------
>  To unsubscribe, e-mail: svnkit-users-unsubscribesvnkit.com For 
> additional commands, e-mail: svnkit-users-helpsvnkit.com

------------------------------------------------------------
---------
To unsubscribe, e-mail: svnkit-users-unsubscribesvnkit.com
For additional commands, e-mail: svnkit-users-helpsvnkit.com