Unable to receive(consume) messages grater than 500k
Hi!
We are using following configuration:
Sun ONE Standard Edition App server ver 7.03c and Sun ONE MQ server 3.5 Enterprise SP1. We installed all three servers on three different Sun Blade 1500 WS with all recomended software (j2se and Solaris).
First application server puts response from the database into MQ destination. Destination does not have limit on message size. That answer is grater than 500kB. Answer is succesfully stored into destination.
Here is the problem. Second Application server async. polls those answers from the MQ destination. We are unable to receive(consume) those large messages. No exception or error is reported on Application server or MQ server log files.
There is no problem with messages <=500kB.
What is the problem?
[806 byte] By [
Pajton] at [2007-11-25 18:26:19]
# 1
There shouldn't be an issue with the message size. I'm wondering if something else is going on and it just appears to be related to message size. Some common reasons that could cause this symptom:
1. Message expiration is set (TTL) and the messages are expiring. If you use message expiration make sure the clocks are synchronized on all systems.
2. The message is produced in a transaction and the transaction is not committed.
3. The consumer uses a message selector that has an error and the selector is not matching.
4. The consumer is mistakenly configured to consume off of the wrong destination.
5. Some configured limit is being reached (destination size, max # of messages in broker, etc).
I would inspect the destination with MQ's imqcmd command and verify the message is on the destination after production. Then start the consumer and see if the message stays on the destination or is removed.
Double check the MQ broker's log file to make sure there are no errors or other messages informing of message expiration, etc.
Joe
jfddp at 2007-7-3 18:29:51 >
# 2
Hi Joe!
1. Message does not expire. It is still present in the MQ destination after several days.
2. We are not using transactions.
3. We are using right msg selector.
4. We are using right destination.
5. All configuration settings are set to unlimited.
I forgot to state that the test case (same destination and msg selector), which triggers database to respond with msg that is less that 500kB, passes succesfully.
