Forward Thread

[David Teh]

Hi folks,

I am having problems with the forward thread config.

Thread 1(IB)->Thread 2(OB)

Thread 3(OB)

Thread 2 is configured to connect to a non-existent system, and is perpetually in OPENING state.

In Thread 2’s OB tab, ‘Thread 3’ is set as the ‘Forward Thread’.

The messages sent from Thread 1 isn’t flowing to Thread 3.

Are there additional configurations required?

TIA!

Topic

[Jim Kosloskey]

David,

I think you need to actually tell the thread to forward in the NetMonitor (or perhaps from the command line).

All the NetConfig entries do is to specify where forwarding will occur once it is started.

If I recall correctly, forwarding is not persistant. In other words, if you cycle thread 2, when it restarts, forwarding will not be active. You will need to activate it again.

email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 60 years IT – old fart.

[David Teh]

Hi Jim,

Thanks for responding.

So I guess that configuration doesn’t help in what I want to achieve.

I am playing with this scenario:

1. Thread 1 (IB) routes messages to Thread 2 (OB).

2. If Thread 2 becomes ‘OPENING’ or ‘ERROR’, Thread 1 will route messages to Thread 3 (OB).

Any idea how this can be done?

Thanks!!!!

Jim Kosloskey wrote:

David,

I think you need to actually tell the thread to forward in the NetMonitor (or perhaps from the command line).

All the NetConfig entries do is to specify where forwarding will occur once it is started.

If I recall correctly, forwarding is not persistant. In other words, if you cycle thread 2, when it restarts, forwarding will not be active. You will need to activate it again.

[Jim Kosloskey]

David,

If you want to use forwarding and have that happen automaticaly (without carbon based entity intervention) you will most likely need to code some Tcl and utilize Alerts.

Be aware about forwarding that when the thread is actually forwarded, I do not believe there is any obvious indication (certainly not in the NetMonitor) that forwarding is occurring. There is not even a route arrow of any kind to indicate what threads are coupled in a forwarding structure.

I had looked at forwarding some years back as an option and rejected it because of the items I have listed. I made suggestions for improvements which have yet to be delivered, Since not many folks seem to be disatisfied with the way forwarding is implemented, I don’t guess I will see any change in it’s function.

Good Luck.

Jim Kosloskey

email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 60 years IT – old fart.

[David Teh]

Hi Jim,

Thanks!

The motivation came about from having to deal with one of these miserably hopeless (I stop short of calling them cheats) vendors who managed to squeeze themselves in some of the hospitals’ projects. After failing to deliver the HA for the application system, the vendor turned around and expected Cloverleaf to do miracles…….sigh……..just ranting……

Jim Kosloskey wrote:

David,

If you want to use forwarding and have that happen automaticaly (without carbon based entity intervention) you will most likely need to code some Tcl and utilize Alerts.

Be aware about forwarding that when the thread is actually forwarded, I do not believe there is any obvious indication (certainly not in the NetMonitor) that forwarding is occurring. There is not even a route arrow of any kind to indicate what threads are coupled in a forwarding structure.

I had looked at forwarding some years back as an option and rejected it because of the items I have listed. I made suggestions for improvements which have yet to be delivered, Since not many folks seem to be disatisfied with the way forwarding is implemented, I don’t guess I will see any change in it’s function.

Good Luck.

Jim Kosloskey

[Author]

Replies