Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 337816

Summary:	Virgo -F parameter doesn't work on Windows
Product:	[RT] Virgo	Reporter:	Alex Blewitt <alex.blewitt>
Component:	runtime	Assignee:	Hristo Iliev <hsiliev>
Status:	CLOSED FIXED	QA Contact:
Severity:	minor
Priority:	P3	CC:	glyn.normington, hsiliev
Version:	3.0.0.M01
Target Milestone:	3.0.0.M02
Hardware:	PC
OS:	All
URL:	http://www.eclipse.org/virgo/documentation/virgo-documentation-3.0.0.x/docs/virgo-user-guide/html/ch06.html
Whiteboard:

Description Alex Blewitt

2011-02-22 07:11:05 EST

The Virgo documentation suggests that you can startup a Virgo isntance with a command line parameter using 'startup.sh -Fosgi.console=2401'.

Using Windows, running 'startup -Fosgi.console=2401', the console port does not appear to be activated. Instead, it looks like the property is defined but has no value. As a result, the osgi> prompt appears in the console log window of the running Virgo session, as if java -Dosgi.console -jar equinox.jar had been executed.

Comment 1 Glyn Normington

2011-02-22 07:13:03 EST

Alex: congratulations on being the first user to raise a bug against M01. :-)

Copying in Hristo for his consideration.

Comment 2 Hristo Iliev

2011-02-22 10:25:59 EST

Windows console understands "=" as separator and the line therefore translates as 'startup -Fosgi.console 2401'. 

Can you please try with:
startup "-Fosgi.console=2401"

Comment 3 Alex Blewitt

2011-02-22 12:17:36 EST

I never knew that :) Yes, using "-Fosgi.console=2401" works on the command line. 

Can the documentation (at http://www.eclipse.org/virgo/documentation/virgo-documentation-3.0.0.x/docs/virgo-user-guide/html/ch06.html) be suitably updated for us poor folk who use Windows on a daily basis?

Comment 4 Hristo Iliev

2011-02-22 15:34:10 EST

Added Windows/Linux specific startup documentation for the console with commit 7a8689850dd78d5669e9bf9f219baed562cdf154