MaxMessages - is not respected?

[dhartford]

Hey all,
Been trying to setup some MDB's to process ONLY one message at a time. To be more specific, process only one message until that message is complete, or is sent to the DLQ.

Here is the configuration I've added to standardjboss.xml under MDB, but this does not seem to work:

<container-invoker-conf>
<MaxMessages>1</MaxMessages>
<Optimized>True</Optimized>
</container-invoker-conf>

Please advise if processing a single message at a time is possible with JbossMQ, and how to do it.
-D

[duslow]

You also need to set the following in your invoker-proxy-binding as well.

1
1

[duslow]

Sorry, the xml got stripped off in the previous post.

<MaximumSize>1</MaximumSize>
<MaxMessages>1</MaxMessages>

[adrian.brock]

You also need to read the bloody FAQ rather than wasting people's time.

[dhartford]

Thank you for your positive feedback Adrian. I did find the answer in the FAQ, although I really needed to know what the answer was first before I could find it. The FAQ is a one-place with everything in it and it is rather difficult to sort through it all. And yes, I also have the pay-for docs.

At any rate, I'm asking this question again (I asked it previously about a year ago) and still do not understand why if I do configure in standard-jboss.xml with:

<MaximumSize>1</MaximumSize>
<MaxMessages>1</MaxMessages>

as to why I'm still processing my 15 items all together instead of one at a time. To be more specific, process only one message until that message is complete, or is sent to the DLQ. Should I be required to write my own Singleton to manage the process? Is this configuration something that is not normally handled by a JMS provider?

[adrian.brock]

You get what you deserve.
The FAQ is there to stop idiots like you continually posting these stupid/repeat questions.

Unlike you I can use search, so I know you are using 3.2.x (even though
you neglect to include any context in this post - not even for your config change,
you could have added those two lines anywhere).

From the little context you have posted and the fact you are using 3.2.3,
I will ask you which part of this sentence in the FAQ you didn't understand?

NOTE: invoker-proxy-bindings apply only to 3.2.x+. In 3.0.x this configuration
was in the container-invoker-conf

The reason why you get so few answers is:
1) Your question is answered many times before
2) Your barrier to entry is too high, think how you would try to answer your own question with so little information to work with?