[
https://issues.apache.org/jira/browse/FELIX-5665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16092025#comment-16092025
]
AnilKumar Attuluri commented on FELIX-5665:
-------------------------------------------
[~karlpauls]
Yep. I was able to build and use the framework version 5.7.0-SNAPSHOT.
I am trying to do the following:
i) Enable logging in felix to log the resource/classes being loaded. (I have
set *felix.log.level=3*) in *$KARAF_HOME/etc/config.properties* but I still
don't see the log statement I added in BundleWiringImpl in
findClassOrResourceByDelegation method. Is there a logger that I have to set
too?
ii) Give you a docker instance where you can reproduce the problem with out
actually sharing our code. (Once I can get i) done, I will get this to you)
I am trying to get these done by tomorrow.
> High CPU usage on
> org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation
> ---------------------------------------------------------------------------------------------
>
> Key: FELIX-5665
> URL: https://issues.apache.org/jira/browse/FELIX-5665
> Project: Felix
> Issue Type: Bug
> Affects Versions: framework-5.6.4
> Reporter: AnilKumar Attuluri
> Attachments: IMG_1.jpg, IMG_2.jpg
>
>
> We have been running some performance tests to prepare our OSGi bundle
> (*running in Apache Karaf*) for production.
> Just to give some background about our OSGi bundle, we converted an existing
> Spring application into an OSGi bundle with all the current dependencies
> packaged into the bundle as an uber artifact.
> When we run >= 500 TPS (each of these calls results in a http call made via a
> library) we run into this high CPU usage spikes reaching up to 100% CPU.
> Please see the image attached, the spikes in the image are 100% CPU usage
> while the average is about 40%. Also see the CPU sampler image which points
> to
> *org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation*
> Is there an existing bug/documentation that already captures this?
> We don't see this behavior when we run the same app in standalone JVM.
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
