February 2010 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-2849) Add caching of JAXR connections

by Kevin Conner (JIRA)

Add caching of JAXR connections ------------------------------- Key: JBESB-2849 URL: https://jira.jboss.org/jira/browse/JBESB-2849 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Registry and Repository Affects Versions: 4.6 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.7 These are heavyweight objects, especially when integrating juddi v3. We should be caching these to reduce the impact. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
6
0 / 0

[JBoss JIRA] Created: (JBESB-3009) GettingStarted.odt -> Maven/JDocbook project contribution

by Darrin Mison (JIRA)

GettingStarted.odt -> Maven/JDocbook project contribution --------------------------------------------------------- Key: JBESB-3009 URL: https://jira.jboss.org/jira/browse/JBESB-3009 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Reporter: Darrin Mison Attachments: Getting_Started_Guide.zip This is a conversion of existing content of the trunk GettingStarted.odt to docbook XML with a Maven pom.xml to build it. source: https://svn.jboss.org/repos/labs/labs/jbossesb/trunk/product/docs/Getting... Revision 30054 Let me know your thoughts and I can continue on with the other documents. Note that the content is word for word, only a few obvious spelling mistakes were corrected. The Author list is based on the SVN log for the file The Legal Notice is a slightly massaged version from the .odt and would need to be verified. The file layout is also compatible with Publican for easy integration into SOA Platform documentation. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
4
0 / 0

[JBoss JIRA] Created: (JBESB-880) The ESB is blocked under heavy load when using JMS

by Jiri Pechanec (JIRA)

The ESB is blocked under heavy load when using JMS -------------------------------------------------- Key: JBESB-880 URL: http://jira.jboss.com/jira/browse/JBESB-880 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta, Transports Affects Versions: 4.2 Milestone Release 3 Environment: RHEL 5, PostgreSQL Reporter: Jiri Pechanec Assigned To: Mark Little Priority: Blocker When the ESB is forced to process a huge batch of messages then it blocks completely. The ESB configuration was just one service with one listener and gateway. Both gateway and listener are using JMS. The testing was executed twice using one and then four threads per listener and gateway. The service contains two actions that serves only for message counting. If you try to send 10000 messages sized around 20 KB it will probaly block after few minutes of processing. The ESB do not respond to TERM signal and even JMX console is not available. The only solution is to kill process violently. With the smaller messages the block does not happend or happends after bigger amount of messages. The sender is generating following log messages [Timer-1][BisocketServerInvoker] org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ControlMonitorTimerTask@201d592a: detected failure on control connection Thread[control: Socket[addr=/10.34.34.47,port=2660,localport=51957],5,main]: requesting new control connection We can not exclude problem in JBoss Messaging itself but when we tried to use plain JMS without ESB we were able to send/receive 300000 messages without any problem. Moreover the more messages were processed the longer time it takes for the next batch to be processed. -- 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

14 years, 2 months

7
33
0 / 0

[JBoss JIRA] Created: (JBESB-1900) Current system date in sql-provider where-condition

by Raghavan TV (JIRA)

Current system date in sql-provider where-condition --------------------------------------------------- Key: JBESB-1900 URL: https://jira.jboss.org/jira/browse/JBESB-1900 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Environment: JBoss ESB 4.3GA + JBoss 4.2.2 or JBOss 4.0.0 + Oracle 10g + Windows Xp or HP-UX 11.0 Reporter: Raghavan TV I have a simple table where I store my Orders. e.g. DB - Oracle 10g Table ORDER_QUEUE ---------------------------------------- ORDER_ID NUMBER(5) FIELD1 VARCHAR2(10) FIELD2 VARCHAR2(10) ORDER_DATE DATE ESB_STATUS VARCHAR2(1) TIMESTAMP_COL DATE ----------------------------------------- My requirement is to process only those records where ORDER_DATE = Current System Date that hosts my AppServer Am trying to work with the sample provided. I updated the where condition as follows and it works fine. <sql-bus busid="helloSQLChannel" > <sql-message-filter tablename="ORDER_QUEUE" status-column="ESB_STATUS" where-condition="TO_DATE(ORDER_DATE,'DD-MON-YYYY') = (SELECT TO_DATE(SYSDATE,'DD-MON-YYYY') FROM DUAL)" message-column="message" message-id-column="ORDER_ID" insert-timestamp-column="TIMESTAMP_COL" /> </sql-bus> [where-condition="TO_CHAR(ORDER_DATE,'DD-MON-YYYY') = (SELECT TO_CHAR(SYSDATE,'DD-MON-YYYY') FROM DUAL)"] But the query is more specific to a Oracle DB. If I decide to change the provider in the future, then this filter will fail! Also if the DB and AppServer are in different TZ, we have a problem Is there some other workaround to use the AppServer Date in the where-condition ? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-3085) Loading of DRL Files in ContentBasedRouter

by Fernando Ribeiro (JIRA)

