You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@felix.apache.org by GERODOLLE Anne RD-MAPS-GRE <an...@orange-ftgroup.com> on 2007/11/28 18:50:41 UTC

"Unknown protocol: felix" with jamvm

 Hi,

I am running into problems when trying to run the http-jetty bundle on
felix running on a jamvm.

The problem occurs also if I run a dummy bundle, with an activator that
tries to instantiate a SimpleDateFormat (code enclosed).

I have tried with serveral combination of those options :
-Dframework.service.urlhandlers=false
-Dframework.service.urlhandlers=true (in case)
Or
-Djava.protocol.handler.pkgs=gnu.java.net.ptotocol

I have just tested with felix 1.0.0 and with felix 0.8.0, it seems that
with felix 0.8.0-incubator it works (at least on a PC. I have to retry
now on the target device NSLU2)

Here is the stack trace :

java.lang.IllegalStateException: Unknown protocol: felix
   at
org.apache.felix.framework.URLHandlersStreamHandlerProxy.parseURL(URLHan
dlersStreamHandlerProxy.java:135)
   at java.net.URL.<init>(URL.java:480)
   at
java.net.URLClassLoader$RemoteURLLoader.getResource(URLClassLoader.java:
484)
   at java.net.URLClassLoader.findURLResource(URLClassLoader.java:1145)
   at java.net.URLClassLoader.findResource(URLClassLoader.java:1160)
   at java.lang.ClassLoader.getResource(ClassLoader.java:609)
   at java.lang.ClassLoader.getResourceAsStream(ClassLoader.java:730)
   at java.util.ResourceBundle.tryBundle(ResourceBundle.java:491)
   at java.util.ResourceBundle.tryBundle(ResourceBundle.java:560)
   at java.util.ResourceBundle.getBundle(ResourceBundle.java:401)
   at java.util.Calendar.getBundle(Calendar.java:436)
   at java.util.Calendar.<init>(Calendar.java:461)
   at java.util.GregorianCalendar.<init>(GregorianCalendar.java:238)
   at java.util.GregorianCalendar.<init>(GregorianCalendar.java:224)
   at java.util.GregorianCalendar.<init>(GregorianCalendar.java:212)
   at java.text.SimpleDateFormat.<init>(SimpleDateFormat.java:407)
   at com.francetelecom.osgi.test.MyActivator.start(MyActivator.java:20)
   at
org.apache.felix.framework.util.SecureAction.startActivator(SecureAction
.java:589)
   at org.apache.felix.framework.Felix._startBundle(Felix.java:1563)
   at org.apache.felix.framework.Felix.startBundle(Felix.java:1497)
   at
org.apache.felix.framework.Felix$RefreshHelper.restart(Felix.java:4203)
   at org.apache.felix.framework.Felix.refreshPackages(Felix.java:3240)
   at org.apache.felix.framework.Felix._updateBundle(Felix.java:1849)
   at org.apache.felix.framework.Felix.updateBundle(Felix.java:1697)
   at org.apache.felix.framework.BundleImpl.update(BundleImpl.java:372)
   at org.apache.felix.framework.BundleImpl.update(BundleImpl.java:359)
   at
org.apache.felix.shell.impl.UpdateCommandImpl.execute(UpdateCommandImpl.
java:96)
   at
org.apache.felix.shell.impl.Activator$ShellServiceImpl.executeCommand(Ac
tivator.java:265)
   at
org.apache.felix.shell.tui.Activator$ShellTuiRunnable.run(Activator.java
:167)
   at java.lang.Thread.run(Thread.java:710)

Thanks in advance,

Anne


Re: Problem with log4j on felix and jamvm

Posted by Karl Pauls <ka...@gmail.com>.
Hi Anne,

I created issue FELIX-435 to track this. I commited a patch to trunk
that should hopefully allow you to run with urlhandlers enabled.

Could you please test the current trunk and close the issue if it
works for you or comment when it doesn't?

regards,

Karl

