March 2008 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-1504) CBR using rules has poor performance

by Martin Vecera (JIRA)

CBR using rules has poor performance ------------------------------------ Key: JBESB-1504 URL: http://jira.jboss.com/jira/browse/JBESB-1504 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Content Based Routing Affects Versions: 4.2.1 Environment: SOA-P 4.2.0.beta1 Reporter: Martin Vecera We have a simple performance that uses ContentBasedRouter to route XML messages: <action class="org.jboss.soa.esb.actions.ContentBasedRouter" name="ContentBasedRouter"> <property name="ruleSet" value="MyESBRules-XPath.drl"/> <property name="ruleLanguage" value="XPathLanguage.dsl"/> <property name="ruleReload" value="true"/> <property name="destinations"> <route-to destination-name="regular1" service-category="wiretapCategory1" service-name="regularService"/> <route-to destination-name="regular2" service-category="wiretapCategory1" service-name="regularService"/> <route-to destination-name="regular3" service-category="wiretapCategory1" service-name="regularService"/> <route-to destination-name="regular4" service-category="wiretapCategory1" service-name="regularService"/> <route-to destination-name="regular5" service-category="wiretapCategory1" service-name="regularService"/> <route-to destination-name="regular6" service-category="wiretapCategory1" service-name="regularService"/> <route-to destination-name="regular7" service-category="wiretapCategory1" service-name="regularService"/> <route-to destination-name="regular8" service-category="wiretapCategory1" service-name="regularService"/> <route-to destination-name="regular9" service-category="wiretapCategory1" service-name="regularService"/> <route-to destination-name="regular0" service-category="wiretapCategory1" service-name="catchService"/> </property> </action> I have created a rule set of 100 rules. Like this: package com.jboss.soa.esb.routing.cbr import org.jboss.soa.esb.message.Message; import org.jboss.soa.esb.message.format.MessageType; expander XPathLanguage.dsl global java.util.List destinations; rule "ProductId1" salience 100 when xpathEquals "/Order/OrderLines/OrderLine/Product/@productId", "1" then Destination : "regular1"; end ... rule "ProductId299" salience 100 when xpathEquals "/Order/OrderLines/OrderLine/Product/@productId", "299" then Destination : "regular0"; end rule "Default rule" salience 1 when then Destination : "regular0"; end See https://svn.corp.jboss.com/repos/soa/trunk/qa/tests/quickstarts/performan... for the whole file. The performance is very poor (see SOA-240 for reports). Only a tens of messages per second. What's the problem here? Is the Rules engine really so slow? Or is it parsing the file every time a message arrives? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 5 months

4
24
0 / 0

[JBoss JIRA] Created: (JBESB-1445) Message Store does not participate in JTA transaction

by Jiri Pechanec (JIRA)

Message Store does not participate in JTA transaction ----------------------------------------------------- Key: JBESB-1445 URL: http://jira.jboss.com/jira/browse/JBESB-1445 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Message Store, Rosetta Affects Versions: 4.2.1 Reporter: Jiri Pechanec Assigned To: Mark Little Fix For: 4.2.1 CP1 Service uses JCA/JMS listener and stores message to message store. If the transaction is rolled back then the messages will reatin in message store as it does not participate in global JTA transaction. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 5 months

3
5
0 / 0

[JBoss JIRA] Created: (JBESB-1153) File Gateway: Consume only a single file at a time

by Burr Sutter (JIRA)

File Gateway: Consume only a single file at a time -------------------------------------------------- Key: JBESB-1153 URL: http://jira.jboss.com/jira/browse/JBESB-1153 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.2 Reporter: Burr Sutter Assigned To: Mark Little Fix For: 4.3 The current File gateway consumes files at a rate faster than the internal/native listener (typically JMS-based) and its associated action chain. This request is for a configuration property that causes the rate of consumption of the file gateway to match the underlying internal/native listener. Basically a file would not be pulled from disk until it has completely passed through the action chain. Here are some notes related to this use case: I have 1000+ files which are very huge in size and when all the files are kept in the folder they are read at same time and placed in configured JMS Queue. - When all the files are placed in Queue there is a chance that the size of messages in Queue may exceed and it may not accept new messages? Or - Sometimes the case may be like the input folder is monitored by one person and the message processing is monitored by other person. In this case when all the files are read at once it gives a wrong assumption that all files are processed but where as due to some application failure the messages may still be in queue. Or - Its always a good option to be able to see how many messages are still in process in the folder rather than browsing the JMS queue and looking for Queue depth. In this case if you look at Queue depth sometimes it may be give you wrong count of messages as there is a chance that some other application also put message some messages into the same queue, when Queue is configured for application sharing. Or - If you want to replace a single file out of 1000+ files in the input folder while in middle of processing the files, it will be easy if the files are read one at a time rather going and deleting the messages from JMS queue after they are read at once and placed in Queue. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 6 months

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-726) JCR Message repository does not support classification and delivery earmark

