Bug 374884 - "Document is closed" exception while writing to the console [ID-UODT8]
Summary: "Document is closed" exception while writing to the console [ID-UODT8]
Status: RESOLVED FIXED
Alias: None
Product: Subversive
Classification: Technology
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Igor Burilo CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 375914 375915 375934 (view as bug list)
Depends on:
Blocks:
 
Reported: 2012-03-21 07:07 EDT by heapifyman CLA
Modified: 2012-04-18 05:02 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description heapifyman CLA 2012-03-21 07:07:23 EDT
Version:	0.7.9.I20120316-1700

SVN Client:	org.eclipse.team.svn.connector.svnkit16 2.3.0.I20120316-1700 SVN/1.6.17 SVNKit/1.3.6-v1 (http://svnkit.com/) r7998_v20111004_1436

JVM Properties:
{java.runtime.name=Java(TM) SE Runtime Environment, java.runtime.version=1.7.0_03-b05, java.vendor=Oracle Corporation, line.separator=
 , java.class.version=51.0, os.name=Windows 7, os.arch=amd64, user.country=DE, os.version=6.1, eclipse.commands=-os win32 -ws win32 -arch x86_64 -showsplash -launcher C:\ATB\Programme\eclipse_indigo_64bit\eclipse\eclipse.exe -name Eclipse --launcher.library C:\ATB\Programme\eclipse_indigo_64bit\eclipse\\plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.100.v20110502\eclipse_1406.dll -startup C:\ATB\Programme\eclipse_indigo_64bit\eclipse\\plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar --launcher.overrideVmargs -exitdata 1af4_5c -product org.eclipse.epp.package.jee.product -vm C:/Program Files/Java/jdk1.7.0/bin/javaw.exe , java.version=1.7.0_03, osgi.framework.version=3.7.2.v20120110-1415, file.separator=\, java.vm.info=mixed mode, path.separator=;, user.timezone=Europe/Berlin, user.language=de, java.vm.name=Java HotSpot(TM) 64-Bit Server VM, file.encoding=Cp1252}

java.io.IOException: Document is closed
java.io.IOException: Document is closed
	at org.eclipse.ui.internal.console.IOConsolePartitioner.streamAppended(IOConsolePartitioner.java:453)
	at org.eclipse.ui.console.IOConsoleOutputStream.notifyParitioner(IOConsoleOutputStream.java:245)
	at org.eclipse.ui.console.IOConsoleOutputStream.encodedWrite(IOConsoleOutputStream.java:240)
	at org.eclipse.ui.console.IOConsoleOutputStream.write(IOConsoleOutputStream.java:225)
	at org.eclipse.team.svn.ui.console.SVNConsole$SVNConsoleStream.print(SVNConsole.java:306)
	at org.eclipse.team.svn.ui.console.SVNConsole$SVNConsoleStream.write(SVNConsole.java:278)
	at org.eclipse.team.svn.ui.console.SVNConsole$SVNConsoleStream.flushBuffer(SVNConsole.java:318)
	at org.eclipse.team.svn.ui.console.SVNConsole$SVNConsoleStream.doComplexWrite(SVNConsole.java:258)
	at org.eclipse.team.svn.core.operation.AbstractActionOperation.complexWriteToConsole(AbstractActionOperation.java:144)
	at org.eclipse.team.svn.core.operation.CompositeOperation.doComplexWrite(CompositeOperation.java:124)
	at org.eclipse.team.svn.core.operation.AbstractActionOperation.complexWriteToConsole(AbstractActionOperation.java:144)
	at org.eclipse.team.svn.core.operation.local.CommitOperation.performCommit(CommitOperation.java:111)
	at org.eclipse.team.svn.core.operation.local.CommitOperation.runImpl(CommitOperation.java:93)
	at org.eclipse.team.svn.core.operation.AbstractActionOperation.run(AbstractActionOperation.java:81)
	at org.eclipse.team.svn.core.utility.ProgressMonitorUtility.doTask(ProgressMonitorUtility.java:104)
	at org.eclipse.team.svn.core.operation.CompositeOperation.runImpl(CompositeOperation.java:95)
	at org.eclipse.team.svn.core.operation.AbstractActionOperation.run(AbstractActionOperation.java:81)
	at org.eclipse.team.svn.core.operation.LoggedOperation.run(LoggedOperation.java:39)
	at org.eclipse.team.svn.core.utility.ProgressMonitorUtility.doTask(ProgressMonitorUtility.java:104)
	at org.eclipse.team.svn.core.utility.ProgressMonitorUtility.doTaskExternal(ProgressMonitorUtility.java:90)
	at org.eclipse.team.svn.ui.utility.WorkspaceModifyCancellableOperationWrapper.execute(WorkspaceModifyCancellableOperationWrapper.java:58)
	at org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(WorkspaceModifyOperation.java:106)
	at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344)
	at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:118)
	at org.eclipse.team.svn.ui.utility.SVNTeamOperationWrapper.run(SVNTeamOperationWrapper.java:35)
	at org.eclipse.team.internal.ui.actions.JobRunnableContext.run(JobRunnableContext.java:144)
	at org.eclipse.team.internal.ui.actions.JobRunnableContext$ResourceJob.runInWorkspace(JobRunnableContext.java:72)
	at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Comment 1 Alexander Gurov CLA 2012-03-22 14:50:58 EDT
