@james-cobane
Forum Replies Created
-
Do you want to delete ALL the messages queued for that thread, or only the first one on the queue?
You can use the Database Administrator tool from the IDE or the command line (depending on your preference and/or skill level).
If you want to delete ALL the messages on the queue for that thread, then the command line option would be:
hcidbdump -r -d destinationthread -D
where destinationthread is the name of your outbound thread
If you want to only delete the first queued message, then get the messageID of the first queued message (i.e. hcidbdump -r -d destinationthread -O i) and look at the ID of the first message queued (i.e. 0.0.12345) and use that in command for the single message. It is likely the first queued message is in a state 16 if you are not getting ACKs from your outbound system. Once you have the message ID then the command is:
hcidbdump -r -m 0.0.12345 -D
Where 0.0.12345 should be replaced with the actual message ID.
I would recommend working with Infor Support if you are not comfortable or are unsure of how to proceed
Jim Cobane – Henry Ford Health
We created a script (getportsall) that searches all your sites NetConfig(s) and pulls the data out of the NetConfig for each site. The output looks like this:
<pre> Port Type Host/site thread Protocol Thread/Dest Site
——– ————— —————————————- ———- —————————— —————
2000 Client & Dest mcwapp840b.corp.ds.some.org pdl-tcpip to_hfh_intellidesk epic1prod
2200 Client & Dest 10.88.205.73 tcpip to_hfhn_topcon_adt hfh1prod
2304 Client lsibase1.wafoote.org tcpip to_hfah_LSI_adt hfah1prod
2505 Client 10.32.75.70 tcpip to_hfah_WestComNurse_adt hfah1prod
2575 Client 10.403.0.108 tcpip to_rhyme_278N_278Referral epic2prod</pre>
Script is attached with a .txt extension added to allow it to be uploaded. Feel free to modify for your needs.Regards,
Jim Cobane – Henry Ford Health
P. S. – It doesn’t look like the formatting of the output stayed in the post, but you get the idea.
You could configure an alert type of “protocol status” == error. If the thread is unable to bind on the port, the protocol status would go to ‘error’.
But regarding the port being in the ephemeral range, that could be why you see it happen occasionally. The ephemeral range is used by the OS to arbitrarily assign ports when needed by the OS. If it goes to use that port (53021), that could be why you see it happen once in a while.
We generally only use ports > 10000 and < 32000 for server threads.
Jim Cobane – Henry Ford Health
