https://issues.apache.org/ooo/show_bug.cgi?id=119858
Ariel Constenla-Haile <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #4 from Ariel Constenla-Haile <[email protected]> --- (In reply to comment #3) > Changing the status as P1 Major as this is blocker issue for upgrade. This won't change the fact that this bug is unconfirmed, which means no developer or QA volunteer could reproduce this. I tried with 3.4.0 and 3.4.1, and could not reproduce your bug. Of course, I did some minimal test, I didn't keep the office running during hours. Did you try with different things? For example: a) a named pipe, instead of a socket b) a connection aware client? http://wiki.openoffice.org/wiki/Documentation/DevGuide/ProUNO/Example:_A_Connection_Aware_Client You shouldn't need to kill the OO process, simply try to establish a new connection. The usage of the UnoUrlResolver has certain disadvantages, as said in http://wiki.openoffice.org/wiki/Documentation/DevGuide/ProUNO/Importing_a_UNO_Object -- You are receiving this mail because: You are the assignee for the bug.