Loading of DRL Files in ContentBasedRouter ------------------------------------------ Key: JBESB-3085 URL: https://jira.jboss.org/jira/browse/JBESB-3085 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Content Based Routing Affects Versions: 4.7 Reporter: Fernando Ribeiro Unlike XsltAction, for example, ContentBasedRouter tries to find the template file in the file system before loading it from the classpath. // Get the properties file stream... if (ruleSetFile.exists()) { try { ruleStream = new FileInputStream(ruleSetFile); } catch (FileNotFoundException e) { throw new MessageRouterException("Unable to open rule properties file '" + ruleSetFile.getAbsolutePath() + "'.", e); } lastLoaded = ruleSetFile.lastModified(); } else { ruleStream = ClassUtil.getResourceAsStream(ruleSetConfig, AbstractPropertyRulesRouter.class); } (from AbstractPropertyRulesRouter.java) It is an easy miss because it is the only parameter that can't begin with "/". -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

3
13
0 / 0

[JBoss JIRA] Created: (JBESB-776) Need a Maven ESB Archetype

by Tom Cunningham (JIRA)

Need a Maven ESB Archetype -------------------------- Key: JBESB-776 URL: http://jira.jboss.com/jira/browse/JBESB-776 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Tooling Reporter: Tom Cunningham Assigned To: Tom Cunningham Fix For: 5.0 We have a maven task which compiles an .esb package. We should also have a maven "archetype" which creates the preferred project layout for Maven. See for details on archetypes http://maven.apache.org/plugins/maven-archetype-plugin/ -- 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

14 years, 3 months

4
3
0 / 0

[JBoss JIRA] Created: (JBESB-3019) Warning during deployment of webservice_proxy_* quickstarts

by Jiri Pechanec (JIRA)

Warning during deployment of webservice_proxy_* quickstarts ----------------------------------------------------------- Key: JBESB-3019 URL: https://jira.jboss.org/jira/browse/JBESB-3019 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.7 Environment: SOA-P 5 CR4 Reporter: Jiri Pechanec Priority: Minor When a qucikstart with webservice proxy is deployed than log generates warning message 08:01:36,522 WARNING [config] Unable to process deployment descriptor for context '/Quickstart_webservice_proxy_basic' -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

5
16
0 / 0

[JBoss JIRA] Created: (JBESB-2444) Modify JAXRRegistryImpl to coalesce multiple registry object creations when discovered

by Kevin Conner (JIRA)

Modify JAXRRegistryImpl to coalesce multiple registry object creations when discovered -------------------------------------------------------------------------------------- Key: JBESB-2444 URL: https://jira.jboss.org/jira/browse/JBESB-2444 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Registry and Repository Affects Versions: 4.5 Reporter: Kevin Conner Fix For: 4.6 It is possible for the same registry objects to be created concurrently, especially with multiple VMs, leading to certain registry objects being created multiple times when only one occurrence is expected. We need to identify those objects which should be single instances and then have the JAXRRegistryImpl check, then coalesce, any discovered. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

1
4
0 / 0

[JBoss JIRA] Created: (JBESB-2902) upgrade messaging to latest stable

by Tom Eicher (JIRA)

upgrade messaging to latest stable ---------------------------------- Key: JBESB-2902 URL: https://jira.jboss.org/jira/browse/JBESB-2902 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.6 Reporter: Tom Eicher ESB 4.6 GA still comes with jboss-messaging.jar : > Implementation-Version: 1.4.0.SP3 (build: CVSTag=JBossMessaging_1_4_0_SP3 date=200712131418) Please upgrade to latest stable messaging version. Also: Please include version information in jar name, i.e. /jbossesb-server-4.6/server/default/lib/jboss-messaging-140sp3.jar instead of /jbossesb-server-4.6/server/default/lib/jboss-messaging.jar Thanks, Tom. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

2
12
0 / 0

[JBoss JIRA] Created: (JBESB-2604) Document registry interceptors

by Aaron Pestel (JIRA)

Document registry interceptors ------------------------------ Key: JBESB-2604 URL: https://jira.jboss.org/jira/browse/JBESB-2604 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Documentation Environment: SOA-P 4.3 SP1 Reporter: Aaron Pestel Priority: Minor This is a request to document the two known registry interceptors: org.jboss.internal.soa.esb.services.registry.InVMRegistryInterceptor and org.jboss.internal.soa.esb.services.registry.CachingRegistryInterceptor The InVMRegistryInterceptor is listed in the services guide, section 2.1 and 3.2: http://www.redhat.com/docs/en-US/JBoss_SOA_Platform/4.3.CP01/html-single/... In section 2.1, it shows an extract of the registry portion of the jbossesb-properties.xml - which includes InVMRegistryInterceptor, and then goes on to describe each property, but neglects to describe the org.jboss.soa.esb.registry.interceptors property where InVMRegistryInterceptor is set. I am requesting a description in section 2.1 of the org.jboss.soa.esb.registry.interceptors property to include: 1.) format for adding 1 or many interceptors (using ", ") 2.) description of two currently available interceptors (InVMRegistryInterceptor and CachingRegistryInterceptor) 3.) description of when it would make sense or not make sense to use these two interceptors Thanks! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

2
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues February 2010