On 12/4/07, GERODOLLE Anne RD-MAPS-GRE
<an...@orange-ftgroup.com> wrote:
> Hi Richard,
>
> I've "solved" the issue by commenting out the static initialisation in ExtensionManager. It's still completely obscure for me, I just searched the code and found this "felix://extension" URL that was only refered there.
>
> Now eveything looks OK (at least I can run log4j correctly, and instantiate a "SimpleDateFormat". Of course now I have to test the complete application...
>
> I put some output traces in the code, and it turned out that there was an (almost) infinite recursion in UrlHandlers.createURLStreamHandler, trying to create a streal handler for the "felix" protocol.
>
> Conerning jamvm, for these tests I used a debian package.
>
> Best regards,
>
> Anne
>
>
> -----Message d'origine-----
> De : Richard S. Hall [mailto:heavy@ungoverned.org]
> Envoyé : mardi 4 décembre 2007 16:40
> À : users@felix.apache.org
> Objet : Re: Problem with log4j on felix and jamvm
>
> Well, the issue for me is that I currently cannot compile JamVM for fedora (my machine's gcc installation seems to be messed up somehow and I have been unable to fix it)...I will work on getting JamVM working...if anyone knows of some binary RPMs for it and/or GNU Classpath that would greatly help.
>
> Once I can run JamVM, then perhaps you can send me a boiled down example to recreate the situation...feel free to send it any time.
>
> -> richard
>
> GERODOLLE Anne RD-MAPS-GRE wrote:
> > Hi Richard,
> >
> > I've just tried with the last version of felix, that is : I've updated from svn, then run "mvn install" from the "main" folder. This downloaded the dependencies from the central repository.
> >
> > Now, here is what happens on jamvm (note that everything works alright on Sun's vm):
> >
> > If I run jamvm without parameters /usr/bin/jamvm -jar bin/felix.jar, and without any changes to the generated configuration file :
> > I get first an "unknown protocol: http" when the obr bundle is loaded, which I ignore (because I only want to install bundles from the file system, and it works).
> >
> > Then, I install the log4j bundle from felix, and then my small example .
> > Instantiation of the Level class now works (no more "Duplicate class").
> > but I get : "Unknown protocol: felix" in the initializarion of
> > LogManager, when calling Logger.getLogger(...); This semms to be in fact the same problem as with the HTTP service :
> > log4j uses "AbsoluteTimeDateFormat", which in turn calls Calendar.getInstance, and this results into this "unknown protocol: felix".
> >
> > If now I type "-Djava.protocol.handle.pkg=gnu.java.net.protocol , the problem with "unknown protocol: http" disappears but the "unknown protocol: felix" stay.
> >
> > If I choose "-Dfelix.service.urlhandlers=false", the calls to Calendar.newInstance simply hang (looks like a deadlock), and the "start" method of an activator calling "new SimpleDateFormat" just never returns.
> >
> > I agree with you that I have to solve the URL handler issue in felix 1.0.1 . But I have no clue how to proceed.
> >
> > Best regards,
> >
> > Anne
> >
> >
> > -----Message d'origine-----
> > De : Richard S. Hall [mailto:heavy@ungoverned.org] Envoyé : lundi 3
> > décembre 2007 21:26 À : users@felix.apache.org Objet : Re: Problem
> > with log4j on felix and jamvm
> >
> > I believe there was a synchronization bug in class loading in Felix 0.8.0 that opened a window for defining the same class more than once...this was fixed in later versions of Felix...so, you might want to go back to trying to solve the URL handler issue on Felix 1.0.1...perhaps you should try the latest trunk build, since there were some changes that might impact the URL handler stuff...regardless, were better off trying to get you on 1.0.x than 0.8.0...
> >
> > -> richard
> >
> > GERODOLLE Anne RD-MAPS-GRE wrote:
> >
> >> Hi all,
> >>
> >> I got into classloading problems using log4j on felix and jamvm, as
> >> soon as I try to use log4j, for example calling Logger.getLogger.
> >> I'm including below a piece of code that exhibits the problem.
> >> The corresponding bundle works OK on felix on sun's VM .
> >> It works OK on prosyst mbs on jamvm.
> >>
> >> On felix on jamvm, I obtain a "duplicate class error", whether I'm
> >> using the log4j bundle from felix or embedding directly log4j in my
> >> test bundle.
> >>
> >> I'm using felix-0.8.0, due to unresolved problems with felix 1.0.1 on
> >> jamvm I mentionned earlier on this list ("unknown protocol: felix").
> >>
> >> I have found a workaround : loading the "Priority" class in advance,
> >> by adding a line like Priority debug = Priority.DEBUG; But this means
> >> that I have to change the code of all bundles that use log4j :(
> >>
> >> Here is the "start" method of my activator :
> >>
> >> public void start(BundleContext context){
> >>     System.out.println("defining a variable of the
> >> org.apache.log4j.Level class");
> >>     org.apache.log4j.Level level;
> >>     System.out.println("now trying to instantiate this variable");
> >>     level=org.apache.log4j.Level.DEBUG;
> >> }
> >>
> >> And here is the stack trace :
> >> ERROR: Error starting
> >> file:/home/gerodol/.m2/repository/com/francetelecom/osgi/test/log4j-t
> >> e st /0.1-SNAPSHOT/log4j-test-0.1-SNAPSHOT.jar
> >> (org.osgi.framework.BundleException: Activator start error.)
> >> java.lang.NoClassDefFoundError: org/apache/log4j/Level
> >>    at com.francetelecom.test.LoggerTest.start(LoggerTest.java:38)
> >>    at
> >> org.apache.felix.framework.util.SecureAction.startActivator(SecureAct
> >> i
> >> on
> >> .java:509)
> >>    at org.apache.felix.framework.Felix._startBundle(Felix.java:1260)
> >>    at org.apache.felix.framework.Felix.startBundle(Felix.java:1201)
> >>    at
> >> org.apache.felix.framework.Felix.setFrameworkStartLevel(Felix.java:807)
> >>    at
> >> org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:256)
> >>    at java.lang.Thread.run(Thread.java:710)
> >> Caused by: java.lang.LinkageError: duplicate class definition
> >>    at java.lang.VMClassLoader.defineClass(Native Method)
> >>    at
> >> java.lang.VMClassLoader.defineClassWithTransformers(VMClassLoader.jav
> >> a
> >> :3
> >> 74)
> >>    at java.lang.ClassLoader.defineClass(ClassLoader.java:472)
> >>    at java.lang.ClassLoader.defineClass(ClassLoader.java:437)
> >>    at
> >> org.apache.felix.framework.searchpolicy.ContentClassLoader.findClass(
> >> C
> >> on
> >> tentClassLoader.java:149)
> >>    at
> >> org.apache.felix.framework.searchpolicy.ContentClassLoader.loadClassF
> >> r
> >> om
> >> Module(ContentClassLoader.java:51)
> >>    at
> >> org.apache.felix.framework.searchpolicy.ContentLoaderImpl.getClass(Co
> >> n
> >> te
> >> ntLoaderImpl.java:121)
> >>    at
> >> org.apache.felix.framework.searchpolicy.R4SearchPolicyCore.findClassO
> >> r
> >> Re
> >> source(R4SearchPolicyCore.java:358)
> >>    at
> >> org.apache.felix.framework.searchpolicy.R4SearchPolicyCore.findClass(
> >> R
> >> 4S
> >> earchPolicyCore.java:136)
> >>    at
> >> org.apache.felix.framework.searchpolicy.R4SearchPolicy.findClass(R4Se
> >> a
> >> rc
> >> hPolicy.java:45)
> >>    at
> >> org.apache.felix.framework.searchpolicy.ContentClassLoader.loadClass(
> >> C
> >> on
> >> tentClassLoader.java:70)
> >>    at java.lang.ClassLoader.loadClass(ClassLoader.java:294)
> >>    at com.francetelecom.test.LoggerTest.start(LoggerTest.java:38)
> >>
> >> Thanks in advance,
> >>
> >> Anne
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> >> For additional commands, e-mail: users-help@felix.apache.org
> >>
> >>
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> > For additional commands, e-mail: users-help@felix.apache.org
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> > For additional commands, e-mail: users-help@felix.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
>


-- 
Karl Pauls
karlpauls@gmail.com

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org


Re: Problem with log4j on felix and jamvm

Posted by Karl Pauls <ka...@gmail.com>.
> That is excellent news, especially since it helps us to debug the
> situation...now I can go beat on Karl... ;-)

:-)

> -> richard


> > Hi Richard,
> >
> > I've "solved" the issue by commenting out the static initialisation in ExtensionManager. It's still completely obscure for me, I just searched the code and found this "felix://extension" URL that was only refered there.
> >
> > Now eveything looks OK (at least I can run log4j correctly, and instantiate a "SimpleDateFormat". Of course now I have to test the complete application...
> >
> > I put some output traces in the code, and it turned out that there was an (almost) infinite recursion in UrlHandlers.createURLStreamHandler, trying to create a streal handler for the "felix" protocol.

Interesting. I'll look into it but it sounds like a bug in classpath
(however, we need to find at least a workaround). Thanks for looking
into this issue.

regards,

Karl

> > Conerning jamvm, for these tests I used a debian package.
> >
> > Best regards,
> >
> > Anne
> >
> >
> > -----Message d'origine-----
> > De : Richard S. Hall [mailto:heavy@ungoverned.org]
> > Envoyé : mardi 4 décembre 2007 16:40
> > À : users@felix.apache.org
> > Objet : Re: Problem with log4j on felix and jamvm
> >
> > Well, the issue for me is that I currently cannot compile JamVM for fedora (my machine's gcc installation seems to be messed up somehow and I have been unable to fix it)...I will work on getting JamVM working...if anyone knows of some binary RPMs for it and/or GNU Classpath that would greatly help.
> >
> > Once I can run JamVM, then perhaps you can send me a boiled down example to recreate the situation...feel free to send it any time.
> >
> > -> richard
> >
> > GERODOLLE Anne RD-MAPS-GRE wrote:
> >
> >> Hi Richard,
> >>
> >> I've just tried with the last version of felix, that is : I've updated from svn, then run "mvn install" from the "main" folder. This downloaded the dependencies from the central repository.
> >>
> >> Now, here is what happens on jamvm (note that everything works alright on Sun's vm):
> >>
> >> If I run jamvm without parameters /usr/bin/jamvm -jar bin/felix.jar, and without any changes to the generated configuration file :
> >> I get first an "unknown protocol: http" when the obr bundle is loaded, which I ignore (because I only want to install bundles from the file system, and it works).
> >>
> >> Then, I install the log4j bundle from felix, and then my small example .
> >> Instantiation of the Level class now works (no more "Duplicate class").
> >> but I get : "Unknown protocol: felix" in the initializarion of
> >> LogManager, when calling Logger.getLogger(...); This semms to be in fact the same problem as with the HTTP service :
> >> log4j uses "AbsoluteTimeDateFormat", which in turn calls Calendar.getInstance, and this results into this "unknown protocol: felix".
> >>
> >> If now I type "-Djava.protocol.handle.pkg=gnu.java.net.protocol , the problem with "unknown protocol: http" disappears but the "unknown protocol: felix" stay.
> >>
> >> If I choose "-Dfelix.service.urlhandlers=false", the calls to Calendar.newInstance simply hang (looks like a deadlock), and the "start" method of an activator calling "new SimpleDateFormat" just never returns.
> >>
> >> I agree with you that I have to solve the URL handler issue in felix 1.0.1 . But I have no clue how to proceed.
> >>
> >> Best regards,
> >>
> >> Anne
> >>
> >>
> >> -----Message d'origine-----
> >> De : Richard S. Hall [mailto:heavy@ungoverned.org] Envoyé : lundi 3
> >> décembre 2007 21:26 À : users@felix.apache.org Objet : Re: Problem
> >> with log4j on felix and jamvm
> >>
> >> I believe there was a synchronization bug in class loading in Felix 0.8.0 that opened a window for defining the same class more than once...this was fixed in later versions of Felix...so, you might want to go back to trying to solve the URL handler issue on Felix 1.0.1...perhaps you should try the latest trunk build, since there were some changes that might impact the URL handler stuff...regardless, were better off trying to get you on 1.0.x than 0.8.0...
> >>
> >> -> richard
> >>
> >> GERODOLLE Anne RD-MAPS-GRE wrote:
> >>
> >>
> >>> Hi all,
> >>>
> >>> I got into classloading problems using log4j on felix and jamvm, as
> >>> soon as I try to use log4j, for example calling Logger.getLogger.
> >>> I'm including below a piece of code that exhibits the problem.
> >>> The corresponding bundle works OK on felix on sun's VM .
> >>> It works OK on prosyst mbs on jamvm.
> >>>
> >>> On felix on jamvm, I obtain a "duplicate class error", whether I'm
> >>> using the log4j bundle from felix or embedding directly log4j in my
> >>> test bundle.
> >>>
> >>> I'm using felix-0.8.0, due to unresolved problems with felix 1.0.1 on
> >>> jamvm I mentionned earlier on this list ("unknown protocol: felix").
> >>>
> >>> I have found a workaround : loading the "Priority" class in advance,
> >>> by adding a line like Priority debug = Priority.DEBUG; But this means
> >>> that I have to change the code of all bundles that use log4j :(
> >>>
> >>> Here is the "start" method of my activator :
> >>>
> >>> public void start(BundleContext context){
> >>>     System.out.println("defining a variable of the
> >>> org.apache.log4j.Level class");
> >>>     org.apache.log4j.Level level;
> >>>     System.out.println("now trying to instantiate this variable");
> >>>     level=org.apache.log4j.Level.DEBUG;
> >>> }
> >>>
> >>> And here is the stack trace :
> >>> ERROR: Error starting
> >>> file:/home/gerodol/.m2/repository/com/francetelecom/osgi/test/log4j-t
> >>> e st /0.1-SNAPSHOT/log4j-test-0.1-SNAPSHOT.jar
> >>> (org.osgi.framework.BundleException: Activator start error.)
> >>> java.lang.NoClassDefFoundError: org/apache/log4j/Level
> >>>    at com.francetelecom.test.LoggerTest.start(LoggerTest.java:38)
> >>>    at
> >>> org.apache.felix.framework.util.SecureAction.startActivator(SecureAct
> >>> i
> >>> on
> >>> .java:509)
> >>>    at org.apache.felix.framework.Felix._startBundle(Felix.java:1260)
> >>>    at org.apache.felix.framework.Felix.startBundle(Felix.java:1201)
> >>>    at
> >>> org.apache.felix.framework.Felix.setFrameworkStartLevel(Felix.java:807)
> >>>    at
> >>> org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:256)
> >>>    at java.lang.Thread.run(Thread.java:710)
> >>> Caused by: java.lang.LinkageError: duplicate class definition
> >>>    at java.lang.VMClassLoader.defineClass(Native Method)
> >>>    at
> >>> java.lang.VMClassLoader.defineClassWithTransformers(VMClassLoader.jav
> >>> a
> >>> :3
> >>> 74)
> >>>    at java.lang.ClassLoader.defineClass(ClassLoader.java:472)
> >>>    at java.lang.ClassLoader.defineClass(ClassLoader.java:437)
> >>>    at
> >>> org.apache.felix.framework.searchpolicy.ContentClassLoader.findClass(
> >>> C
> >>> on
> >>> tentClassLoader.java:149)
> >>>    at
> >>> org.apache.felix.framework.searchpolicy.ContentClassLoader.loadClassF
> >>> r
> >>> om
> >>> Module(ContentClassLoader.java:51)
> >>>    at
> >>> org.apache.felix.framework.searchpolicy.ContentLoaderImpl.getClass(Co
> >>> n
> >>> te
> >>> ntLoaderImpl.java:121)
> >>>    at
> >>> org.apache.felix.framework.searchpolicy.R4SearchPolicyCore.findClassO
> >>> r
> >>> Re
> >>> source(R4SearchPolicyCore.java:358)
> >>>    at
> >>> org.apache.felix.framework.searchpolicy.R4SearchPolicyCore.findClass(
> >>> R
> >>> 4S
> >>> earchPolicyCore.java:136)
> >>>    at
> >>> org.apache.felix.framework.searchpolicy.R4SearchPolicy.findClass(R4Se
> >>> a
> >>> rc
> >>> hPolicy.java:45)
> >>>    at
> >>> org.apache.felix.framework.searchpolicy.ContentClassLoader.loadClass(
> >>> C
> >>> on
> >>> tentClassLoader.java:70)
> >>>    at java.lang.ClassLoader.loadClass(ClassLoader.java:294)
> >>>    at com.francetelecom.test.LoggerTest.start(LoggerTest.java:38)
> >>>
> >>> Thanks in advance,
> >>>
> >>> Anne
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> >>> For additional commands, e-mail: users-help@felix.apache.org
> >>>
> >>>
> >>>
> >>>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> >> For additional commands, e-mail: users-help@felix.apache.org
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> >> For additional commands, e-mail: users-help@felix.apache.org
> >>
> >>
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> > For additional commands, e-mail: users-help@felix.apache.org
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> > For additional commands, e-mail: users-help@felix.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
>


-- 
Karl Pauls
karlpauls@gmail.com

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org


Re: Problem with log4j on felix and jamvm

Posted by "Richard S. Hall" <he...@ungoverned.org>.
That is excellent news, especially since it helps us to debug the 
situation...now I can go beat on Karl... ;-)

-> richard

GERODOLLE Anne RD-MAPS-GRE wrote:
> Hi Richard,
>
> I've "solved" the issue by commenting out the static initialisation in ExtensionManager. It's still completely obscure for me, I just searched the code and found this "felix://extension" URL that was only refered there.
>
> Now eveything looks OK (at least I can run log4j correctly, and instantiate a "SimpleDateFormat". Of course now I have to test the complete application...
>
> I put some output traces in the code, and it turned out that there was an (almost) infinite recursion in UrlHandlers.createURLStreamHandler, trying to create a streal handler for the "felix" protocol.
>
> Conerning jamvm, for these tests I used a debian package.
>
> Best regards,
>
> Anne
>  
>
> -----Message d'origine-----
> De : Richard S. Hall [mailto:heavy@ungoverned.org] 
> Envoyé : mardi 4 décembre 2007 16:40
> À : users@felix.apache.org
> Objet : Re: Problem with log4j on felix and jamvm
>
> Well, the issue for me is that I currently cannot compile JamVM for fedora (my machine's gcc installation seems to be messed up somehow and I have been unable to fix it)...I will work on getting JamVM working...if anyone knows of some binary RPMs for it and/or GNU Classpath that would greatly help.
>
> Once I can run JamVM, then perhaps you can send me a boiled down example to recreate the situation...feel free to send it any time.
>
> -> richard
>
> GERODOLLE Anne RD-MAPS-GRE wrote:
>   
>> Hi Richard,
>>
>> I've just tried with the last version of felix, that is : I've updated from svn, then run "mvn install" from the "main" folder. This downloaded the dependencies from the central repository.
>>
>> Now, here is what happens on jamvm (note that everything works alright on Sun's vm):
>>
>> If I run jamvm without parameters /usr/bin/jamvm -jar bin/felix.jar, and without any changes to the generated configuration file :
>> I get first an "unknown protocol: http" when the obr bundle is loaded, which I ignore (because I only want to install bundles from the file system, and it works).
>>
>> Then, I install the log4j bundle from felix, and then my small example .
>> Instantiation of the Level class now works (no more "Duplicate class").
>> but I get : "Unknown protocol: felix" in the initializarion of 
>> LogManager, when calling Logger.getLogger(...); This semms to be in fact the same problem as with the HTTP service :
>> log4j uses "AbsoluteTimeDateFormat", which in turn calls Calendar.getInstance, and this results into this "unknown protocol: felix".
>>
>> If now I type "-Djava.protocol.handle.pkg=gnu.java.net.protocol , the problem with "unknown protocol: http" disappears but the "unknown protocol: felix" stay.
>>
>> If I choose "-Dfelix.service.urlhandlers=false", the calls to Calendar.newInstance simply hang (looks like a deadlock), and the "start" method of an activator calling "new SimpleDateFormat" just never returns. 
>>
>> I agree with you that I have to solve the URL handler issue in felix 1.0.1 . But I have no clue how to proceed.
>>
>> Best regards,
>>
>> Anne
>>
>>
>> -----Message d'origine-----
>> De : Richard S. Hall [mailto:heavy@ungoverned.org] Envoyé : lundi 3 
>> décembre 2007 21:26 À : users@felix.apache.org Objet : Re: Problem 
>> with log4j on felix and jamvm
>>
>> I believe there was a synchronization bug in class loading in Felix 0.8.0 that opened a window for defining the same class more than once...this was fixed in later versions of Felix...so, you might want to go back to trying to solve the URL handler issue on Felix 1.0.1...perhaps you should try the latest trunk build, since there were some changes that might impact the URL handler stuff...regardless, were better off trying to get you on 1.0.x than 0.8.0...
>>
>> -> richard
>>
>> GERODOLLE Anne RD-MAPS-GRE wrote:
>>   
>>     
>>> Hi all,
>>>
>>> I got into classloading problems using log4j on felix and jamvm, as 
>>> soon as I try to use log4j, for example calling Logger.getLogger.
>>> I'm including below a piece of code that exhibits the problem.
>>> The corresponding bundle works OK on felix on sun's VM .
>>> It works OK on prosyst mbs on jamvm.
>>>
>>> On felix on jamvm, I obtain a "duplicate class error", whether I'm 
>>> using the log4j bundle from felix or embedding directly log4j in my 
>>> test bundle.
>>>
>>> I'm using felix-0.8.0, due to unresolved problems with felix 1.0.1 on 
>>> jamvm I mentionned earlier on this list ("unknown protocol: felix").
>>>
>>> I have found a workaround : loading the "Priority" class in advance, 
>>> by adding a line like Priority debug = Priority.DEBUG; But this means 
>>> that I have to change the code of all bundles that use log4j :(
>>>
>>> Here is the "start" method of my activator :
>>>
>>> public void start(BundleContext context){
>>>     System.out.println("defining a variable of the 
>>> org.apache.log4j.Level class");
>>>     org.apache.log4j.Level level;
>>>     System.out.println("now trying to instantiate this variable");
>>>     level=org.apache.log4j.Level.DEBUG;   
>>> }
>>>
>>> And here is the stack trace :
>>> ERROR: Error starting
>>> file:/home/gerodol/.m2/repository/com/francetelecom/osgi/test/log4j-t
>>> e st /0.1-SNAPSHOT/log4j-test-0.1-SNAPSHOT.jar
>>> (org.osgi.framework.BundleException: Activator start error.)
>>> java.lang.NoClassDefFoundError: org/apache/log4j/Level
>>>    at com.francetelecom.test.LoggerTest.start(LoggerTest.java:38)
>>>    at
>>> org.apache.felix.framework.util.SecureAction.startActivator(SecureAct
>>> i
>>> on
>>> .java:509)
>>>    at org.apache.felix.framework.Felix._startBundle(Felix.java:1260)
>>>    at org.apache.felix.framework.Felix.startBundle(Felix.java:1201)
>>>    at
>>> org.apache.felix.framework.Felix.setFrameworkStartLevel(Felix.java:807)
>>>    at
>>> org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:256)
>>>    at java.lang.Thread.run(Thread.java:710)
>>> Caused by: java.lang.LinkageError: duplicate class definition
>>>    at java.lang.VMClassLoader.defineClass(Native Method)
>>>    at
>>> java.lang.VMClassLoader.defineClassWithTransformers(VMClassLoader.jav
>>> a
>>> :3
>>> 74)
>>>    at java.lang.ClassLoader.defineClass(ClassLoader.java:472)
>>>    at java.lang.ClassLoader.defineClass(ClassLoader.java:437)
>>>    at
>>> org.apache.felix.framework.searchpolicy.ContentClassLoader.findClass(
>>> C
>>> on
>>> tentClassLoader.java:149)
>>>    at
>>> org.apache.felix.framework.searchpolicy.ContentClassLoader.loadClassF
>>> r
>>> om
>>> Module(ContentClassLoader.java:51)
>>>    at
>>> org.apache.felix.framework.searchpolicy.ContentLoaderImpl.getClass(Co
>>> n
>>> te
>>> ntLoaderImpl.java:121)
>>>    at
>>> org.apache.felix.framework.searchpolicy.R4SearchPolicyCore.findClassO
>>> r
>>> Re
>>> source(R4SearchPolicyCore.java:358)
>>>    at
>>> org.apache.felix.framework.searchpolicy.R4SearchPolicyCore.findClass(
>>> R
>>> 4S
>>> earchPolicyCore.java:136)
>>>    at
>>> org.apache.felix.framework.searchpolicy.R4SearchPolicy.findClass(R4Se
>>> a
>>> rc
>>> hPolicy.java:45)
>>>    at
>>> org.apache.felix.framework.searchpolicy.ContentClassLoader.loadClass(
>>> C
>>> on
>>> tentClassLoader.java:70)
>>>    at java.lang.ClassLoader.loadClass(ClassLoader.java:294)
>>>    at com.francetelecom.test.LoggerTest.start(LoggerTest.java:38)
>>>
>>> Thanks in advance,
>>>
>>> Anne
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>> For additional commands, e-mail: users-help@felix.apache.org
>>>
>>>   
>>>     
>>>       
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>> For additional commands, e-mail: users-help@felix.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>> For additional commands, e-mail: users-help@felix.apache.org
>>
>>   
>>     
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
>   

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org


RE: Problem with log4j on felix and jamvm

Posted by GERODOLLE Anne RD-MAPS-GRE <an...@orange-ftgroup.com>.
Hi Richard,

I've "solved" the issue by commenting out the static initialisation in ExtensionManager. It's still completely obscure for me, I just searched the code and found this "felix://extension" URL that was only refered there.

Now eveything looks OK (at least I can run log4j correctly, and instantiate a "SimpleDateFormat". Of course now I have to test the complete application...

I put some output traces in the code, and it turned out that there was an (almost) infinite recursion in UrlHandlers.createURLStreamHandler, trying to create a streal handler for the "felix" protocol.

Conerning jamvm, for these tests I used a debian package.

Best regards,

Anne
 

-----Message d'origine-----
De : Richard S. Hall [mailto:heavy@ungoverned.org] 
Envoyé : mardi 4 décembre 2007 16:40
À : users@felix.apache.org
Objet : Re: Problem with log4j on felix and jamvm

Well, the issue for me is that I currently cannot compile JamVM for fedora (my machine's gcc installation seems to be messed up somehow and I have been unable to fix it)...I will work on getting JamVM working...if anyone knows of some binary RPMs for it and/or GNU Classpath that would greatly help.

Once I can run JamVM, then perhaps you can send me a boiled down example to recreate the situation...feel free to send it any time.

-> richard

GERODOLLE Anne RD-MAPS-GRE wrote:
> Hi Richard,
>
> I've just tried with the last version of felix, that is : I've updated from svn, then run "mvn install" from the "main" folder. This downloaded the dependencies from the central repository.
>
> Now, here is what happens on jamvm (note that everything works alright on Sun's vm):
>
> If I run jamvm without parameters /usr/bin/jamvm -jar bin/felix.jar, and without any changes to the generated configuration file :
> I get first an "unknown protocol: http" when the obr bundle is loaded, which I ignore (because I only want to install bundles from the file system, and it works).
>
> Then, I install the log4j bundle from felix, and then my small example .
> Instantiation of the Level class now works (no more "Duplicate class").
> but I get : "Unknown protocol: felix" in the initializarion of 
> LogManager, when calling Logger.getLogger(...); This semms to be in fact the same problem as with the HTTP service :
> log4j uses "AbsoluteTimeDateFormat", which in turn calls Calendar.getInstance, and this results into this "unknown protocol: felix".
>
> If now I type "-Djava.protocol.handle.pkg=gnu.java.net.protocol , the problem with "unknown protocol: http" disappears but the "unknown protocol: felix" stay.
>
> If I choose "-Dfelix.service.urlhandlers=false", the calls to Calendar.newInstance simply hang (looks like a deadlock), and the "start" method of an activator calling "new SimpleDateFormat" just never returns. 
>
> I agree with you that I have to solve the URL handler issue in felix 1.0.1 . But I have no clue how to proceed.
>
> Best regards,
>
> Anne
>
>
> -----Message d'origine-----
> De : Richard S. Hall [mailto:heavy@ungoverned.org] Envoyé : lundi 3 
> décembre 2007 21:26 À : users@felix.apache.org Objet : Re: Problem 
> with log4j on felix and jamvm
>
> I believe there was a synchronization bug in class loading in Felix 0.8.0 that opened a window for defining the same class more than once...this was fixed in later versions of Felix...so, you might want to go back to trying to solve the URL handler issue on Felix 1.0.1...perhaps you should try the latest trunk build, since there were some changes that might impact the URL handler stuff...regardless, were better off trying to get you on 1.0.x than 0.8.0...
>
> -> richard
>
> GERODOLLE Anne RD-MAPS-GRE wrote:
>   
>> Hi all,
>>
>> I got into classloading problems using log4j on felix and jamvm, as 
>> soon as I try to use log4j, for example calling Logger.getLogger.
>> I'm including below a piece of code that exhibits the problem.
>> The corresponding bundle works OK on felix on sun's VM .
>> It works OK on prosyst mbs on jamvm.
>>
>> On felix on jamvm, I obtain a "duplicate class error", whether I'm 
>> using the log4j bundle from felix or embedding directly log4j in my 
>> test bundle.
>>
>> I'm using felix-0.8.0, due to unresolved problems with felix 1.0.1 on 
>> jamvm I mentionned earlier on this list ("unknown protocol: felix").
>>
>> I have found a workaround : loading the "Priority" class in advance, 
>> by adding a line like Priority debug = Priority.DEBUG; But this means 
>> that I have to change the code of all bundles that use log4j :(
>>
>> Here is the "start" method of my activator :
>>
>> public void start(BundleContext context){
>>     System.out.println("defining a variable of the 
>> org.apache.log4j.Level class");
>>     org.apache.log4j.Level level;
>>     System.out.println("now trying to instantiate this variable");
>>     level=org.apache.log4j.Level.DEBUG;   
>> }
>>
>> And here is the stack trace :
>> ERROR: Error starting
>> file:/home/gerodol/.m2/repository/com/francetelecom/osgi/test/log4j-t
>> e st /0.1-SNAPSHOT/log4j-test-0.1-SNAPSHOT.jar
>> (org.osgi.framework.BundleException: Activator start error.)
>> java.lang.NoClassDefFoundError: org/apache/log4j/Level
>>    at com.francetelecom.test.LoggerTest.start(LoggerTest.java:38)
>>    at
>> org.apache.felix.framework.util.SecureAction.startActivator(SecureAct
>> i
>> on
>> .java:509)
>>    at org.apache.felix.framework.Felix._startBundle(Felix.java:1260)
>>    at org.apache.felix.framework.Felix.startBundle(Felix.java:1201)
>>    at
>> org.apache.felix.framework.Felix.setFrameworkStartLevel(Felix.java:807)
>>    at
>> org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:256)
>>    at java.lang.Thread.run(Thread.java:710)
>> Caused by: java.lang.LinkageError: duplicate class definition
>>    at java.lang.VMClassLoader.defineClass(Native Method)
>>    at
>> java.lang.VMClassLoader.defineClassWithTransformers(VMClassLoader.jav
>> a
>> :3
>> 74)
>>    at java.lang.ClassLoader.defineClass(ClassLoader.java:472)
>>    at java.lang.ClassLoader.defineClass(ClassLoader.java:437)
>>    at
>> org.apache.felix.framework.searchpolicy.ContentClassLoader.findClass(
>> C
>> on
>> tentClassLoader.java:149)
>>    at
>> org.apache.felix.framework.searchpolicy.ContentClassLoader.loadClassF
>> r
>> om
>> Module(ContentClassLoader.java:51)
>>    at
>> org.apache.felix.framework.searchpolicy.ContentLoaderImpl.getClass(Co
>> n
>> te
>> ntLoaderImpl.java:121)
>>    at
>> org.apache.felix.framework.searchpolicy.R4SearchPolicyCore.findClassO
>> r
>> Re
>> source(R4SearchPolicyCore.java:358)
>>    at
>> org.apache.felix.framework.searchpolicy.R4SearchPolicyCore.findClass(
>> R
>> 4S
>> earchPolicyCore.java:136)
>>    at
>> org.apache.felix.framework.searchpolicy.R4SearchPolicy.findClass(R4Se
>> a
>> rc
>> hPolicy.java:45)
>>    at
>> org.apache.felix.framework.searchpolicy.ContentClassLoader.loadClass(
>> C
>> on
>> tentClassLoader.java:70)
>>    at java.lang.ClassLoader.loadClass(ClassLoader.java:294)
>>    at com.francetelecom.test.LoggerTest.start(LoggerTest.java:38)
>>
>> Thanks in advance,
>>
>> Anne
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>> For additional commands, e-mail: users-help@felix.apache.org
>>
>>   
>>     
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
>   

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org


Re: Problem with log4j on felix and jamvm

Posted by "Richard S. Hall" <he...@ungoverned.org>.
Well, the issue for me is that I currently cannot compile JamVM for 
fedora (my machine's gcc installation seems to be messed up somehow and 
I have been unable to fix it)...I will work on getting JamVM 
working...if anyone knows of some binary RPMs for it and/or GNU 
Classpath that would greatly help.

Once I can run JamVM, then perhaps you can send me a boiled down example 
to recreate the situation...feel free to send it any time.

-> richard

GERODOLLE Anne RD-MAPS-GRE wrote:
> Hi Richard,
>
> I've just tried with the last version of felix, that is : I've updated from svn, then run "mvn install" from the "main" folder. This downloaded the dependencies from the central repository.
>
> Now, here is what happens on jamvm (note that everything works alright on Sun's vm):
>
> If I run jamvm without parameters /usr/bin/jamvm -jar bin/felix.jar, and without any changes to the generated configuration file :
> I get first an "unknown protocol: http" when the obr bundle is loaded, which I ignore (because I only want to install bundles from the file system, and it works).
>
> Then, I install the log4j bundle from felix, and then my small example .
> Instantiation of the Level class now works (no more "Duplicate class").
> but I get : "Unknown protocol: felix" in the initializarion of LogManager, when calling Logger.getLogger(...);
> This semms to be in fact the same problem as with the HTTP service : 
> log4j uses "AbsoluteTimeDateFormat", which in turn calls Calendar.getInstance, and this results into this "unknown protocol: felix".
>
> If now I type "-Djava.protocol.handle.pkg=gnu.java.net.protocol , the problem with "unknown protocol: http" disappears but the "unknown protocol: felix" stay.
>
> If I choose "-Dfelix.service.urlhandlers=false", the calls to Calendar.newInstance simply hang (looks like a deadlock), and the "start" method of an activator calling "new SimpleDateFormat" just never returns. 
>
> I agree with you that I have to solve the URL handler issue in felix 1.0.1 . But I have no clue how to proceed.
>
> Best regards,
>
> Anne
>
>
> -----Message d'origine-----
> De : Richard S. Hall [mailto:heavy@ungoverned.org] 
> Envoyé : lundi 3 décembre 2007 21:26
> À : users@felix.apache.org
> Objet : Re: Problem with log4j on felix and jamvm
>
> I believe there was a synchronization bug in class loading in Felix 0.8.0 that opened a window for defining the same class more than once...this was fixed in later versions of Felix...so, you might want to go back to trying to solve the URL handler issue on Felix 1.0.1...perhaps you should try the latest trunk build, since there were some changes that might impact the URL handler stuff...regardless, were better off trying to get you on 1.0.x than 0.8.0...
>
> -> richard
>
> GERODOLLE Anne RD-MAPS-GRE wrote:
>   
>> Hi all,
>>
>> I got into classloading problems using log4j on felix and jamvm, as 
>> soon as I try to use log4j, for example calling Logger.getLogger.
>> I'm including below a piece of code that exhibits the problem.
>> The corresponding bundle works OK on felix on sun's VM .
>> It works OK on prosyst mbs on jamvm.
>>
>> On felix on jamvm, I obtain a "duplicate class error", whether I'm 
>> using the log4j bundle from felix or embedding directly log4j in my 
>> test bundle.
>>
>> I'm using felix-0.8.0, due to unresolved problems with felix 1.0.1 on 
>> jamvm I mentionned earlier on this list ("unknown protocol: felix").
>>
>> I have found a workaround : loading the "Priority" class in advance, 
>> by adding a line like Priority debug = Priority.DEBUG; But this means 
>> that I have to change the code of all bundles that use log4j :(
>>
>> Here is the "start" method of my activator :
>>
>> public void start(BundleContext context){
>>     System.out.println("defining a variable of the 
>> org.apache.log4j.Level class");
>>     org.apache.log4j.Level level;
>>     System.out.println("now trying to instantiate this variable");
>>     level=org.apache.log4j.Level.DEBUG;   
>> }
>>
>> And here is the stack trace :
>> ERROR: Error starting
>> file:/home/gerodol/.m2/repository/com/francetelecom/osgi/test/log4j-te
>> st /0.1-SNAPSHOT/log4j-test-0.1-SNAPSHOT.jar
>> (org.osgi.framework.BundleException: Activator start error.)
>> java.lang.NoClassDefFoundError: org/apache/log4j/Level
>>    at com.francetelecom.test.LoggerTest.start(LoggerTest.java:38)
>>    at
>> org.apache.felix.framework.util.SecureAction.startActivator(SecureActi
>> on
>> .java:509)
>>    at org.apache.felix.framework.Felix._startBundle(Felix.java:1260)
>>    at org.apache.felix.framework.Felix.startBundle(Felix.java:1201)
>>    at
>> org.apache.felix.framework.Felix.setFrameworkStartLevel(Felix.java:807)
>>    at
>> org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:256)
>>    at java.lang.Thread.run(Thread.java:710)
>> Caused by: java.lang.LinkageError: duplicate class definition
>>    at java.lang.VMClassLoader.defineClass(Native Method)
>>    at
>> java.lang.VMClassLoader.defineClassWithTransformers(VMClassLoader.java
>> :3
>> 74)
>>    at java.lang.ClassLoader.defineClass(ClassLoader.java:472)
>>    at java.lang.ClassLoader.defineClass(ClassLoader.java:437)
>>    at
>> org.apache.felix.framework.searchpolicy.ContentClassLoader.findClass(C
>> on
>> tentClassLoader.java:149)
>>    at
>> org.apache.felix.framework.searchpolicy.ContentClassLoader.loadClassFr
>> om
>> Module(ContentClassLoader.java:51)
>>    at
>> org.apache.felix.framework.searchpolicy.ContentLoaderImpl.getClass(Con
>> te
>> ntLoaderImpl.java:121)
>>    at
>> org.apache.felix.framework.searchpolicy.R4SearchPolicyCore.findClassOr
>> Re
>> source(R4SearchPolicyCore.java:358)
>>    at
>> org.apache.felix.framework.searchpolicy.R4SearchPolicyCore.findClass(R
>> 4S
>> earchPolicyCore.java:136)
>>    at
>> org.apache.felix.framework.searchpolicy.R4SearchPolicy.findClass(R4Sea
>> rc
>> hPolicy.java:45)
>>    at
>> org.apache.felix.framework.searchpolicy.ContentClassLoader.loadClass(C
>> on
>> tentClassLoader.java:70)
>>    at java.lang.ClassLoader.loadClass(ClassLoader.java:294)
>>    at com.francetelecom.test.LoggerTest.start(LoggerTest.java:38)
>>
>> Thanks in advance,
>>
>> Anne
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>> For additional commands, e-mail: users-help@felix.apache.org
>>
>>   
>>     
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
>   

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org


RE: Problem with log4j on felix and jamvm

Posted by GERODOLLE Anne RD-MAPS-GRE <an...@orange-ftgroup.com>.
Hi Richard,

I've just tried with the last version of felix, that is : I've updated from svn, then run "mvn install" from the "main" folder. This downloaded the dependencies from the central repository.

Now, here is what happens on jamvm (note that everything works alright on Sun's vm):

If I run jamvm without parameters /usr/bin/jamvm -jar bin/felix.jar, and without any changes to the generated configuration file :
I get first an "unknown protocol: http" when the obr bundle is loaded, which I ignore (because I only want to install bundles from the file system, and it works).

Then, I install the log4j bundle from felix, and then my small example .
Instantiation of the Level class now works (no more "Duplicate class").
but I get : "Unknown protocol: felix" in the initializarion of LogManager, when calling Logger.getLogger(...);
This semms to be in fact the same problem as with the HTTP service : 
log4j uses "AbsoluteTimeDateFormat", which in turn calls Calendar.getInstance, and this results into this "unknown protocol: felix".

If now I type "-Djava.protocol.handle.pkg=gnu.java.net.protocol , the problem with "unknown protocol: http" disappears but the "unknown protocol: felix" stay.

If I choose "-Dfelix.service.urlhandlers=false", the calls to Calendar.newInstance simply hang (looks like a deadlock), and the "start" method of an activator calling "new SimpleDateFormat" just never returns. 

I agree with you that I have to solve the URL handler issue in felix 1.0.1 . But I have no clue how to proceed.

Best regards,

Anne


-----Message d'origine-----
De : Richard S. Hall [mailto:heavy@ungoverned.org] 
Envoyé : lundi 3 décembre 2007 21:26
À : users@felix.apache.org
Objet : Re: Problem with log4j on felix and jamvm

I believe there was a synchronization bug in class loading in Felix 0.8.0 that opened a window for defining the same class more than once...this was fixed in later versions of Felix...so, you might want to go back to trying to solve the URL handler issue on Felix 1.0.1...perhaps you should try the latest trunk build, since there were some changes that might impact the URL handler stuff...regardless, were better off trying to get you on 1.0.x than 0.8.0...

-> richard

GERODOLLE Anne RD-MAPS-GRE wrote:
> Hi all,
>
> I got into classloading problems using log4j on felix and jamvm, as 
> soon as I try to use log4j, for example calling Logger.getLogger.
> I'm including below a piece of code that exhibits the problem.
> The corresponding bundle works OK on felix on sun's VM .
> It works OK on prosyst mbs on jamvm.
>
> On felix on jamvm, I obtain a "duplicate class error", whether I'm 
> using the log4j bundle from felix or embedding directly log4j in my 
> test bundle.
>
> I'm using felix-0.8.0, due to unresolved problems with felix 1.0.1 on 
> jamvm I mentionned earlier on this list ("unknown protocol: felix").
>
> I have found a workaround : loading the "Priority" class in advance, 
> by adding a line like Priority debug = Priority.DEBUG; But this means 
> that I have to change the code of all bundles that use log4j :(
>
> Here is the "start" method of my activator :
>
> public void start(BundleContext context){
>     System.out.println("defining a variable of the 
> org.apache.log4j.Level class");
>     org.apache.log4j.Level level;
>     System.out.println("now trying to instantiate this variable");
>     level=org.apache.log4j.Level.DEBUG;   
> }
>
> And here is the stack trace :
> ERROR: Error starting
> file:/home/gerodol/.m2/repository/com/francetelecom/osgi/test/log4j-te
> st /0.1-SNAPSHOT/log4j-test-0.1-SNAPSHOT.jar
> (org.osgi.framework.BundleException: Activator start error.)
> java.lang.NoClassDefFoundError: org/apache/log4j/Level
>    at com.francetelecom.test.LoggerTest.start(LoggerTest.java:38)
>    at
> org.apache.felix.framework.util.SecureAction.startActivator(SecureActi
> on
> .java:509)
>    at org.apache.felix.framework.Felix._startBundle(Felix.java:1260)
>    at org.apache.felix.framework.Felix.startBundle(Felix.java:1201)
>    at
> org.apache.felix.framework.Felix.setFrameworkStartLevel(Felix.java:807)
>    at
> org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:256)
>    at java.lang.Thread.run(Thread.java:710)
> Caused by: java.lang.LinkageError: duplicate class definition
>    at java.lang.VMClassLoader.defineClass(Native Method)
>    at
> java.lang.VMClassLoader.defineClassWithTransformers(VMClassLoader.java
> :3
> 74)
>    at java.lang.ClassLoader.defineClass(ClassLoader.java:472)
>    at java.lang.ClassLoader.defineClass(ClassLoader.java:437)
>    at
> org.apache.felix.framework.searchpolicy.ContentClassLoader.findClass(C
> on
> tentClassLoader.java:149)
>    at
> org.apache.felix.framework.searchpolicy.ContentClassLoader.loadClassFr
> om
> Module(ContentClassLoader.java:51)
>    at
> org.apache.felix.framework.searchpolicy.ContentLoaderImpl.getClass(Con
> te
> ntLoaderImpl.java:121)
>    at
> org.apache.felix.framework.searchpolicy.R4SearchPolicyCore.findClassOr
> Re
> source(R4SearchPolicyCore.java:358)
>    at
> org.apache.felix.framework.searchpolicy.R4SearchPolicyCore.findClass(R
> 4S
> earchPolicyCore.java:136)
>    at
> org.apache.felix.framework.searchpolicy.R4SearchPolicy.findClass(R4Sea
> rc
> hPolicy.java:45)
>    at
> org.apache.felix.framework.searchpolicy.ContentClassLoader.loadClass(C
> on
> tentClassLoader.java:70)
>    at java.lang.ClassLoader.loadClass(ClassLoader.java:294)
>    at com.francetelecom.test.LoggerTest.start(LoggerTest.java:38)
>
> Thanks in advance,
>
> Anne
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
>   

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org


Re: Problem with log4j on felix and jamvm

Posted by "Richard S. Hall" <he...@ungoverned.org>.
I believe there was a synchronization bug in class loading in Felix 
0.8.0 that opened a window for defining the same class more than 
once...this was fixed in later versions of Felix...so, you might want to 
go back to trying to solve the URL handler issue on Felix 
1.0.1...perhaps you should try the latest trunk build, since there were 
some changes that might impact the URL handler stuff...regardless, were 
better off trying to get you on 1.0.x than 0.8.0...

-> richard

GERODOLLE Anne RD-MAPS-GRE wrote:
> Hi all,
>
> I got into classloading problems using log4j on felix and jamvm, as soon
> as I try to use log4j, for example calling Logger.getLogger.
> I'm including below a piece of code that exhibits the problem.
> The corresponding bundle works OK on felix on sun's VM .
> It works OK on prosyst mbs on jamvm.
>
> On felix on jamvm, I obtain a "duplicate class error", whether I'm using
> the log4j bundle from felix or embedding directly log4j in my test
> bundle.
>
> I'm using felix-0.8.0, due to unresolved problems with felix 1.0.1 on
> jamvm I mentionned earlier on this list ("unknown protocol: felix").
>
> I have found a workaround : loading the "Priority" class in advance, by
> adding a line like 
> Priority debug = Priority.DEBUG;
> But this means that I have to change the code of all bundles that use
> log4j :(
>
> Here is the "start" method of my activator :
>
> public void start(BundleContext context){
>     System.out.println("defining a variable of the
> org.apache.log4j.Level class");
>     org.apache.log4j.Level level;
>     System.out.println("now trying to instantiate this variable");
>     level=org.apache.log4j.Level.DEBUG;   
> }
>
> And here is the stack trace :
> ERROR: Error starting
> file:/home/gerodol/.m2/repository/com/francetelecom/osgi/test/log4j-test
> /0.1-SNAPSHOT/log4j-test-0.1-SNAPSHOT.jar
> (org.osgi.framework.BundleException: Activator start error.)
> java.lang.NoClassDefFoundError: org/apache/log4j/Level
>    at com.francetelecom.test.LoggerTest.start(LoggerTest.java:38)
>    at
> org.apache.felix.framework.util.SecureAction.startActivator(SecureAction
> .java:509)
>    at org.apache.felix.framework.Felix._startBundle(Felix.java:1260)
>    at org.apache.felix.framework.Felix.startBundle(Felix.java:1201)
>    at
> org.apache.felix.framework.Felix.setFrameworkStartLevel(Felix.java:807)
>    at
> org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:256)
>    at java.lang.Thread.run(Thread.java:710)
> Caused by: java.lang.LinkageError: duplicate class definition
>    at java.lang.VMClassLoader.defineClass(Native Method)
>    at
> java.lang.VMClassLoader.defineClassWithTransformers(VMClassLoader.java:3
> 74)
>    at java.lang.ClassLoader.defineClass(ClassLoader.java:472)
>    at java.lang.ClassLoader.defineClass(ClassLoader.java:437)
>    at
> org.apache.felix.framework.searchpolicy.ContentClassLoader.findClass(Con
> tentClassLoader.java:149)
>    at
> org.apache.felix.framework.searchpolicy.ContentClassLoader.loadClassFrom
> Module(ContentClassLoader.java:51)
>    at
> org.apache.felix.framework.searchpolicy.ContentLoaderImpl.getClass(Conte
> ntLoaderImpl.java:121)
>    at
> org.apache.felix.framework.searchpolicy.R4SearchPolicyCore.findClassOrRe
> source(R4SearchPolicyCore.java:358)
>    at
> org.apache.felix.framework.searchpolicy.R4SearchPolicyCore.findClass(R4S
> earchPolicyCore.java:136)
>    at
> org.apache.felix.framework.searchpolicy.R4SearchPolicy.findClass(R4Searc
> hPolicy.java:45)
>    at
> org.apache.felix.framework.searchpolicy.ContentClassLoader.loadClass(Con
> tentClassLoader.java:70)
>    at java.lang.ClassLoader.loadClass(ClassLoader.java:294)
>    at com.francetelecom.test.LoggerTest.start(LoggerTest.java:38)
>
> Thanks in advance,
>
> Anne
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
>   

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org


Problem with log4j on felix and jamvm

Posted by GERODOLLE Anne RD-MAPS-GRE <an...@orange-ftgroup.com>.
Hi all,

I got into classloading problems using log4j on felix and jamvm, as soon
as I try to use log4j, for example calling Logger.getLogger.
I'm including below a piece of code that exhibits the problem.
The corresponding bundle works OK on felix on sun's VM .
It works OK on prosyst mbs on jamvm.

On felix on jamvm, I obtain a "duplicate class error", whether I'm using
the log4j bundle from felix or embedding directly log4j in my test
bundle.

I'm using felix-0.8.0, due to unresolved problems with felix 1.0.1 on
jamvm I mentionned earlier on this list ("unknown protocol: felix").

I have found a workaround : loading the "Priority" class in advance, by
adding a line like 
Priority debug = Priority.DEBUG;
But this means that I have to change the code of all bundles that use
log4j :(

Here is the "start" method of my activator :

public void start(BundleContext context){
    System.out.println("defining a variable of the
org.apache.log4j.Level class");
    org.apache.log4j.Level level;
    System.out.println("now trying to instantiate this variable");
    level=org.apache.log4j.Level.DEBUG;   
}

And here is the stack trace :
ERROR: Error starting
file:/home/gerodol/.m2/repository/com/francetelecom/osgi/test/log4j-test
/0.1-SNAPSHOT/log4j-test-0.1-SNAPSHOT.jar
(org.osgi.framework.BundleException: Activator start error.)
java.lang.NoClassDefFoundError: org/apache/log4j/Level
   at com.francetelecom.test.LoggerTest.start(LoggerTest.java:38)
   at
org.apache.felix.framework.util.SecureAction.startActivator(SecureAction
.java:509)
   at org.apache.felix.framework.Felix._startBundle(Felix.java:1260)
   at org.apache.felix.framework.Felix.startBundle(Felix.java:1201)
   at
org.apache.felix.framework.Felix.setFrameworkStartLevel(Felix.java:807)
   at
org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:256)
   at java.lang.Thread.run(Thread.java:710)
Caused by: java.lang.LinkageError: duplicate class definition
   at java.lang.VMClassLoader.defineClass(Native Method)
   at
java.lang.VMClassLoader.defineClassWithTransformers(VMClassLoader.java:3
74)
   at java.lang.ClassLoader.defineClass(ClassLoader.java:472)
   at java.lang.ClassLoader.defineClass(ClassLoader.java:437)
   at
org.apache.felix.framework.searchpolicy.ContentClassLoader.findClass(Con
tentClassLoader.java:149)
   at
org.apache.felix.framework.searchpolicy.ContentClassLoader.loadClassFrom
Module(ContentClassLoader.java:51)
   at
org.apache.felix.framework.searchpolicy.ContentLoaderImpl.getClass(Conte
ntLoaderImpl.java:121)
   at
org.apache.felix.framework.searchpolicy.R4SearchPolicyCore.findClassOrRe
source(R4SearchPolicyCore.java:358)
   at
org.apache.felix.framework.searchpolicy.R4SearchPolicyCore.findClass(R4S
earchPolicyCore.java:136)
   at
org.apache.felix.framework.searchpolicy.R4SearchPolicy.findClass(R4Searc
hPolicy.java:45)
   at
org.apache.felix.framework.searchpolicy.ContentClassLoader.loadClass(Con
tentClassLoader.java:70)
   at java.lang.ClassLoader.loadClass(ClassLoader.java:294)
   at com.francetelecom.test.LoggerTest.start(LoggerTest.java:38)

Thanks in advance,

Anne

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org


RE: "Unknown protocol: felix" with jamvm

Posted by GERODOLLE Anne RD-MAPS-GRE <an...@orange-ftgroup.com>.
Felix, Karl,
Thanks for your help. However :

Using either felix-1.0.1 build, or a fresh rebuild of the last svn version (I built "feramework" then "main") does not help.

Using  felix.service.urlhandlers=false has the effect that the call to "new SimpleDateFormat" simply hangs and never returns (well, does not return after 1 minute on my PC) . This what Ken Robinson observed also.
http://mail-archives.apache.org/mod_mbox/felix-dev/200709.mbox/%3caa7ce83b0709110617s554ccea8y35f641eafc6e9243@mail.gmail.com%3e


Best regards,

Anne

-----Message d'origine-----
De : Karl Pauls [mailto:karlpauls@gmail.com] 
Envoyé : mercredi 28 novembre 2007 21:37
À : users@felix.apache.org
Objet : Re: "Unknown protocol: felix" with jamvm

Anne,

your problem is that you have the wrong properties. It is now called:

felix.service.urlhandlers=false

to be more consistent with the other properties.

regards,

Karl

On 11/28/07, GERODOLLE Anne RD-MAPS-GRE
<an...@orange-ftgroup.com> wrote:
>  Hi,
>
> I am running into problems when trying to run the http-jetty bundle on 
> felix running on a jamvm.
>
> The problem occurs also if I run a dummy bundle, with an activator 
> that tries to instantiate a SimpleDateFormat (code enclosed).
>
> I have tried with serveral combination of those options :
> -Dframework.service.urlhandlers=false
> -Dframework.service.urlhandlers=true (in case) Or 
> -Djava.protocol.handler.pkgs=gnu.java.net.ptotocol
>
> I have just tested with felix 1.0.0 and with felix 0.8.0, it seems 
> that with felix 0.8.0-incubator it works (at least on a PC. I have to 
> retry now on the target device NSLU2)
>
> Here is the stack trace :
>
> java.lang.IllegalStateException: Unknown protocol: felix
>    at
> org.apache.felix.framework.URLHandlersStreamHandlerProxy.parseURL(URLH
> an
> dlersStreamHandlerProxy.java:135)
>    at java.net.URL.<init>(URL.java:480)
>    at
> java.net.URLClassLoader$RemoteURLLoader.getResource(URLClassLoader.java:
> 484)
>    at java.net.URLClassLoader.findURLResource(URLClassLoader.java:1145)
>    at java.net.URLClassLoader.findResource(URLClassLoader.java:1160)
>    at java.lang.ClassLoader.getResource(ClassLoader.java:609)
>    at java.lang.ClassLoader.getResourceAsStream(ClassLoader.java:730)
>    at java.util.ResourceBundle.tryBundle(ResourceBundle.java:491)
>    at java.util.ResourceBundle.tryBundle(ResourceBundle.java:560)
>    at java.util.ResourceBundle.getBundle(ResourceBundle.java:401)
>    at java.util.Calendar.getBundle(Calendar.java:436)
>    at java.util.Calendar.<init>(Calendar.java:461)
>    at java.util.GregorianCalendar.<init>(GregorianCalendar.java:238)
>    at java.util.GregorianCalendar.<init>(GregorianCalendar.java:224)
>    at java.util.GregorianCalendar.<init>(GregorianCalendar.java:212)
>    at java.text.SimpleDateFormat.<init>(SimpleDateFormat.java:407)
>    at com.francetelecom.osgi.test.MyActivator.start(MyActivator.java:20)
>    at
> org.apache.felix.framework.util.SecureAction.startActivator(SecureActi
> on
> .java:589)
>    at org.apache.felix.framework.Felix._startBundle(Felix.java:1563)
>    at org.apache.felix.framework.Felix.startBundle(Felix.java:1497)
>    at
> org.apache.felix.framework.Felix$RefreshHelper.restart(Felix.java:4203)
>    at org.apache.felix.framework.Felix.refreshPackages(Felix.java:3240)
>    at org.apache.felix.framework.Felix._updateBundle(Felix.java:1849)
>    at org.apache.felix.framework.Felix.updateBundle(Felix.java:1697)
>    at org.apache.felix.framework.BundleImpl.update(BundleImpl.java:372)
>    at org.apache.felix.framework.BundleImpl.update(BundleImpl.java:359)
>    at
> org.apache.felix.shell.impl.UpdateCommandImpl.execute(UpdateCommandImpl.
> java:96)
>    at
> org.apache.felix.shell.impl.Activator$ShellServiceImpl.executeCommand(
> Ac
> tivator.java:265)
>    at
> org.apache.felix.shell.tui.Activator$ShellTuiRunnable.run(Activator.ja
> va
> :167)
>    at java.lang.Thread.run(Thread.java:710)
>
> Thanks in advance,
>
> Anne
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>


--
Karl Pauls
karlpauls@gmail.com

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org


Re: "Unknown protocol: felix" with jamvm

Posted by Karl Pauls <ka...@gmail.com>.
Anne,

your problem is that you have the wrong properties. It is now called:

felix.service.urlhandlers=false

to be more consistent with the other properties.

regards,

Karl

On 11/28/07, GERODOLLE Anne RD-MAPS-GRE
<an...@orange-ftgroup.com> wrote:
>  Hi,
>
> I am running into problems when trying to run the http-jetty bundle on
> felix running on a jamvm.
>
> The problem occurs also if I run a dummy bundle, with an activator that
> tries to instantiate a SimpleDateFormat (code enclosed).
>
> I have tried with serveral combination of those options :
> -Dframework.service.urlhandlers=false
> -Dframework.service.urlhandlers=true (in case)
> Or
> -Djava.protocol.handler.pkgs=gnu.java.net.ptotocol
>
> I have just tested with felix 1.0.0 and with felix 0.8.0, it seems that
> with felix 0.8.0-incubator it works (at least on a PC. I have to retry
> now on the target device NSLU2)
>
> Here is the stack trace :
>
> java.lang.IllegalStateException: Unknown protocol: felix
>    at
> org.apache.felix.framework.URLHandlersStreamHandlerProxy.parseURL(URLHan
> dlersStreamHandlerProxy.java:135)
>    at java.net.URL.<init>(URL.java:480)
>    at
> java.net.URLClassLoader$RemoteURLLoader.getResource(URLClassLoader.java:
> 484)
>    at java.net.URLClassLoader.findURLResource(URLClassLoader.java:1145)
>    at java.net.URLClassLoader.findResource(URLClassLoader.java:1160)
>    at java.lang.ClassLoader.getResource(ClassLoader.java:609)
>    at java.lang.ClassLoader.getResourceAsStream(ClassLoader.java:730)
>    at java.util.ResourceBundle.tryBundle(ResourceBundle.java:491)
>    at java.util.ResourceBundle.tryBundle(ResourceBundle.java:560)
>    at java.util.ResourceBundle.getBundle(ResourceBundle.java:401)
>    at java.util.Calendar.getBundle(Calendar.java:436)
>    at java.util.Calendar.<init>(Calendar.java:461)
>    at java.util.GregorianCalendar.<init>(GregorianCalendar.java:238)
>    at java.util.GregorianCalendar.<init>(GregorianCalendar.java:224)
>    at java.util.GregorianCalendar.<init>(GregorianCalendar.java:212)
>    at java.text.SimpleDateFormat.<init>(SimpleDateFormat.java:407)
>    at com.francetelecom.osgi.test.MyActivator.start(MyActivator.java:20)
>    at
> org.apache.felix.framework.util.SecureAction.startActivator(SecureAction
> .java:589)
>    at org.apache.felix.framework.Felix._startBundle(Felix.java:1563)
>    at org.apache.felix.framework.Felix.startBundle(Felix.java:1497)
>    at
> org.apache.felix.framework.Felix$RefreshHelper.restart(Felix.java:4203)
>    at org.apache.felix.framework.Felix.refreshPackages(Felix.java:3240)
>    at org.apache.felix.framework.Felix._updateBundle(Felix.java:1849)
>    at org.apache.felix.framework.Felix.updateBundle(Felix.java:1697)
>    at org.apache.felix.framework.BundleImpl.update(BundleImpl.java:372)
>    at org.apache.felix.framework.BundleImpl.update(BundleImpl.java:359)
>    at
> org.apache.felix.shell.impl.UpdateCommandImpl.execute(UpdateCommandImpl.
> java:96)
>    at
> org.apache.felix.shell.impl.Activator$ShellServiceImpl.executeCommand(Ac
> tivator.java:265)
>    at
> org.apache.felix.shell.tui.Activator$ShellTuiRunnable.run(Activator.java
> :167)
>    at java.lang.Thread.run(Thread.java:710)
>
> Thanks in advance,
>
> Anne
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>


-- 
Karl Pauls
karlpauls@gmail.com

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org


Re: "Unknown protocol: felix" with jamvm

Posted by Felix Meschberger <fm...@gmail.com>.
Hi Anne,

Did you try the latest framework SNAPSHOT ? I seem to remember vaguely,
that there has been something fixed around this issue, not sure, though.

Regards
Felix

Am Mittwoch, den 28.11.2007, 18:50 +0100 schrieb GERODOLLE Anne
RD-MAPS-GRE:
> Hi,
> 
> I am running into problems when trying to run the http-jetty bundle on
> felix running on a jamvm.
> 
> The problem occurs also if I run a dummy bundle, with an activator that
> tries to instantiate a SimpleDateFormat (code enclosed).
> 
> I have tried with serveral combination of those options :
> -Dframework.service.urlhandlers=false
> -Dframework.service.urlhandlers=true (in case)
> Or
> -Djava.protocol.handler.pkgs=gnu.java.net.ptotocol
> 
> I have just tested with felix 1.0.0 and with felix 0.8.0, it seems that
> with felix 0.8.0-incubator it works (at least on a PC. I have to retry
> now on the target device NSLU2)
> 
> Here is the stack trace :
> 
> java.lang.IllegalStateException: Unknown protocol: felix
>    at
> org.apache.felix.framework.URLHandlersStreamHandlerProxy.parseURL(URLHan
> dlersStreamHandlerProxy.java:135)
>    at java.net.URL.<init>(URL.java:480)
>    at
> java.net.URLClassLoader$RemoteURLLoader.getResource(URLClassLoader.java:
> 484)
>    at java.net.URLClassLoader.findURLResource(URLClassLoader.java:1145)
>    at java.net.URLClassLoader.findResource(URLClassLoader.java:1160)
>    at java.lang.ClassLoader.getResource(ClassLoader.java:609)
>    at java.lang.ClassLoader.getResourceAsStream(ClassLoader.java:730)
>    at java.util.ResourceBundle.tryBundle(ResourceBundle.java:491)
>    at java.util.ResourceBundle.tryBundle(ResourceBundle.java:560)
>    at java.util.ResourceBundle.getBundle(ResourceBundle.java:401)
>    at java.util.Calendar.getBundle(Calendar.java:436)
>    at java.util.Calendar.<init>(Calendar.java:461)
>    at java.util.GregorianCalendar.<init>(GregorianCalendar.java:238)
>    at java.util.GregorianCalendar.<init>(GregorianCalendar.java:224)
>    at java.util.GregorianCalendar.<init>(GregorianCalendar.java:212)
>    at java.text.SimpleDateFormat.<init>(SimpleDateFormat.java:407)
>    at com.francetelecom.osgi.test.MyActivator.start(MyActivator.java:20)
>    at
> org.apache.felix.framework.util.SecureAction.startActivator(SecureAction
> .java:589)
>    at org.apache.felix.framework.Felix._startBundle(Felix.java:1563)
>    at org.apache.felix.framework.Felix.startBundle(Felix.java:1497)
>    at
> org.apache.felix.framework.Felix$RefreshHelper.restart(Felix.java:4203)
>    at org.apache.felix.framework.Felix.refreshPackages(Felix.java:3240)
>    at org.apache.felix.framework.Felix._updateBundle(Felix.java:1849)
>    at org.apache.felix.framework.Felix.updateBundle(Felix.java:1697)
>    at org.apache.felix.framework.BundleImpl.update(BundleImpl.java:372)
>    at org.apache.felix.framework.BundleImpl.update(BundleImpl.java:359)
>    at
> org.apache.felix.shell.impl.UpdateCommandImpl.execute(UpdateCommandImpl.
> java:96)
>    at
> org.apache.felix.shell.impl.Activator$ShellServiceImpl.executeCommand(Ac
> tivator.java:265)
>    at
> org.apache.felix.shell.tui.Activator$ShellTuiRunnable.run(Activator.java
> :167)
>    at java.lang.Thread.run(Thread.java:710)
> 
> Thanks in advance,
> 
> Anne
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org