On 7 Jan 2010, at 22:12, jongraf wrote:
1) So when onMessage() is called, it is actually coming from the
prefetch?
Yes - which by default is 1000
2) I'd like to take the messages from the queue and put them in a
collection
and send that collection to my REST service, this way I only nee
On Thu, 2010-01-07 at 15:11 -0800, Jim Lloyd wrote:
> Whoops! Sorry, I meant to hit save and not send, since I suddenly realized
> what might be the cause of my problem. And indeed, I was right, so I no
> longer need assistance. But thanks anyway for replying quickly!
>
> My problem was indeed rel
Whoops! Sorry, I meant to hit save and not send, since I suddenly realized
what might be the cause of my problem. And indeed, I was right, so I no
longer need assistance. But thanks anyway for replying quickly!
My problem was indeed related to initializing the library, and I had figured
out that I
On Thu, 2010-01-07 at 14:27 -0800, Jim Lloyd wrote:
> I'm finally upgrading some applications to use activemq-cpp 3.1.1. We had
> been using 2.2.6
Great, let us know how it goes, lots of new features in there.
Make sure you take a look at the sample apps for some hints on the
changes, you need
I'm finally upgrading some applications to use activemq-cpp 3.1.1. We had
been using 2.2.6
1) So when onMessage() is called, it is actually coming from the prefetch?
2) I'd like to take the messages from the queue and put them in a collection
and send that collection to my REST service, this way I only need to make
one HTTP call. Do you think I'll be able to do this in my MessageListe
By default, ActiveMQ sends or streams messages to a consumer's local buffer
in batches. The batching of the messages can be controlled via the prefetch
limit. So AMQ pushes messages to the consumer as opposed to having the
consumer pull each message on demand.
http://activemq.apache.org/what-is-
On Thu, 2010-01-07 at 11:19 -0800, zdvickery wrote:
>
> Timothy Bish wrote:
> >
> > If you think you've found an issue then by all means open a new Jira
> > issue. We'd need a good description of the problem along with steps to
> > reproduce it and a sample app that demonstrates the problem if
>
Hello fellow developers,
I find myself in the midst of the age-old dilemma of needing to provide
scalable code where our load tests currently indicate that the code is
otherwise. I am coding a message-driven POJO. Originally I implemented the
queue using the Spring DefaultMessageListenerContain
Timothy Bish wrote:
>
> If you think you've found an issue then by all means open a new Jira
> issue. We'd need a good description of the problem along with steps to
> reproduce it and a sample app that demonstrates the problem if
> possible.
>
> When you say the TCP connect is getting close
On Thu, 2010-01-07 at 10:52 -0800, zdvickery wrote:
>
> Timothy Bish wrote:
> >
> > I'd need some more information on your setup to give you a definite
> > answer. Are you using the Failover transport? If so then the exception
> > listener is not notified if the connection is dropped, the Failo
Timothy Bish wrote:
>
> I'd need some more information on your setup to give you a definite
> answer. Are you using the Failover transport? If so then the exception
> listener is not notified if the connection is dropped, the Failover
> transport just sits in the background attempting to recon
12 matches
Mail list logo
