[jira] [Created] (FELIX-3706) gogo shell startup failure in busy system
Derek Baum created FELIX-3706: - Summary: gogo shell startup failure in busy system Key: FELIX-3706 URL: https://issues.apache.org/jira/browse/FELIX-3706 Project: Felix Issue Type: Bug Components: Gogo Shell Affects Versions: gogo.shell-0.10.0 Reporter: Derek Baum Assignee: Derek Baum Priority: Minor launching felix from within Eclipse using bndtools, occasionally fails: gogo: CommandNotFoundException: Command not found: gosh org.apache.felix.gogo.runtime.CommandNotFoundException: Command not found: gosh at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:474) at org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:403) at org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108) at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183) at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120) at org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:89) at org.apache.felix.gogo.shell.Activator.run(Activator.java:75) at java.lang.Thread.run(Thread.java:680) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (FELIX-3706) gogo shell startup failure in busy system
[ https://issues.apache.org/jira/browse/FELIX-3706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Derek Baum resolved FELIX-3706. --- Resolution: Fixed Fix Version/s: gogo.shell-0.12.0 changed fixed sleep of 100ms to loop that explicitly tests for gogo:gosh command becoming available. > gogo shell startup failure in busy system > - > > Key: FELIX-3706 > URL: https://issues.apache.org/jira/browse/FELIX-3706 > Project: Felix > Issue Type: Bug > Components: Gogo Shell >Affects Versions: gogo.shell-0.10.0 >Reporter: Derek Baum >Assignee: Derek Baum >Priority: Minor > Fix For: gogo.shell-0.12.0 > > > launching felix from within Eclipse using bndtools, occasionally fails: > gogo: CommandNotFoundException: Command not found: gosh > org.apache.felix.gogo.runtime.CommandNotFoundException: Command not found: > gosh > at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:474) > at > org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:403) > at org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108) > at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183) > at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120) > at > org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:89) > at org.apache.felix.gogo.shell.Activator.run(Activator.java:75) > at java.lang.Thread.run(Thread.java:680) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Declarative Service: "Activate" Method
OK I think you are right and I have to find another solution:) Thanks for you answer:) Best regards Marcel Am 09.10.2012 09:12, schrieb David Jencks: > That is as expected. If the references are required or static that is the > only possible order. > > You could try to force the other order by making the references optional and > dynamic and registering the target services for the references after the > component you are interested in, but I think you will find it difficult to > maintain this order in a working system. > > david jencks > > On Oct 8, 2012, at 4:07 PM, Marcel Schlegel wrote: > >> Hi, >> >> I have a short question realating to the "Activate" method of a >> ComponentClass: >> Is it possible to call always at first the Activate method of a >> component or set a higher priority for it? >> >> e.g.: >> >> I have a class with an "@Component" and two"@Reference" annotations on >> class level. >> Furthermore I have the "@Activate" annotated method and some >> bind/unbind methods for my references. >> >> My problem: >> If I use this class in my osgi environment the "@Activate" method isn't >> called before the"bind..." methods. >> >> Best regards >> Marcel >> >>
[jira] [Commented] (FELIX-3701) Intermittent CNFE with embedded jars in Fragment Bundles
[ https://issues.apache.org/jira/browse/FELIX-3701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13473356#comment-13473356 ] Richard S. Hall commented on FELIX-3701: I doesn't seem like there should be a race condition here. Are you sure that the fragments are being attached in the case where you see failures? Certainly a reproducible setup would be good. > Intermittent CNFE with embedded jars in Fragment Bundles > > > Key: FELIX-3701 > URL: https://issues.apache.org/jira/browse/FELIX-3701 > Project: Felix > Issue Type: Bug > Components: Framework >Affects Versions: framework-4.0.2 >Reporter: Chetan Mehrotra >Priority: Minor > Attachments: fragment-bug.zip > > > In our Sling based OSGi application we are observing intermittent > ClassNotFoundException for classes which are present in a jar embedded in > Fragment bundle. Below are the details about the scenario > 1. Host bundle BundleA com.day.crx.sling.server [52] > 2. It has two fragment bundles attached. > - FragBundle1 - com.day.crx.crx-auth-ldap > - FragBundle2 - org.jcrutil.aws > 3. FragBundle2 - Has some embedded jars referred in the classpath > - FragJar2-1 - aws-java-sdk-1.3.11.jar > - FragJar2-2 - httpclient-4.2-beta1.jar > 4. There is a DS Component in BundleA which on activate tries to create an > instance of class which is present in FragJar2-1 > Now the issue is at times on clean start we get a CNFE at #4. On getting the > Felix debug logs following things were observed > 1. The logs report that INFO: Bundle BundleA [52] Class path entry not found: > FragJar2-1.jar > 2. The above entries are not observed if CNFE is not thrown > 3. If I try to debug the code the issue goes away which indicates that its > possible a race condition issue > 4. In case the issue is seen and I see the fragment bundle dir in the felix > folder the fragment jar is NOT exploded i.e. no bundle.jar-embedded directory > 5. Once the issue is seen it does not go away in restart > 6. The issue was not seen in 3.0.x releases > 7. If I flatten the jars present in fragment bundles the issue is not seen > 8. Exception seen is [1] > [1] > 05.10.2012 12:03:19.362 *ERROR* [FelixStartLevel] com.day.crx.sling.server > [com.day.crx.sling.server.impl.jmx.ManagedRepository] The activate method has > thrown an exception (java.lang.NoClassDefFoundError: > com/amazonaws/services/s3/model/S3ObjectSummary) > java.lang.NoClassDefFoundError: > com/amazonaws/services/s3/model/S3ObjectSummary > at java.lang.Class.forName0(Native Method) > at java.lang.Class.forName(Class.java:247) > at > org.apache.jackrabbit.core.config.SimpleBeanFactory.newInstance(SimpleBeanFactory.java:30) > at > org.apache.jackrabbit.core.config.BeanConfig.newInstance(BeanConfig.java:191) > at > org.apache.jackrabbit.core.config.RepositoryConfigurationParser$4.getDataStore(RepositoryConfigurationParser.java:997) > at > org.apache.jackrabbit.core.config.RepositoryConfig.getDataStore(RepositoryConfig.java:1072) > at > org.apache.jackrabbit.core.RepositoryImpl.(RepositoryImpl.java:279) > at com.day.crx.core.CRXRepositoryImpl.(CRXRepositoryImpl.java:307) > at com.day.crx.core.CRXRepositoryImpl.create(CRXRepositoryImpl.java:262) > at com.day.crx.core.CRXRepositoryImpl.create(CRXRepositoryImpl.java:245) > at > com.day.crx.sling.server.impl.jmx.ManagedRepository.activate(ManagedRepository.java:169) > 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.apache.felix.scr.impl.helper.BaseMethod.invokeMethod(BaseMethod.java:227) > at > org.apache.felix.scr.impl.helper.BaseMethod.access$500(BaseMethod.java:38) > at > org.apache.felix.scr.impl.helper.BaseMethod$Resolved.invoke(BaseMethod.java:591) > at > org.apache.felix.scr.impl.helper.BaseMethod.invoke(BaseMethod.java:472) > at > org.apache.felix.scr.impl.helper.ActivateMethod.invoke(ActivateMethod.java:146) > at > org.apache.felix.scr.impl.manager.ImmediateComponentManager.createImplementationObject(ImmediateComponentManager.java:226) > at > org.apache.felix.scr.impl.manager.ImmediateComponentManager.createComponent(ImmediateComponentManager.java:118) > at > org.apache.felix.scr.impl.manager.DelayedComponentManager.createRealComponent(DelayedComponentManager.java:95) > at > org.apache.felix.scr.impl.manager.AbstractComponentManager$Registered.getService(AbstractComponentManager.java:1296) > at > o
[jira] [Commented] (FELIX-3701) Intermittent CNFE with embedded jars in Fragment Bundles
[ https://issues.apache.org/jira/browse/FELIX-3701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13473818#comment-13473818 ] Chetan Mehrotra commented on FELIX-3701: >> Are you sure that the fragments are being attached in the case where you see >> failures? Yup. I forgot to mention one aspect. The code in host bundle instantiates a class (C1) using reflection which is present inline in FragBundle2 (i.e. directly present). This class in turn depends on a class C2 which is present in FragJar2-1. And CNFE is shown for C2 which confirms that C1 is found and hence the fragment is resolved Also as mentioned in logs above the FRAGMENT WIRE logs were present. Which indicate that fragment bundle did got resolved. >>Certainly a reproducible setup would be good. Would try to create one > Intermittent CNFE with embedded jars in Fragment Bundles > > > Key: FELIX-3701 > URL: https://issues.apache.org/jira/browse/FELIX-3701 > Project: Felix > Issue Type: Bug > Components: Framework >Affects Versions: framework-4.0.2 >Reporter: Chetan Mehrotra >Priority: Minor > Attachments: fragment-bug.zip > > > In our Sling based OSGi application we are observing intermittent > ClassNotFoundException for classes which are present in a jar embedded in > Fragment bundle. Below are the details about the scenario > 1. Host bundle BundleA com.day.crx.sling.server [52] > 2. It has two fragment bundles attached. > - FragBundle1 - com.day.crx.crx-auth-ldap > - FragBundle2 - org.jcrutil.aws > 3. FragBundle2 - Has some embedded jars referred in the classpath > - FragJar2-1 - aws-java-sdk-1.3.11.jar > - FragJar2-2 - httpclient-4.2-beta1.jar > 4. There is a DS Component in BundleA which on activate tries to create an > instance of class which is present in FragJar2-1 > Now the issue is at times on clean start we get a CNFE at #4. On getting the > Felix debug logs following things were observed > 1. The logs report that INFO: Bundle BundleA [52] Class path entry not found: > FragJar2-1.jar > 2. The above entries are not observed if CNFE is not thrown > 3. If I try to debug the code the issue goes away which indicates that its > possible a race condition issue > 4. In case the issue is seen and I see the fragment bundle dir in the felix > folder the fragment jar is NOT exploded i.e. no bundle.jar-embedded directory > 5. Once the issue is seen it does not go away in restart > 6. The issue was not seen in 3.0.x releases > 7. If I flatten the jars present in fragment bundles the issue is not seen > 8. Exception seen is [1] > [1] > 05.10.2012 12:03:19.362 *ERROR* [FelixStartLevel] com.day.crx.sling.server > [com.day.crx.sling.server.impl.jmx.ManagedRepository] The activate method has > thrown an exception (java.lang.NoClassDefFoundError: > com/amazonaws/services/s3/model/S3ObjectSummary) > java.lang.NoClassDefFoundError: > com/amazonaws/services/s3/model/S3ObjectSummary > at java.lang.Class.forName0(Native Method) > at java.lang.Class.forName(Class.java:247) > at > org.apache.jackrabbit.core.config.SimpleBeanFactory.newInstance(SimpleBeanFactory.java:30) > at > org.apache.jackrabbit.core.config.BeanConfig.newInstance(BeanConfig.java:191) > at > org.apache.jackrabbit.core.config.RepositoryConfigurationParser$4.getDataStore(RepositoryConfigurationParser.java:997) > at > org.apache.jackrabbit.core.config.RepositoryConfig.getDataStore(RepositoryConfig.java:1072) > at > org.apache.jackrabbit.core.RepositoryImpl.(RepositoryImpl.java:279) > at com.day.crx.core.CRXRepositoryImpl.(CRXRepositoryImpl.java:307) > at com.day.crx.core.CRXRepositoryImpl.create(CRXRepositoryImpl.java:262) > at com.day.crx.core.CRXRepositoryImpl.create(CRXRepositoryImpl.java:245) > at > com.day.crx.sling.server.impl.jmx.ManagedRepository.activate(ManagedRepository.java:169) > 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.apache.felix.scr.impl.helper.BaseMethod.invokeMethod(BaseMethod.java:227) > at > org.apache.felix.scr.impl.helper.BaseMethod.access$500(BaseMethod.java:38) > at > org.apache.felix.scr.impl.helper.BaseMethod$Resolved.invoke(BaseMethod.java:591) > at > org.apache.felix.scr.impl.helper.BaseMethod.invoke(BaseMethod.java:472) > at > org.apache.felix.scr.impl.helper.ActivateMethod.invoke(ActivateMethod.java:146) > at > org.apache.felix.scr.impl.manager.ImmediateComponentManager.createImplementationObj
[jira] [Commented] (FELIX-3674) Embedded Felix on Android - loading Ressource
[
https://issues.apache.org/jira/browse/FELIX-3674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13473884#comment-13473884
]
Mustafa commented on FELIX-3674:
hi,
after adding the property "felix.bootdelegation.implicit=false" to felix my
ressource will load from felix. Karl, if you would like you can close this
issue :) I would like to thanks again this perfect support.
> Embedded Felix on Android - loading Ressource
> --
>
> Key: FELIX-3674
> URL: https://issues.apache.org/jira/browse/FELIX-3674
> Project: Felix
> Issue Type: Bug
> Components: Framework
>Affects Versions: framework-4.0.3
> Environment: Android
>Reporter: Mustafa
>Assignee: Karl Pauls
>Priority: Critical
> Attachments: Android-Resource-Test.zip
>
>
> http://www.mail-archive.com/users@felix.apache.org/msg12978.html
> Hi,
> i trying to work with apache felix on android. My Bundles starting without
> any problems but i found one problem. If i trying to load a ressource
> property:
> ResourceBundle bundle =
> ResourceBundle.getBundle("bundle0.services.propertyfile");
> i getting following nullpointer exception:
> 09-21 12:26:08.450: I/System.out(2178): Caused by:
> java.lang.NullPointerException
> 09-21 12:26:08.450: I/System.out(2178): at
> org.apache.felix.framework.BundleWiringImpl.doImplicitBootDelegation(BundleWiringImpl.java:1626)
> 09-21 12:26:08.450: I/System.out(2178): at
> org.apache.felix.framework.BundleWiringImpl.searchDynamicImports(BundleWiringImpl.java:1603)
> 09-21 12:26:08.450: I/System.out(2178): at
> org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1439)
> 09-21 12:26:08.450: I/System.out(2178): at
> org.apache.felix.framework.BundleWiringImpl.getResourceByDelegation(BundleWiringImpl.java:1360)
> 09-21 12:26:08.450: I/System.out(2178): at
> org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.getResource(BundleWiringImpl.java:2256)
> 09-21 12:26:08.450: I/System.out(2178): at
> java.lang.ClassLoader.getResourceAsStream(ClassLoader.java:434)
> 09-21 12:26:08.450: I/System.out(2178): at
> java.util.ResourceBundle.handleGetBundle(ResourceBundle.java:514)
> 09-21 12:26:08.450: I/System.out(2178): at
> java.util.ResourceBundle.getBundle(ResourceBundle.java:227)
> 09-21 12:26:08.460: I/System.out(2178): at
> java.util.ResourceBundle.getBundle(ResourceBundle.java:140)
> This problem occurs also if i trying to load jTDS driver to conntect to a
> database, because they trying to load some property file.
> I actually running the release version of felix and components.
> Following components of felix im using:
> felix.jar
> bundlerespository.jar
> ipojo.jar
> ipojo-annotation.jar
> ipojo-arch.jar
> shell.jar
> Regards,
> mustafa
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
