"[EMAIL PROTECTED]" wrote : You haven't posted your configuration that shows you have
1000 mdbs.
|
| Most likely you have configured the pool and not the most important part
| which is the serversession pool (default size 15).
| See the FAQ topic for some examples.
|
messag
When we were using JBoss 3.2.2 it also hang after more than 1000 messages. This was
solved by using 3.2.3.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3828836#3828836
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3
I did some tests, one with a time-to-live of 20 seconds and one with a time-to-live of
120 seconds. When the time-to-live is 120 seconds all requests (approx. 1600 in 8
minutes) are handled by a MDB. But with 20 seconds approx 25% expire on the topic and
are therfore never handled by a MDB.
I c
"[EMAIL PROTECTED]" wrote : This looks like the cause of your problem:
|
| 2004-04-01 14:31:10,812 TRACE [org.jboss.mq.server.BasicQueue] message expired:
6530 msg=2428 hard NOT_STORED PERSISTENT queue=TOPIC.testTopic.ID:3.-2147483648
priority=1 hashCode=23099805
|
| The message is pass
I've changed the cache size settings. No memory problems are logged anymore. But the
problem of the disappearing messages still exist.
Below a new log (hope it is not too big). The message with ID 1080826270812105 is sent
to the topic, but it never seems to actually be added to the topic.
2004
"[EMAIL PROTECTED]" wrote : But the default message cache size is 50M and 60M see
persistence service.
| Once memory exceeds 50M you will hit the stage where jbossmq tries to move
| messages onto disk trying to keep memory below 60M.
|
| Regards,
| Adrian
Ah, I see. I've changed the hs
"[EMAIL PROTECTED]" wrote : You haven't posted the log all the way through to
conclusion.
| You should see
| RETURN: addMessage
| when the add message has finished.
|
| In the second log, you have the problem that memory is tight so JBossMQ is
| pushing messages onto disk.
| 2004-0
Hi,
JBoss version 3.2.3
We've a system with a session bean that publishes messages on a topic. Message driven
beans are subscribed to the topic. The system works fine if a approx 3 messages per
seconds are posted. When more messages are posted, messages appear to disappear. They
are sent to th
"[EMAIL PROTECTED]" wrote : This was a known bug with 3.2.2, try 3.2.3
|
| If you have configured the MessageCache to aggressively soften it can
| thrash trying to soften persistent messages that don't need to be softened.
|
| Regards,
| Adrian
|
Thanks. We're installing 3.2.3 rig
When i log the mq the following lines keep repeating for thousands of times:
...
2004-03-26 18:20:03,937 TRACE [org.jboss.mq.server.MessageReference] makeSoft lock
aquire 4268 msg=8250 hard NOT_STORED PERSISTENT queue=QUEUE.testQueue priority=4
hashCode=12569355
2004-03-26 18:20:03,937 T
Dump (small part)
Full thread dump Java HotSpot(TM) Client VM (1.4.2_03-b02 mixed mode):
"RMI ConnectionExpiration-[192.168.25.32:]" daemon prio=5 tid=0x037b9a28 nid=0x72c
waiting on condition [ac7f000..ac7fd88]
at java.lang.Thread.sleep(Native Method)
at sun.rmi.transport.tc
Btw it is running on:
Windows 2000
j2sdk 1.4.2_03
the messages are non-persistent
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3827636#3827636";>View
the original post
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3827636>Reply
to the post
---
Hi,
We're using jboss 3.2.2 and depend heavily on JMS.
A request is received by a session bean which sends it to a topic, a MDB does some
things and sends a message to a queue. Another MDB gets this message, also does some
things and returns it.
After approx. 1000-2000 requests JMS appears t
13 matches
Mail list logo
