mysterious problem

[k***@yahoo.com]

Hi all,
I have an async. remote queue on my pocketPC 2002 pointing to a queue on my PC (the PPC is connected via a cradle & ActiveSync). I also have a sync. queue defined to be able to send messages from the PC to the PPC.
On the PPC I use Native C, and I use Java on the PC. I defined a thread on the PPC to listen to messages arriving from the PC, and defined a message listener on my PC to receive messages from the pocket.
Wheneve I call mqeQueueManager_putMessage on the pocket, I call mqeQueueManager_triggerTransmission right after it. Everything works fine for a number of messages from the pocket to the PC and vice versa.
The problem is, after a number of messages, the pocket just freezes after I attempt to send a message through the async queue, it freezes completely that I must reset the pocket. Sometimes the application just exits instead of freexing.
I cannot think of the reason causing this strange behavior, I would appreciate any help from you,,

thanx,
bye

[vijay]

Hi,

Can you pls tell me what version of Active Sync are ou using?

regards,
Vijay Raj K

Post by k***@yahoo.com
Hi all,
I have an async. remote queue on my pocketPC 2002 pointing to a queue on

my PC (the PPC is connected via a cradle & ActiveSync). I also have a sync.
queue defined to be able to send messages from the PC to the PPC.

Post by k***@yahoo.com
On the PPC I use Native C, and I use Java on the PC. I defined a thread on

the PPC to listen to messages arriving from the PC, and defined a message
listener on my PC to receive messages from the pocket.

Post by k***@yahoo.com
Wheneve I call mqeQueueManager_putMessage on the pocket, I call

mqeQueueManager_triggerTransmission right after it. Everything works fine
for a number of messages from the pocket to the PC and vice versa.

Post by k***@yahoo.com
The problem is, after a number of messages, the pocket just freezes after

I attempt to send a message through the async queue, it freezes completely
that I must reset the pocket. Sometimes the application just exits instead
of freexing.

Post by k***@yahoo.com
I cannot think of the reason causing this strange behavior, I would

appreciate any help from you,,

Post by k***@yahoo.com
thanx,
bye

[k***@yahoo.com]

version 3.8.0

I've solved the hanging up problem (it seemed to be happening because I stop the QM in the wonr time or something, I'm not quite sure yet!)
currently everything is going fine for ~20 msgs then no msgs reach the PC until I restart the application.
in the MQe docs it says
"If a remote queue definition and the remote queue do not match, then it
is possible that a message may become undeliverable. In this case the message is
not lost, but remains stored on the local queue manager."
Could this be my problem? (I dont understand what it means that the definition doesn't match the queue)

[vijay]

Hi,
Guess the remote queue definition is correct.Otherwise even at restart
the msgs will not reach other end.
Remote queue definition mismatch means eiher a wrong Qm name or a wrong
queue name while the creation of remote Queue.(Even though this definition
is correct, it is possible that the corresponding connection definition is
not correct,then msgs will not be delivered.In your case every thing looks
fine)

You need to ensure triggerTransmission is been called correctly or will
be worth writing a rule such a way that for every
message(or even after 5-6 msgs) put, it will call the triggerTransmission

regards,
Vijay

Post by k***@yahoo.com
version 3.8.0
I've solved the hanging up problem (it seemed to be happening because I

stop the QM in the wonr time or something, I'm not quite sure yet!)

Post by k***@yahoo.com
currently everything is going fine for ~20 msgs then no msgs reach the PC

until I restart the application.

Post by k***@yahoo.com
in the MQe docs it says
"If a remote queue definition and the remote queue do not match, then it
is possible that a message may become undeliverable. In this case the message is
not lost, but remains stored on the local queue manager."
Could this be my problem? (I dont understand what it means that the

definition doesn't match the queue)

[k***@yahoo.com]

so its not ActiveSync 3.8.0 that is the problem?

I have a thread that calls triggerTransmission (and does other stuff), so I think this is not the problem

[vijay]

ActiveSync 3.8.0 is known for these type of Connection problems

Vijay

Post by k***@yahoo.com
so its not ActiveSync 3.8.0 that is the problem?
I have a thread that calls triggerTransmission (and does other stuff), so

I think this is not the problem