May 2009 - jboss-dev-forums - Jboss List Archives

[Design of JBoss ESB] - Re: (Excessive?) Drools class loading in ContentBasedRouter

by Hamlansa

Here is the stack of the resources being loaded. Inherent time: 68,033 ms (14 %) Average Time: 34 Microseconds Invocations: 1,953,902 java.util.Enumeration.hasMoreElements 13.6% - 62,817 ms - 1,808,208 hot spot inv. org.jboss.mx.loading.UnifiedLoaderRepository3.getResources 13.6% - 62,817 ms - 1,808,208 hot spot inv. org.jboss.mx.loading.RepositoryClassLoader.findResources 13.6% - 62,817 ms - 1,808,208 hot spot inv. java.lang.ClassLoader.getResources 13.6% - 62,817 ms - 1,808,208 hot spot inv. org.drools.util.ChainedProperties.getResources 13.6% - 62,817 ms - 1,808,208 hot spot inv. org.drools.util.ChainedProperties. 13.6% - 62,817 ms - 1,808,208 hot spot inv. org.drools.util.ChainedProperties. 13.6% - 62,817 ms - 1,808,208 hot spot inv. org.drools.util.ChainedProperties. 13.6% - 62,817 ms - 1,808,208 hot spot inv. org.drools.SessionConfiguration.init 13.6% - 62,817 ms - 1,808,208 hot spot inv. org.drools.SessionConfiguration. 13.6% - 62,817 ms - 1,808,208 hot spot inv. org.drools.reteoo.ReteooStatelessSession.newWorkingMemory 13.6% - 62,817 ms - 1,808,208 hot spot inv. org.drools.reteoo.ReteooStatelessSession.execute 13.6% - 62,817 ms - 1,808,208 hot spot inv. org.jboss.internal.soa.esb.services.rules.DroolsRuleService.executeStatelessRules 13.6% - 62,817 ms - 1,808,208 hot spot inv. org.jboss.internal.soa.esb.services.rules.DroolsRuleService.executeStatelessRules 13.6% - 62,817 ms - 1,808,208 hot spot inv. org.jboss.internal.soa.esb.services.rules.RuleServiceCallHelper.executeRulesService 13.6% - 62,817 ms - 1,808,208 hot spot inv. org.jboss.internal.soa.esb.services.routing.cbr.JBossRulesRouter.route 13.6% - 62,817 ms - 1,808,208 hot spot inv. org.jboss.soa.esb.actions.ContentBasedWiretap.executeRules 13.6% - 62,817 ms - 1,808,208 hot spot inv. org.jboss.soa.esb.actions.ContentBasedWiretap.process 13.6% - 62,817 ms - 1,808,208 hot spot inv. org.jboss.soa.esb.actions.ContentBasedRouter.process 13.6% - 62,817 ms - 1,808,208 hot spot inv. org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline 13.6% - 62,817 ms - 1,808,208 hot spot inv. org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline 13.6% - 62,817 ms - 1,808,208 hot spot inv. org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process 13.6% - 62,817 ms - 1,808,208 hot spot inv. org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run 13.6% - 62,817 ms - 1,808,208 hot spot inv. java.util.concurrent.ThreadPoolExecutor$Worker.run View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4233900#4233900 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4233900

15 years, 7 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBM 2.0 release checklist

by jmesnil

0) start from a clean svn checkout View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4233893#4233893 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4233893

15 years, 7 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - JBM 2.0 release checklist

by timfox

I gave up trying to create and link a wiki page for this, so here it is: 1) Check version numbers are correct 2) Check and update README 3) Check docs are correct 4) Run full test suite 5) Run all examples 6) Tag release 7) Build distro 8) Unzip distro on clean directory 9) Test all examples work from distro 10) check docs from distro 11) check readme from distro 12) test stopping and starting server using run.sh from distro 13) upload to jboss.org, including distro + all docs + javadoc 14) announce on user forum. 15) announce on blog 16) announce on twitter View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4233886#4233886 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4233886

