StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POActiveMQ Request-Reply timeout
primarykey
Id
7686023
data
AcceptedAnswerId
0
AnswerCount
1
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-10-07T10:29:35.237
FavoriteCount
0
LastActivityDate
2011-11-09T10:37:14.563
LastEditDate
LastEditorUserId
0
OwnerUserId
477324
ParentId
0
PostTypeId
1
Score
0
ViewCount
1276
LastEditorDisplayName
text
Body
I have this activeMQ issue where I send a request to a remote broker (from a Camel Application). See config below: <pre><code><bean id="providerJMSConnectionFactory" class="org.apache.activemq.ActiveMQConnectionFactory"> <property name="alwaysSessionAsync" value="false"/> <property name="alwaysSyncSend" value="true"/> <property name="brokerURL"><value>${remote-broker-url}</value></property> <property name="clientID" value=""/> <property name="closeTimeout" value="150000"/> <property name="copyMessageOnSend" value="true"/> <property name="disableTimeStampsByDefault" value="false"/> <property name="dispatchAsync" value="false"/> <property name="objectMessageSerializationDefered" value="false"/> <property name="optimizeAcknowledge" value="true"/> <property name="optimizedMessageDispatch" value="true"/> <property name="password" value=""/> <property name="producerWindowSize" value="0"/> <property name="statsEnabled" value="false"/> <property name="useAsyncSend" value="false"/> <property name="useCompression" value="false"/> <property name="useRetroactiveConsumer" value="false"/> <property name="userName" value=""/> <property name="watchTopicAdvisories" value="true"/> <property name="sendTimeout" value="0"/> </bean> <bean id="aeroProviderJMSConfig" class="org.apache.camel.component.jms.JmsConfiguration"> <property name="connectionFactory" ref="providerJMSConnectionFactory"/> <property name="deliveryPersistent" value="true"/> <property name="explicitQosEnabled" value="true"/> <property name="priority" value="${jms-message-priority}"/> <property name="acceptMessagesWhileStopping" value="false"/> </bean> <bean id="providerJMS" class="org.apache.camel.component.jms.JmsComponent"> <property name="configuration" ref="providerJMSConfig"/> </bean> <osgi:camelContext xmlns="http://camel.apache.org/schema/spring" trace="true"> <endpoint id="providerEndpoint" uri="providerJMS:queue:provider?replyTo=providerResponse&requestTimeout=120000"/> <route> <from .....> <to ref="providerEndpoint"/> .... </route> </code></pre> Whenever I check the "providerResponse" queue on the remote broker, I realise the resposne message is never picked up. it remains in the message even I had asked response messages be queued in there (which was actually done). My question is, why will the Camel refuse to get this message from this queue? Note that Exchange pattern was explicitly set to InOut. I noticed it said the CorrelationID were not the same even though I check the JMSCorrelationID for the request and the response which look the same to me. Is there an alternate Selector I can use for matching JMS Request/Reply response?
Tags
<activemq><apache-camel>
Title
ActiveMQ Request-Reply timeout
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USLekkie
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.