Java client doesnt work with https

HI, I am trying to getting java consumer work over https. In my aactivemq.xml at broker side, i have configured ssl and https transport connectors, https://localhost:8443"/> At the consumer side (java client), I am specifying the connection factory as, ActiveMQConnectionFactory factory =

Pending Messages, but Browsing Queue Shows No Messages

Hello All, I am looking for some help in troubleshooting an ActiveMQ installation. We are running ActiveMQ 5.4.2 on Linux on Java 1.6.0.25 using Java Hot Spot 64-bit Server VM. We're using KahaDB as our persistent store and we have pre-fetch values set to 3000 for these consumers. We're running ab

Re: Prefetch problem/misuderstanding.

the connection.createSession("true" in the consumer should have been false, but the problem remains. -- View this message in context: http://activemq.2283324.n4.nabble.com/Prefetch-problem-misuderstanding-tp4222551p4222555.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Prefetch problem/misuderstanding.

Hi all, I am having an issue and I'm not sure whether it's my misunderstanding of ActiveMQ prefetch or if I'm doing something wrong. Basically I want to slow down my consumer by prefetching 10 messages and having no more messages incoming until I send acknowledges back. From my reading on the Act

Re: Backlog data causes producers to slow down.

@ harry143, not easily. Do you have a test case you can share... would like to get to the bottom of this but it would be great to have some shared code that correctly captures the use case. Something in Junit would be ideal. On 21 December 2011 16:23, harry143 wrote: > Yea i tried With optimized

Re: Backlog data causes producers to slow down.

Yea i tried With optimizedDispatch="false" as well as "true".But it really did not affect much. The problem of degradation in producer throughput remained. @gary : hey you mentioned in your previous post that producer and consumer share a common resource "consumer dispatch queue " . Is it also the

Re: Backlog data causes producers to slow down.

Gary, I moved on to HornetQ as our underlying transport technology after we were not able to debug/fix this particular issue. I tried looking into the code etc. Best Bhupesh On Wed, Dec 21, 2011 at 2:20 AM, Gary Tully [via ActiveMQ] < ml-node+s2283324n4221130...@n4.nabble.com> wrote: > @Bhupes

Re: failover invalid connect parameters

That is because XML has some 'special characters' that need encoding; see http://en.wikipedia.org/wiki/List_of_XML_and_HTML_character_entity_references On 21 December 2011 12:37, liny wrote: > Hi, Gary: > > Thanks for reply. > I changed to > > Yes, I must use "&" to replace "&", can't just use "&

Re: failover invalid connect parameters

Hi, Gary: Thanks for reply. I changed to Yes, I must use "&" to replace "&", can't just use "&" in your broker URL. That's very strange! -- View this message in context: http://activemq.2283324.n4.nabble.com/failover-invalid-connect-parameters-tp3923668p4221517.html Sent from the ActiveMQ - Us

Re: failover invalid connect parameters

have a look through some of the usage in the tests. I gave google code search a whirl to pull them out, the result is reasonable: http://www.google.com/codesearch#search/&q=%22failover%22%20lang:%5Ejava$%20license:%5Eapache$%20activemq&type=cs On 21 December 2011 09:58, liny wrote: > Hi, > > I do

Re: Backlog data causes producers to slow down.

@Bhupesh, the prefetch may be part of the problem, as by default the broker will try and dispatch 1000 messages to each consumer. If the consumer (stomp connection) is short lived, this is a waste of resources. A consumers acks, will contend message production to some extent, this is expected as t

Re: failover invalid connect parameters

Hi, I don't understand why below two broker URLs don't work: I still get Any help is appreciated -- View this message in context: http://activemq.2283324.n4.nabble.com/failover-invalid-connect-parameters-tp3923668p4221073.html Sent from the ActiveMQ - User mailing list archive at Nabble

Re: Backlog data causes producer to slow down.

Hi Torsten, yea i tried with optimizedDispatch="false" also. And i am using queue. Here is my kahaDb settings : And i also tried with enableIndexWriteAsync="false" but nothing changes much. Also when i ran profiler then i found out when the consumer starts for the first time the

Re: Backlog data causes producer to slow down.

Hard to say what exactly the problem is. In the past I got to learn the optimizedDispatch="true" isn't always a good choice. Can you try without it? In addition I recently found that enableIndexWriteAsync="true" on your kahadb config may not bring any performance improvement. Not sure if you hav