I posted this question in the API forum first - http://www.oooforum.org/forum/viewtopic.phtml?t=52286 , but it seems I have stuck deeper than I thought and will need developer's point of view. As described in thread the expected scheme is that my application will start an OO instance in every user's session when needed and will fill and show a Writer document in it. For this purpose each instance is started with command line given a different port for each user (or in my second attempt with pipes - a different pipe name). Thus I expect that the scheme is single threaded because for each instance of OO there is only one connection from one user.
But at certain moments it seems that the different sessions begin interacting although they are given different ports/pipe names: closing or opening an instance in one user's session kills the connection of another user to his own soffice. The exception is a DisposedException and was caused by "SocketException: Connection reset" when using socket connection and an "EOFException" when using pipes. The trace points at java_remote_bridge.java$MessageDispatcher.run() method. Is there something wrong in the scheme being used - is it not possible to have different instances of OO (they are shown as different processes in Task Manager) that listen on different ports/pipes? What could be the reason of that interprocess communication - is there something that is common for all OO instances in a more general level than user session? Is there a specific installation case for Windows Terminal Server (2003) environment? I have tried with admin installations for every user (setup /a) in different folders, starting OO outside the java process, all without success. Any ideas and suggestions are welcome, since I am deeply stuck with this. Many thanks Mike ----------------------------------------------------------------- Заложете на късмета си със Спортингбет! --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
