G
Guest
Hello,
We are using MSMQ on Windows CE 4.1.
We are sending messages every 10 seconds to a private remote server queue.
The application is a C# application, and it uses a wrapper around MSMQ that
exposes one function for sending recoverable messages to that particular
queue. Each message is about 400-500bytes.
The MSMQ functions properly, until, at some moment, it simply stops sending
the messages, although the device is connected via GPRS. The new messages are
however stored by MSMQ until the maximum quota is reached. When the maximum
quota is reached, the wrapper returns MQ_ERROR_INSUFFICIENT_RESOURCES (fails
at call to MQSendMessage) for some time, and later it fails already by
calling MQOpenQueue.
In the MQLOGFILE.TXT I get the message:
"Reader thread for session mySession has been forcefully terminated. Memory
may have been leaked."
If the device is rebooted, MSMQ sends the messages that it has stored (if
there is a net connection) and it functions again properly for a while.
Is there any explanation for this behaviour? Could it be related to the
periodic cleanup of empty Message Queuing message files (does this apply to
MSMQ CE at all)?
Thank you,
Lucia.
We are using MSMQ on Windows CE 4.1.
We are sending messages every 10 seconds to a private remote server queue.
The application is a C# application, and it uses a wrapper around MSMQ that
exposes one function for sending recoverable messages to that particular
queue. Each message is about 400-500bytes.
The MSMQ functions properly, until, at some moment, it simply stops sending
the messages, although the device is connected via GPRS. The new messages are
however stored by MSMQ until the maximum quota is reached. When the maximum
quota is reached, the wrapper returns MQ_ERROR_INSUFFICIENT_RESOURCES (fails
at call to MQSendMessage) for some time, and later it fails already by
calling MQOpenQueue.
In the MQLOGFILE.TXT I get the message:
"Reader thread for session mySession has been forcefully terminated. Memory
may have been leaked."
If the device is rebooted, MSMQ sends the messages that it has stored (if
there is a net connection) and it functions again properly for a while.
Is there any explanation for this behaviour? Could it be related to the
periodic cleanup of empty Message Queuing message files (does this apply to
MSMQ CE at all)?
Thank you,
Lucia.