InOut message over JMS, across firewall

[bryan <br...@gmail.com>]

I have a simple network topology. I have an ActiveMQ broker outside a
firewall, and a camel client behind a NAT that connects to the broker via
TCP. This works fine if all messages are of type InOnly. I can send messages
from broker to client, and I can send messages from client to broker, all
over the single outbound TCP connection from client to broker.

I am having trouble when I use the InOut exchange pattern. Basically the
message does not get transferred and the exchange times out when I use InOut
exchanges. There is nothing in the logs indicating any connectivity issues.
The client appears to queue the message OK but then times out waiting for a
response.

The server never receives the message from the client. The server does,
however, initialize the temp reply queue and some advisory queues and
topics, so the client and server are attempting a handshake of some sort. I
tried defining my own replyTo queue rather than using the Camel-generated
temp queue, but this did nothing to fix the problem.

Does anyone know why InOut exchanges do not work across a NAT, but InOnly
exchanges can?


--
View this message in context: http://camel.465427.n5.nabble.com/InOut-message-over-JMS-across-firewall-tp3408704p3408704.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: InOut message over JMS, across firewall

[bryan <br...@gmail.com>]

I resolved this issue. It turned out that when using the InOut exchange
pattern with JMS, the message expiration time is set. With InOnly it is not
set. It happened that my two test machines did not have clocks that were in
sync, so the messages were being treated as expired with InOut, but not with
InOnly.

--
View this message in context: http://camel.465427.n5.nabble.com/InOut-message-over-JMS-across-firewall-tp3408704p3408906.html
Sent from the Camel - Users mailing list archive at Nabble.com.