Issue 102064 - soffice -accept=socket should exit with error if port busy
Summary: soffice -accept=socket should exit with error if port busy
Status: CONFIRMED
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: OOo 3.1
Hardware: Unknown Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-19 15:02 UTC by mnasato
Modified: 2013-08-07 15:31 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description mnasato 2009-05-19 15:02:02 UTC 
OOo can be made to listen on a given port for use with remote UNO by starting it
with the -accept switch, e.g.:

  $ soffice "-accept=socket,host=0,port=2002;urp;"

If there already is another process listening on the same port (e.g. a web
server), I would expect the above command to exit with a code other than 0.

Instead it starts anyway apparently without errors, but of course it won't be
listening on the port that was already busy. So an external application starting
OOo won't be notified of any errors, but won't be able to connect to it either.

Additionally, OOo seems to consume 100% of one CPU. (This may or may not be
related to issue 94471.)
Comment 1 mst.ooo 2009-06-30 11:13:07 UTC 
this bothers me as well:
if i accidentally start two offices with -accept and then some unit test, the
results are generally puzzling...