-
1. Re: large queue problems
toddhunter Jan 7, 2002 12:56 AM (in response to toddhunter)Sorry thats
<container-transaction>
<ejb-name>DocListener</ejb-name>
<method-name>*</method-name>
<trans-attribute>NotSupported</trans-attribute>
</container-transaction>
Everything works okay except for the memory and queue size. I figure the messages are not being acknowledged even though they are being received okay -
2. Re: large queue problems
toddhunter Jan 8, 2002 11:50 PM (in response to toddhunter)Sorry to bug, but can anyone help with this? It's being a big problem for me (and others too judging by the forums/mailing lists).
-
3. Re: large queue problems
toddhunter Jan 28, 2002 5:24 PM (in response to toddhunter)I made the change from rollinglogged to file as my persistance manager. I also upgraded to 2.4.4 (jboss)
This seems to have fixed my problems for me. Memory is now okay and there is no growing queue.
However, going through the docs, it seems rollinglogged is the one I want to be using. When I switch back I still get the log seemingly growing without bound even though no messages fail.
Any ideas now? -
4. Re: large queue problems
midday Jan 29, 2002 6:22 AM (in response to toddhunter)Hi,
I too am encountering a similar problem as the one you had posted in the
jboss forumn.
I am using a topic instead of a queue, it works fine but as the number of
messages increase,
the JMS stops publishing to the MDB and i seem to lose the messages. The
memory utilzation also is pretty high. I am currently using
JBoss-2.4.3_Tomcat-3.2.3 as my server.
Did you get any workarounds for this , will it help if i switch to JBOSS
2.4.4.
Sorry for the trouble......
Regards
Jack -
5. Re: large queue problems
dim Mar 19, 2002 1:06 AM (in response to toddhunter)Did either of you guys get around this?
-
6. Re: large queue problems
jaywright00 Mar 19, 2002 5:21 PM (in response to toddhunter)
How did you change your persistence management for the queue? I am using 2.4.4 and trying to turn it off altogether, but haven't had any luck identifying where I would change this.