To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=46312
------- Additional comments from [EMAIL PROTECTED] Fri Apr 8 06:41:25 -0700 2005 ------- This occurs only with StarOffice when APOC is installed, but not enabled (which is the case for a Solaris 10/JDS). Analysis by geoffh from the apoc group: --- BEGIN ---- I managed to come up with a recreation of this problem without using StarOffice ( or apoc ). Like most things it's quite simple really ( just difficult to figure out in the first place ). 1. Write a client program that infinitely attempts to connect in a tight loop to a local port which is not being listened to by any other process. 2. Write another program which also tries a single connect call, again to a local port which is not being listened to by any other process. 3. Start the first program 4. Start the second program 5. Not always, but more often than not, the second program will "struggle" to complete its call to connect() 6. Forcing the first client to sleep a while between calls to connect() allows the second client to connect in a more reasonable time. In your test scenario, the testtool corresponds to the first client mentioned above, trying to connect to localhost:31567. The office eventually starts listening on that port. I'm don't know if the tool uses this connection only to verify that the office is running or if the two processes actually communicate over the connection. The second client mentioned above corresponds to the papi trying to make a connection to the APOC daemon ( localhost:38900 ). I can't be sure if the fact that both applications are trying to connect to the local machine is also key to the problem. Maybe. ( Probably ). So, it would seem that, in theory, it would be possible to see this problem happen when running the office outside of the testtool. I wouldn't really like to guess the liklihood of an office starting up on a given machine at the same time as a customer application is trying furiously to connect to a local port. Probably slim enough. There is some stuff on google relating to this kind of thing ( look specifically for things like SYN_SENT ). I didn't find anything really helpful though. ---- END ---- Of course the problem could strike the other way around, without apoc: While testtool is waiting for OOo, a socket connect by any other application on the same machine may similarly hang. --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
