What happens if Apache is configured with a Java agent?
Hi,
I've just seen a situation where a client extracted a Java agent onto a web server, then configured Apache's httpd.conf to load the libdtagent.so agent as a module. The Apache server starts up without any problem, but the agent obviously cannot connect to the collector, as it has no name or reference to the collector IP.
Is Apache just ignoring the request to load the agent as a module, or can this cause a problem?
Thanks,
Derick
Correction, the web server doesn't start the agent. It does actually complain that the agent isn't an Apache module.
Hi. I think this shouldnt have any impact at all. Apache will try to load the module but figures out that it is in fact not a module and therefore just does nothing with it. So - the only impact there is that you will find this information in the log files of Apache - but - it should not impact the actual processing of requests. I would however remove it when possible to avoid any potential overhead that comes with "trying to load the module" and logging the log message
Welcome the
Dynatrace Community Forums
Check out the Forum User Guide and Forum Guidelines to learn how to get started.Community Member of the Month
August 2017
Announcing Dynatrace's Community Member of the Month for August 2017, Rick B.! Click here to read more! 
