"Accept on connect failed: Software caused connection a

[Jeannette Wistrom]

Our inbound connection from Meditech gets flooded with ADT’s and the inbound thread starts turning yellow and red (with messages pending).  Meditech NMI goes bazerk (one thing it logs is “invalid Message control id”) and keeps closing the connection, which causes the ib thread to go to opening.  This goes on for awhile and finally the engine threads get stopped/started and restart with the error “Accept on connect failed: Software caused connection abort”.  

Has anyone else had this happen and what, if anything, can we do on Cloverleaf?  

Donna Ledgerwood

Senior Integration Specialist

Micro Star Inc.

dledgerwood@micro-star-inc.com

Topic

[Russ Ross]

The symptons you described make me wonder if 2 independent interfaces (perhaps one test and one prod) are sending to the same inbound cloverleaf listener.

Russ Ross
RussRoss318@gmail.com

[Jeannette Wistrom]

We’ve actually determined it’s a Bar Batch job that is sending the numerous updates out NMI.  Most of the time it just slows down everything on the engine for a bit and catches up without big issues.  Once in awhile though it seems to bring NMI to a screeching halt.  It’s as if the engine gets confused, NMI gets confused and until the engine process gets reset NMI backs up more.  There’s actually 2 inbound threads that are affected:  one regular adt’s and the other pac’s.   Have you ever had anything weird like that happen?

[Author]

Replies