Could it be that the health logger is actually not taking into account the rising column value?
2016-09-19 11:18:16 INFO HealthLogger:193 - DB_JDBC_URL=jdbc:mysql://127.0.0.1:3306/ganetec FREE_MEMORY=610374208 FUNCTION=dbinputAdvanceIterator LABEL=JP MAX_MEMORY=2112618496 PROTOCOL=HTTP SQL="SELECT alert.id AS alert_id,
alert.timestamp AS alert_timestamp,
occupancy.occupancy AS occupancy_occupancy,
barrier.id AS barrier_id,
barrier.name AS barrier_name,
barrier.process_id AS barrier_process_id
FROM
(SELECT *
FROM alert
WHERE alert.id > ?) AS alert
JOIN occupancy
ON alert.id=occupancy.alert_id
JOIN barrier
ON occupancy.barrier_id=barrier.id
JOIN process
ON alert.process_id=process.id
WHERE process.license_id>1099
AND process.license_id<1200
AND process.active=1
AND barrier.process_id is NOT NULL" STATE=completed TOTAL_MEMORY=1838809088 TRANS_OBJECT_ID=2f7c0541-7a0d-48ee-9b4e-fa928e024b95 UPTIME=3493782 task_id=da9bd483-156b-41fc-9ed2-29e0accc828a
Is there a way I can disable it to see if that is the case? Or does it just reflect what my dbinput is quering?
... View more