Some news on that: in the meantime, we have switched to only using static
bridges in our project for connection of the mobile brokers to the back
office. Is much more stable now.
However, there is still some problem which shows up now and then: sometimes
the back office broker "forgets" to start
Hi,
sorry, but the issue was a different one. It was my misunderstanding of the
idleTimeout property. Is doesn't timeout a connection which is used from the
pool, but the connection which the pool opens to the broker. My settings
were such that the timeout was too short for the connection pool to
Hi Mike,
good idea. I still have to do some testing, but on a first glance, I saw
that in the JUnit test, they never close a created connection.
I thought that after getting a connection from the PooledConnectionFactory
with connection = pooledConnectionFactory.createConnection() and having
Hi Tim,
thanks for clarifying this. I may have expressed it not precisely in my
answer: the problem exactly was that for the broker1_broker2_simplex bridge,
when sending messages to a queue which is initially only known by broker 2
(because only there a consumer exists for this queue), sometimes
Hi Mike,
thanks for the answer. Of course I have checked this . It says: "A JMS
provider which pools Connection, Session and MessageProducer instances so it
can be used with tools like Camel and Spring's JmsTemplate and
MessagListenerContainer. Connections, sessions and producers are returned to
Hello,
I'm just starting using the PooledConnectionFactory. Before calling the
start() method, the idleTimeout (3 ms), the maxConnections (10) and the
maximumActiveSessionPerConnection (500) are set.
I would have expected that on startup, 10 connections are opened to the
broker
Hi Jakub,
thanks for the explanation! I was not aware that this even overrides the
duplex="false" setting. But thinking about it again, it makes sense, since
the duplex setting is relevant for the sync direction of consumers, not for
the push direction / filtering of messages.
So no other way
Hello,
I have a configuration where one broker builds network connections to other
brokers. Some of the queues have to be two-way (duplex="true") and some have
to be one-way (duplex="false"). For the network connector configuration, see
below. The ActiveMQ version is 5.14.5.
The goal is that
Hi Tim,
what you propose is difficult to test, since the HA proxy can only deliver
the SSL ports (it routes based upon SNI, so SSL is mandatory for the
routing). It won't work with plain tcp ports.
However, if I still use SSL but directly define mapped ports for both
brokers in the network
Hi,
I have a configuration where a broker needs to make a network connection to
brokers behind a load balancer (HAProxy) which make a master-slave
configuration. The HAProxy does the routing based upon the SSL SNI, and does
the SSL termination.
So the uri for the network connector looks like
Saw it again.
- The backoffice broker had shut down the connection (Channel was inactive
for too (>3) long).
- The mobile broker logged "Transport failed, not attempting to
automatically reconnect; java.io.EOFException" and "bridge to stopped"
- One second later, the mobile broker tries
I'll check this next time the issue shows up. But I'm pretty sure that if the
connection is there on TCP level, it can be to nothing else than one of the
two backoffice brokers, since only these are defined in the connection URI
for the network connection. But anyways a good idea to check whether
Hello,
found the right command: activemq:query | grep -A 10 -B 10
networkConnectors.
And the problem occurred again, so I could check this. The network connector
is present on the mobile broker, but the web console of the backoffice
broker doesn't show a connection.
Regards,
Jochen
--
View
Hi Tim,
how can I see the outbound connection on the mobile broker? I only have the
activemq commands in the karaf shell, and neither activemq:bstat nore
activemq:dstat show the connections. On the backoffice broker, I'm not sure,
but I think that no connection was shown (I will have to wait
Hi Tim,
first the respectve lines from karaf.log (the mobile broker is running in
Karaf). You can see the successful connection at 04:46:01,955. Then, bit
before 05:37:11, the mobile radio connection obviously was lost (I can also
see this from a process which monitors the ppp connection -
Hi,
in the meantime, I have digged bit deeper into that. I can see from the
logs, that when the mobile radio network connectivity breaks, after 30
seconds both brokers close the connection and the network broker bridge is
stopped. Then the network connector tries to reconnect. Most of the time,
That's it. Thanks!
Sorry to not have checked the ActiveMQ user forum .
Do you know whether there is a Jira for ActiveMQ for this topic? For 5.14.1
it might have been bit tight - maybe with the next release.
Regards,
Jochen
--
View this message in context:
Hello,
I have two back office brokers connected via a broker network, and multiple
moving devices with their own broker, which connect to the backoffice
brokers via a network connection in failover mode (secured via ssl -
Hello,
I have a target with ActiveMQ 5.11.1 running in Karaf in an environment
where sudden power-offs can happen. In general, the system restarts without
problems. However, now and then ActiveMQ seems to hang. The logs indicate
the message broker starting correctly, but other OSGi bundles fail
Looks like the maxReconnectAttempts=0 helped me. Thanks, Tim!
When switching to 5.13, I'll check again if there are some problems
remaining - currently it seems to work fine.
Best Regards,
Jochen
--
View this message in context:
Hello,
I've got a very similar problem with ActiveMQ 5.12.0 when building a broker
network via a SSL connector. I have set
networkConnector
21 matches
Mail list logo
