[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[virgo-dev] Inner framework command

Hi Hristo

The solution below fixed the basic crash and I can now start Virgo successfully and see the frk command in the Equinox console. However, when I run it without parameters, I get:

osgi> frk
	at com.sap.osgi.command.frameworkinfo.FrameworkInfoCommand.processTree(FrameworkInfoCommand.java:549)
	at com.sap.osgi.command.frameworkinfo.FrameworkInfoCommand.processTree(FrameworkInfoCommand.java:563)
	at com.sap.osgi.command.frameworkinfo.FrameworkInfoCommand.list(FrameworkInfoCommand.java:463)
	at com.sap.osgi.command.frameworkinfo.FrameworkInfoCommand._frk(FrameworkInfoCommand.java:152)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at org.eclipse.osgi.framework.internal.core.FrameworkCommandInterpreter.execute(FrameworkCommandInterpreter.java:155)
	at org.eclipse.osgi.framework.internal.core.FrameworkConsole.docommand(FrameworkConsole.java:303)
	at org.eclipse.osgi.framework.internal.core.FrameworkConsole.console(FrameworkConsole.java:288)
	at org.eclipse.osgi.framework.internal.core.FrameworkConsole.run(FrameworkConsole.java:224)
	at java.lang.Thread.run(Thread.java:637)

It does a bit better with a framework id:

osgi> frk 0 ss
Listing bundles in framework [0]..
Inner framework [0] is not available, check if it is stopped

but that's not very interesting. Is an inner framework is the same thing as a nested framework as currently supported by Equinox? I guess not as the user region is a nested framework.

PS. I'll comment on the class loading command separately as it's a completely disjoint topic.
On 7 Jul 2010, at 10:47, Iliev, Hristo wrote:

> Follow-up for "There is a problem running the nested framework agent on Mac OS X which we will continue to discuss on virgo-dev":
> The problem turned out to be a misspelled name - dot after the first jar in the manifest of the java agent:
> 	Boot-Class-Path: javassist.jar. com.sap.core.supportability.innerfrk.d
> 	 etectionlib-0.7.0-SNAPSHOT.jar
> To fix the issue one can simply remove the dot:
> 	Boot-Class-Path: javassist.jar com.sap.core.supportability.innerfrk.d
> 	 etectionlib-0.7.0-SNAPSHOT.jar
> Strangely enough - on Windows this did not caused problems as I would expect...