1) consumer -> broker - inactivity monitor closing connections ?
for this connection loss we will apply patch which you provided http
broken. this answer we got.
2) while configuring n/w connector do we need to provide any inactivity
parameters ? because I
have not provided due to
hello
thank you for the link on inactivity monitor, we will apply that patch and
we will verify.
I have attached link also https://pastebin.com/M9u7TJZB from this I
understand that network connector is not closing connection b/w host1 &
host2.
do we need to provide specific parameters while
Thank you, actually we searched but not found any bug fix on inactivity
monitor. there is only one bug which is
https://issues.apache.org/jira/browse/AMQ-6877 on http connector with queue
prefetch 0. this we applied and queue-prefetch is working fine.
can you please help us. because in our case
Hello
We have broker -> client environment. we have set 5 minutes as inactivity
monitor timeout. using 5.12.3 version of activemq [ service mix 5.6.0 ]
my question is : we have set connecttimeout to 5 minutes and also keepalive
as true, still always after 5 minutes channel is closed by
Thank you Tim
for this IOException, we have not observed any reasonable exceptions on
broker [ producer ] side.
attached thread dump jstack.out. Can you please look into and help.
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
it seems blockingQueue is not actually ACTiveMQDestination, just it is java,
so any other suggestions ?
at that state we are not able to connect to cloud broker , on client side we
are getting :
Caused by: java.io.EOFException
at java.io.DataInputStream.readInt(Unknown Source)[:1.8.0_60]
thank you Tim,
>>Caused by: java.io.IOException: Failed to perform GET on: https://URL
>>Reason: null
>>at
org.apache.activemq.util.IOExceptionSupport.create(IOExceptionSupport.java:33)[120:org.apache.activemq.activemq-osgi:5.12.3]
>>at
>Is your client using a failover transport? If so, it's the failover
>transport that's re-establishing the connection.
we are not using any failover transport
I see you're using the https transport. Does it work if you connect with
the tcp transport instead? It's possible that there's some
Hello,
we are facing similar problem Consumer is closed. and we are setting below
parameters on DMLC
listenerContainer.setIdleConsumerLimit(idleConsumerLimit);
listenerContainer.setReceiveTimeout(defaultReceiveTimeout);
listenerContainer.setRecoveryInterval(defaultRecoveryInterval);
so the cache
when we are looking into Server broker, it has many temperary queues around
more than 2000. So we have removed one network peer.
A->B
B->A
now, after some hours tmp-queues are around 2 digits only. we have applied
below patch :
https://issues.apache.org/jira/browse/AMQ-6262
still after some hours
following error messages we are seeing on client side :
2018-03-08 18:38:24,248 41319597 [Camel (jcsCoreCamelContext) thread #12 -
JmsConsumer[uniquequename]]
(org.apache.activemq.activemq-osgi:org.apache.activemq.jms.pool.PooledSession:126)
WARN - Caught exception trying close() when putting
we are using activemq : 5.12.3
apache camel : 2.16.2
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Hi
we are using mesh n/w connectors A,B,C. and we have two consumers. upto some
hours system is working fine, after that when we are checking messages those
are generated by camel with correlationId as null
ActiveMQObjectMessage {commandId = 4, responseRequired = true, messageId =
Thank you so much for your help & quick response. We are planning to remove
this addDynamicallyIncludedDestination and even we dont exclude
Advisory.ActiveMQ.*.
Thank you Tim
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Tim
if we remove addDynamicallyIncludedDestination, then not only queue, even
topic messages also replicated to another broker
am I right ? this is the only reason we just want to restrict to some
queues.
we dont want any of ActiveMq.Advisory. topics to be replicated. bcz we dont
know what
thank you for response,
I got it from the links which you provided. Thank you so much
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Hello Team
we are connecting n/w connectors
A->B
A->C
B->C
B->A
C->B
C->A
same broker xml file using to create jcs-brokers, however providing
different network connector name to each network connector so that we dont
get invalidclientid exception.
n/w connector name : A-C, A-B, B-C, B-A,
Can anybody please provide reply for this. What pattern we need to use ?
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Hello
We are having similar problem in request/reply pattern with temp queue. we
are not getting response when we are using addDynamicallyIncludedDestination
on networkconnector with some queues.
so can anybody suggest what pattern to use if we are using in java code. for
example :
Please refer this link also :
http://activemq.2283324.n4.nabble.com/Reply-message-not-forwarded-across-temporary-bridged-destination-td4688578.html
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Hello
we migrated activemq from < 5.5 version to 5.12.3. below is code snippet for
to create n/w connector
NetworkConnector networkConnector = new DiscoveryNetworkConnector(uri);
networkConnector.addDynamicallyIncludedDestination(...)
networkConnector.addExcludedDestination(...)
we are using
Thank you Tim,
activemq version 5.12.3
it is our own code. dynamically using UI we are creating n/w connector. at
that time below code execute.
code snippet :
NetworkConnector networkConnector = new DiscoveryNetworkConnector(uri);
networkConnector.setNetworkTTL(this.networkTTL);
Hello
we are creating network connector b/w
A->B
A->C
B->C
B->A
C->B
C->A
using networkttl=10.
Sample Network connector creation :
NetworkConnector networkConnector = new DiscoveryNetworkConnector(uri);
networkConnector.setNetworkTTL(this.networkTTL);
We are using n/w connectors between 3 brokers
is
A->B
A->C
B->A
B->C
C->A
C->B
also we are using synchronous request and reply pattern using camel to send
and receive message in temp queue.
we have question is it good to use networkTTL = 2 in above configuration ?
will it work properly or
is
24 matches
Mail list logo
