browseMessages() method not picking up 1st msg in queue

[Randy N. Villa]

The call to MQeQueueManager.browseMessages() is not properly including the
1st message in the local queue when returning an MQeEnumeration of
messages. It's always skipping the 1st message that gets previously
generated in an empty queue. Also, the 1st message has a bigger file size
for it's header file, i.e. 71 bytes vs. 56 bytes for other messages. Could
this be reason why it's not being included in the enumeration?

Any help is appreciated. Currently using MQe v2.0.1.10. Regards.

[Raja Sreenivasan]

Hi Randy,
The MQeQueueManager.browseMessages() fetches copy of all the messages in the queue specified. This method uses a MQeAttribute parameter to verify(filter) before fetching the message. If the MQeAttribute value is passed as null, then it fetches all the messages irrespective of the filter set in the message.

The only case this method wont get some message is if the message filter check is failed.

Can you give me the details of what filters being set to the first message and what filter is used to browse message, also the recreate scenario for this. So that I can come back with relavent information on the problem and solution for the same.

regards
Raja
"Randy N. Villa" <***@us.ibm.com> wrote in message news:e4sv0m$2f806$***@news.boulder.ibm.com...

The call to MQeQueueManager.browseMessages() is not properly including the 1st message in the local queue when returning an MQeEnumeration of messages. It's always skipping the 1st message that gets previously generated in an empty queue. Also, the 1st message has a bigger file size for it's header file, i.e. 71 bytes vs. 56 bytes for other messages. Could this be reason why it's not being included in the enumeration?

Any help is appreciated. Currently using MQe v2.0.1.10. Regards.

[Raja Sreenivasan]

Hi,
The filter parameter is MQeFields and not MQeAttribute.

Regards
Raja
"Raja Sreenivasan" <***@in.ibm.com> wrote in message news:e4uo3k$2as3e$***@news.boulder.ibm.com...
Hi Randy,
The MQeQueueManager.browseMessages() fetches copy of all the messages in the queue specified. This method uses a MQeAttribute parameter to verify(filter) before fetching the message. If the MQeAttribute value is passed as null, then it fetches all the messages irrespective of the filter set in the message.

The only case this method wont get some message is if the message filter check is failed.

Can you give me the details of what filters being set to the first message and what filter is used to browse message, also the recreate scenario for this. So that I can come back with relavent information on the problem and solution for the same.

regards
Raja
"Randy N. Villa" <***@us.ibm.com> wrote in message news:e4sv0m$2f806$***@news.boulder.ibm.com...

The call to MQeQueueManager.browseMessages() is not properly including the 1st message in the local queue when returning an MQeEnumeration of messages. It's always skipping the 1st message that gets previously generated in an empty queue. Also, the 1st message has a bigger file size for it's header file, i.e. 71 bytes vs. 56 bytes for other messages. Could this be reason why it's not being included in the enumeration?

Any help is appreciated. Currently using MQe v2.0.1.10. Regards.

[Randy N. Villa]

Hi Raja,

A null value is passed for the filter parameter, i.e. no filter is being
used. Also, the 1st message is generated similarly as the other messages.

Thanks.

Randy