Hi,
We have implemented Manager & Worker concept in reportcaster in hostA and hostB as below.

hostA : 8300 - Primary distribution manager
hostA : 8301 - Worker1

hostB : 8300 - Secondary distribution manager
hostb : 8301 - Worker2

When Worker2 goes down, Worker1 is executing the schedules without any issues, But when worker1 goes down we are getting the below error and schedules are not getting picked up.


i.b.s.u.SCHConsoleUtil ERROR - Console Reader: Failed to establish connection to console (hostA:8301) java.net.ConnectException: Connection refused

We are expecting Worker2 to take care of schedules when worker1 goes down for some reason.

Please let us know are we missing any configuration or step to be done to overcome this issue.

Thanks

This message has been edited. Last edited by: FP Mod Chuck,

SridhartLakshmipathy

This could be a firewall issue between the two machines..

quote:

Originally posted by FP Mod Chuck:
SridhartLakshmipathy

This could be a firewall issue between the two machines..

Hi,
We have all the firewalls opened between the servers. The question is different. Its all working fine when both the workers are up. The issue comes when one worker goes down.

I think you may have this configured incorrectly. The distribution failover is configured with the secondary distribution server information not the workload distribution.

quote:

Originally posted by FP Mod Chuck:
I think you may have this configured incorrectly. The distribution failover is configured with the secondary distribution server information not the workload distribution.

Hi,
Yes, we understand the primary and secondary distribution manager and they are working fine.
Our question is, If we have 2 workers configured and one of the worker is down , We expect the other worker to run the schedules but that is not happening.

SridharLakshmipathy

Sorry, I was just trying to verify you just weren't using the workload distribution for failover. I suggest you open a case with techsupport as they can do a remote session with you and debug the issue.