Hi,, Did you find any solution to the issue mentioned? Kindly let me know if
you have.
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
On Mon, Apr 2, 2018 at 10:35 PM, Rajesh Malla wrote:
> 1) consumer -> broker - inactivity monitor closing connections ?
> for this connection loss we will apply patch which you provided http
> broken. this answer we got.
>
OK, perfect.
> 2) while configuring n/w conne
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
On Mon, Apr 2, 2018, 11:01 AM Rajesh Malla wrote:
> 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 c
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 w
On Sun, Apr 1, 2018, 11:05 PM Rajesh Malla wrote:
> 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
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
ll or something is capturing the keepAlive commands.
On 04/01/2018 12:02 PM, Rajesh Malla wrote:
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
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
Hi
We have setup two brokers in network of brokers config in version 5.15.0
Its a simple config that has:
2017-09-27 13:08:52,029 | INFO | Waited 2.000 seconds for ExecutorService:
java.util.concurrent.ThreadPoolExecutor@1d225cd9[Shutting down,
In a client application, ActiveMQ is just one JAR (or several) that's part
of a much larger whole. The client application establishes how logging will
be done, and ActiveMQ plays by those rules. Since you're seeing ActiveMQ
content in the client logs, this is already working, and your job is to
fin
Hello,
I searched in the documentation and archives how to change logging for
client applications but any my attempt doesn't work.
I use activemq 5.14.3 and my IDE is eclipse neon.
The problem is that I would like to remove debug info produced by:
InactivityMonitor Worker, WriteCheckTimer an
Hello,
I searched in the documentation and archives how to change logging for
client applications but any my attempt doesn't work.
I use activemq 5.14.3 and my IDE is eclipse neon.
The problem is that I would like to remove debug info produced by:
InactivityMonitor Worker, WriteCheckTimer an
side.
"xbhanu
[via ActiveMQ]" <ml-node+s2283324n4675926...@n4.nabble.com>
01/02/2014 05:17 PM
To
Prashant
Kumar41/India/IBM@IBMIN,
cc
Subject
Re:
Inactivity Monitor
So, I were to increase it this would require me to specify
maxInactivityDuration at bro
seconds ?
Thanks,
Bhanu
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Inactivity-Monitor-tp4672969p4675926.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
that would disable it, by the same logic that calculates the minimum
both ends would see 0 and disable.
On 18 October 2013 08:05, Prashant wrote:
> If we disable Inactivity Monitor from broker side by adding
> maxInactivityMonitor=0 parameter in broker's transport connector URL
If we disable Inactivity Monitor from broker side by adding
maxInactivityMonitor=0 parameter in broker's transport connector URL but it
is enabled from client side using their connection url, what would be the
effect?
We know that if duration is set differently on both sides of connection,
l
time inactivity monitor should check for
clients and it should disconnect all clients which are not sending
pingRequest. Source: http://activemq.apache.org/mqtt.html . But this is not
happening as Broker is holding connection for more time .Inactivity monitor
is closing the connection sometimes in
If a client or broker abnormally dies, without the inactivity monitor
you are dependent on OS level timeouts to notice the absence of
network activity. So OS level tcp/ip settings for read timeouts etc.
Essentially you get half closed sockets so the other end is in the
dark. But the OS has options
investigating the possibility of disabling the Inactivity
Monitor however I would like to know;
1. If there are any adverse affects on the broker or client?
2. What happens if the client terminates the connection abnormally? how does
the broker know the client is no longer present?
Any input and advice
http://issues.apache.org/activemq/browse/CAMEL-1751
Disregard this section. It was a double paste ..
> class="com.inwk.jobtemplate.server.ReturnedQueueRouteBuilder"
> lazy-init="false" init-method="init" destroy-method="stop">
>
>
>
> class="com.inwk.jobtemplate.server.ReturnedQuotesProce
On Tue, Jun 23, 2009 at 8:34 AM, David Durham wrote:
> On Tue, Jun 23, 2009 at 4:35 AM, Gary Tully wrote:
>> I wonder if this is the result of code registered with a shutdown hook and
>> at shutdown some of the required classes are not longer available.
>> One way to check is to have the broker not
On Tue, Jun 23, 2009 at 4:35 AM, Gary Tully wrote:
> I wonder if this is the result of code registered with a shutdown hook and
> at shutdown some of the required classes are not longer available.
> One way to check is to have the broker not register any shutdown hook.
>
> Set the 'useShutdownHook'
n your
xml configuration.
2009/6/22 David Durham
> >> I've got a simple ActiveMQ client running inside Tomcat. When I
> >> shutdown Tomcat I get an exception from the "Inactivity Monitor Write
> >> Check" thread. My question is has anyone seen this issue
>> I've got a simple ActiveMQ client running inside Tomcat. When I
>> shutdown Tomcat I get an exception from the "Inactivity Monitor Write
>> Check" thread. My question is has anyone seen this issue and have a
>> fix for it? I've tried making
On Mon, Jun 22, 2009 at 2:40 PM, David Durham wrote:
> Hi all,
>
> I've got a simple ActiveMQ client running inside Tomcat. When I
> shutdown Tomcat I get an exception from the "Inactivity Monitor Write
> Check" thread. My question is has anyone seen this issue
Hi all,
I've got a simple ActiveMQ client running inside Tomcat. When I
shutdown Tomcat I get an exception from the "Inactivity Monitor Write
Check" thread. My question is has anyone seen this issue and have a
fix for it? I've tried making sure that I call the stop() metho
port.doRun(TcpTransport.java:184)
> at
> org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:172)
> at java.lang.Thread.run(Unknown Source)
>
>
> I don't know what is the problem.
> Please help me.
> Thanks in advance.
>
>
--
View this message in context:
http://www.nabble.com/Inactivity-monitor-exception-is-closing-connection.-tp15404620s2354p16116806.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Is this still planned? Does anyone have an idea when it may happen?
rajdavies wrote:
>
>
> [] We should be coming out with a 5.0.1
> real soon that will include the fix
>
>
>
>
--
View this message in context:
http://www.nabble.com/Inactivity-moni
? I don't really want to go to
production with a snapshot version. If it's a simple fix, do you
think it's
possible to backport it to the 5.0 branch?
Regards,
Cedric.
---
Could you try a snaphot of ActiveMQ 5.1 ?
thanks,
Rob
--
View this message in context:
http://www.nabb
with a snapshot version. If it's a simple fix, do you think it's
possible to backport it to the 5.0 branch?
Regards,
Cedric.
---
Could you try a snaphot of ActiveMQ 5.1 ?
thanks,
Rob
--
View this message in context:
http://www.nabble.com/Inactivity-monitor-except
; at
>>> org
>>> .apache
>>> .activemq
>>> .transport.TransportFilter.onException(TransportFilter.java:99)
>>> at
>>> org
>>> .apache
>>> .activemq
>>> .transport.TransportFilter.onException(
ccell/10.0.55.197:61616
... 4 more
Anybody have a workaround? I am having problems using this version
because
it just kicks off all of my services after awhile!
--
View this message in context:
http://www.nabble.com/Inactivity-monitor-exception-is-closing-connection.-tp15404620s2354p15622035
t; at
>> > org.apache.activemq.transport.WireFormatNegotiator.onException(
>> WireFormatNegotiator.java:143)
>> > at
>> > org.apache.activemq.transport.InactivityMonitor.onException(
>> InactivityMonitor.java:204)
>> > at
>>
ivityMonitor$4.run(
> InactivityMonitor.java:142)
> > at
> > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(
> ThreadPoolExecutor.java:650)
> > at
> > java.util.concurrent.ThreadPoolExecutor$Worker.run(
> ThreadPoolExecutor.java:675)
> >
for too long: puccell/10.0.55.197:61616
> ... 4 more
>
> Anybody have a workaround? I am having problems using this version because
> it just kicks off all of my services after awhile!
>
--
View this message in context:
http://www.nabble.com/Inactivity-monitor-exception-is-closing-connection.-tp15404620s2354p15622035.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
using this version because
it just kicks off all of my services after awhile!
--
View this message in context:
http://www.nabble.com/Inactivity-monitor-exception-is-closing-connection.-tp15404620s2354p15611505.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
InputStream.fill(TcpBufferedInputStream.java:50)
>> at
>> org
>> .apache
>> .activemq
>> .transport
>> .tcp.TcpBufferedInputStream.read(TcpBufferedInputStream.java:58)
>> at java.io.DataInputStream.readInt(Unknown Source)
>> at
>> org
>> .apache
>>
> .transport
>> .tcp.TcpBufferedInputStream.read(TcpBufferedInputStream.java:58)
>> at java.io.DataInputStream.readInt(Unknown Source)
>> at
>> org
>> .apache
>> .activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:268)
>> at
&
at
org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:
172)
at java.lang.Thread.run(Unknown Source)
I don't know what is the problem.
Please help me.
Thanks in advance.
--
View this message in context:
http://www.nabble.com/Inactivity-monitor-exception-is-closing-
message in context:
http://www.nabble.com/Inactivity-monitor-exception-is-closing-connection.-tp15404620s2354p15404620.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
On Jan 16, 2008, at 3:26 AM, Rob Davies wrote:
This is a known bug in 5.0 - please use the latest 5.1 snapshot
willdo, thanks!
-pete
--
[EMAIL PROTECTED] - http://fotap.org/~osi
smime.p7s
Description: S/MIME cryptographic signature
This is a known bug in 5.0 - please use the latest 5.1 snapshot
On Jan 16, 2008, at 3:42 AM, peter royal wrote:
we're having the occasional/random explosion of threads in our
broker. it appears to be related to the client using the failover
transport and reconnecting to the broker, and the br
we're having the occasional/random explosion of threads in our broker.
it appears to be related to the client using the failover transport
and reconnecting to the broker, and the broker not cleaning itself up
properly.
there are a bunch of threads doing:
"ActiveMQ Transport: tcp:///127.0.0
45 matches
Mail list logo
