Topic
  • 2 replies
  • Latest Post - ‏2012-04-23T21:48:44Z by SystemAdmin
SystemAdmin
SystemAdmin
3556 Posts

Pinned topic Not process the XML message from persistent JMS queue

‏2012-04-18T15:56:44Z |
We have mediation module is responsible for:

Receiving the Request XML message from SCA destination.
Perform validations of the input request
Persist the input message to a JMS queue
We have another mediation module is responsible for:
Receiving the XML message from persistent JMS queue
Invoke the EIS-FTP import component (FTP adapter) and places the file in dealer specific input folder of DMSI FTP server.
We have noticed that second mediation module not process the XML message from persistent JMS queue that had failed earlier which has unlocked state.

Mediation module process the XML message from persistent JMS queue that had failed earlier which has locked. Why mediation modules not process the unlocked state messages? Please find attached Unlocked state.doc
How we can fix this problem? Can you please help?

Thanks
Karthik
  • mmalc
    mmalc
    231 Posts

    Re: Not process the XML message from persistent JMS queue

    ‏2012-04-22T23:02:44Z  
    First check that this isn't your problem

    http://www-01.ibm.com/support/docview.wss?uid=swg21326860
  • SystemAdmin
    SystemAdmin
    3556 Posts

    Re: Not process the XML message from persistent JMS queue

    ‏2012-04-23T21:48:44Z  
    • mmalc
    • ‏2012-04-22T23:02:44Z
    First check that this isn't your problem

    http://www-01.ibm.com/support/docview.wss?uid=swg21326860
    Regarding the the technote
    We have below version.
    WebSphere Application Server 6.1.0.31
    WebSphere Process Server 6.2.0.3

    http://www-01.ibm.com/support/docview.wss?uid=swg21326860 which
    references APAR iFixes for PK73716 and JR30708...

    We do have the APAR fix for PK73716 since it first went into WebSphere
    AppServer 6.1.0.23 and you have ND 6.1.0.31 cf311015.02.

    The APAR iFix for JR30708 was included in WPS 6.2.0.1 per this link

    http://www-01.ibm.com/support/docview.wss?uid=swg24022185

    and we have WBI 6.2.0.3 of1024.07.

    So we do have both the iFixes referenced in the suggestion from
    technote, so that is not relevant to our situation.

    Thanks
    Karthik