How To Figure Out why the code that sends to a queue is slow

[newway]

Hello All,

I need some pointers on where to check why my code that handles sending to a queue is slow.

this is the scenario I have:

• there are about 60,000 messages that are sent
• each message goes through several components and queue
• but I am not sending the whole 60,00 in one bit - I divide them into chunks of 100 each time
  • potentially 100 messages can be sent every 10 seconds to the first queue, but the sending of a new chunk isn't initiated if the previous chunk wasn't fully delivered to the queue
• The logic of the sending is as follows
  • get 100 Id's to be sent
  • loop over the id's
    • get the entity correlated to the id from the DB - average time 10 milliseconds
    • send a message to the queue that contains only the ID - average time 900 milliseconds
      • session.createObjectMessage() - average time 300 milliseconds
      • producer.send(objectMsg) - average time 600 milliseconds

the session and producer instances are created and closed for each chunk of 100 messages

so - do you have any idea what should I check? queues configuration? paging? ...?

Thanks,

Noa

[raydecampo]

Have you tried hooking up a profiler to see where the process is spending the most time?

[jbertram]

Couple of questions...

• Is your code running inside the container or outside?
• What connection factory is it using?
• Is it sending persistent messages?
• How large are the messages?
• Can you attach the related code?
• Can you attach your standalone*.xml?

[newway]

I think I managed to set up the system.

basically I have one persistent Q and 4 other Qs that are not persistent.

but I thought that setting the delivery mode of the producer to DeliveryMode.NON_PERSISTENT is not enough - I added <durable>false</durable> to the 4 non persistent Qs and now every thing is flying