Try stopping and starting activemq service on DA.
Once it's started, confirm it's listening on all 4 ports:
netstat -an | grep 61
Should see LISTEN for 61616/61618/61620/61622.
Then try starting the DA. Another thing it could be is the DA is taking too long to load the attributes from the DB, and AMQ connections will time out and get recreated over and over.
If you keep seeing this message over and over and it's been an hour, it's possible your DA doesn't have enough memory to load the DB. Startup requires more memory than normal run time as we need to load the DB into structures before we construct the objects in the item repository cache.
INFO | xtenderThread-97 | 2020-06-15 13:05:49,106 | ItemDbInterfaceImpl | vertica.impl.ItemDbInterfaceImpl 752 | re.database.irep.vertica | | Waiting for Attribute loading to complete - Load time: 0:04:00.018
If this is happening, open a support case.
Original Message:
Sent: 07-20-2020 10:14 AM
From: Planning And Performance Management
Subject: JAVA SERVICE ON DATA AGGREGATOR
failure in java service of the data aggregator.
The java service of the data aggregator server is restarting frequently.
displays message :
- JMS broker does not respond to heartbeat in 300 secs.. (error count:10)
- FailoverTransport; Transport (tcp://127.0.0.1:61616) failed , attempting to automatically reconnect: java.io.EOFException
How can I get around this? Any guidance?
Cássio Pinheiro - PRODEMGE
------------------------------
Analista
Cia de Tecnologia da Informação de Minas Gerais - PRODEMGE
------------------------------