15 years, 7 months

1
0
0 / 0

[Design of POJO Server] - Re: Various performance issues in core projects

by jaikiran

It's now in jboss-dev mailing list http://lists.jboss.org/pipermail/jboss-development/2009-May/014464.html :) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4233884#4233884 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4233884

15 years, 7 months

1
0
0 / 0

[Design of POJO Server] - Re: Various performance issues in core projects

by alesj

"jaikiran" wrote : | If no one has any objections, i am going to comment out the JMX annotation on Deployers MC bean in conf/bootstrap/deployers.xml of AS trunk. I'll create a JIRA | I guess we need a bigger audience to confirm this. ;-) e.g. jboss-dev to check if any user/dev complains (as not everybody follows this forum, where ml is more observed) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4233878#4233878 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4233878

15 years, 7 months

1
0
0 / 0

[Design of POJO Server] - Re: Various performance issues in core projects

by jaikiran

https://jira.jboss.org/jira/browse/JBAS-6987 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4233875#4233875 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4233875

15 years, 7 months

1
0
0 / 0

[Design of POJO Server] - Re: Various performance issues in core projects

by jaikiran

"adrian(a)jboss.org" wrote : | 4) The correct way to not register (sub-)deployment/components in JMX is | to remove the @JMX annotation from the DeployersImpl bean in conf/bootstrap/deployers.xml | | If the DeployersImpl is not registered in JMX then neither will be the deployments. | | This has nothing directly to do with the bean. | | It is letting you look (using JMX) at what deployers the deployment/component went | through, the attachments (deployment descriptors) associated with the | deployment/component and maybe how long the processing took for each deployer | if you enable the stats. | | It's just debug information so it is optional. If no one has any objections, i am going to comment out the JMX annotation on Deployers MC bean in conf/bootstrap/deployers.xml of AS trunk. I'll create a JIRA View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4233874#4233874 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4233874

15 years, 7 months

1
0
0 / 0

[Design of JBoss ESB] - Re: (Excessive?) Drools class loading in ContentBasedRouter

by Kevin.Conner＠jboss.com

It sounds as if there is something wrong somewhere. Can you provide a stack for the resource loading? We can take a look and see if it is something we are doing or something inherent in drools. Thanks Kev View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4233859#4233859 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4233859

15 years, 7 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Making bean validaton part of kernel configuration

by jaikiran

"alesj" wrote : | Can you check if it makes any difference? Sure. Let me just go through these changes. Will update this thread with the results. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4233853#4233853 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4233853

15 years, 7 months

1
0
0 / 0

[Design of JBoss ESB] - XsltAction

by beve

I'm starting work on https://jira.jboss.org/jira/browse/JBESB-2584 and wanted to gather requirements/requests. A suggested sample config could look like this: <action name="xslt-transform" class="org.jboss.soa.esb.actions.transformation.xslt.XsltAction"> | <property name="templateFile" value="/sample.xsl"/> | <property name="failOnWarning" value="true"/> | </action> I was thinking that we also should support the ability to add TranformerFactoryFeatures and attributes. For example, adding a feature could look like this: <property name="factory.feature.http://javax.xml.XMLConstants/feature/secure-processing" value="true"/> The same things would then apply to attributes but the prefix would be 'factory.attribute'. Also the ability to specify a URIResolver (http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/transform/URIResolver.html) to make things flexible. Suggestion from TomF: anonymous wrote : I think the impl should support multiple Source types, defaulting to StreamSource So the message payload could be a File, an InputStream, or Reader (String payload would be a StringReader in which case a a StreamSource would be used). The message payload could also be a DOMSource or a SAXSource. Are there any others ? The same options should exist for the result as well then right? All suggestions are welcome! Thanks, /Daniel View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4233813#4233813 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4233813

15 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums May 2009