ok, got it, so the persistent message don't get paged to database, because they
are saved to database already..
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4165548#4165548
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&
thanks for the quick response.
"Wellnot exactly, all messages will actually go in to the down cache however
only non persistent messages will get paged to the database. "
I am so confused by this above line. my understanding was : for non-persistent
messages, when the DownCache reaches the limi
It is getting to the point I wanted to know, really appreciate. still some
questions.
1. so if I set DeliveryMode=Persistent, the DownCacheSize which does the batch
paging is not useful any more, since it gets saved to database right away, is
it correct?
2. why is AUTO_ACKNOWLEDGE =slow ? I ca
thanks for the answer. here are my questions again:
1. are you talking about DeliveryMode.PERSISTENT ? if I choose to use database
persistence, why do I still have to set this property?
as mentioned in your last post, it will get lost if it has not been paged to
database yet, if I don't set it
I was talking about database persistent messages.
when DownCacheSize=1, client puts 5000 messages in the queue, the client
finishes sending, then I check right away, queue size from jmx console shows
5000, but database jbm_msg table shows size still 2000, but it is increasing,
so if I res
if Downcachesize is set to 1 and the messages are cached in the memory in
queue until it reaches count=1, will the messages get lost if the server
is restarted in the middle?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4164639#4164639
Reply to t
can we use jboss messaging with other application server? such as OC4J?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4155839#4155839
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4155839
___
set messagechuck =1 still won't work with really large queue. even the keys can
blow the system itself
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4153082#4153082
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4153082
you need to set your message to expire after certain number processing, so the
top 100 messages will be removed from the table after certain time. this is
just a workaround, not a solution.
I think jboss has abandoned the this version jms impl, I saw the jboss
messaging has covered this Huge Qu
I am having the same issue. After I went through the source code, i found the
problem. it tries to select all messages for a queue and then evaluate the
memory mark, which definitely fail with millions of messages.
the work around I have so far is to change the select sql in jdbc2.xml to only
s
10 matches
Mail list logo
