Maximo

Maximo

Come for answers, stay for best practices. All we're missing is you.

 View Only
Expand all | Collapse all

Ignore certain kinds of failed integration messages? (don't send email if BMXAA8229W)

  • 1.  Ignore certain kinds of failed integration messages? (don't send email if BMXAA8229W)

    Posted Sun August 01, 2021 10:49 PM
    Edited by System Admin Wed March 22, 2023 11:53 AM
    I have an external financial system that integrates POs to Maximo (interface tables; sequential queue).

    We have a minor issue where the inbound POs to Maximo are temporarily failing:
    Emailed from: maxintadm@...
    Emailed to: IT-staff1@... Error in integration transaction. An error occured in an integration transaction. Review the 987654321 error file in the Message Reprocessing application for information about the transaction that caused the error. psdi.util.MXRowUpdateException: BMXAA8229W - Record PO : Site=SERVICES PO=00000123456 Revision=0 has been updated by another user. Your changes have not been saved. Refresh the record and try again. at psdi.mbo.MboSet.updateMbo(MboSet.java:9332) at psdi.mbo.MboSet.saveTransaction(MboSet.java:7743) at psdi.txn.MXTransactionImpl.saveTransaction(MXTransactionImpl.java:221) at psdi.txn.MXTransactionImpl.saveTransaction(MXTransactionImpl.java:221) at psdi.txn.MXTransactionImpl.save(MXTransactionImpl.java:156) at psdi.iface.mos.MosProcessImpl.save(MosProcessImpl.java:2605) at psdi.iface.mos.MosProcessImpl.processExternalData(MosProcessImpl.java:392) at psdi.iface.mic.MicSetIn.processExternalData(MicSetIn.java:149) at psdi.iface.mic.EntMicService.processDataIn(EntMicService.java:1439) at psdi.iface.mic.EntMicService.processExternalData(EntMicService.java:1335) at psdi.iface.jms.QueueToMaximoProcessor.processMessage(QueueToMaximoProcessor.java:129) at psdi.iface.jms.JMSContQueueProcessor.processMessage(JMSContQueueProcessor.java:227) at psdi.iface.jms.JMSListenerBean.onMessage(JMSListenerBean.java:203) at psdi.iface.jms.MDBProxyJMSContQueueProcessor_1_5bf7eeaa.onMessage(MDBProxyJMSContQueueProcessor_1_5bf7eeaa.java) at com.ibm.ws.sib.api.jmsra.impl.JmsJcaEndpointInvokerImpl.invokeEndpoint(JmsJcaEndpointInvokerImpl.java:258) at com.ibm.ws.sib.ra.inbound.impl.SibRaDispatcher.dispatch(SibRaDispatcher.java:919) at com.ibm.ws.sib.ra.inbound.impl.SibRaSingleProcessListener$SibRaWork.run(SibRaSingleProcessListener.java:597) at com.ibm.ejs.j2c.work.WorkProxy$RunWork.run(WorkProxy.java:282) at java.security.AccessController.doPrivileged(AccessController.java:666) at javax.security.auth.Subject.doAs(Subject.java:490) at com.ibm.websphere.security.auth.WSSubject.doAs(WSSubject.java:133) at com.ibm.ejs.j2c.work.WorkProxy$RunWork.run(WorkProxy.java:285) at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:63) at com.ibm.ejs.j2c.work.WorkProxy.run(WorkProxy.java:667) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1909)

    Eventually, Maximo is able to automatically resolve the issue by re-trying until the Maximo PO is freed up. So we don't usually need to intervene in this scenario...the problem eventually goes away on it's own.


    Question:

    Realistically, solving that issue is likely beyond my skillset. I've read @Mark Robbins articles on BMXAA8229W (Article 1, Article 2, Article 3) ​and it sounds like getting to the root cause requires expert analysis. Whereas I couldn't even tell you if it's a legitimate conflict, like like a user editing the PO via the Maximo UI, or if there is an issue with the integration. And regardless, the issue just goes away on it's own, so it might not be worth spending a lot of time troubleshooting it.

    Instead, I'm wondering if I could just configure Maximo to ignore failed messages if certain conditions are met:
    What I mean by “ignore” is: If the only message in Message Reprocessing is a BMXAA8229W message, then don't email me.

    Is there a way to ignore certain kinds of failed messages in Maximo?


    #AssetandFacilitiesManagement
    #Maximo


  • 2.  RE: Ignore certain kinds of failed integration messages? (don't send email if BMXAA8229W)

    Posted Mon August 02, 2021 02:15 AM
    Hi User1971,

    I would recommend investigating this kind of issue. You might loose important integration data.

    Few things to think about and try:
    1. How often is this happening?
    2. Can you replicate this at will? This would also give your a clear idea if it is an issue with your interface.
    3. Try to replicate it in Lower environment and enable sql and integration logs to find the sequence of events that cause this issue.


    Thanks,
    Biplab

    ------------------------------
    Biplab Choudhury
    Maximo Consultant
    Tata Consultancy Services
    Melbourne
    ------------------------------