Transaction Trace Warehouse (TTW) displays Internal Server Error message in user interface

Categories:
Aternity APM
Solution Number:
S25403
Last Modified:
2014-11-25
Issue

The Internal Server Error message appears in the Transaction Trace Warehouse (TTW) user interface.

Possible Symptoms:

1) User is not able to search for any traces in the TTW user interface.

2) TTW is not able to download or process any traces.

3) The following error messages were logged in <datadir>\TTW_Data\logs\silo_store.log :

WARNING: ODBClient: unable to establish connection to localhost:29104 in 05m
[main:238]: ERROR: Database connections failed.Please check the recent silo_store log file for additional messages.

4) The following error messages were logged in <datadir>\TTW_Data\logs\silo_query.log :

WARNING: ODBClient: unable to establish connection to localhost:29104 in 10s
[main:1341]: ERROR: Database connections failed.Please check the recent silo_store log file for additional messages.

5) The following error messages were logged in <datadir>\TTW_Data\logs\silo_serve.log :

[ODB::ResourceLock::acquire_core:3621]: ERROR: Unable to acquire lock [C:\TTW_Data/odb_store/.tg.lck]
[ODB::odb_server_run:1049]: ERROR: Unable to start silo_serve for [C:\TTW_Data/odb_store] @ [29104]

6) The following error messages were logged in <installdir>\OPNET\AppInternals Xpert Transaction Trace Warehouse\TomEE\logs\ttw0.log :

org.apache.catalina.core.StandardWrapperValve invoke
SEVERE: Servlet.service() for servlet [SiloProxyServlet] in context with path [] threw exception
org.apache.http.conn.HttpHostConnectException: Connection to http://127.0.0.1:29101 refused
at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection (DefaultClientConnectionOperator.java:190)
at org.apache.http.impl.conn.ManagedClientConnectionImpl.open (ManagedClientConnectionImpl.java:294)
at org.apache.http.impl.client.DefaultRequestDirector.tryConnect (DefaultRequestDirector.java:643)
at org.apache.http.impl.client.DefaultRequestDirector.execute (DefaultRequestDirector.java:479)
at org.apache.http.impl.client.AbstractHttpClient.execute (AbstractHttpClient.java:906)
at org.apache.http.impl.client.AbstractHttpClient.execute (AbstractHttpClient.java:805)
at org.apache.http.impl.client.AbstractHttpClient.execute (AbstractHttpClient.java:784)
at com.opnet.harvester.server.api.servlet.backend.SiloProxyServlet.executeProxyRequest (SiloProxyServlet.java:178)
Solution

Possible Causes:

1) The following port numbers may be in use:

  • 29101
  • 29102
  • 29103
  • 29104

2) The following processes may have been orphaned:

  • silo_query64.exe
  • silo_store64.exe
  • and silo_serve64.exe

Solution 1:

  1. Reboot the machine

Solution 2:

  1. Stop the OPNET AppInternals Xpert Transaction Trace Warehouse service
  2. Stop the OPNET AppInternals Xpert Transaction Trace Warehouse backend processes service
  3. Kill all the silo_xxx.exe processes (silo_query64.exe, silo_store64.exe, and silo_serve64.exe)
  4. Start the OPNET AppInternals Xpert Transaction Trace Warehouse backend processes service
  5. Start the OPNET AppInternals Xpert Transaction Trace Warehouse service

Solution 3 (for ports that are used by other processes):

  1. Open the configuration file, silo.cfg, in the folder, <datadir>\TTW_Data\config\silo.cfg, with a text editor
  2. If port number 29101 is affected, change "silo_query_control_port" : 29101 to another unused port number
  3. If port number 29102 is affected, change "silo_store_control_port" : 29102 to another unused port number
  4. If port number 29103 is affected, change "silo_serve_control_port" : 29103 to another unused port number
  5. If port number 29104 is affected, change "silo_serve_db_port" : 29104 to another unused port number
  6. Restart the OPNET AppInternals Xpert Transaction Trace Warehouse backend processes service
Environment
  • SteelCentral AppInternals aka AppInternals Xpert (AIX)
  • SteelCentral AppInternals Transaction Trace Warehouse (TTW)
  • Windows
Attachments
NOTICE: Riverbed® product names have changed. Please refer to the Product List for a complete list of product names.
Can't find an answer? Create a case