January 2010 - jboss-dev-forums - Jboss List Archives

[JBoss Profiler Development] New message: "Re: Has this project stalled?"

by Pat Arneson

JBoss development, A new message was posted in the thread "Has this project stalled?": http://community.jboss.org/message/520346#520346 Author : Pat Arneson Profile : http://community.jboss.org/people/noise_is_life Message: -------------------------------------------------------------- So if I'm understanding what you are saying, it seems things should be in order. I've been through the entire document a couple of times, what it doesn't really tell me is how to exactly string all those dandy properties and commands together in a meaningful way. Obviously the default properties file goes a long way in that regard. A couple follow-ups. The classes in question live in an EAR, should that matter? When I run a list from the client I get the following: > [admin@g2a jboss-profiler-2.0.0.Beta5]$ java -jar jboss-profiler-client.jar -h 0.0.0.0 -p 5400 list > org.jboss.profiler.* > org.apache.jsp.* Neither of those packages are defined in my config and there is no sign of the packages I did define. -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/520346#520346

16 years, 2 months

1
0
0 / 0

[JBoss Profiler Development] New message: "Re: Has this project stalled?"

by Jesper Pedersen

JBoss development, A new message was posted in the thread "Has this project stalled?": http://community.jboss.org/message/520342#520342 Author : Jesper Pedersen Profile : http://community.jboss.org/people/jesper.pedersen Message: -------------------------------------------------------------- Start with the static configuration in order to get a setup that works for you. The "includes" property in your case means that all public methods in com.upstream.inbound and sub-packages will be profiled. The "visibility" property means that by default private methods are being profiled. See Chapter 4 in the user guide for a description of the various properties - then Chapter 5 for the supported commands. Once you got it running feel free to submit a "Quick Start" chapter as a patch to our JIRA installation. -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/520342#520342

16 years, 2 months

1
0
0 / 0

[JBoss Profiler Development] New message: "Re: Has this project stalled?"

by Pat Arneson

JBoss development, A new message was posted in the thread "Has this project stalled?": http://community.jboss.org/message/520339#520339 Author : Pat Arneson Profile : http://community.jboss.org/people/noise_is_life Message: -------------------------------------------------------------- Great! The most obvious thing would be to help out with some documentation once I figure things out enough for my own purposes. So on to my questions to at least get the thing working. I have the profiler running and am able to take snapshots, but have been unable to get my classes to show up in the profile. Here are the first few lines of my jboss-profiler.properties: > enable=yes > precompiled=no > cpu=yes > memory=yes > includes=com.upstream.inbound.*|public,com.upstream.inbound.*|public > excludes=* > visibility=private > save=yes > savelocation=. > startup=yes > ... I'm unclear as to the purpose of the private/public visibility attribute so I guessed. I also tried the following command in an attempt to get the profiler to see my classes: java -jar jboss-profiler-client.jar -h 0.0.0.0 -p 5400 add com.upstream.inbound.* But no luck. My attempts so far have been with 2.0.0.Beta5. Thanks. -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/520339#520339

16 years, 2 months

1
0
0 / 0

[JBoss Profiler Development] New message: "Re: Has this project stalled?"

by Jesper Pedersen

JBoss development, A new message was posted in the thread "Has this project stalled?": http://community.jboss.org/message/520326#520326 Author : Jesper Pedersen Profile : http://community.jboss.org/people/jesper.pedersen Message: -------------------------------------------------------------- The project is not dead - we just have limited resources currently add new features. So feel free to help out in an area that interest you -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/520326#520326

16 years, 2 months

1
0
0 / 0

[JBoss Profiler Development] New message: "Has this project stalled?"

by Pat Arneson

JBoss development, A new message was posted in the thread "Has this project stalled?": http://community.jboss.org/message/520324#520324 Author : Pat Arneson Profile : http://community.jboss.org/people/noise_is_life Message: -------------------------------------------------------------- I see quite a few user questions that have gone unanswered and no beta release since early last year. I'm interested in the project but don't want to spend the time if it is a dead end. I believe I have the profiler running, but am unable to get it to profile my classes. Thanks! -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/520324#520324

16 years, 2 months

1
0
0 / 0

[EJB 3.0 Development] New message: "Re: Source Location for EJB3 Components"

by Andrew Rubinger

JBoss development, A new message was posted in the thread "Source Location for EJB3 Components": http://community.jboss.org/message/520306#520306 Author : Andrew Rubinger Profile : http://community.jboss.org/people/ALRubinger Message: -------------------------------------------------------------- Minor change after a discussion w/ Carlo: I've moved the structure to leave space representing branches for each component. http://anonsvn.jboss.org/repos/jbossas/projects/ejb3/components/async/trunk S, ALR -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/520306#520306

16 years, 2 months

1
0
0 / 0

[JBoss Microcontainer Development] New message: "Pluggable dependency resolver"

by Kabir Khan

