Execution Servers are not connecting

Document ID : KB000007007
Last Modified Date : 14/02/2018
Show Technical Document Details
Issue:

RA Execution Server is running but in ASAP UI and ROC it show as unreachable and we can see the activemq errors displayed below with in active_mq_nac log file.

 

[LevelDB IOException handler.] INFO (org.apache.activemq.broker.BrokerService:2561) - No IOExceptionHandler registered, ignoring IO exception
java.io.IOException: Could not open table 42
at org.apache.activemq.util.IOExceptionSupport.create(IOExceptionSupport.java:39)
at org.apache.activemq.leveldb.LevelDBClient.might_fail(LevelDBClient.scala:552)
at org.apache.activemq.leveldb.LevelDBClient.might_fail_using_index(LevelDBClient.scala:1032)
at org.apache.activemq.leveldb.LevelDBClient.listCollections(LevelDBClient.scala:1155)
at org.apache.activemq.leveldb.DBManager$$anonfun$3.apply(DBManager.scala:837)
at org.apache.activemq.leveldb.DBManager$$anonfun$3.apply(DBManager.scala:837)
at org.fusesource.hawtdispatch.package$RichExecutorTrait$$anonfun$future$1.apply$mcV$sp(hawtdispatch.scala:116)
at org.fusesource.hawtdispatch.package$$anon$4.run(hawtdispatch.scala:330)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

 

Environment:
Release Automation Server 6.1
Cause:

If there is any problem with LevelDB and if it gets corrupted then we will see the NES (Execution Server) as Unreachable.

Resolution:

1. Log in to the Release Automation Server and stop RA Services

2. Delete/Move LevelDB files from below path <C:\Program Files (x86)\CA\ReleaseAutomationServer\activemq-data\nac\LevelDB>

3. Once deleted come back to the Execution Server (Stop NES Service) and delete the LevelDB contents as mentioned above.

4. Now start the NES ( Execution Server ) and then start the NAC (Release Automation Management) Server services.

Additional Information:

This NES(Execution Server) Connectivity issue has been fixed in latest version of Release Automation Server i.e in 6.2 and 6.3