We have a new programmer that had seen the tpsOverMsg used before at other hospitals to replace the TCP/IP in and out threads. We installed it in the test system and it is routing the messages to the appropriate threads. I informed him of our problem with the loss of the metadata with the msgcreate command. He changed the msgcreate command to msgcopy. Now when the data is sent from thread A it is routed to thread B, thread B contains the proc in the Outbound tps that does the OVER. We expected it to go to the inbound of thread B and then route to thread C like before when the proc contained the msgcreate command. But now it appears that the message is routed back to thread A which routes it back to thread B. This loop continued creating messages and putting them into the recovery database. This almost caused production to go down. Do you have any insite?
Thanks,
Elizabeth Wilson
