Yah, excellent. If it still doesn't work, post your route and configs and I
can give it a shot for you on my side.
Christian
On Thu, Oct 11, 2012 at 8:33 AM, guerra wrote:
> Thanks and yes, I think you are fully right. It must be camel is building
> up
> the memory. In fact that is what it show
Thanks and yes, I think you are fully right. It must be camel is building up
the memory. In fact that is what it shows up on the camel monitor anyway!. I
was confused myself!
I was reading your link and it looks promising alright. I looked up the
"Database Sample" and it seems that it could solve
Hi,
I am designing a system around an embedded broker using file-based
cursors. I am trying to make sure I understand the way file-based
cursors work: Am I right in thinking that temporary files is
functionally the same as memory with respect to transactions and data
security? If the system was t
In the printed copy that I have, it's pp132/133.
But yes, building custom security plugin is the right section :)
On Thu, Oct 11, 2012 at 6:43 AM, Praveen Bysani wrote:
> Hi,
>
> Thanks for the suggestion. The pp 132-133, in the book you referred to has
> something related to JDBC tables and
Within the broker, if your messages are marked persistent, they will be
stored on disk (in your KahaDB) until they are delivered to a consumer and
the consumer acks them.
It sounds like your camel route is building them up in memory, not the
broker.
Run your route in a transaction so that when ca
Hi,
Thanks for the suggestion. The pp 132-133, in the book you referred to has
something related to JDBC tables and Message store. Are you referring to
the section that explains about building custom security plugins ?
On 11 October 2012 20:58, Christian Posta wrote:
> Not sure if this is direc
The broker is queueing up messages in RAM. When I start the database again
the messages are dequeued and sent okay to the database, but from memory. I
am using the camel monitor and the seda queue is building up messages
continuously . My point is why this messages are not stored on disk and if
the
So it sounds like the camel route is consuming from an activemq queue and
dumping to DB. And then when the DB goes down, the camel route is consuming
them and holding them in memory (since the DB is down)? Or it's not
consuming them and they're getting queued up in the broker?
On Thu, Oct 11, 2012
Not sure if this is directly configurable out of the box, but it's
definitely something that can be addressed.
For some of these highly specific use cases, ActiveMQ was written to be
pluggable. You can plug in a broker filter that does exactly what you're
looking to do. ActiveMQ in Action has a gre
Just curious if you can explain a little more about what you mean by "same
code but run separately" "because of the messages mixture"
A broker can handle all kinds of different message types and applications,
so running multiple brokers per app might not make sense. You can also open
up different
Yep, that's related to this:
https://issues.apache.org/jira/browse/AMQ-4098
On Wed, Oct 10, 2012 at 5:00 AM, lernen.2007
wrote:
> Hi,
>
> I download the new version but if I start the activemq in linux 64 bit then
> I get the following exception to see:
>
>
> apache-activemq-5.7.0/bin/linux-x
Hi,
I've a ActiveMQ broker to insert messages into the Oracle database. I have a
working version with a JDBC camel component and it is inserting messages
into it. So, no problems so far.
Now the scenario is, JMS messages have the PERSISTED flag enabled, KahaDB is
also setup and apparently message
12 matches
Mail list logo
