MDB with message selector only processes 2 messages at a time

[seacuke23]

I have a HornetQ queue and I've put 100 messages on it each with a 'name' property set to either F1, F2, F3, F4 or F5...evenly distributed...20 each.  I've set up an MDB and added a message selector.

        <activation-config-property>
          <activation-config-property-name>messageSelector</activation-config-property-name>
          <activation-config-property-value>name = 'F1'</activation-config-property-value>
        </activation-config-property>

I wanted to confirm that I would be able to control the number of MDBs I get when selecting messages so I just put a 5 second sleep in the onMessage.

    public void onMessage(Message message) {
        TextMessage msg = null;
        try {
            if (message instanceof TextMessage) {
                msg = (TextMessage) message;
                System.out.println("Received Message: " + msg.getText());
            } else {
                System.out.println("Message of wrong type: "  + message.getClass().getName());
            }
        } catch (JMSException e) {
            throw new RuntimeException(e);
        }
        try {
            Thread.sleep(5000);
        } catch (InterruptedException e) {
            e.printStackTrace();
        }
    }

It doesn't seem to matter what I do...whether it's setting maxSession to 100, increasing all my AS thread pools to 500, I only get a max of 2 messages at a time. 

10:29:06,098 INFO  [stdout] (Thread-1 (HornetQ-client-global-threads-227391438)) Received Message: This is message 1
10:29:06,099 INFO  [stdout] (Thread-2 (HornetQ-client-global-threads-227391438)) Received Message: This is message 1
10:29:11,102 INFO  [stdout] (Thread-1 (HornetQ-client-global-threads-227391438)) Received Message: This is message 1
10:29:11,104 INFO  [stdout] (Thread-2 (HornetQ-client-global-threads-227391438)) Received Message: This is message 1
10:29:16,108 INFO  [stdout] (Thread-1 (HornetQ-client-global-threads-227391438)) Received Message: This is message 1
10:29:16,110 INFO  [stdout] (Thread-2 (HornetQ-client-global-threads-227391438)) Received Message: This is message 1
10:29:21,113 INFO  [stdout] (Thread-1 (HornetQ-client-global-threads-227391438)) Received Message: This is message 1
10:29:21,115 INFO  [stdout] (Thread-2 (HornetQ-client-global-threads-227391438)) Received Message: This is message 1

However, when I remove the selector altogether, I get every single message...which is why I'm posting in the HornetQ forum.  When I set maxSession to 1 it only processes 1 at a time, but when I set maxSession to anything over 2 it gets 2 at a time.  Is there something I'm missing?

Here's the version printout on server startup:

10:28:51,807 INFO  [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-13) HornetQ Server version 2.2.13.Final (HQ_2_2_13_FINAL_AS7, 122) [1930ddca-8d6d-11e1-bdd4-2c41389967d9]) started

[ataylor]

how big is your MDB pool size?

[seacuke23]

This is from my standalone-full:

            <mdb>
                <resource-adapter-ref resource-adapter-name="hornetq-ra"/>
                <bean-instance-pool-ref pool-name="mdb-strict-max-pool"/>
            </mdb>
            <pools>
                <bean-instance-pools>
                    <strict-max-pool name="slsb-strict-max-pool" max-pool-size="100" instance-acquisition-timeout="5" instance-acquisition-timeout-unit="MINUTES"/>
                    <strict-max-pool name="mdb-strict-max-pool" max-pool-size="500" instance-acquisition-timeout="5" instance-acquisition-timeout-unit="MINUTES"/>
                </bean-instance-pools>
            </pools>

Is that what you're looking for?

[ataylor]

maybe you should provide a test

[seacuke23]

Here's an example.  What I'm experiencing is with the message selector in the ejb-jar it seems to be processing 2 requests at a time and without, it pulls every message.  I've jacked up the maxSession to take that out of the equation.  I've included server startup logs and my config file in case there's any info in there that interests you.

I send this to the webservice to kick it off:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:nb="http://www.jboss.com/jbossas/quickstarts/wsat/simple/nb">
   <soapenv:Header/>
   <soapenv:Body>
      <nb:receiveRequest/>
   </soapenv:Body>
</soapenv:Envelope>

Thanks for taking the time to help me out!

[clebert.suconic]

Try diminishing the consumerWindowSize, set it to 0.

What probably happened was:

- the MDB is creating one Consumer and it will batch all the messages up to the consumer-window-size

- Same thing on the second consumer (or second instance)

- By the time it created the third, all the messages are already buffered

if you have slow consumers, you need to disable client caching.

[seacuke23]

Thank you both for looking at this for me........really appreciate it!

[ataylor]

If you give me some instructions on how to run your test I will take a look today

[clebert.suconic]

@Andy: I think he fixed his issue. He marked my answer as the correct answer.

[seacuke23]

Yes, sorry for the delay.  Disabling the client caching resolved the problem.  If you're still interested in recreating it you could just deploy the test.jar I provided above and copy the queue configuration from my standalone-full...there should be a webservice that shows up under the deployment...hit it with the soap provided earlier in the thread.

Thanks again you two for your assistance.

[clebert.suconic]

Well.. it is not a bug, so no need to replicate it.

If you set the client to cache, you are expected to have it caching. It's more performant. But if you have slow consumers performance doesn't really matter hence you have to disable it explicitly.