Eclipse Community Forums

Help

Home

Today's Messages (on) | Unanswered Messages (off)

Forum: Virgo

Topic: Virgo / Equinox console usage

Re: Virgo / Equinox console usage [message #1060506 is a reply to message #1058438]

Sat, 25 May 2013 11:41

Franck Mising name
Messages: 84
Registered: July 2009
Location: France

Member

Lazar Kirchev wrote on Tue, 14 May 2013 08:20

Hello,

@Franck The console commands are available only in the user region. Most probably you are connecting to the telnet of the kernel region and therefore cannot see the commands. If you like to use them, you should enable telnet in the user region (modify telnet configuration in repository/ext/osgi.console.properties - set telnet.enabled to true) and connect to port 2501. The "headers" subcommand is used as follows: vhs:bundle headers <bundle_id>, where bundle_id is the number of the bundle
...
Lazar

Nope, I am connecting alternatively to one of the other console and I am having similar issues in both (the command sets do differ somewhat):

osgi> vhs:bundle headers 3
gogo: CommandNotFoundException: Command not found: vhs:bundle
osgi>

Franck

Report message to a moderator

Re: Virgo / Equinox console usage [message #1060507 is a reply to message #1060506]

Sat, 25 May 2013 11:46

Franck Mising name
Messages: 84
Registered: July 2009
Location: France

Member

Hmmm, just discovered that some commands do work for certain bundles:

osgi> bundle 142
gogo: IllegalArgumentException: Cannot coerce bundle(Long) to any of [(Bundle[])]
osgi> bundle 3
ch.qos.logback.classic_1.0.7.v20121108-1250 [3]
Id=3, Status=RESOLVED Data Root=C:\virgo-tomcat-3.6.1\work\org.eclipse.osgi\bundles\3\data

Bundle 142 was loaded through a plan, could this be the reason?
Is there any way to address bundles loaded through a plan?

Report message to a moderator

Re: Virgo / Equinox console usage [message #1060508 is a reply to message #1060507]

Sat, 25 May 2013 11:59

Franck Mising name
Messages: 84
Registered: July 2009
Location: France

Member

Ooops, my bad, I was connecting to the wrong console this time.

So problem solved it seems, here is the wrapup for me:
- forget the vsh: prefix, it doesn't seem needed
- can't coerce args etc doesn't necessarily mean that you are using the wrong syntax, you get that message if the bundle isn't found in the region
- the two regions don't have the same set of commands - e.g. plan is only available in the user region

Moving on to trying to refresh a bundle by name from the command line...

Report message to a moderator

Current Time: Sat May 25 12:03:02 EDT 2013