-
Notifications
You must be signed in to change notification settings - Fork 160
/
camel.xml
217 lines (202 loc) · 12.2 KB
/
camel.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
<?xml version="1.0" encoding="utf-8"?>
<!--
Copyright (c) 2016, 2020 Eurotech and/or its affiliates and others
This program and the accompanying materials are made
available under the terms of the Eclipse Public License 2.0
which is available at https://www.eclipse.org/legal/epl-2.0/
SPDX-License-Identifier: EPL-2.0
Contributors:
Eurotech - initial API and implementation
Red Hat Inc
-->
<beans
xmlns="http://www.springframework.org/schema/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd
http://camel.apache.org/schema/spring
http://camel.apache.org/schema/spring/camel-spring-2.15.1.xsd">
<!-- Configure the ActiveMQ broker connection -->
<!-- we can use also the tcp regular connection. it should be no performance difference! -->
<bean id="kapuaConnectionFactory" class="org.apache.activemq.ActiveMQConnectionFactory" depends-on="message-broker-id">
<property name="brokerURL" value="vm://message-broker?create=false"/>
</bean>
<bean id="cachingConnectionFactory" class="org.springframework.jms.connection.CachingConnectionFactory">
<property name="targetConnectionFactory" ref="kapuaConnectionFactory"/>
</bean>
<bean id="jmsConfig" class="org.apache.camel.component.jms.JmsConfiguration">
<property name="connectionFactory" ref="cachingConnectionFactory"/>
<!-- we can remove this setting because is overwritten by the concurrent consumer on jms route -->
<property name="concurrentConsumers" value="10"/>
<property name="cacheLevelName" value="CACHE_CONSUMER"/>
</bean>
<bean id="activemq" class="org.apache.activemq.camel.component.ActiveMQComponent">
<property name="configuration" ref="jmsConfig"/>
</bean>
<!-- create connection pooling!!! -->
<!-- session filers (to bind Kapua and Shiro thread context) -->
<bean id="kapuaCamelFilter" class="org.eclipse.kapua.broker.core.converter.KapuaCamelFilter">
</bean>
<bean id="kapuaCamelDefaultRouter" class="org.eclipse.kapua.broker.core.router.CamelKapuaDefaultRouter">
</bean>
<!-- Converter -->
<!-- BEGIN DATASTORE PERSISTENCE -->
<bean id="kapuaDataConverter" class="org.eclipse.kapua.broker.core.converter.KapuaDataConverter"/>
<!-- END DATASTORE PERSISTENCE -->
<bean id="deviceManagementNotificationConverter" class="org.eclipse.kapua.broker.core.converter.DeviceManagementNotificationConverter"/>
<bean id="kapuaLifeCycleConverter" class="org.eclipse.kapua.broker.core.converter.KapuaLifeCycleConverter"/>
<!-- Consumer -->
<!-- ASSISTANTS -->
<bean id="deviceMessageListener" class="org.eclipse.kapua.broker.core.listener.DeviceMessageListener"></bean>
<!-- BEGIN DATASTORE PERSISTENCE -->
<bean id="dataStorageMessageProcessor" class="org.eclipse.kapua.broker.core.listener.DataStorageMessageProcessor"></bean>
<!-- END DATASTORE PERSISTENCE -->
<bean id="deviceManagementNotificationMessageProcessor" class="org.eclipse.kapua.broker.core.listener.DeviceManagementNotificationMessageProcessor"></bean>
<!-- ERROR -->
<bean id="errorMessageListener" class="org.eclipse.kapua.broker.core.listener.ErrorMessageListener">
</bean>
<camelContext id="camelContext" xmlns="http://camel.apache.org/schema/spring">
<!-- the beans are defined as spring bean so check if it's possible to remove the package scan at all. Remove also the endpoint annotation from the pojo endpoints and all should works. -->
<packageScan>
<package>org.ecplise.kapua</package>
<excludes>**.*Excluded*</excludes>
<includes>**.*</includes>
</packageScan>
<!-- exception/error handler -->
<!--
by default the errorHandler forward the message to a dead letter queue but in that way we lose the failure end point
deadLetterUri="activemq:queue:processedMessageWithError"
if we forward the message directly to an end point with the exchange in the signature
deadLetterUri="bean:errorMessagePojo?method=processMessage"
we have these properties evaluated (in the exchange field)
CamelFailureRouteId
CamelFailureEndpoint
CamelExceptionCaught
(others useful fields CamelMulticastIndex - CamelMessageHistory - CamelCreatedTimestamp)
-->
<errorHandler id="mainRouteMessageErrorHandler" redeliveryPolicyRef="kapuaRedeliveryPolicy"
type="DeadLetterChannel"
deadLetterUri="activemq:queue:notProcessableMessage"
useOriginalMessage="true">
</errorHandler>
<errorHandler id="messageErrorHandler" redeliveryPolicyRef="kapuaErrorRedeliveryPolicy"
type="DeadLetterChannel"
deadLetterUri="activemq:queue:notProcessableMessage"
useOriginalMessage="true">
</errorHandler>
<redeliveryPolicyProfile id="kapuaRedeliveryPolicy" maximumRedeliveries="0" redeliveryDelay="0" retryAttemptedLogLevel="WARN" logRetryAttempted="true"/>
<redeliveryPolicyProfile id="kapuaErrorRedeliveryPolicy" maximumRedeliveries="0" redeliveryDelay="0" retryAttemptedLogLevel="WARN" logRetryAttempted="true"/>
<!--
For the transaction/acknowledge mode please follow http://stackoverflow.com/questions/13498652/camel-jms-client-acknowledge-mode
Camel uses spring MessageListenerContainers.
The AbstractMessageListenerContainer, in case of CLIENT_AKNOWLEDGE mode, invokes comitIfNecessary method acknowledging message.
This happens only AFTER registered MessageListener processes message successfully (no exceptions)
Camel uses EndpointMessageListener which, eventually, invokes process method of next processor (or Producer) down the route.
As this is classic chain of responsibilities, if any processor down the route throws exception or sets exception on the Exchange,
it will be re-thrown by EndpointMessageListener preventing the AbstractMessageListener to acknowledge message.
So the camel-jms connections CONFIGURATION TESTED are:
acknowledgementModeName=CLIENT_ACKNOWLEDGE
transacted=false
-->
<route errorHandlerRef="mainRouteMessageErrorHandler" id="mainKapuaRoute">
<from uri="activemq:queue:Consumer.eurotech:mainRoutelisteners:EXACTLY_ONCE.VirtualTopic.>?asyncConsumer=false&acknowledgementModeName=CLIENT_ACKNOWLEDGE&transacted=false&concurrentConsumers=20&maxConcurrentConsumers=50"/>
<!-- handling timeout and communication exceptions in a retry queue -->
<!-- BEGIN DATASTORE PERSISTENCE -->
<onException>
<exception>org.eclipse.kapua.service.datastore.internal.mediator.DatastoreCommunicationException</exception>
<redeliveryPolicy maximumRedeliveries="0" logRetryAttempted="true" retryAttemptedLogLevel="WARN"/>
<handled>
<constant>true</constant>
</handled>
<bean ref="kapuaCamelFilter" method="bridgeError"/>
<to uri="activemq:queue:storeCommunicationException"/>
</onException>
<!-- handling configuration error -->
<onException>
<exception>org.eclipse.kapua.service.datastore.internal.mediator.ConfigurationException</exception>
<redeliveryPolicy maximumRedeliveries="0" logRetryAttempted="true" retryAttemptedLogLevel="WARN"/>
<handled>
<constant>true</constant>
</handled>
<bean ref="kapuaCamelFilter" method="bridgeError"/>
<to uri="activemq:queue:storeConfigurationException"/>
</onException>
<onException>
<exception>org.eclipse.kapua.service.datastore.internal.mediator.DatastoreException</exception>
<redeliveryPolicy maximumRedeliveries="0" logRetryAttempted="true" retryAttemptedLogLevel="WARN"/>
<handled>
<constant>true</constant>
</handled>
<bean ref="kapuaCamelFilter" method="bridgeError"/>
<to uri="activemq:queue:storeGenericException"/>
</onException>
<!-- END DATASTORE PERSISTENCE -->
<onException>
<exception>org.eclipse.kapua.KapuaException</exception>
<redeliveryPolicy maximumRedeliveries="0" logRetryAttempted="true" retryAttemptedLogLevel="WARN"/>
<handled>
<constant>true</constant>
</handled>
<bean ref="kapuaCamelFilter" method="bridgeError"/>
<to uri="activemq:queue:notProcessableMessage"/>
</onException>
<pipeline>
<doTry>
<bean ref="kapuaCamelFilter" method="bindSession"/>
<dynamicRouter>
<method ref="kapuaCamelDefaultRouter" method="defaultRoute"/>
</dynamicRouter>
<doFinally>
<bean ref="kapuaCamelFilter" method="unbindSession"/>
</doFinally>
</doTry>
</pipeline>
</route>
<!-- BEGIN DATASTORE PERSISTENCE -->
<route errorHandlerRef="messageErrorHandler" id="dataMessageCommunicationErrorRoute">
<from uri="activemq:queue:storeCommunicationException?asyncConsumer=false&acknowledgementModeName=CLIENT_ACKNOWLEDGE&transacted=false&concurrentConsumers=2&maxConcurrentConsumers=5"/>
<pipeline>
<delay>
<constant>1000</constant>
</delay>
<bean ref="kapuaCamelFilter" method="bindSession"/>
<bean ref="kapuaDataConverter" method="convertToDataOnException"/>
<to uri="bean:dataStorageMessageProcessor?method=processCommunicationErrorMessage"/>
<bean ref="kapuaCamelFilter" method="unbindSession"/>
</pipeline>
</route>
<route errorHandlerRef="messageErrorHandler" id="dataMessageConfigurationErrorRoute">
<from uri="activemq:queue:storeConfigurationException?asyncConsumer=false&acknowledgementModeName=CLIENT_ACKNOWLEDGE&transacted=false&concurrentConsumers=2&maxConcurrentConsumers=5"/>
<pipeline>
<delay>
<constant>1000</constant>
</delay>
<bean ref="kapuaCamelFilter" method="bindSession"/>
<bean ref="kapuaDataConverter" method="convertToDataOnException"/>
<to uri="bean:dataStorageMessageProcessor?method=processConfigurationErrorMessage"/>
<bean ref="kapuaCamelFilter" method="unbindSession"/>
</pipeline>
</route>
<route errorHandlerRef="messageErrorHandler" id="dataMessageGenericErrorRoute">
<from uri="activemq:queue:storeGenericException?asyncConsumer=false&acknowledgementModeName=CLIENT_ACKNOWLEDGE&transacted=false&concurrentConsumers=2&maxConcurrentConsumers=5"/>
<pipeline>
<delay>
<constant>1000</constant>
</delay>
<bean ref="kapuaCamelFilter" method="bindSession"/>
<bean ref="kapuaDataConverter" method="convertToDataOnException"/>
<to uri="bean:dataStorageMessageProcessor?method=processGenericErrorMessage"/>
<bean ref="kapuaCamelFilter" method="unbindSession"/>
</pipeline>
</route>
<!-- END DATASTORE PERSISTENCE -->
<route id="notProcessableMessage">
<from uri="activemq:queue:notProcessableMessage?asyncConsumer=false&acknowledgementModeName=CLIENT_ACKNOWLEDGE&transacted=false&concurrentConsumers=2&maxConcurrentConsumers=5"/>
<pipeline>
<bean ref="kapuaCamelFilter" method="bindSession"/>
<to uri="bean:errorMessageListener?method=processMessage"/>
<bean ref="kapuaCamelFilter" method="unbindSession"/>
</pipeline>
</route>
</camelContext>
</beans>