Bug 780094 (SOA-2462)

Summary:	It's not possible to set polling frequency on HTTP component of CamelGateway
Product:	[JBoss] JBoss Enterprise SOA Platform 5	Reporter:	Robert Balent <rbalent>
Component:	Integration	Assignee:	Kevin Conner <kevin.conner>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	5.1.0.ER3	CC:	mvecera
Target Milestone:	---
Target Release:	5.1.0 GA
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/SOA-2462
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-02-11 00:09:40 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Robert Balent 2010-10-22 16:00:13 UTC

project_key: SOA

One of Camel components is http component: http://camel.apache.org/http.html

When the http component is used in jboss-esb.xml in <from..> element, there's no way to set frequency of polling http source. Http Gateway is working, but the polling frequency is too high and it's producing a lot of messages.

On the camel webpage there's described way how to set polling frequency with timer and <to..> element, but it's not currently supported.

Comment 1 Anne-Louise Tangring 2010-10-27 19:16:27 UTC

Investigate for SOA 5.1.0

Comment 2 Kevin Conner 2010-11-01 11:01:12 UTC

Link: Added: This issue depends JBESB-3525

Comment 4 Dana Mison 2011-01-05 00:14:40 UTC

Writer: Added: dlesage

Comment 5 Robert Balent 2011-02-10 16:23:34 UTC

Verified in 5.1.0.ER9

Comment 6 David Le Sage 2011-02-11 00:06:46 UTC

Temporarily reopening to update release note info.

Comment 7 David Le Sage 2011-02-11 00:09:31 UTC

Release Notes Docs Status: Added: Documented as Resolved Issue
Release Notes Text: Added: https://issues.jboss.org/browse/JBESB-3525

There was no way to set the polling frequency for the Camel HTTP component. The default polling frequency was too high, producing a lot of messages.  Support for scheduling has now been added to the Camel Gateway.