MSMQ Adapter

Home Page › Forums › BizTalk 2004 – BizTalk 2010 › MSMQ Adapter

Viewing 2 reply threads
  • Author
    Posts
    • October 10, 2008 at 10:24 AM #20948
      community-content

         Hi,

        In my application I am using MSMQ Recieve port and Send Ports. The response time from picking up the document from queue and sending the response back to another queue is almost 15 secs which is not acceptable with my users.

        What options do I have. My collegue is suggesting to replace MSMQ with something else.. and I don’t know what something else is.. any suggestions..

        Thanks

      • October 10, 2008 at 11:04 AM #20950
        community-content

           

           HI I am also facing the same can you please help me here…

          I am passing a message to MQseries by setting up MQSeries.Msg-ID and MQSeries.Coor_id. The message is placed on queue and i am trying to consume same message within the same orchestration using diffrent receive port i could able to consume the message but the message is not moved to my out folder.

          I get an error…

          Event Type: Error
          Event Source: BizTalk Server 2006
          Event Category: BizTalk Server 2006
          Event ID: 5778
          Date:  10/10/2008
          Time:  10:44:30 AM
          User:  N/A
          Computer: XXXXXXX
          Description:
          The Messaging engine failed to process a message submitted by adapter:MQSeries Source URL:MQS://198.238.39.12/TQM/OFM.TQM.GCLM.PORTAL.TESTING. Details:The published message could not be routed because no subscribers were found. This error occurs if the subscribing orchestration or send port has not been enlisted, or if some of the message properties necessary for subscription evaluation have not been promoted. Please use the Biztalk Administration console to troubleshoot this failure.

          Please help me as i need to meet the dead line…..

        • October 10, 2008 at 11:07 AM #20951
          community-content

             

            MQAdapter Problem…

            I am passing a message to MQseries by setting up MQSeries.Msg-ID and MQSeries.Coor_id. The message is placed on queue and i am trying to consume same message within the same orchestration using diffrent receive port i could able to consume the message but the message is not moved to my out folder.

            I get an error…

            Event Type: Error
            Event Source: BizTalk Server 2006
            Event Category: BizTalk Server 2006
            Event ID: 5778
            Date:  10/10/2008
            Time:  10:44:30 AM
            User:  N/A
            Computer: XXXXXXX
            Description:
            The Messaging engine failed to process a message submitted by adapter:MQSeries Source xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx. Details:The published message could not be routed because no subscribers were found. This error occurs if the subscribing orchestration or send port has not been enlisted, or if some of the message properties necessary for subscription evaluation have not been promoted. Please use the Biztalk Administration console to troubleshoot this failure.

            Please help me as i need to meet the dead line…..

            • October 10, 2008 at 11:51 AM #20953
              community-content

                I receieved such kind of messages almost 50 times from the time I started with Biztalk. But each a different solution worked..

                Here are the options:

                1) In your send ports .. Under Filters try BTS.ReceivePortName = [YourReceivePortName]

                2) Terminate all the running and suspended instances

                3) Restart the host instance.

                4) Check the Queue name.That helped me lot of times

                5) Try to delete evreything and try redoing it.. may you are doing something wrong if you are a beginner.. That helped me as I am a beginner myself.

          • Author
            Posts
          Viewing 2 reply threads
          • The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.