Immediate transfer configuration issue?

Jean-Philippe Plourde
Jean-Philippe Plourde
in AppWorks #1

We are setting up a file transfer between 2 entreprise node.

 

When invoking immediate transfer, we end up with blank files on the receiving node and the data portion ends up in the DLQ of the receiving QM. The transfer eventually times out and the transfer - of course - ends up in the Fixit because the receiving end didn't responded within the timeout value.

 

When looking at the messages DLH, we see that the MIM.FTS.IMMED.xxxxxx queue doesn't exist.

 

We do understand that the immediate transfer uses temporary dynamic queue, but can't figure out why it is not created.

 

Any idea?

Tagged:

Comments

  • Doug Johnson
    Doug Johnson
    #2

    I believe there is a model queue that needs to be in the MQ environment.  I'd double check that it was created.

  • Jean-Philippe Plourde
    Jean-Philippe Plourde
    #3

    We do have the MIM.TEMPORARY.MODEL queue in place.

     

    I didn't mention it originally but this is for MIM 8.5.2.

  • Ethan Beisher
    Ethan Beisher E Community Moderator
    #4

    It may be a MQ permissions error. Check the error log for Websphere MQ.  You may want to open a helpdesk ticket by clicking on the Support button on the top of this page.

  • Jean-Philippe Plourde
    Jean-Philippe Plourde
    #5

    Problem was resolved ; we had to increase the timeout values related to immediate transfer in the xmofts.xml and xmofts_client.xml.

     

    Our architecture imposes a delay that could go up to 50 seconds before the MQ message reaches it's destination. So, It turn out that the temporary queue was created correctly but was deleted before the data was put in. When data messages finally arrived, the queue was already gone.

     

    Increasing the timeout values corrected the behavior.

Categories

image
OpenText CE Products
AppWorks
Gateway & Platform