https://community.appian.com/support/w/kb/1057/kb-1653-how-to-find-the-number-of-transactions-left-to-replay-for-an-appian-engine-in-the-event-of-an-unexpected-shutdownen-USTelligent Community 12https://community.appian.com/support/w/kb/1057/kb-1653-how-to-find-the-number-of-transactions-left-to-replay-for-an-appian-engine-in-the-event-of-an-unexpected-shutdownTue, 14 Aug 2018 16:04:17 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:124d7bc0-fc94-4158-b287-d76f30d84b95Jordan Horwathttps://community.appian.com/support/w/kb/1057/kb-1653-how-to-find-the-number-of-transactions-left-to-replay-for-an-appian-engine-in-the-event-of-an-unexpected-shutdown#commentsCurrent Revision posted to Appian Knowledge Base by Jordan Horwat on 8/14/2018 4:04:17 PM<br /> <h2>Purpose</h2> <p>Appian engines will replay transactions in an event of an unexpected shutdown.&nbsp;When this occurs, the engine startup time will depend on the number of transactions it has to replay. A large number of transactions can delay the engine start-up time.</p> <p>This article outlines the following:</p> <ul> <li>How to find the number of transactions left to replay</li> <li>How to find how much time will it take for the Appian engines to boot up</li> </ul> <h2>Instructions</h2> <p>On the server which hosts the Appian Engines, navigate to <code>&lt;APPIAN_HOME&gt;\logs\service_manager.log</code>&nbsp;and search for log entries of the following type which have details on the engine name, number of transactions to replay and the approximate time this will take:</p> <pre>[KomodoEventBus-50] INFO&nbsp; com.appian.komodo.engine.status.ReplayStateProvider - download-stats 15 of 142 transactions replayed (10%). Approximately 00:57 remaining.</pre> <h2>Affected Versions</h2> <p>This article applies to Appian 17.3 and later.</p> <div class="content"> <p>Last Reviewed:&nbsp;August 2018</p> </div><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: engines, how-to, infrastructure, service manager</div> https://community.appian.com/support/w/kb/1057/kb-1653-how-to-find-the-number-of-transactions-left-to-replay-for-an-appian-engine-in-the-event-of-an-unexpected-shutdown/revision/6Tue, 14 Aug 2018 12:02:33 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:124d7bc0-fc94-4158-b287-d76f30d84b95Jordan Horwathttps://community.appian.com/support/w/kb/1057/kb-1653-how-to-find-the-number-of-transactions-left-to-replay-for-an-appian-engine-in-the-event-of-an-unexpected-shutdown#commentsRevision 6 posted to Appian Knowledge Base by Jordan Horwat on 8/14/2018 12:02:33 PM<br /> <h2>Purpose</h2> <p>Appian engines will replay transactions in an event of an unexpected shutdown.&nbsp;When this occurs, the engine startup time will depend on the number of transactions it has to replay. A large number of transactions can delay the engine start-up time.</p> <p>This article outlines the following:</p> <ul> <li>Find out the number of transactions left to replay</li> <li>Find out how much time will it take for the Appian engines to boot up</li> </ul> <h2>Instructions</h2> <p>On the server which hosts the Appian Engines, navigate to <code>&lt;APPIAN_HOME&gt;\logs\service_manager.log</code>&nbsp;and search for log entries of the following type which have details on the engine name, number of transactions to replay and the approximate time this will take:</p> <pre>[KomodoEventBus-50] INFO&nbsp; com.appian.komodo.engine.status.ReplayStateProvider - download-stats 15 of 142 transactions replayed (10%). Approximately 00:57 remaining.</pre> <h2>Affected Versions</h2> <p>This article applies to Appian 17.3 and later.</p> <div class="content"> <p>Last Reviewed:&nbsp;August 2018</p> </div><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: engines, how-to, infrastructure, service manager</div> https://community.appian.com/support/w/kb/1057/kb-1653-how-to-find-the-number-of-transactions-left-to-replay-for-an-appian-engine-in-the-event-of-an-unexpected-shutdown/revision/5Tue, 14 Aug 2018 10:48:08 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:124d7bc0-fc94-4158-b287-d76f30d84b95Tejas Kargutkarhttps://community.appian.com/support/w/kb/1057/kb-1653-how-to-find-the-number-of-transactions-left-to-replay-for-an-appian-engine-in-the-event-of-an-unexpected-shutdown#commentsRevision 5 posted to Appian Knowledge Base by Tejas Kargutkar on 8/14/2018 10:48:08 AM<br /> <h2>Purpose</h2> <p>Appian engines will replay transactions in an event of an unexpected shutdown.&nbsp;When this occurs, the engine startup time will depend on the number of transactions it has to replay. A large number of transactions can delay the engine start-up time.</p> <p>This article outlines the following:</p> <ul> <li>Find out the number of transactions left to replay</li> <li>Find out how much time will it take for the Appian engines to boot up</li> </ul> <h2>Instructions</h2> <p>On the server which hosts the Appian Engines, navigate to <code>&lt;APPIAN_HOME&gt;\logs\service_manager.log</code>&nbsp;and search for log entries of the following type which have details on the engine name, number of transactions to replay and the approximate time this will take:</p> <pre>[KomodoEventBus-50] INFO&nbsp; com.appian.komodo.engine.status.ReplayStateProvider - download-stats 15 of 142 transactions replayed (10%). Approximately 00:57 remaining.</pre> <h2>Affected Versions</h2> <p>This article applies to Appian 17.3 and later.</p> <div class="content"> <p>Last Reviewed:&nbsp;August 2018</p> </div><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: engines, how-to, infrastructure, service manager</div> https://community.appian.com/support/w/kb/1057/kb-1653-how-to-find-the-number-of-transactions-left-to-replay-for-an-appian-engine-in-the-event-of-an-unexpected-shutdown/revision/4Thu, 09 Aug 2018 13:23:09 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:124d7bc0-fc94-4158-b287-d76f30d84b95Tejas Kargutkarhttps://community.appian.com/support/w/kb/1057/kb-1653-how-to-find-the-number-of-transactions-left-to-replay-for-an-appian-engine-in-the-event-of-an-unexpected-shutdown#commentsRevision 4 posted to Appian Knowledge Base by Tejas Kargutkar on 8/9/2018 1:23:09 PM<br /> <h2>Purpose</h2> <p>Appian engines will replay transactions in an event of an unexpected shutdown. In an event of such occurrence, the engine startup time will depend on how many transactions the engines have to replay, such that a higher number of replays can delay the engine start up time.</p> <p>This article outlines how to find out how many transactions are left to replay and how much time will it take for the Appian engines to boot up.</p> <h2>Instructions</h2> <p>Navigate to <code>&lt;APPIAN_HOME&gt;\logs\service_manager.log</code>&nbsp;and search for log entries of the following type which have details on the engine name, number of transactions to replay and the approximate time this will take:</p> <pre>[KomodoEventBus-50] INFO&nbsp; com.appian.komodo.engine.status.ReplayStateProvider - download-stats 15 of 142 transactions replayed (10%). Approximately 00:57 remaining.</pre> <h2>Affected Versions</h2> <p>This article applies to Appian 17.3 and later.</p> <div class="content"> <p>Last Reviewed:&nbsp;August 2018</p> </div><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: engines, how-to, infrastructure, service manager</div> https://community.appian.com/support/w/kb/1057/kb-1653-how-to-find-the-number-of-transactions-left-to-replay-for-an-appian-engine-in-the-event-of-an-unexpected-shutdown/revision/1Wed, 08 Aug 2018 18:36:52 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:124d7bc0-fc94-4158-b287-d76f30d84b95Tejas Kargutkarhttps://community.appian.com/support/w/kb/1057/kb-1653-how-to-find-the-number-of-transactions-left-to-replay-for-an-appian-engine-in-the-event-of-an-unexpected-shutdown#commentsRevision 1 posted to Appian Knowledge Base by Tejas Kargutkar on 8/8/2018 6:36:52 PM<br /> <h2>Purpose</h2> <p>Appian engines will replay transactions in an event of an unexpected shutdown.</p> <p>Replaying transactions delays the engine start up time. The engine startup time depends on how many transactions the engines have to replay.</p> <p>This article outlines how to find out how many transactions are left to replay and how much time will it take for the engines to boot up.</p> <h2>Instructions</h2> <p>Navigate to <code>&lt;APPIAN_HOME&gt;\logs\service_manager.log </code>and search for log entries of the following type which have details on the engine name, number of transactions to replay and the approximate time this will take:</p> <pre>[KomodoEventBus-50] INFO&nbsp; com.appian.komodo.engine.status.ReplayStateProvider - download-stats 15 of 142 transactions replayed (10%). Approximately 00:57 remaining.<br /><br /></pre> <h2>Affected Versions</h2> <p>This article applies to Appian 17.3 and later.</p> <div class="content"> <p>Last Reviewed:&nbsp;August 2018</p> </div><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: engines, how-to, infrastructure, service manager</div> https://community.appian.com/support/w/kb/1057/kb-1653-how-to-find-the-number-of-transactions-left-to-replay-for-an-appian-engine-in-the-event-of-an-unexpected-shutdown/revision/3Wed, 08 Aug 2018 17:28:47 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:124d7bc0-fc94-4158-b287-d76f30d84b95Jordan Horwathttps://community.appian.com/support/w/kb/1057/kb-1653-how-to-find-the-number-of-transactions-left-to-replay-for-an-appian-engine-in-the-event-of-an-unexpected-shutdown#commentsRevision 3 posted to Appian Knowledge Base by Jordan Horwat on 8/8/2018 5:28:47 PM<br /> <h2>Purpose</h2> <p>Appian engines will replay transactions in an event of an unexpected shutdown.</p> <p>Replaying transactions delays the engine start up time. The engine startup time depends on how many transactions the engines have to replay.</p> <p>This article outlines how to find out how many transactions are left to replay and how much time will it take for the engines to boot up.</p> <h2>Instructions</h2> <p>Navigate to <code>&lt;APPIAN_HOME&gt;\logs\service_manager.log </code>and search for log entries of the following type which have details on the engine name, number of transactions to replay and the approximate time this will take:</p> <pre>[KomodoEventBus-50] INFO&nbsp; com.appian.komodo.engine.status.ReplayStateProvider - download-stats 15 of 142 transactions replayed (10%). Approximately 00:57 remaining.<br /><br /></pre> <h2>Affected Versions</h2> <p>This article applies to Appian 17.3 and later.</p> <div class="content"> <p>Last Reviewed:&nbsp;August 2018</p> </div><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: engines, how-to, infrastructure, service manager</div> https://community.appian.com/support/w/kb/1057/kb-1653-how-to-find-the-number-of-transactions-left-to-replay-for-an-appian-engine-in-the-event-of-an-unexpected-shutdown/revision/2Wed, 08 Aug 2018 14:37:47 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:124d7bc0-fc94-4158-b287-d76f30d84b95Tejas Kargutkarhttps://community.appian.com/support/w/kb/1057/kb-1653-how-to-find-the-number-of-transactions-left-to-replay-for-an-appian-engine-in-the-event-of-an-unexpected-shutdown#commentsRevision 2 posted to Appian Knowledge Base by Tejas Kargutkar on 8/8/2018 2:37:47 PM<br /> <h2>Purpose</h2> <p>Appian engines will replay transactions in an event of an unexpected shutdown.</p> <p>Replaying transactions delays the engine start up time. The engine startup time depends on how many transactions the engines have to replay.</p> <p>This article outlines how to find out how many transactions are left to replay and how much time will it take for the engines to boot up.</p> <h2>Instructions</h2> <p>Navigate to <code>&lt;APPIAN_HOME&gt;\logs\service_manager.log </code>and search for log entries of the following type which have details on the engine name, number of transactions to replay and the approximate time this will take:</p> <pre>[KomodoEventBus-50] INFO&nbsp; com.appian.komodo.engine.status.ReplayStateProvider - download-stats 15 of 142 transactions replayed (10%). Approximately 00:57 remaining.<br /><br /></pre> <h2>Affected Versions</h2> <p>This article applies to Appian 17.3 and later.</p> <div class="content"> <p>Last Reviewed:&nbsp;August 2018</p> </div><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: engines, how-to, infrastructure, service manager</div>