Fastpath: Admin Console: System > Settings > Activity Engine
What Matters Stream(s) Not Working Properly
If a stream is not working properly, it may be due to one of the following. Note that on
the page, servers shown in yellow are down.
- The Jive
web application node may not be able to connect to the Activity Engine
server. Test the connection by clicking Test
Connection. If this test is successful, the Activity Engine
server can properly process activity. If this test fails, you'll see a
failure message describing the problem. Typically, test failures are caused
by the Activity Engine database being down or unavailable. Note that your
instance of Jive may not allow you access to the Activity Engine's core
server.
You'll need to troubleshoot to bring the
Activity Engine back online before running another test.
- The Activity Engine server may not be able to connect to its database.
Verify that the Activity Engine database has been created and you can
connect to it.
- The Activity Engine server may not be able to connect to the Jive Genius
Recommender. Try pinging the Recommender from the Activity Engine.
If you have fixed and verified these connections but continue to experience problems,
make sure that all of the configuration settings are correct.
Long Delays Between Post and Stream Publication Times
If there are long delays between post and stream publication times, try sending a
trace through the Activity Engine by clicking Send Connectivity
Trace on the page. This sends a blank activity through the Activity Engine
processing pipelines, and then reports the length of time it took to complete the
trip. If you send the trace and get back a valid time measurement, the Activity
Engine node is up and functioning properly. Typical return times on an idle system
would be a few seconds.
Log Files Related to the Activity Engine
For further troubleshooting, look at the error messages in the application logs
under , or view the application log directly in
/usr/local/jive/services/eae-service/var/logs on the Activity
Engine node.
- eae-service.log -- this is the output of all log statements in the Activity
Engine server. Server errors will be logged here.
- eae-service.out -- this holds anything written to the standard output stream
from the Activity Engine server. Initialization and out-of-memory errors
will likely be logged here.
- eae-service-gc.log -- analyze this log to determine garbage collection
effectiveness and performance.