Fixed.
Comment 2 heapifyman CLA 2012-03-30 06:47:10 EDT
(In reply to comment #1)
> Fixed.

Hi,

when and where can I get the fix?
I get an error message for every commit and update. Commits and updates still work, but the error message is really annoying.

Thanks
Comment 3 Alexander Gurov CLA 2012-03-30 06:48:15 EDT
(In reply to comment #2)
Hello,

The build will be available in two weeks.
Comment 4 Alexander Gurov CLA 2012-04-07 11:19:23 EDT
*** Bug 375914 has been marked as a duplicate of this bug. ***
Comment 5 Alexander Gurov CLA 2012-04-07 11:19:50 EDT
*** Bug 375915 has been marked as a duplicate of this bug. ***
Comment 6 Alexander Gurov CLA 2012-04-07 11:20:14 EDT
*** Bug 375934 has been marked as a duplicate of this bug. ***
Comment 7 heapifyman CLA 2012-04-15 17:02:55 EDT
Just updated to:
- Subversive SVN Connectors 2.3.0.I20120413-1700
- Subversive SVN Team Provider (Incubation) 0.7.9.I20120413-1700
- SVNKit 1.3.7 Implementation (Optional) 2.3.0.I20120413-1700

and I still get the error message below when doing something like Team -> Update or Team -> Commit and the SVN Console is not open in the Console View:

SVN: 'org.eclipse.team.svn.ui.console.SVNConsole$SVNConsoleStream' operation finished with error: Document is closed
Document is closed

If I run Update or Commit again while the Console View shows the SVN Console, there is no error message.
However, the SVN Console also does not show any of the usual log output.
Comment 8 Alexander Gurov CLA 2012-04-17 01:47:50 EDT
(In reply to comment #7)
I've found one more issue with the console lifecycle management and have fixed it, but I'm not sure if there are no more issues left. Could you please describe how you get the error? Thank you in advance!

P.S.
The last found one was reproducable like this:
1) do update/commit or any other operation that writes to console when the option "shown on output" is selected
2) close console manually
3) try update/commit again and the error is shown.
Comment 9 heapifyman CLA 2012-04-17 04:30:07 EDT
(In reply to comment #8)
> (In reply to comment #7)
> I've found one more issue with the console lifecycle management and have fixed
> it, but I'm not sure if there are no more issues left. Could you please
> describe how you get the error? Thank you in advance!
> 
> P.S.
> The last found one was reproducable like this:
> 1) do update/commit or any other operation that writes to console when the
> option "shown on output" is selected
> 2) close console manually
> 3) try update/commit again and the error is shown.

Yes, that seems to be what happens (at least when I tried now).
1. I have set SVN console to "show on output".
2. I do something SVN related (sycnhronize, commit, update...) and console shows
up alright
3. I close the console manually
4. I try update/commit again and the error occurs. (now the console is there but empty)
5. I try update/commit again --> no error popup message but also no output in SVN console

Hope that helps. I did not encounter any other problems so far.
Comment 10 Alexander Gurov CLA 2012-04-18 02:36:06 EDT
Thank you. I haven't found any other way to reproduce the issue and so, it seems the problem is finally solved.
I've updated the early access update site to cover the issue.
Comment 11 heapifyman CLA 2012-04-18 05:02:11 EDT
(In reply to comment #10)
> Thank you. I haven't found any other way to reproduce the issue and so, it
> seems the problem is finally solved.
> I've updated the early access update site to cover the issue.

Thanks for the quick response. So far I haven't had any problems with the latest version.