The problem discussion began in the forum:
http://www.oooforum.org/forum/viewtopic.phtml?t=52286
Summary:
Connecting to OO and generating lengthy documents using the UNO API crashes on
multiple processor machines with 
com.sun.star.lang.DisposedException: java.io.EOFException
        at
com.sun.star.lib.uno.bridges.java_remote.java_remote_bridge$MessageDispatcher.run(java_remote_bridge.java:176)

When connecting/listening using pipes, or DisposedException again, but because
of a SocketException: Connection reset when connecting using socket.

The problem was spotted under Windows TS 2003, but is reproducable in XP SP2 if
it runs on a Core Duo machine, while on the same version of Windows it runs fine
on single processor machine. The solution was to run the process by specifying
an affinity mask to use only one processor (there is no problem if distinct
instances of OO work on distinct processor, as long as one instance is not
allowed to use multiple processors).

Tests were made with OO2.0.3, 2.1.0, 2.2 development version, all with the same
result.

Short-timed connections(<5-10 seconds) manage to survive in most cases, but the
lengthy ones fail even if there is only one user working (no matter Terminal
server or a workstation).

Mike