- This topic has 2 replies, 2 voices, and was last updated 14 years, 6 months ago by .
We have had two different vendors tell us that when the engine is disconnecting from them, it is not sending them a properly formatted disconnect message. It is causing broken pipe type issues in there systems.
We have alerts that bounce connections on last received and outbound que depth. I use a tcl proc to process the alert. I bounce it first and see if it corrects itself. If it does not fix it, it sends out emails to notify the appropriate people. The commands I issue for the bounce are:
hcicmd -p $ProsName -p $ConnName phold_obd
hcicmd -p $ProsName -p $ConnName pstop
hcicmd -p $ProsName -p $ConnName pstart
This causes broken pipes and I cause broken pipes if I bounce the connection from the GUI as well.
Is there a way to bounce a connection that sends out a disconnect message first???
Thanks in advance,
- The forum ‘Cloverleaf’ is closed to new topics and replies.