August 2009 - jboss-osgi-dev - Jboss List Archives

[JBoss OSGi Development] - Re: Performance problem

by alesj

I guess you're reading a lot of different manifest files. Since all of the code in VFSCLPolicy is cached. But to read manifest a lot of slow ops are present. * find the root with class file ** read-in all jars ** navigate to class file * read manifest.mf ** again navigate ** read manifest attributes Which means a lot of PathTokenizer and StructuredVirtualFileHandler usage. With VFS-performance issue already present in MC dev forum, I'll have a look what can be improved, and then re-run this here. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251540#4251540 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251540

15 years

1
0
0 / 0

[JBoss OSGi Development] - Re: Performance problem

by adrian＠jboss.org

The issue appears to be in the VFS. If I comment out the reading of the manifest for the package information (which uses the VFS) then the tests take about 16 seconds (i.e. less than half the time). BaseClassLoader::definePackage | - PackageInformation pi = policy.getClassPackageInformation(className, packageName); | + PackageInformation pi = null; | This is using jboss-vfs 2.1.2.GA View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251529#4251529 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251529

15 years

1
0
0 / 0

[JBoss OSGi Development] - Re: Performance problem

by kabir.khan＠jboss.com

One thing I worked on in the past is https://jira.jboss.org/jira/browse/JBKERNEL-4 which does more work on undeploy, but it should not be that much. Try commenting the call to uninstallUnusedOnDemandContexts() in AbstractController.uninstallContext() to see if it makes any difference. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251523#4251523 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251523

15 years

1
0
0 / 0

[JBoss OSGi Development] - Re: Bundle.start() does not transition to ACTIVE

by adrian＠jboss.org

I'd actually already fixed this TODO, but not committed it yet. The issue is more general than your fix. My fix is to checkIncomplete() on the deployment since there are other things besides missing dependencies that can cause the bundle not to start. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251500#4251500 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251500

15 years

1
0
0 / 0

[JBoss OSGi Development] - Re: HOWTO chage the behaviour of the CL policy

by adrian＠jboss.org

This test is currently broken for me. But if there is a PackageRequirement there should be a delegate (which the OSGi spec calls a "wire"). Although you have put some code that weeds out system packages that I don't understand? My understanding was that non-core api had to be referenced using Import-Package e.g. the logging or compendium api. and that this would resolve to the implementing (extension) bundle - possibly the system bundle? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251493#4251493 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251493

15 years

1
0
0 / 0

[JBoss OSGi Development] - Re: Package cannot have multiple exporters

by adrian＠jboss.org

This is what I mentioned last week about split packages need more work. There's a JIRA issue it for it in the classloading. AFAIK, the issue in the validation (consistency checking) rather than the runtime? An OSGi implementation doesn't have to support split packages so its not a priorty for me. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251490#4251490 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251490

15 years

1
0
0 / 0

[JBoss OSGi Development] - snapshots

by adrian＠jboss.org

Can you please make sure you deploy any snapshots that are being used. I managed to build my own 2.0.9-SNAPSHOT of the MC, but there are others that appear to missing which is I think why tests are failing for me? | [WARNING] Attempting to build MavenProject instance for Artifact (org.apache.felix:org.apache.felix.log:1.1.0-20090817.141229-3) of type: jar; constructing POM artifact instead. | [WARNING] Attempting to build MavenProject instance for Artifact (org.jboss.osgi.bundles:jboss-osgi-common:1.0.1-20090729.115819-1) of type: jar; constructing POM artifact instead. | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251485#4251485 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251485

15 years

1
0
0 / 0

[JBoss OSGi Development] - Performance problem

by adrian＠jboss.org

Before I merged with mc-osgi-int trunk the testsuite was taking about 10 seconds for the whole thing. After the merge it is 40 seconds! There are no new tests for me (Thomas's new tests are not included in the OSGiTestSuite), only other changes, so something inefficient has been introduced. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251484#4251484 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251484

15 years

1
0
0 / 0

[JBoss OSGi Development] - refactoring

by adrian＠jboss.org

I've said this many times before: PLEASE BUT A BIG STOP SIGN OVER YOUR REFACTORING BUTTON It makes it very difficult for others to merge changes, especially when a project is being actively developed. I just wasted 3 hours trying to merge my latest changes because things had moved (including the whole svn repository :-) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251483#4251483 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251483

15 years

1
0
0 / 0

[JBoss OSGi Development] - tests log4j.xml

by adrian＠jboss.org

I've removed this again. Having a default log4j.xml for tests is stupid because of the following reasons. 1) log4j.test.dir is not always set - e.g. impossible to run the tests under eclipse 2) you don't get the logging when you look the test reports in the target folder 3) turning off console logging means you have to hunt around for different information related to the test instead of searching in one place View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251481#4251481 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251481

15 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

jboss-osgi-dev August 2009