Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Virgo/Diagnostics"

m (Virgo Shell commands)
m (Added header for logger usage)
Line 22: Line 22:
  
 
When running in the user region, the Virgo shell commands are offered via the ''vsh'' command.  Type ''vsh help'' to see a list of the shell commands available.  
 
When running in the user region, the Virgo shell commands are offered via the ''vsh'' command.  Type ''vsh help'' to see a list of the shell commands available.  
 +
 +
== Precision Debug logging ==
 +
 +
  
 
[[Category:Virgo]] [[Category:EclipseRT]]
 
[[Category:Virgo]] [[Category:EclipseRT]]

Revision as of 06:09, 23 July 2010


This page contains hints and tips for diagnosing problems with Virgo and Virgo applications.

Equinox Console

The Equinox Console is useful for examining either the kernel framework or the user region framework.

Virgo offers shell commands to the user region Equinox Console for slightly more friendly inspection of user region artefacts.

To enable an Equinox console, you need to set a framework property, like this:

osgi.console=2402
identifying the port to use.

In the case of the user region, add this property to the file config/org.eclipse.virgo.kernel.userregion.properties. In the case of the kernel region, add this property to the file lib/org.eclipse.virgo.kernel.launch.properties.

You can even enable an Equinox console in both regions at once, using two different ports of course.

To use the console, telnet in:

> telnet localhost 2402

The most useful commands are ss to list all bundles, bundle <n> to display information about the bundle with bundle id <n>, and help to see other commands.

When running in the user region, the Virgo shell commands are offered via the vsh command. Type vsh help to see a list of the shell commands available.

Precision Debug logging

Back to the top