Jump to: navigation, search

Difference between revisions of "Virgo/Diagnostics"

m (Virgo/Diagnose moved to Virgo/Diagnostics: still playing with the basic Virgo pages)
Line 1: Line 1:
[[Category:Virgo]][[Category:EclipseRT]]
+
{{Virgo}} This page contains hints and tips for diagnosing problems with Virgo and Virgo applications.  
{{Virgo}}
+
This page contains hints and tips for diagnosing problems with Virgo and Virgo applications.
+
  
== Equinox Console ==
+
== Equinox Console ==
  
The Virgo shell is useful for inspecting the contents of the user region, but sometimes it is necessary to use a feature only available in the Equinox console or to inspect the contents of the kernel region. For example, at the time of writing, the Virgo shell is unable to display package wirings established by DynamicImport-Package.
+
The Virgo shell is useful for inspecting the contents of the user region, but sometimes it is necessary to use a feature only available in the Equinox console or to inspect the contents of the kernel region. For example, at the time of writing, the Virgo shell is unable to display package wirings established by DynamicImport-Package.  
  
To enable the Equinox console, you need to set a framework property like this:
+
To enable the Equinox console, you need to set a framework property like this:  
 +
<pre>osgi.console=2402
 +
</pre>
 +
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.
  
osgi.console=2402
+
You can even enable an Equinox console in both regions at once, using two different ports of course.
  
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.
+
To use the console, telnet in:
 +
<pre>telnet localhost 2402
 +
</pre>
 +
The most useful commands are "ss" to list all bundles, "bundle &lt;n&gt;" to display information about the bundle with bundle id &lt;n&gt;, and "help" to see other commands.  
  
You can even enable an Equinox console in both regions at once, using two different ports of course.
+
[[Category:Virgo]] [[Category:EclipseRT]]
 
+
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.
+

Revision as of 07:19, 21 April 2010

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

Equinox Console

The Virgo shell is useful for inspecting the contents of the user region, but sometimes it is necessary to use a feature only available in the Equinox console or to inspect the contents of the kernel region. For example, at the time of writing, the Virgo shell is unable to display package wirings established by DynamicImport-Package.

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

osgi.console=2402

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.