by Jiri Pechanec (JIRA)

JCR Message repository does not support classification and delivery earmark --------------------------------------------------------------------------- Key: JBESB-726 URL: http://jira.jboss.com/jira/browse/JBESB-726 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2 Milestone Release 3 Reporter: Jiri Pechanec Assigned To: Mark Little Priority: Minor JCR Message repository currently does not support classification and delivery flag. Proposed solution 1) Add special property under which the classification will be stored 2) Add special property under which delivery earmark will be stored 3) Implement all get<Collection> actions as JCR query and return the results -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 6 months

3
5
0 / 0

[JBoss JIRA] Created: (JBESB-549) Automate war deployment for quickstarts

by Kevin Conner (JIRA)

Automate war deployment for quickstarts --------------------------------------- Key: JBESB-549 URL: http://jira.jboss.com/jira/browse/JBESB-549 Project: JBoss ESB Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2 We need to be able to automatically deploy the QSes into a war deployment. The main blocker for this issue is the new requirement to merge jboss-esb.xml configuration files. This is required because of the ESB internal services. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 6 months

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-643) Add BRMS support to RuleService

by Jeff DeLong (JIRA)

Add BRMS support to RuleService -------------------------------- Key: JBESB-643 URL: http://jira.jboss.com/jira/browse/JBESB-643 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Content Based Routing Reporter: Jeff DeLong Assigned To: Mark Little Add BRMS support to the platform. In particular the capability to specify a rulesBase in the ruleService configuration and have the ruleService retrieve the ruleBase from the BRMS instead of creating ruleBase on the fly from drl / dsl files on the classpath. This will allow for better maintenance and management of the rules, as well as "hot" deployment on the rules. Note - I listed this under CBR as there is not a RuleService Component listed, however it applies to both CBR and RuleService. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 6 months

4
8
0 / 0

[JBoss JIRA] Created: (JBESB-550) ESB war deployment for websphere/weblogic

by Kevin Conner (JIRA)

ESB war deployment for websphere/weblogic ----------------------------------------- Key: JBESB-550 URL: http://jira.jboss.com/jira/browse/JBESB-550 Project: JBoss ESB Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Kevin Conner Assigned To: Kevin Conner Priority: Optional Fix For: 4.2 Look at deploying the ESB war file into websphere/weblogic -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 6 months

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-645) Add support for decision tables to RuleServices

by Jeff DeLong (JIRA)

Add support for decision tables to RuleServices ----------------------------------------------- Key: JBESB-645 URL: http://jira.jboss.com/jira/browse/JBESB-645 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Content Based Routing Reporter: Jeff DeLong Assigned To: Mark Little The current ruleService does not appear to support Decision Tables. Decision Tables require the use of the SpreadsheetCompiler API to create a drl from a spreadsheet on the classpath. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 6 months

4
6
0 / 0

[JBoss JIRA] Created: (JBESB-644) Add support for both stateless and stateful RuleServices

by Jeff DeLong (JIRA)

Add support for both stateless and stateful RuleServices -------------------------------------------------------- Key: JBESB-644 URL: http://jira.jboss.com/jira/browse/JBESB-644 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Content Based Routing Reporter: Jeff DeLong Assigned To: Mark Little The current JBossRuleRouter (which currently implements the RuleService) uses StatefulSessions in a Stateless way. Which is fine in most cases). JBossRulesRouter creates a new workingMemory (StatefulSession), asserts facts, and should (although it does not currently, disponse of the workingMemory - See also JBESB-642. ). JBoss Rules support StatelessSessions. The need to dispose of workingMemory is eliminated if StatelessSessions are used. StatelessSession have some limitations compared to Stateful, but are designed for instance, for rule applications deployed as web services, where basically a single method needs to transfer all the data, create the workingMemory, assert the data (as a single object or list of objects) and fire the rules. CBR can be thought of as a stateless service. A single Message object is asserted into working memory, and the rules are fired. Many rule application will be like this. However, some rule applications are truly stateful. For example, the rules accumulated facts with specific attribute values over time and then fired when a certain number was reached. These types of services would require that the workingMemory not be re-created with the receipt of each message, and disposed of after the rules have fired, but have a long-lived working memory that gets added to over time. The current JBossRulesRouter cannot support truly stateful services because it creates a new workingMemory with each message. Truly stateful interactions would require a way to identify the stateful session / working memory that a message is for, and also when to finally dispose of it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 6 months

4
6
0 / 0

[JBoss JIRA] Created: (JBESB-547) Add jbpm support to war deployment

by Kevin Conner (JIRA)

Add jbpm support to war deployment ---------------------------------- Key: JBESB-547 URL: http://jira.jboss.com/jira/browse/JBESB-547 Project: JBoss ESB Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2 Add support for jbpm into war deployment -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 6 months

2
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues March 2008