May 2008 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-1686) readme file of helloworld_tx_sql_action needs to be updated

by Jehudi Castro (JIRA)

readme file of helloworld_tx_sql_action needs to be updated ----------------------------------------------------------- Key: JBESB-1686 URL: http://jira.jboss.com/jira/browse/JBESB-1686 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2.1 CP2 Reporter: Jehudi Castro Priority: Minor As Len says: http://jira.jboss.com/jira/browse/SOA-513#action_12408977 the message (BAD READ ON DATA) and also the RuntimeException is alarming, the readme file should alert about that. -- 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
2
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, 10 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, 10 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-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-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

17 years, 10 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

17 years, 10 months

3
5
0 / 0

[JBoss JIRA] Created: (JBESB-1714) helloworld_sql_action QS has a missing dependency on the database initialiser MBean

by Kevin Conner (JIRA)

helloworld_sql_action QS has a missing dependency on the database initialiser MBean ----------------------------------------------------------------------------------- Key: JBESB-1714 URL: http://jira.jboss.com/jira/browse/JBESB-1714 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 Reporter: Kevin Conner Fix For: 4.4 The helloworld_sal_action has a race on deployment, leasing to the following output 15:30:12,330 ERROR [SimpleDataSource] Could not create connection for jdbc:hsqldb:hsql://localhost:1703 - datasource may be unavailable. See server log for details. There are a couple of issues - the datasource is explicitly copied into the deploy directory, whereas it should be included within the ear file - there is no dependency on the database initialiser MBean -- 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
2
0 / 0

[JBoss JIRA] Created: (JBESB-1682) Fix helloworld_file_notifier QS

by Tom Cunningham (JIRA)

Fix helloworld_file_notifier QS ------------------------------- Key: JBESB-1682 URL: http://jira.jboss.com/jira/browse/JBESB-1682 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 CP2 Reporter: Tom Cunningham Assigned To: Tom Cunningham Fix For: 4.3 Fix the helloworld_notify_files QS so that it uses the new property substitution that was added in JBESB-1589. There's no longer any need to do the ant based token replacement in this QS. -- 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

2
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues May 2008