JBoss development, A new message was posted in the thread "Pluggable dependency resolver": http://community.jboss.org/message/520287#520287 Author : Kabir Khan Profile : http://community.jboss.org/people/kabir.khan@jboss.com Message: -------------------------------------------------------------- I have made a start on the pluggable dependency resolvers and am committing stuff to https://svn.jboss.org/repos/jbossas/projects/kernel/branches/resolver. So far I am just playing to get a rough idea of what is needed. I have extracted the contents of https://svn.jboss.org/repos/jbossas/projects/kernel/branches/resolver/dep... and what it calls with https://svn.jboss.org/repos/jbossas/projects/kernel/branches/resolver/dep... and https://svn.jboss.org/repos/jbossas/projects/kernel/branches/resolver/dep.... AbstractDependencyResolver contains a reference to the controller and utility methods to do work on the controller. DefaultDependencyResolver contains the "work" done by resolveContexts and the methods it called. At the moment DefaultDependencyResolver contains too much controller specific stuff, which I want to move out, but I just wanted to get something in for further discussion. -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/520287#520287

16 years, 2 months

1
0
0 / 0

[JBoss Microcontainer Development] New message: "Re: Activating OnDemand beans from child controller"

by Kabir Khan

JBoss development, A new message was posted in the thread "Activating OnDemand beans from child controller": http://community.jboss.org/message/520262#520262 Author : Kabir Khan Profile : http://community.jboss.org/people/kabir.khan@jboss.com Message: -------------------------------------------------------------- > mailto:kabir.khan@jboss.com wrote: > > After a trying a few different things what I have now is. > -Leaving DependencyItem as is > -Modifying AbstractController.enableOnDemand() to set onDemandEnabled for the initiating controller (i.e. scoped in this case) and also for the controller the OnDemand context actually belongs to. > -Modifying the AbstractController.resolveContexts() loop to record if onDemandEnabled was true, and if it was when finishing the loop to call resolveContexts() on the parent controller. Committed against https://jira.jboss.org/jira/browse/JBKERNEL-79 -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/520262#520262

16 years, 2 months

1
0
0 / 0

[JBoss Microcontainer Development] New message: "Re: Activating OnDemand beans from child controller"

by Kabir Khan

JBoss development, A new message was posted in the thread "Activating OnDemand beans from child controller": http://community.jboss.org/message/520261#520261 Author : Kabir Khan Profile : http://community.jboss.org/people/kabir.khan@jboss.com Message: -------------------------------------------------------------- > mailto:kabir.khan@jboss.com wrote: > > Fixing http://lists.jboss.org/pipermail/jboss-development/2010-January/015434.html I am adding a ScopedOnDemandDependencyTestCase (extends OnDemandDependencyTestCase similar to (Scoped)DuplicateAliasTestCase), but have found a deeper problem. If an OnDemand bean is installed in the main controller and is depended on by a bean in a child controller the OnDemand bean never gets activated and the child controller bean's dependency never resolved. > I install Bean1 with OnDemand, goes to Describe state > I install scoped Bean2 with Automatic and a dependency on Bean1, goes to Instantiated state fine > > When trying to move Bean2 to Configured state it does not resolve for the following reasons: > When enabling ondemand beans in AbstractDependencyItem.resolve(), it was looking at the wrong controller, I changed: > > *if* (unresolvedContext != *null* && ControllerMode.ON_DEMAND.equals(unresolvedContext.getMode())) > { > *try* > { > controller.enableOnDemand(unresolvedContext); > > > > > to > > > *if* (unresolvedContext != *null* && ControllerMode.ON_DEMAND.equals(unresolvedContext.getMode())) > { > *try* > { > unresolvedContext.getController().enableOnDemand(unresolvedContext); > > > > > > > Now Bean1 correctly gets its requiredState set to INSTALLED. Unfortunately this is not enough. > > > > In the normal/unscoped mode the mechanism is that AbstractDI.resolve() returns false, and we end up back in the resolveContexts() loop which finds Bean1 is not in its requiredState (INSTALLED). > > > > In the scoped test, it does not get picked up since Bean2 was installed in the scoped controller whose resolveContexts() does not involve the main controller so Bean1 is never found. > > > > I'll see if I can fix this > > After a trying a few different things what I have now is. -Leaving DependencyItem as is -Modifying AbstractController.enableOnDemand() to set onDemandEnabled for the initiating controller (i.e. scoped in this case) and also for the controller the OnDemand context actually belongs to. -Modifying the AbstractController.resolveContexts() loop to record if onDemandEnabled was true, and if it was when finishing the loop to call resolveContexts() on the parent controller. -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/520261#520261

16 years, 2 months

1
0
0 / 0

[JBoss Microcontainer Development] New message: "Re: Activating OnDemand beans from child controller"

by Kabir Khan

JBoss development, A new message was posted in the thread "Activating OnDemand beans from child controller": http://community.jboss.org/message/520260#520260 Author : Kabir Khan Profile : http://community.jboss.org/people/kabir.khan@jboss.com Message: -------------------------------------------------------------- This is an issue when uninstalling a bean and checking the OnDemand beans we depend on. We check the OnDemand beans dependsOnMe to see if the contexts are still installed. It works fine now, but we do get that warning for beans that have been uninstalled already since dependsOnMe is never cleaned up. Anyway, as discussed offline we can wait until we do some more work on the dependencies. -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/520260#520260

16 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums January 2010