Test #9 - Application Server Loses, the Re-establishes Network Connectivity
This demonstrates overall system behavior when the application server loses network connectivity. Pulling the network cable from the application server while it actively processes events from the active mediation server, waiting 2 minutes and then plugging the network cable back in simulates the loss of network connectivity.
• The standby server discards any events received until the application server process ends.
• The active server successfully delivers any events received until the application server process ends.
• After losing connectivity to the application server, the active mediation server should continue to try and deliver its current batch, spooling all other events that it receives.
• After losing connectivity to the application server, the standby server should spool all events that it receives since it cannot discard events that the active server has not yet delivered.
• After the application server reconnects to the network, the active server resumes forwarding events to the application server, and the standby server resumes dropping events.
• The total number of events delivered to the application server should be 30,000, and the standby server drops all 30,000, less the number of events queued. Because the active server does not receive any events after the 30,000, the standby server should still have a batch queued which has not yet been dropped.
Actual Results: SUCCESS
• Active Server - The active server processed 6722 events, with 2178 in batch, when the appserver lost connectivity. It began to queue events, ending with 18399 in batch, and one about to be added to the batch. The total number of events accounted for is 30000. Once the application server was reconnected, it continued to deliver events, finally delivering all 30000.
• Standby Server - The standby server discarded 6100 events, with 2700 in batch, when the appserver lost connectivity. Before the appserver reconnected, it queued 18099 events, with one about to be added to the batch. The total number of events accounted for is 30000. Once the appserver reconnected, resumed dropping events, ending with a total of 28800 events dropped, with 1200 remaining in batch.