Topic
  • 6 replies
  • Latest Post - ‏2005-08-04T14:41:56Z by SystemAdmin
SystemAdmin
SystemAdmin
684 Posts

Pinned topic mysterious problem

‏2005-07-28T10:47:27Z |
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
Updated on 2005-08-04T14:41:56Z at 2005-08-04T14:41:56Z by SystemAdmin
  • SystemAdmin
    SystemAdmin
    684 Posts

    Re: mysterious problem

    ‏2005-08-01T09:59:00Z  
    Hi,

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

    regards,
    Vijay Raj K
    <kma_mousa@yahoo.com> wrote in message
    news:319722565.1122547677409.JavaMail.wassrvr@ltsgwas007.sby.ibm.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

  • SystemAdmin
    SystemAdmin
    684 Posts

    Re: mysterious problem

    ‏2005-08-01T15:48:06Z  
    Hi,

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

    regards,
    Vijay Raj K
    <kma_mousa@yahoo.com> wrote in message
    news:319722565.1122547677409.JavaMail.wassrvr@ltsgwas007.sby.ibm.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

    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)
  • SystemAdmin
    SystemAdmin
    684 Posts

    Re: mysterious problem

    ‏2005-08-03T06:00:55Z  
    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)
    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
    <kma_mousa@yahoo.com> wrote in message
    news:134616965.1122911322042.JavaMail.wassrvr@ltsgwas007.sby.ibm.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)

  • SystemAdmin
    SystemAdmin
    684 Posts

    Re: mysterious problem

    ‏2005-08-03T07:12:41Z  
    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
    <kma_mousa@yahoo.com> wrote in message
    news:134616965.1122911322042.JavaMail.wassrvr@ltsgwas007.sby.ibm.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)


    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
  • SystemAdmin
    SystemAdmin
    684 Posts

    Re: mysterious problem

    ‏2005-08-04T08:10:36Z  

    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
    ActiveSync 3.8.0 is known for these type of Connection problems

    Vijay

    <kma_mousa@yahoo.com> wrote in message
    news:167580720.1123053196802.JavaMail.wassrvr@ltsgwas007.sby.ibm.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

  • SystemAdmin
    SystemAdmin
    684 Posts

    Re: mysterious problem

    ‏2005-08-04T14:41:56Z  
    ActiveSync 3.8.0 is known for these type of Connection problems

    Vijay

    <kma_mousa@yahoo.com> wrote in message
    news:167580720.1123053196802.JavaMail.wassrvr@ltsgwas007.sby.ibm.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

    So which version of ActiveSync should be the most reliable to use with MQe? Or do I have to use a network?

    thanks for your help Vijay :o)