Issue 87894 - Unable to connect to Socket launched from command line
Summary: Unable to connect to Socket launched from command line
Status: CLOSED DUPLICATE of issue 95028
Alias: None
Product: General
Classification: Code
Component: scripting (show other issues)
Version: OOo 2.4.0
Hardware: PC Windows, all
: P3 Trivial with 3 votes (vote)
Target Milestone: ---
Assignee: Stephan Bergmann
QA Contact: issues@framework
URL:
Keywords: oooqa, regression
Depends on:
Blocks:
 
Reported: 2008-04-04 21:23 UTC by icon
Modified: 2008-11-26 13:03 UTC (History)
4 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 icon 2008-04-04 21:23:40 UTC 
When trying to start OpenOffice 2.4.0 with the following command:

program\soffice.exe -accept=socket,host=localhost,port=2002;urp;

OpenOffice opens but is unreachable using the hello_world.py example found at
http://udk.openoffice.org/python/python-bridge.html.  The following message is
returned:

ctx = resolver.resolve(
"uno:socket,host=localhost,port=2002;urp;StarOffice.ComponentContext" )
__main__.com.sun.star.connection.NoConnectException: Connector : couldn't
connect to socket (WSANOTINITIALISED, WSAStartup() has not been called)

Using previously released versions of OpenOffice (OOo 2.3x) and running the same
command line and script generates no errors.  The above behavior was exhibited
on two different machines a 2003 Windows Server and a Windows XP professional
workstation.
Comment 1 aziem 2008-04-06 19:33:04 UTC 
I have the same error on OOo 2.4.0 Win XP with same hello_world, but doubtfully
is priority 1.
Comment 2 aziem 2008-04-07 02:42:09 UTC 
Confirmed: reverting from 2.4.0 to 2.3.1 on Win XP solves the problem.
Comment 3 ab 2008-04-07 11:02:00 UTC 
It's not even P2 (no crash, no data loss, most users not affected at all) -> P3

ab->as: I don't know if this is an Office startup or a Python binding related
problem.
In any case it's not my issue as Python is a Sun external project. Please have a
look and assign to (still?) Joerg Budischewski if it's no Office problem.
Comment 4 ab 2008-04-07 11:02:47 UTC 
P3, next try
Comment 5 aziem 2008-04-08 14:35:17 UTC 
Workaround is to use pipe instead of socket:
http://www.oooforum.org/forum/viewtopic.phtml?p=280746#280746
Comment 6 aziem 2008-04-28 14:41:12 UTC 
Can this be targeted for 2.4.1?  I raised this on the releases mailing list but
I received no reply.
Comment 7 icon 2008-10-07 19:08:59 UTC 
This issue seems to have been resolved (or rather default functionality has
changed) by http://www.openoffice.org/issues/show_bug.cgi?id=86692.

Can someone confirm?
Comment 8 andreas.schluens 2008-11-26 12:01:07 UTC 
as->sb: Any changes inside that area ?
Comment 9 Stephan Bergmann 2008-11-26 13:02:01 UTC 
.

*** This issue has been marked as a duplicate of 95028 ***
Comment 10 Stephan Bergmann 2008-11-26 13:03:06 UTC 
.