On Wednesday 12 September 2007, Andreas Schlüns wrote: > Hello Hal Vaughan, > > > Oh, and I am using XCloseable.close(true) to close a document. > > mmmhhhh ... in my last mail I've mentioned to use close(false) .-) > It's always better to errors on closing documents by yourself instead > of delivering the owner ship to any other and ignore errors here. > Lates on closing the whole application you will find such "not realy > closed documents" and will run into trouble.
Okay, confusion here. I could have sworn I read to use "close(true)." I don't know how I got that confused. That's an easy change to make. Thanks for catching that! > > 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? > > "Multi CPU systems" have a different timing then single CPU machines. > Thats a fact. So you will be able to find bugs inside OOo which will > might be never occure on a single CPU system. > > On the other side OOo has some problems with threading. Most times > deadlocks occure ... but sometimes also crashes reasoned by non > synchronized code sections will occure. > > That does not mean "you cant use OOo on multi CPU machines". > That means only - the chance to find bugs in OOo will be a little bit > higher then on single CPU machines :-) Okay, so I'm a little relieved about that and it could tie in with the different printer, since that could mean there could be a different timing with the drivers than with the printer that works. On the other hand, there's a good point here. I can tell the client, "It's not my fault!" ;-) (I hope nobody takes that as an attack!) > > 2) How can I keep the Document Recovery Window from popping up and > > get Java to throw an error instead? > > You can disable the whole recovery stuff be passing an option > "-norecovery" to your command line if you start the office. Okay. What happens then? Does it throw an error instead? Do I get any notice? Is there a way to disable recovery form within Java? I've had a few issues with running from the command line and using multiple arguments. (Long story on that...) In one trail, I got the recovery window, closed it, and let my program continue. It then tried to close the document and I got an error because the document had already been disposed of. If I stop the recovery window, it'd be nice to have some other error thrown so I don't find out there's a problem until I try to close it. If there were a way to catch an error or know a document had been lost, that would be a HUGE help and, as long as the document is lost *after* printing, I could program around it. > > 3) Is there any other way to find out what problem is causing the > > Document Recovery issue? > > Yes - dont cancel recovery and have look on the last dialog. There > you will find button which show you the stacktrace. Another idea: > attach a debugger to the running office and let your operation run > till it crashes. The debugger will show you all threads and stacks. > On windows you can use the free Microsoft Visual C++ Express 2005 > edition. I don't have access to Windows development tools. The other issue is that I'm self taught. I've never used any kind of debugger other than print statements. > But note: A debugger will also change the timing so it can happen > that the problem does not occure then :-) That's a consideration. Right now my client is quite happy printing to the other printer, but I still want to figure out what is going on here so I can solve it and don't have the same problem again with other clients. I'm going to have to space out my use of her computer for debugging for a while because she's had to give up a lot of time on it for me to debug everything. I will be looking at what I can do along the way and hope that I don't have to ask for time on her system until I have a clear idea of what I can do and have the code completely done. Hal --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
