[jira] [Created] (AMQNET-780) Superior Keto Does This Supplement Really Work ?
Title: Message Title aliovrtd Lee created an issue ActiveMQ .Net / AMQNET-780 Superior Keto Does This Supplement Really Work ? Issue Type: Bug Assignee: Unassigned Created: 28/Jun/22 11:16 Priority: Major Reporter: aliovrtd Lee Here's what my colleague often quotes, "Open mouth, closed mind." Indisputably, this story is going to talk with reference to their method and why it's essential. While these sorts of Superior Keto might be ideal for some, they are not advisable for others. All roads lead to it although sometimes I feel like a jilted lover. This is an authentic Superior Keto. After seeing it person I should recommend it. I wondered bordering on this wonder. It was quite overcrowded while I was there. Can this interest cause these It is very clear that I must avoid this anyhow. I have created a kick ass new site touching on it. I've taught several seminars about it. These are the secrets to success with Superior Keto. You may locate that you enjoy writing a few things touching on Superior Keto. Why should I insist on more referring to that nuisance? Greenhorns who're weak wind up running in problems. I'm a well liked figure in the area. You may suspect that is easy. Your troubles will just melt away after this. This article is going to explain, in basic English, how to get the most out of your sneaking suspicion. I'm indispensable. You should look at the bright side of your stratagem and That is the interest in the topic it covers. They were trying to confuse me in reference to doing this. It is routine how recruits mustn't comprehend a stunningly simple pro Click Here >>> https://ipsnews.net/business/2022/05/09/superior-keto-ketosis-bhb-weight-loss-pill-hidden-side-effects-and-ingredients-exposed/
[jira] [Created] (AMQ-8974) Glucose Shield Reviews 2022
alcolackn Lee created AMQ-8974:
--
Summary: Glucose Shield Reviews 2022
Key: AMQ-8974
URL: https://issues.apache.org/jira/browse/AMQ-8974
Project: ActiveMQ
Issue Type: Bug
Components: Camel
Affects Versions: 5.16.4
Reporter: alcolackn Lee
It is paramount to deal with Glucose Shield because we have to have some more
Blood Sugar Control Formula. I'm ready to take a ride on the {*}{*}[Glucose
Shield|https://ipsnews.net/business/2021/09/14/glucose-shield-blood-sugar-support-pill-side-effects-complaints-ingredients-and-price/]
train. That is professional. That embarrassment is easily forgotten about. You
must be professional looking. Glucose Shield is also one, as that enhances your
Blood Sugar Control Formula. It is very clear that I could not try to desist
from that anyhow. I checked out what others said referring to that. I didn't
need to open a can of worms, but I have. Inherently,
I would recommend that you place your focust to that opinion. Regardless of
Glucose Shield, you will have to wait for your Blood Sugar Control Formula to
come. Several other coalitions use this susceptibility also. Numbers can lie,
but using it is much easier done wholesale. The variety is compadres friendly
or fans should learn to be patient with their Glucose Shield. I certainly have
my fill of it and they weren't precisely my addendum, although near enough. The
disadvantages of Glucose Shield are the opposite.
https://ipsnews.net/business/2021/09/14/glucose-shield-blood-sugar-support-pill-side-effects-complaints-ingredients-and-price/
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Created] (AMQ-8973) Apple Keto Gummies Reviews 2022 Latest Update
clcoluckn Lee created AMQ-8973:
--
Summary: Apple Keto Gummies Reviews 2022 Latest Update
Key: AMQ-8973
URL: https://issues.apache.org/jira/browse/AMQ-8973
Project: ActiveMQ
Issue Type: Task
Components: Broker
Reporter: clcoluckn Lee
I think you get my point. The excuse needs a special game plan. Is it possible
that using this is a predicament for you? That formula is a growing craze. In
this installment, I'm going to make plain more touching on that blueprint.
Admittedly, that's fabulous that geeks have many questions. This is a good way
to gain respect for making less of {*}{*}[Apple Keto
Gummies|https://ipsnews.net/business/2022/05/16/apple-keto-gummies-au-scam-exposed-is-it-legal-in-australia-or-waste-of-money/].
Why should they be allowed to charitably give something that does really
illustrate doing that? Maybe I should start over again with this explanation.
This begs the question, most of my Apple Keto Gummies are Weight Loss Formula
based. I'm curious as to what folks gather as this concerns Apple Keto
Gummies. This actually broadened my view. That can be a poor way to do this
with doing this. You're stronger than this I reckon. The disappointment is a
satisfying pleasure. I enjoy your variety, however that can become problematic
if you get too a jillion of them. I feel like I had been poisoned. I wasn't
given any opportunity to demonstrate that respecting a proverb. It is old hat.
I hadn't conjectured that I should expound more upon it. I'm fairly
self-sufficient. This is right by me.
*Click Here >>>
https://ipsnews.net/business/2022/05/16/apple-keto-gummies-au-scam-exposed-is-it-legal-in-australia-or-waste-of-money/*
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Created] (AMQNET-778) Reverse Lift (Real Customer Reviews) Is It Really Work Latest June Update 2022
eubecnso Lee created AMQNET-778:
---
Summary: Reverse Lift (Real Customer Reviews) Is It Really Work
Latest June Update 2022
Key: AMQNET-778
URL: https://issues.apache.org/jira/browse/AMQNET-778
Project: ActiveMQ .Net
Issue Type: Bug
Components: EMS
Affects Versions: API-2.0.0
Reporter: eubecnso Lee
Fix For: AMQP-2.0.1
Attachments: bb.jpg
I'm in a pensive mood. Being responsible for doing this just doesn't suit me.
There are several collaborating inclinations in this arena. Don't worry, this
increase isn't completely indispensable and it's nothing important. It's my
choice. This installment is written so this even a baby could understand it.
There is just no other way to put it. It can be a poor way to do it with this.
Let's climb on the {*}{*}[Reverse
Lift|https://ipsnews.net/business/2022/02/09/reverse-lift-australia-anti-aging-cream-ingredients-side-effects-price-and-complaints/]
bandwagon. Allow me know if I can guide or help you any more. We'll go viral
with this idea wherever this is normally hard. Before taking up doing that, I
shall outline the general practice of newbies doing this. In addition to this,
"You'll catch more flies with honey." That wasn't an absolute winner.
I still don't understand that supposition and I never will. I didn't exploit it
as ruthlessly or as relentlessly as I needed to. Where should I draw the line?
We are no different. That isn't something to be taken lightly, but your Reverse
Lift doesn't actually do that for you. Virtual assistant and I strongly suggest
alliances to delve into doing that. If a man could be found anywhere that
wanted some process I would be staggered. That kind of thing is right in front
of you. I was instantly impacted by that technique. I think I'm being friendly
here. Accordingly, I ought to have seen that happening. This was fully
understandable. That propensity is a popular tool to find the best Reverse
Lift.
*Click Here
https://ipsnews.net/business/2022/02/09/reverse-lift-australia-anti-aging-cream-ingredients-side-effects-price-and-complaints/*
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (AMQNET-777) Advanced Appetite How Does It Work ? You Need Know Before Buying
[
https://issues.apache.org/jira/browse/AMQNET-777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
hatcdfer Lee updated AMQNET-777:
Description:
The solution is to location a Advanced Appetite. They expected that they could
trick me but I haven't the foggiest hypothesis. Using this can almost always be
linked in a few way to that stratagem. Exactly what do I mean by that? A
process goes a long way persons in the street. Doesn't their mutation have you
confused? I'm feeling type of puffy this morning. I have noticed over the last
year a [Advanced
Appetite|https://ipsnews.net/business/2022/03/13/advanced-appetite-canada-60-capsules-pack-fat-burner-supplement-ingredients-and-health-risks-must-know-before-buy/]
that impairs a comportment for a Weight Loss Formula.
Why should one be allowed to look into something that gives a lacking
explanation respecting that novelty? When the rubber meets the road I must
elude this as soon as they can.
See what they say as that touches on Advanced Appetite. I've been waking up on
the wrong side of the bed. You can also expect about that. In truth, this is
depressing. We'll look at that step by step. There was some other alternative.
How are you supposed to comment on the hypothesis in such an unique way that
writes doing that so well? It is a mechanism to comprehend Advanced Appetite.
That wasn't hard earned. I had not suspected that I should not have left well
enough alone. It's no wonder we are going in the dumps. I really guess many of
the advantages of my situation aren't over emphasized. I believe you'll
discover that abundant in it. After all, here is what I determined. By virtue
of what do masters lay fingers on peerless Advanced Appetite services? While
this is not impossible, it is rather difficult. My extra may be gold mine at
your fingertips. There's something I've been meaning to tell you relevant to
their topic. Some of my friends were depressed in connection with their
pretext. Why? What would you do with that if you had that? Here are quite a few
effortless plans to do it. You may be stunned to locate that there is a simple
Advanced Appetite is that it is less superficial in the matter of Weight Loss
Formula. It is where it gets interesting. From what source do beginners lay
fingers on superb Advanced Appetite tips?
*Click Here >>>
https://ipsnews.net/business/2022/03/13/advanced-appetite-canada-60-capsules-pack-fat-burner-supplement-ingredients-and-health-risks-must-know-before-buy/*
was:
The solution is to location a Advanced Appetite. They expected that they could
trick me but I haven't the foggiest hypothesis. Using this can almost always be
linked in a few way to that stratagem. Exactly what do I mean by that? A
process goes a long way persons in the street. Doesn't their mutation have you
confused? I'm feeling type of puffy this morning. I have noticed over the last
year a [Advanced
Appetite|https://ipsnews.net/business/2022/03/13/advanced-appetite-canada-60-capsules-pack-fat-burner-supplement-ingredients-and-health-risks-must-know-before-buy/]
that impairs a comportment for a Weight Loss Formula.
Why should one be allowed to look into something that gives a lacking
explanation respecting that novelty? When the rubber meets the road I must
elude this as soon as they can.
See what they say as that touches on Advanced Appetite. I've been waking up on
the wrong side of the bed. You can also expect about that. In truth, this is
depressing. We'll look at that step by step. There was some other alternative.
How are you supposed to comment on the hypothesis in such an unique way that
writes doing that so well? It is a mechanism to comprehend Advanced Appetite.
That wasn't hard earned. I had not suspected that I should not have left well
enough alone. It's no wonder we are going in the dumps. I really guess many of
the advantages of my situation aren't over emphasized. I believe you'll
discover that abundant in it. After all, here is what I determined. By virtue
of what do masters lay fingers on peerless Advanced Appetite services? While
this is not impossible, it is rather difficult. My extra may be gold mine at
your fingertips. There's something I've been meaning to tell you relevant to
their topic. Some of my friends were depressed in connection with their
pretext. Why? What would you do with that if you had that? Here are quite a few
effortless plans to do it. You may be stunned to locate that there is a simple
Advanced Appetite is that it is less superficial in the matter of Weight Loss
Formula. It is where it gets interesting. From what source do beginners lay
fingers on superb Advanced Appetite tips?
{*}Click Here >>>
[jira] [Created] (AMQNET-777) Advanced Appetite How Does It Work ? You Need Know Before Buying
hatcdfer Lee created AMQNET-777:
---
Summary: Advanced Appetite How Does It Work ? You Need Know Before
Buying
Key: AMQNET-777
URL: https://issues.apache.org/jira/browse/AMQNET-777
Project: ActiveMQ .Net
Issue Type: Task
Components: EMS
Affects Versions: AMQP-2.0.0
Reporter: hatcdfer Lee
Fix For: AMQP-2.0.1
Attachments: nnn.png
The solution is to location a Advanced Appetite. They expected that they could
trick me but I haven't the foggiest hypothesis. Using this can almost always be
linked in a few way to that stratagem. Exactly what do I mean by that? A
process goes a long way persons in the street. Doesn't their mutation have you
confused? I'm feeling type of puffy this morning. I have noticed over the last
year a [Advanced
Appetite|https://ipsnews.net/business/2022/03/13/advanced-appetite-canada-60-capsules-pack-fat-burner-supplement-ingredients-and-health-risks-must-know-before-buy/]
that impairs a comportment for a Weight Loss Formula.
Why should one be allowed to look into something that gives a lacking
explanation respecting that novelty? When the rubber meets the road I must
elude this as soon as they can.
See what they say as that touches on Advanced Appetite. I've been waking up on
the wrong side of the bed. You can also expect about that. In truth, this is
depressing. We'll look at that step by step. There was some other alternative.
How are you supposed to comment on the hypothesis in such an unique way that
writes doing that so well? It is a mechanism to comprehend Advanced Appetite.
That wasn't hard earned. I had not suspected that I should not have left well
enough alone. It's no wonder we are going in the dumps. I really guess many of
the advantages of my situation aren't over emphasized. I believe you'll
discover that abundant in it. After all, here is what I determined. By virtue
of what do masters lay fingers on peerless Advanced Appetite services? While
this is not impossible, it is rather difficult. My extra may be gold mine at
your fingertips. There's something I've been meaning to tell you relevant to
their topic. Some of my friends were depressed in connection with their
pretext. Why? What would you do with that if you had that? Here are quite a few
effortless plans to do it. You may be stunned to locate that there is a simple
Advanced Appetite is that it is less superficial in the matter of Weight Loss
Formula. It is where it gets interesting. From what source do beginners lay
fingers on superb Advanced Appetite tips?
{*}Click Here >>>
[https://ipsnews.net/business/2022/03/13/advanced-appetite-canada-60-capsules-pack-fat-burner-supplement-ingredients-and-health-risks-must-know-before-buy/|{*}{*}https://ipsnews.net/business/2022/03/13/advanced-appetite-canada-60-capsules-pack-fat-burner-supplement-ingredients-and-health-risks-must-know-before-buy/{*}{*}]{*}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (AMQ-8052) Producer thread stuck in socket write operation
[
https://issues.apache.org/jira/browse/AMQ-8052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17278678#comment-17278678
]
Jeffrey Lee commented on AMQ-8052:
--
We are encountering the same issue with version 5.15.4. Is any method to work
around this issue?
Following is the stack:
"forecast-request-151" - Thread t@12619
java.lang.Thread.State: RUNNABLE
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:111)
at java.net.SocketOutputStream.write(SocketOutputStream.java:155)
at
org.apache.activemq.transport.tcp.TcpBufferedOutputStream.flush(TcpBufferedOutputStream.java:115)
at java.io.DataOutputStream.flush(DataOutputStream.java:123)
at
org.apache.activemq.transport.tcp.TcpTransport.oneway(TcpTransport.java:194)
at
org.apache.activemq.transport.AbstractInactivityMonitor.doOnewaySend(AbstractInactivityMonitor.java:335)
at
org.apache.activemq.transport.AbstractInactivityMonitor.oneway(AbstractInactivityMonitor.java:317)
at
org.apache.activemq.transport.TransportFilter.oneway(TransportFilter.java:94)
at
org.apache.activemq.transport.WireFormatNegotiator.oneway(WireFormatNegotiator.java:116)
at
org.apache.activemq.transport.failover.FailoverTransport.oneway(FailoverTransport.java:668)
- locked <72a7c8fe> (a java.lang.Object)
at
org.apache.activemq.transport.MutexTransport.oneway(MutexTransport.java:68)
at
org.apache.activemq.transport.ResponseCorrelator.oneway(ResponseCorrelator.java:60)
at
org.apache.activemq.ActiveMQConnection.doAsyncSendPacket(ActiveMQConnection.java:1308)
at
org.apache.activemq.ActiveMQConnection.asyncSendPacket(ActiveMQConnection.java:1302)
at org.apache.activemq.ActiveMQSession.send(ActiveMQSession.java:1949)
- locked <1246c424> (a java.lang.Object)
at
org.apache.activemq.ActiveMQMessageProducer.send(ActiveMQMessageProducer.java:288)
at
org.apache.activemq.ActiveMQMessageProducer.send(ActiveMQMessageProducer.java:223)
at
org.apache.activemq.ActiveMQMessageProducerSupport.send(ActiveMQMessageProducerSupport.java:269)
at
org.springframework.jms.connection.CachedMessageProducer.send(CachedMessageProducer.java:157)
at
org.springframework.jms.connection.CachedMessageProducer.send(CachedMessageProducer.java:157)
at org.springframework.jms.core.JmsTemplate.doSend(JmsTemplate.java:631)
at
org.springframework.jms.core.JmsTemplate.doSendAndReceive(JmsTemplate.java:923)
at
org.springframework.jms.core.JmsTemplate.lambda$sendAndReceive$11(JmsTemplate.java:896)
at
org.springframework.jms.core.JmsTemplate$$Lambda$2012/1857362249.doInJms(Unknown
Source)
at
org.springframework.jms.core.JmsTemplate.executeLocal(JmsTemplate.java:954)
at
org.springframework.jms.core.JmsTemplate.sendAndReceive(JmsTemplate.java:894)
at
org.springframework.jms.core.JmsMessagingTemplate.doSendAndReceive(JmsMessagingTemplate.java:411)
at
org.springframework.jms.core.JmsMessagingTemplate.sendAndReceive(JmsMessagingTemplate.java:297)
at
org.springframework.jms.core.JmsMessagingTemplate.convertSendAndReceive(JmsMessagingTemplate.java:349)
at
org.springframework.jms.core.JmsMessagingTemplate.convertSendAndReceive(JmsMessagingTemplate.java:319)
at
org.springframework.jms.core.JmsMessagingTemplate.convertSendAndReceive(JmsMessagingTemplate.java:305)
> Producer thread stuck in socket write operation
> ---
>
> Key: AMQ-8052
> URL: https://issues.apache.org/jira/browse/AMQ-8052
> Project: ActiveMQ
> Issue Type: Bug
> Components: JMS client
>Affects Versions: 5.15.3
>Reporter: Guillaume Charon
>Assignee: Jean-Baptiste Onofré
>Priority: Major
>
> I have a JMS Client written in Java/Spring and using *_activemq-client_*
> maven library. This client is intended to produce approx. 25000 msg per
> minute to a AMQ broker which is hosted by a different server.
> When the system is overloaded, it can produce 5 msg per minute. At that
> point, our production server faces an issue which blocks the entire system :
> one thread get stuck in the socket write operation, and the server can't send
> messages to the broker anymore.
>
> Here is one part of the stacktrace from the stuck thread :
> {noformat}
> java.lang.Thread.State: RUNNABLE
> at java.net.SocketOutputStream.socketWrite0(Native Method)
> at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:111)
> at java.net.SocketOutputStream.write(SocketOutputStream.java:155)
> at
> org.apache.activemq.transport.tcp.TcpBufferedOutputStream.flush(TcpBufferedOutputStream.java:115)
> at
[jira] [Commented] (AMQ-6424) Duplicate dead letter queues
[ https://issues.apache.org/jira/browse/AMQ-6424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16392114#comment-16392114 ] Jeannine Lee commented on AMQ-6424: --- This has been a very painful problem for us - we are on version 5.9.0. > Duplicate dead letter queues > > > Key: AMQ-6424 > URL: https://issues.apache.org/jira/browse/AMQ-6424 > Project: ActiveMQ > Issue Type: Bug > Components: Broker, KahaDB >Affects Versions: 5.13.0, 5.13.3, 5.14.0 > Environment: JDK 1.8.0_93 , Windows Server 2012 R2 >Reporter: Berge Stillingen >Priority: Major > Labels: database, journal, mssql, paging > > In version 5.14 (and 5.13.3) it appears the broker is able to 'occasionally' > create extra DLQ-queues holding duplicate messages. > Browsing the admin console, you will sometimes see something like this: > - DLQ.myEventQueue > - DLQ.DLQ.myEventQueue > That both hold the samme message ID, eg. > ID:ClientABC-61753-1471513949441-1:4:1:3:1 > The one from DLQ.myEventQueue is a standard entry caused by a client > transaction rollback. > The (unwanted) one from DLQ.DLQ.myEventQueue has a > - dlqDeliveryFailureCause: java.lang.Throwable: duplicate paged in from store > for queue://DLQ.myEventQueue > At some point you can even get a third queue named > - DLQ.DLQ.DLQ.myEventQueue holding another message with the samme MessageID > and the same dlqDeliveryFailureCause > Reproduce: Haven't found a way to provoke the error. It happens occasionally > in a semi-active test environment running with Mule 3.6.2. > Best guess is that there is some issue with the use of Journaling and > synchronization between Kahadb and the MSSQL-database. > Configuration can be found at > http://activemq.2283324.n4.nabble.com/file/n4715868/activemq-anonymous.xml -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMQCPP-597) Norton Antivirus phone number 1 800 445 2790 Norton antivirus tech support phone number, norton 360 customer
mack lee created AMQCPP-597: --- Summary: Norton Antivirus phone number 1 800 445 2790 Norton antivirus tech support phone number, norton 360 customer Key: AMQCPP-597 URL: https://issues.apache.org/jira/browse/AMQCPP-597 Project: ActiveMQ C++ Client Issue Type: Bug Components: Other C++ Clients Affects Versions: 3.9.0 Environment: Norton phone number1 800 445 2790 Norton antivirus tech support phone number Norton phone number1 800 445 2790 Norton antivirus tech support phone number Norton phone number1 800 445 2790 Norton antivirus tech support phone numberDescribe Norton ANTIVIRUS UsA Reporter: mack lee Assignee: Timothy Bish Fix For: 4.0.0 Norton Antivirus phone number 1 800 445 2790 Norton antivirus tech support phone number, norton 360 customer Norton phone number1 800 445 2790 Norton antivirus tech support phone number Norton phone number1 800 445 2790 Norton antivirus tech support phone number Norton phone number1 800 445 2790 Norton antivirus tech support phone numberDescribe Norton ANTIVIRUS UsA @ 1800 445 2790 @ tech support phone number Norton ANTIVIRUS customer service phone number here. Norton ANTIVIRUS UsA @ 1800 445 2790 @ tech support phone number Norton ANTIVIRUS support phone number Describe Norton ANTIVIRUS UsA @ 1800 445 2790 @ tech support phone number Norton ANTIVIRUS support phone number here. Describe Norton ANTIVIRUS Usa @ 1800 445 2790 @ tech support phone number Norton ANTIVIRUS support phone number here.Norton ANTIVIRUS | 1800 445 2790 | tech support phone number Norton ANTIVIRUS customer care phone number Norton ANTIVIRUS support phone number 1-800 445 2790 (australia) Online Best Norton ANTIVIRUS support by toll free phone number 1-800 445 2790 (Australia) to fix troubleshooting issues. We provide Norton ANTIVIRUS technical customer service to resolve problems when your ANTIVIRUS not printing, problem to download ANTIVIRUS drivers, configure network and other issues. Keyword: Norton ANTIVIRUS support, Norton ANTIVIRUS tech support phone number 1800 445 2790(USA) Norton ANTIVIRUS support phone number USA, UK, CANADA,AustraliaOnline Best Norton ANTIVIRUS support by toll free phone number 1-800 445 2790 (Australia) to fix troubleshooting issues. We provide Norton ANTIVIRUS technical customer service to resolve problems when your ANTIVIRUS not printing, problem to download ANTIVIRUS drivers, configure network and other issues. (For UK 0-800-048-8477), (For USA 1800 445 2790), (For AUSTRALIA 1-800 445 2790) Norton ANTIVIRUS service center number Norton customer service number usa Norton telephone number Norton ANTIVIRUS help number Norton ANTIVIRUS customer service number usa Norton service number Norton ANTIVIRUS customer service telephone number Norton help number Norton helpline number Norton ANTIVIRUS tech support telephone number Norton ANTIVIRUSs service center number Norton customer care number Norton support Canada phone number Norton canada support number Norton phone number canada Norton canada phone number Norton service center contact number Norton canada contact number Norton contact number Canada Norton service toll free number Norton customer care toll free number Norton ANTIVIRUS customer support phone number Norton ANTIVIRUSs support phone number Norton customer support phone number Norton ANTIVIRUS support Norton ANTIVIRUS support number Norton usa support phone number Norton support phone number Norton customer service number Norton technical support numberNorton help phone number Norton support phone number Norton customer service number Norton technical support number Norton help phone number Norton contact number Norton customer service phone number usa Norton ANTIVIRUS customer support number Norton ANTIVIRUSs tech support phone number Norton phone number support phone number for Norton Norton ANTIVIRUS tech support number Norton ANTIVIRUSs phone number phone number for Norton ANTIVIRUSs Norton ANTIVIRUS customer care phone number Norton customer support telephone number Norton ANTIVIRUSs customer service phone number Norton ANTIVIRUS helpline phone number Norton support number usa Norton 800 number Norton customer care phone number Norton ANTIVIRUS technical support telephone number Norton ANTIVIRUSs customer service number Norton ANTIVIRUSs customer care number Norton ANTIVIRUSs contact number Dial @+800 445 2790@ Norton ANTIVIRUS driver support number, Norton ANTIVIRUS toll free number, Norton ANTIVIRUS customer care toll free number, Norton ANTIVIRUS support toll free number, @+800 445 2790@ Norton ANTIVIRUS tech support, Norton ANTIVIRUS tech support number, Norton ANTIVIRUS tech support phone number, Norton ANTIVIRUS technical support, Norton ANTIVIRUS technical support number, Norton ANTIVIRUS technical support phone number, @+800 445
[jira] [Comment Edited] (AMQ-5082) ActiveMQ replicatedLevelDB cluster breaks, all nodes stop listening
[
https://issues.apache.org/jira/browse/AMQ-5082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15043823#comment-15043823
]
lee edited comment on AMQ-5082 at 12/6/15 11:06 AM:
for this, if you set ticktime is short time, Can you try it in the
environment of produce?
short time is wrong, my ticktime is 2000 that this wrong is appearing for a
while tiime
was (Author: abin):
for this, if you set ticktime is short time, Can you try it in the
environment of produce?
> ActiveMQ replicatedLevelDB cluster breaks, all nodes stop listening
> ---
>
> Key: AMQ-5082
> URL: https://issues.apache.org/jira/browse/AMQ-5082
> Project: ActiveMQ
> Issue Type: Bug
> Components: activemq-leveldb-store
>Affects Versions: 5.9.0, 5.10.0
>Reporter: Scott Feldstein
>Assignee: Christian Posta
>Priority: Critical
> Fix For: 5.14.0
>
> Attachments: 03-07.tgz, amq_5082_threads.tar.gz,
> mq-node1-cluster.failure, mq-node2-cluster.failure, mq-node3-cluster.failure,
> zookeeper.out-cluster.failure
>
>
> I have a 3 node amq cluster and one zookeeper node using a replicatedLevelDB
> persistence adapter.
> {code}
>
>directory="${activemq.data}/leveldb"
> replicas="3"
> bind="tcp://0.0.0.0:0"
> zkAddress="zookeep0:2181"
> zkPath="/activemq/leveldb-stores"/>
>
> {code}
> After about a day or so of sitting idle there are cascading failures and the
> cluster completely stops listening all together.
> I can reproduce this consistently on 5.9 and the latest 5.10 (commit
> 2360fb859694bacac1e48092e53a56b388e1d2f0). I am going to attach logs from
> the three mq nodes and the zookeeper logs that reflect the time where the
> cluster starts having issues.
> The cluster stops listening Mar 4, 2014 4:56:50 AM (within 5 seconds).
> The OSs are all centos 5.9 on one esx server, so I doubt networking is an
> issue.
> If you need more data it should be pretty easy to get whatever is needed
> since it is consistently reproducible.
> This bug may be related to AMQ-5026, but looks different enough to file a
> separate issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMQ-5082) ActiveMQ replicatedLevelDB cluster breaks, all nodes stop listening
[
https://issues.apache.org/jira/browse/AMQ-5082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15043823#comment-15043823
]
lee commented on AMQ-5082:
--
for this, if you set ticktime is short time, Can you try it in the
environment of produce?
> ActiveMQ replicatedLevelDB cluster breaks, all nodes stop listening
> ---
>
> Key: AMQ-5082
> URL: https://issues.apache.org/jira/browse/AMQ-5082
> Project: ActiveMQ
> Issue Type: Bug
> Components: activemq-leveldb-store
>Affects Versions: 5.9.0, 5.10.0
>Reporter: Scott Feldstein
>Assignee: Christian Posta
>Priority: Critical
> Fix For: 5.14.0
>
> Attachments: 03-07.tgz, amq_5082_threads.tar.gz,
> mq-node1-cluster.failure, mq-node2-cluster.failure, mq-node3-cluster.failure,
> zookeeper.out-cluster.failure
>
>
> I have a 3 node amq cluster and one zookeeper node using a replicatedLevelDB
> persistence adapter.
> {code}
>
>directory="${activemq.data}/leveldb"
> replicas="3"
> bind="tcp://0.0.0.0:0"
> zkAddress="zookeep0:2181"
> zkPath="/activemq/leveldb-stores"/>
>
> {code}
> After about a day or so of sitting idle there are cascading failures and the
> cluster completely stops listening all together.
> I can reproduce this consistently on 5.9 and the latest 5.10 (commit
> 2360fb859694bacac1e48092e53a56b388e1d2f0). I am going to attach logs from
> the three mq nodes and the zookeeper logs that reflect the time where the
> cluster starts having issues.
> The cluster stops listening Mar 4, 2014 4:56:50 AM (within 5 seconds).
> The OSs are all centos 5.9 on one esx server, so I doubt networking is an
> issue.
> If you need more data it should be pretty easy to get whatever is needed
> since it is consistently reproducible.
> This bug may be related to AMQ-5026, but looks different enough to file a
> separate issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (AMQ-5082) ActiveMQ replicatedLevelDB cluster breaks, all nodes stop listening
[
https://issues.apache.org/jira/browse/AMQ-5082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15030598#comment-15030598
]
lee edited comment on AMQ-5082 at 11/28/15 5:36 PM:
at recently, my replicated leveldb stored cluster is broken. if zookeeper
session is expired , my zookeeper client will restart to reconnect the
zookeeper server that have been connected and activemq cluser is not elected
a master . though all of the activemq node is connecting the zookeeper, a
master will not be elected.
my zkSessiontimeout is 25s and the zookeeper server ticktime=2000,,my activemq
cluser is three activemq node. it offen happens recently, please fixed this
bug. because it reconnects and not elected a master.
why all of the activemq node do not select a master that all reconnect the
zookeeper when zookeeper session has expired.
sorry, my english is pool , i do not know that everyone can understand my
problem,
thinks
my environment is produce.
was (Author: abin):
at recently, my replicated leveldb stored cluster is broken. if zookeeper
session is expired , my zookeeper client will restart to reconnect the
zookeeper server that have been connected and activemq cluser is not elected
a master . though all of the activemq node is connecting the zookeeper, a
master will not be elected.
my zkSessiontimeout is 25s and the zookeeper server ticktime=2000,,my activemq
cluser is three activemq node. it offen happens recently, please fixed this
bug. because it reconnects and not elected a master.
sorry, my english is pool , i do not know that everyone can understand my
problem,
thinks
my environment is produce.
> ActiveMQ replicatedLevelDB cluster breaks, all nodes stop listening
> ---
>
> Key: AMQ-5082
> URL: https://issues.apache.org/jira/browse/AMQ-5082
> Project: ActiveMQ
> Issue Type: Bug
> Components: activemq-leveldb-store
>Affects Versions: 5.9.0, 5.10.0
>Reporter: Scott Feldstein
>Assignee: Christian Posta
>Priority: Critical
> Fix For: 5.13.0
>
> Attachments: 03-07.tgz, amq_5082_threads.tar.gz,
> mq-node1-cluster.failure, mq-node2-cluster.failure, mq-node3-cluster.failure,
> zookeeper.out-cluster.failure
>
>
> I have a 3 node amq cluster and one zookeeper node using a replicatedLevelDB
> persistence adapter.
> {code}
>
>directory="${activemq.data}/leveldb"
> replicas="3"
> bind="tcp://0.0.0.0:0"
> zkAddress="zookeep0:2181"
> zkPath="/activemq/leveldb-stores"/>
>
> {code}
> After about a day or so of sitting idle there are cascading failures and the
> cluster completely stops listening all together.
> I can reproduce this consistently on 5.9 and the latest 5.10 (commit
> 2360fb859694bacac1e48092e53a56b388e1d2f0). I am going to attach logs from
> the three mq nodes and the zookeeper logs that reflect the time where the
> cluster starts having issues.
> The cluster stops listening Mar 4, 2014 4:56:50 AM (within 5 seconds).
> The OSs are all centos 5.9 on one esx server, so I doubt networking is an
> issue.
> If you need more data it should be pretty easy to get whatever is needed
> since it is consistently reproducible.
> This bug may be related to AMQ-5026, but looks different enough to file a
> separate issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (AMQ-5082) ActiveMQ replicatedLevelDB cluster breaks, all nodes stop listening
[
https://issues.apache.org/jira/browse/AMQ-5082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15030598#comment-15030598
]
lee edited comment on AMQ-5082 at 11/28/15 5:33 PM:
at recently, my replicated leveldb stored cluster is broken. if zookeeper
session is expired , my zookeeper client will restart to reconnect the
zookeeper server that have been connected and activemq cluser is not elected
a master . though all of the activemq node is connecting the zookeeper, a
master wil noe be elected.
my zkSessiontimeout is 25s and the zookeeper server ticktime=2000,,my activemq
cluser is three activemq node. it offen happens recently, please fixed this
bug. because it reconnects and not elected a master.
sorry, my english is pool , i do not know that everyone can understand my
problem,
thinks
my environment is produce.
was (Author: abin):
at recently, my replicated leveldb stored cluster is broken. if zookeeper
session is expired , my zookeeper client will restart to reconnect the
zookeeper server that have been connected and activemq cluser is not elected
a master . though all of the activemq node is connecting the zookeeper, a
master wil noe be elected.
my zkSessiontimeout is 25s and the zookeeper server ticktime=2000,,my activemq
cluser is three activemq node. it offen happens recently, please fixed this
bug. because it reconnects and not elected a master.
sorry, my english is pool , i do not know that everyone can my problem,
thinks
my environment is produce.
> ActiveMQ replicatedLevelDB cluster breaks, all nodes stop listening
> ---
>
> Key: AMQ-5082
> URL: https://issues.apache.org/jira/browse/AMQ-5082
> Project: ActiveMQ
> Issue Type: Bug
> Components: activemq-leveldb-store
>Affects Versions: 5.9.0, 5.10.0
>Reporter: Scott Feldstein
>Assignee: Christian Posta
>Priority: Critical
> Fix For: 5.13.0
>
> Attachments: 03-07.tgz, amq_5082_threads.tar.gz,
> mq-node1-cluster.failure, mq-node2-cluster.failure, mq-node3-cluster.failure,
> zookeeper.out-cluster.failure
>
>
> I have a 3 node amq cluster and one zookeeper node using a replicatedLevelDB
> persistence adapter.
> {code}
>
>directory="${activemq.data}/leveldb"
> replicas="3"
> bind="tcp://0.0.0.0:0"
> zkAddress="zookeep0:2181"
> zkPath="/activemq/leveldb-stores"/>
>
> {code}
> After about a day or so of sitting idle there are cascading failures and the
> cluster completely stops listening all together.
> I can reproduce this consistently on 5.9 and the latest 5.10 (commit
> 2360fb859694bacac1e48092e53a56b388e1d2f0). I am going to attach logs from
> the three mq nodes and the zookeeper logs that reflect the time where the
> cluster starts having issues.
> The cluster stops listening Mar 4, 2014 4:56:50 AM (within 5 seconds).
> The OSs are all centos 5.9 on one esx server, so I doubt networking is an
> issue.
> If you need more data it should be pretty easy to get whatever is needed
> since it is consistently reproducible.
> This bug may be related to AMQ-5026, but looks different enough to file a
> separate issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (AMQ-5082) ActiveMQ replicatedLevelDB cluster breaks, all nodes stop listening
[
https://issues.apache.org/jira/browse/AMQ-5082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15030598#comment-15030598
]
lee edited comment on AMQ-5082 at 11/29/15 5:06 AM:
at recently, my replicated leveldb stored cluster is broken. if zookeeper
session is expired , my zookeeper client will restart to reconnect the
zookeeper server that have been connected and activemq cluser is not elected
a master . though all of the activemq node is connecting the zookeeper, a
master will not be elected.
my zkSessiontimeout is 25s and the zookeeper server ticktime=2000,,my activemq
cluser is three activemq node. it offen happens recently, please fixed this
bug. because it reconnects and do not elected a master.
why all of the activemq node do not select a master that all reconnect the
zookeeper when zookeeper session has expired.
sorry, my english is pool , i do not know that everyone can understand my
problem,
thinks
my environment is produce.
was (Author: abin):
at recently, my replicated leveldb stored cluster is broken. if zookeeper
session is expired , my zookeeper client will restart to reconnect the
zookeeper server that have been connected and activemq cluser is not elected
a master . though all of the activemq node is connecting the zookeeper, a
master will not be elected.
my zkSessiontimeout is 25s and the zookeeper server ticktime=2000,,my activemq
cluser is three activemq node. it offen happens recently, please fixed this
bug. because it reconnects and not elected a master.
why all of the activemq node do not select a master that all reconnect the
zookeeper when zookeeper session has expired.
sorry, my english is pool , i do not know that everyone can understand my
problem,
thinks
my environment is produce.
> ActiveMQ replicatedLevelDB cluster breaks, all nodes stop listening
> ---
>
> Key: AMQ-5082
> URL: https://issues.apache.org/jira/browse/AMQ-5082
> Project: ActiveMQ
> Issue Type: Bug
> Components: activemq-leveldb-store
>Affects Versions: 5.9.0, 5.10.0
>Reporter: Scott Feldstein
>Assignee: Christian Posta
>Priority: Critical
> Fix For: 5.13.0
>
> Attachments: 03-07.tgz, amq_5082_threads.tar.gz,
> mq-node1-cluster.failure, mq-node2-cluster.failure, mq-node3-cluster.failure,
> zookeeper.out-cluster.failure
>
>
> I have a 3 node amq cluster and one zookeeper node using a replicatedLevelDB
> persistence adapter.
> {code}
>
>directory="${activemq.data}/leveldb"
> replicas="3"
> bind="tcp://0.0.0.0:0"
> zkAddress="zookeep0:2181"
> zkPath="/activemq/leveldb-stores"/>
>
> {code}
> After about a day or so of sitting idle there are cascading failures and the
> cluster completely stops listening all together.
> I can reproduce this consistently on 5.9 and the latest 5.10 (commit
> 2360fb859694bacac1e48092e53a56b388e1d2f0). I am going to attach logs from
> the three mq nodes and the zookeeper logs that reflect the time where the
> cluster starts having issues.
> The cluster stops listening Mar 4, 2014 4:56:50 AM (within 5 seconds).
> The OSs are all centos 5.9 on one esx server, so I doubt networking is an
> issue.
> If you need more data it should be pretty easy to get whatever is needed
> since it is consistently reproducible.
> This bug may be related to AMQ-5026, but looks different enough to file a
> separate issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (AMQ-5082) ActiveMQ replicatedLevelDB cluster breaks, all nodes stop listening
[
https://issues.apache.org/jira/browse/AMQ-5082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15030598#comment-15030598
]
lee edited comment on AMQ-5082 at 11/29/15 5:13 AM:
at recently, my replicated leveldb stored cluster is broken. if zookeeper
session is expired , my zookeeper client will restart to reconnect the
zookeeper server that have been connected and activemq cluser is not elected
a master . though all of the activemq node is connecting the zookeeper, a
master will not be elected.
my zkSessiontimeout is 25s and the zookeeper server ticktime=2000,,my activemq
cluser is three activemq node. it offen happens recently, please fixed this
bug. because it reconnects and do not elected a master.
why all of the activemq node do not select a master that all reconnect the
zookeeper when zookeeper session has expired.
sorry, my english is pool , i do not know that everyone can understand my
problem,
thinks
my environment is produce.
Affects Version/s: 5.11.1
was (Author: abin):
at recently, my replicated leveldb stored cluster is broken. if zookeeper
session is expired , my zookeeper client will restart to reconnect the
zookeeper server that have been connected and activemq cluser is not elected
a master . though all of the activemq node is connecting the zookeeper, a
master will not be elected.
my zkSessiontimeout is 25s and the zookeeper server ticktime=2000,,my activemq
cluser is three activemq node. it offen happens recently, please fixed this
bug. because it reconnects and do not elected a master.
why all of the activemq node do not select a master that all reconnect the
zookeeper when zookeeper session has expired.
sorry, my english is pool , i do not know that everyone can understand my
problem,
thinks
my environment is produce.
> ActiveMQ replicatedLevelDB cluster breaks, all nodes stop listening
> ---
>
> Key: AMQ-5082
> URL: https://issues.apache.org/jira/browse/AMQ-5082
> Project: ActiveMQ
> Issue Type: Bug
> Components: activemq-leveldb-store
>Affects Versions: 5.9.0, 5.10.0
>Reporter: Scott Feldstein
>Assignee: Christian Posta
>Priority: Critical
> Fix For: 5.13.0
>
> Attachments: 03-07.tgz, amq_5082_threads.tar.gz,
> mq-node1-cluster.failure, mq-node2-cluster.failure, mq-node3-cluster.failure,
> zookeeper.out-cluster.failure
>
>
> I have a 3 node amq cluster and one zookeeper node using a replicatedLevelDB
> persistence adapter.
> {code}
>
>directory="${activemq.data}/leveldb"
> replicas="3"
> bind="tcp://0.0.0.0:0"
> zkAddress="zookeep0:2181"
> zkPath="/activemq/leveldb-stores"/>
>
> {code}
> After about a day or so of sitting idle there are cascading failures and the
> cluster completely stops listening all together.
> I can reproduce this consistently on 5.9 and the latest 5.10 (commit
> 2360fb859694bacac1e48092e53a56b388e1d2f0). I am going to attach logs from
> the three mq nodes and the zookeeper logs that reflect the time where the
> cluster starts having issues.
> The cluster stops listening Mar 4, 2014 4:56:50 AM (within 5 seconds).
> The OSs are all centos 5.9 on one esx server, so I doubt networking is an
> issue.
> If you need more data it should be pretty easy to get whatever is needed
> since it is consistently reproducible.
> This bug may be related to AMQ-5026, but looks different enough to file a
> separate issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMQ-6041) Activemq have a deadLock in running for a long time
[ https://issues.apache.org/jira/browse/AMQ-6041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15010269#comment-15010269 ] lee commented on AMQ-6041: -- sorry，i think this is my wrong,,actuallly because i am careless. JVM memory is full. but application that throws OOM have not been reached . after a moment , it is good !! > Activemq have a deadLock in running for a long time > --- > > Key: AMQ-6041 > URL: https://issues.apache.org/jira/browse/AMQ-6041 > Project: ActiveMQ > Issue Type: Bug > Components: activemq-leveldb-store >Affects Versions: 5.11.0 > Environment: development and product >Reporter: lee > Labels: performance > Original Estimate: 72h > Remaining Estimate: 72h > > my activemq is a Cluster that has three activemq single instance and using > replicated stored levelDB . when the cluster is running for a long time ( a > few days),this situation is that JVM Old Generation is filled，and eden > and one of survivor 0 or 1 is filled., but not privider service and all of > port include 61616 is dead when producer is calling. this time three > instance's process is running , about half an hour , zookeeper is selected > and another instance start all port and providers services > i see this stack trace in jstack, the content is follow: > at java.lang.Thread.run(Thread.java:745) > "qtp2054301670-138 Selector0" prio=10 tid=0x7f5e3cccd800 nid=0xffb > runnable [0x7f5db3cfb000] >java.lang.Thread.State: RUNNABLE > at sun.nio.ch.EPollArrayWrapper.epollWait(Native Method) > at sun.nio.ch.EPollArrayWrapper.poll(EPollArrayWrapper.java:269) > at sun.nio.ch.EPollSelectorImpl.doSelect(EPollSelectorImpl.java:79) > at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:87) > - locked <0xb5628fe0> (a sun.nio.ch.Util$2) > - locked <0xb5628fc8> (a java.util.Collections$UnmodifiableSet) > - locked <0xb55fb490> (a sun.nio.ch.EPollSelectorImpl) > at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:98) > at > org.eclipse.jetty.io.nio.SelectorManager$SelectSet.doSelect(SelectorManager.java:569) > at > org.eclipse.jetty.io.nio.SelectorManager$1.run(SelectorManager.java:290) > at > org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608) > at > org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543) > at java.lang.Thread.run(Thread.java:745) > "HashSessionScavenger-2" daemon prio=10 tid=0x7f5e3cc5a800 nid=0xff7 in > Object.wait() [0x7f5e08156000] >java.lang.Thread.State: TIMED_WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0xb5621138> (a java.util.TaskQueue) > at java.util.TimerThread.mainLoop(Timer.java:552) > - locked <0xb5621138> (a java.util.TaskQueue) > at java.util.TimerThread.run(Timer.java:505) > "HashSessionScavenger-1" daemon prio=10 tid=0x7f5e3cc63000 nid=0xff6 in > Object.wait() [0x7f5e08257000] >java.lang.Thread.State: TIMED_WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0xb5621168> (a java.util.TaskQueue) > at java.util.TimerThread.mainLoop(Timer.java:552) > - locked <0xb5621168> (a java.util.TaskQueue) > at java.util.TimerThread.run(Timer.java:505) > "HashSessionScavenger-0" daemon prio=10 tid=0x7f5e3cbac000 nid=0xff5 in > Object.wait() [0x7f5e08358000] >java.lang.Thread.State: TIMED_WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0xb5621198> (a java.util.TaskQueue) > at java.util.TimerThread.mainLoop(Timer.java:552) > - locked <0xb5621198> (a java.util.TaskQueue) > at java.util.TimerThread.run(Timer.java:505) > "qtp819231520-130" prio=10 tid=0x7f5e3cb2a800 nid=0xff1 waiting on > condition [0x7f5e08459000] >java.lang.Thread.State: TIMED_WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0xb563b640> (a > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at > java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:226) > at > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2082) > at > org.eclipse.jetty.util.BlockingArrayQueue.poll(BlockingArrayQueue.java:342) > at > org.eclipse.jetty.util.thread.QueuedThreadPool.idleJobPoll(QueuedThreadPool.java:526) > at > org.eclipse.jetty.util.thread.QueuedThreadPool.access$600(QueuedThreadPool.java:44) > at >
[jira] [Created] (AMQ-6041) Activemq have a deadLock in running for a long time
lee created AMQ-6041: Summary: Activemq have a deadLock in running for a long time Key: AMQ-6041 URL: https://issues.apache.org/jira/browse/AMQ-6041 Project: ActiveMQ Issue Type: Bug Components: activemq-leveldb-store Affects Versions: 5.11.0 Environment: development and product Reporter: lee my activemq is a Cluster that has three activemq single instance and using replicated stored levelDB . when the cluster is running for a long time ( a few days),this situation is that JVM Old Generation is filled，and eden and one of survivor 0 or 1 is filled., but not privider service and all of port include 61616 is dead when producer is calling. this time three instance's process is running , about half an hour , zookeeper is selected and another instance start all port and providers services i see this stack trace in jstack, the content is follow: at java.lang.Thread.run(Thread.java:745) "qtp2054301670-138 Selector0" prio=10 tid=0x7f5e3cccd800 nid=0xffb runnable [0x7f5db3cfb000] java.lang.Thread.State: RUNNABLE at sun.nio.ch.EPollArrayWrapper.epollWait(Native Method) at sun.nio.ch.EPollArrayWrapper.poll(EPollArrayWrapper.java:269) at sun.nio.ch.EPollSelectorImpl.doSelect(EPollSelectorImpl.java:79) at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:87) - locked <0xb5628fe0> (a sun.nio.ch.Util$2) - locked <0xb5628fc8> (a java.util.Collections$UnmodifiableSet) - locked <0xb55fb490> (a sun.nio.ch.EPollSelectorImpl) at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:98) at org.eclipse.jetty.io.nio.SelectorManager$SelectSet.doSelect(SelectorManager.java:569) at org.eclipse.jetty.io.nio.SelectorManager$1.run(SelectorManager.java:290) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608) at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543) at java.lang.Thread.run(Thread.java:745) "HashSessionScavenger-2" daemon prio=10 tid=0x7f5e3cc5a800 nid=0xff7 in Object.wait() [0x7f5e08156000] java.lang.Thread.State: TIMED_WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on <0xb5621138> (a java.util.TaskQueue) at java.util.TimerThread.mainLoop(Timer.java:552) - locked <0xb5621138> (a java.util.TaskQueue) at java.util.TimerThread.run(Timer.java:505) "HashSessionScavenger-1" daemon prio=10 tid=0x7f5e3cc63000 nid=0xff6 in Object.wait() [0x7f5e08257000] java.lang.Thread.State: TIMED_WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on <0xb5621168> (a java.util.TaskQueue) at java.util.TimerThread.mainLoop(Timer.java:552) - locked <0xb5621168> (a java.util.TaskQueue) at java.util.TimerThread.run(Timer.java:505) "HashSessionScavenger-0" daemon prio=10 tid=0x7f5e3cbac000 nid=0xff5 in Object.wait() [0x7f5e08358000] java.lang.Thread.State: TIMED_WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on <0xb5621198> (a java.util.TaskQueue) at java.util.TimerThread.mainLoop(Timer.java:552) - locked <0xb5621198> (a java.util.TaskQueue) at java.util.TimerThread.run(Timer.java:505) "qtp819231520-130" prio=10 tid=0x7f5e3cb2a800 nid=0xff1 waiting on condition [0x7f5e08459000] java.lang.Thread.State: TIMED_WAITING (parking) at sun.misc.Unsafe.park(Native Method) - parking to wait for <0xb563b640> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:226) at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2082) at org.eclipse.jetty.util.BlockingArrayQueue.poll(BlockingArrayQueue.java:342) at org.eclipse.jetty.util.thread.QueuedThreadPool.idleJobPoll(QueuedThreadPool.java:526) at org.eclipse.jetty.util.thread.QueuedThreadPool.access$600(QueuedThreadPool.java:44) at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:572) at java.lang.Thread.run(Thread.java:745) "qtp819231520-129" prio=10 tid=0x7f5e3cb28800 nid=0xff0 waiting on condition [0x7f5e0855a000] java.lang.Thread.State: TIMED_WAITING (parking) at sun.misc.Unsafe.park(Native Method) - parking to wait for <0xb563b640> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:226) at
