i encourage you to take a look at and understand all of the options,
but only apply them once you've seen proof (through benchmarking and
observations) that they help your situation and solve the bottlenecks
you've observed. attempting to tune a broker for performance by
switching on options "becau
can you explain the performance bottlenecks you're seeing for your use
case (heavy thread context switch, lock contention?)?
On Mon, Feb 24, 2014 at 2:17 AM, khandelwalanuj
wrote:
>>> I do not see a reason why you would want idle threads to be kept for a
> longer period, especially if there >> ar
well, i would take a look here about how redelivery works:
https://activemq.apache.org/redelivery-policy.html
essentially, a poison pill will be placed into a DLQ. check the docs
on DLQ for configuring your use case
On Sun, Feb 23, 2014 at 9:07 PM, rdifrango
wrote:
> It seems as if, if I use the
Try it out. And check the source. The source is your friend. We are an
open source community, and happy to be so.
On Tue, Feb 25, 2014 at 2:52 AM, xabhi wrote:
> Please respond
>
> -
> Abhi
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Slow-KahaDB-access-
No. You have to disable advisory support, and the
jms.watchTopicAdvisories=false needs to go on the client (or you can
setWatchTopicAdvisories(false) on the connectionFactory). You may also
want to disable creation of advisory topics via ActiveMQ authorization
security to enforce this policy (alth
what version of activemq?
On Wed, Feb 26, 2014 at 7:52 AM, fliot wrote:
> Hi,
>
> We run activemq web console + broker as a war app in tomcat, with "-Xms2048m
> -Xmx8192m -XX:MaxPermSize=3072m -Xss256k".
>
> We did follow JDBC persistence tutorial, and we use :
>class="org.springframework.be
What's the rest of your code trying to do with these APIs? See
BrokerService or BrokerFactoryBean as possible replacements, but maybe
a quick explanation of what you're trying to do would help.
On Thu, Feb 27, 2014 at 6:46 AM, tvijayram wrote:
> Hi,
>
> I am currently using *Activemq-3.2.2* versi
interesting. are you looking at the topic itself? what about for the
TopicSubscription?
On Thu, Feb 27, 2014 at 10:49 PM, khandelwalanuj
wrote:
> Hi,
>
> ActiveMQ version : 5.8
>
> Problem: Inflight count is not going down for topics once consumer is
> disconnected.
>
> Test Scenario: When there
so your websocket clients can connect to the broker via the broker's
WS transport connector. WS is not a client transport to be used in
java code. take a look at jetty's websocket impl for the client side
(or some other imp) if you want to use websockets as the transport
from a java client. however
On 02/28/2014 07:46 AM, racarlson wrote:
have installed activemq and connected it to mysql - I can see three new
activemq tables created by activemq in mysql. I then run a test program to
put persistent messages onto the Q - however they do not show up in queries
of the mysql database. Do I hav
have installed activemq and connected it to mysql - I can see three new
activemq tables created by activemq in mysql. I then run a test program to
put persistent messages onto the Q - however they do not show up in queries
of the mysql database. Do I have to do some specific configuration for the
I was debugging. I generated the war and I deployed it in the tomcat7 server
but the exception is thrown too.
The broker is listenint ws and tcp transport. I tried to change the url
connection using tcp instead ws and it works, but when I use the ws
transport the exception is thrown.
I'm using ac
12 matches
Mail list logo
