Inbound and outbound threads status of ‘initializing’

[Paul Johnston]

Hi All.

Although my issue is not a critical it is somewhat of an annoyance.

We have Pathology Reports ( ORU messages ) sent to an external client

using an internet VPN tunnel.

The messages are sent without any problem but in the mornings

both inbound and outbound threads have a Proto Status of ” initializing “

until a new message is sent. Then the status changes to ‘up ‘.

Any thoughts why the threads do not show a ‘up ‘ status all the time.

Paul

Topic

[Rob Abbott]

Are you zeroing statistics overnight with hcimsiutil -Z?

This will also reset protocol statuses to “initializing”.  Threads will not update their protocol status until an event occurs on the protocol driver (read,write, disconnect, etc).

Rob Abbott
Cloverleaf Emeritus

[Paul Johnston]

Rob,

We do use ‘hcimsiutil -Z’ as part of the daily cycling .

I was going to say that we do this for other threads as well but their status

is always ‘UP’ when I view it in the morning (around 8am) .

As you say the protocol status does not change until an event occurs on the driver. This explains the threads showing  ‘Initializing’ , the first event occurs on this thread around 8 or 9 am.

I thought the status of ‘OPENING’ was what you described. Could you please describe the meaning of this status .

Thanks

Paul

[Rob Abbott]

OPENING means that the thread is running, but it’s protocol is not connected.  (e.g. client retrying connections to a server or a server without any clients connected to it)

INITIALIZING means that the statistics on the thread have been reset (or this particular thread has just been started for the very first time) and no events have occured on the thread that would cause it to update it’s protocol status.

You might be able to get INITIALIZING to go away by sending any command to the threads in question after your daily cycling, like ‘reload’ any Tcl proc or something similar.  If I remember correctly it’s any event on the thread that will cause it to update it’s status – not just a protocol event.

Rob Abbott
Cloverleaf Emeritus

[Paul Johnston]

Rob,

Thanks for your response and appreciate your explaination.  I will try your suggestion also.

Paul

[Author]

Replies