The problem is still going on and I thought I had the perfect solution.
I thought it was the print listener or there was a problem with an
extra thread I started that did NOTHING but watch to make sure a call
to OOo completed.
This is on a Windows XP system with 2 CPUs. (Is that part of the issue
with OOo and multiple CPUs?)
----
I was going to change the entire letter below. We changed to a
different printer and everything went smoothly. The problem comes up
with an HP Laser Jet 4250 with PCL6. When we switched, we had no
trouble at all. I can't see why there would be a printer issue like
this, since Windows should handle all the details, but once we switched
printers, everything worked fine.
I've left all the text below intact, describing all the problems and
every symptom I could, just in case any of it relates to or helps
troubleshooting this problem.
Thanks, everyone, for all the help!
---
I'm still getting problems. After printing anywhere from one to a huge
number of files, I get the "OpenOffice.org Document Recovery" window
with the "Due to unexpected error, OpenOffice.org crashed. All the
files you were working on will be saved now. The next time
OpenOffice.org is launched, your files will be recovered
automatically."
I'm sure everyone knows the rest on this window.
So, supposedly, OOo has crashed, but the Quickstart icon is still in the
system tray and when I run my program again, it is able to connect
immediately to OOo without having to run it again. I do NOT get an
exception on the command line and do not get a stacktrace. All I see
on the command line is no more output as the program freezes. If I
click the "Okay" button on the Document Recovery Window, then OOo will
crash on the next attempt to close the open document:
XModel oModel = (XModel)
UnoRuntime.queryInterface(XModel.class, oooDoc);
Where oooDoc is of type XComponent. I couldn't get an entire stack
trace, but the error is that the doc (or component) has been disposed
of.
Once I get the Document Recovery Window, I kill my job in the command
line with CTRL-C then close the Document Recovery Window. I get a bug
report window, but I've done that once so I cancel it. I've tried
other solutions, but for now, I just have to kill my program. After
that, the Quickstart icon is still in the tray and both soffice.exe and
soffice.bin still show up in the Task Manager. At times I've run
Writer manually to see what document would be recovered, but it just
opens a new, blank, untitled document and there is no window asking if
I want to recover any documents.
Oh, and I am using XCloseable.close(true) to close a document.
Ideally I'd like to stop this problem once and for all. If anyone knows
what's going on, any help is GREATLY appreciated! Otherwise, these
questions might help me:
1) Is there a problem with OOo using a dual CPU system with version
2.0.2? Is there a problem with the Java interface using a dual CPU
system in the same version?
2) How can I keep the Document Recovery Window from popping up and get
Java to throw an error instead?
3) Is there any other way to find out what problem is causing the
Document Recovery issue?
As an update, I just ran this again, this time printing to a different
printer, and so far it's printed over 500 letters with no error (there
were over 1,100 to print). Still holding my breath and waiting... And
it did over 1,100 in a row with no error.
And, by the way, even though there's no solution yet, I cannot tell
everyone just how much I appreciate the help here. I really get the
sense people want to make sure this problem is solved. Thank you,
everyone!
Hal
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
