June 2008 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-1807) The InVM should support message delivery "byReference" or "byValue"

by Tom Fennelly (JIRA)

The InVM should support message delivery "byReference" or "byValue" ------------------------------------------------------------------- Key: JBESB-1807 URL: http://jira.jboss.com/jira/browse/JBESB-1807 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.3 Reporter: Tom Fennelly Fix For: 4.4 At the moment, the InVM courier delivers messages by reference. There should be an option to deliver by value too because if the message is multicast to multiple services (all over InVM), they could all be modifying the same message instance. In fact... "by-value" should probably be the default (for safety reasons). -- 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

17 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-1343) Integrate JBossWS test suite with the ESB

by Heiko Braun (JIRA)

Integrate JBossWS test suite with the ESB ----------------------------------------- Key: JBESB-1343 URL: http://jira.jboss.com/jira/browse/JBESB-1343 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Testing Reporter: Heiko Braun Assigned To: Heiko Braun Fix For: 4.3 We need to execute the jbossws smoke tests (jax-ws baseline) against the ESB. -- 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

17 years, 9 months

3
2
0 / 0

[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

17 years, 9 months

4
24
0 / 0

[JBoss JIRA] Created: (JBESB-1638) Adapters / Actions documentation missing for JMSRouter, others?

by David Smiley (JIRA)

Adapters / Actions documentation missing for JMSRouter, others? --------------------------------------------------------------- Key: JBESB-1638 URL: http://jira.jboss.com/jira/browse/JBESB-1638 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Reporter: David Smiley To see what actions JBoss ESB came with out of the box, I looked at the adapters pdf. This document apparently only has a subset of them. JMSRouter, for one, is missing. I suggest that as these are developed, they get added to this document (and perhaps somewhere on the wiki) ASAP so this step is not forgotten. If people don't know about them, it's almost like they don't even exist. -- 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

17 years, 10 months

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-1844) Document RuleService

by Daniel Bevenius (JIRA)

Document RuleService -------------------- Key: JBESB-1844 URL: http://jira.jboss.com/jira/browse/JBESB-1844 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Reporter: Daniel Bevenius Assigned To: Daniel Bevenius Fix For: 4.4 -- 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

17 years, 10 months

1
5
0 / 0

[JBoss JIRA] Created: (JBESB-1783) Update ContentBasedRouting documentation

by Kevin Conner (JIRA)

Update ContentBasedRouting documentation ---------------------------------------- Key: JBESB-1783 URL: http://jira.jboss.com/jira/browse/JBESB-1783 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.3 Reporter: Kevin Conner Fix For: 4.4 JBESB-841 changed the CBR configuration (incompatibly) but the documentation was not updated to reflect the new configuration. We need to update the documentation to show the correct configuration. -- 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

17 years, 10 months

3
3
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

17 years, 10 months

3
5
0 / 0

[JBoss JIRA] Created: (JBESB-1795) SOAPClient: Make it possible to override the endpoint address defined in the target WSDL

by Tom Fennelly (JIRA)

SOAPClient: Make it possible to override the endpoint address defined in the target WSDL ---------------------------------------------------------------------------------------- Key: JBESB-1795 URL: http://jira.jboss.com/jira/browse/JBESB-1795 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.2.1 CP3, 4.3, 4.2.1 TP-FP1 Reporter: Tom Fennelly Fix For: 4.4 -- 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

17 years, 10 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-1850) Ship the messaging schema DDL rather than relying upon auto creation at runtime.

by chris alfonso (JIRA)

Ship the messaging schema DDL rather than relying upon auto creation at runtime. -------------------------------------------------------------------------------- Key: JBESB-1850 URL: http://jira.jboss.com/jira/browse/JBESB-1850 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Deployment Affects Versions: 4.3 Environment: All supported platforms Reporter: chris alfonso The messaging database schema is auto created at runtime, and only exists as a file in xml format. This is problematic in the case the user for runtime connections does not have appropriate create privileges. The request is to prepare the messaging DB schema for the major RDBMs vendors in a DDL file that can be shipped with the messaging package. -- 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

17 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-1849) bpm_orchestration3 quickstart not acting as documented

by Lukas Petrovicky (JIRA)

bpm_orchestration3 quickstart not acting as documented ------------------------------------------------------ Key: JBESB-1849 URL: http://jira.jboss.com/jira/browse/JBESB-1849 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 CP4 Reporter: Lukas Petrovicky readme.txt for the quickstart says that it should result in the following on the server console: [SetupSignal] -------------------------------- [SetupSignal] jbpmTokenId: 1 [SetupSignal] Body: Hello Signal [SetupSignal] -------------------------------- [STDOUT] ** Begin Service 2 ** [STDOUT] In: Hello Signal [STDOUT] Out: Hello Signal 'Service 2' [STDOUT] ** End Service 2 ** [STDOUT] ** Begin Service 3 ** [STDOUT] In: Hello Signal 'Service 2' [STDOUT] Out: Hello Signal 'Service 2' 'Service 3' [STDOUT] ** End Service 3 ** [SetupSignal] -------------------------------- [SetupSignal] jbpmTokenId: 1 [SetupSignal] Body: Hello Signal [SetupSignal] -------------------------------- However, it only results in: [SetupSignal] -------------------------------- [SetupSignal] jbpmTokenId: 1 [SetupSignal] Body: Hello Signal [SetupSignal] -------------------------------- [STDOUT] ** Begin Service 2 ** [STDOUT] In: Hello Signal [STDOUT] Out: Hello Signal 'Service 2' [STDOUT] ** End Service 2 ** [STDOUT] ** Begin Service 3 ** [STDOUT] In: Hello Signal 'Service 2' [STDOUT] Out: Hello Signal 'Service 2' 'Service 3' [STDOUT] ** End Service 3 ** We checked the jboss-esb.xml and found no way that it could ever end as documented, so I suppose this is a documentation issue. Other than this, the quickstart runs fine. -- 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

17 years, 10 months

1
1
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues June 2008