Known issues

This describes small, short-term issues being addressed by New Relic's development engineers prior to 2013, and cross references to any known issues since then.

Java known issues

For information about Java known issues since 2012, see Troubleshooting.

Invalid license key message: If you get a message in your Java agent log about invalid license keys and find that your newrelic.yml contains a license_key parameter with values other than numbers or letters in it, and if you downloaded it from[account number[/support, remove those extraneous characters and restart your app server. (as of 15 Feb 2012 - ETA for a fix 17 Feb 2012)

Glassfish: The Java agent between version 2.2.0 and version 2.3.x has issues running under some configurations of the Glassfish Application Server. New Relic recommends downgrading to 2.1.2 until a patch is available. (as of 7 Feb 2012)

JBoss AS 7 bytecode instrumentation: With JBoss AS 7, New Relic's bytecode instrumentation adds interfaces that the JBoss module and classloading system cannot find. New Relic anticipates an in-agent solution to this in the near future.

As a workaround, add newrelic.jar and a new module.xml file to modules/com/newrelic/agent/main in your JBoss home directory. The module.xml file should contain:

<?xml version="1.0" encoding="UTF-8"?>

<module xmlns="urn:jboss:module:1.0" name="com.newrelic.agent">
        <resource-root path="newrelic.jar"/>
        <!-- Insert resources here -->

Then, insert two new lines into bin/

# Specify options to pass to the Java VM.
if [ "x$JAVA_OPTS" = "x" ]; then
JAVA_OPTS="-Xms64m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000"
JAVA_OPTS="$JAVA_OPTS -Djboss.modules.system.pkgs=$JBOSS_MODULES_SYSTEM_PKGS -Djava.awt.headless=true"
JAVA_OPTS="$JAVA_OPTS -javaagent:<path to newrelic directory>/newrelic.jar

With these changes in place, JBoss AS 7 should start cleanly.

.NET known issues

For information about .NET known issues since 2012, see:

Node.js known issues

The Node.js agent was released in 2013. For information about known issues since then, see Known Node.js limitations.

PHP known issues

For information about PHP known issues since 2012, see New Relic for PHP.

Segmentation faults and core dumps: There were a couple of outstanding issues with the PHP agent that led to segmentation faults and core dumps. These have been fixed with the agent. If you experience these symptoms with an earlier 2.6.x agent, upgrade your agent. (as of 9 Jan 2012)

PHP 5.4: PHP 5.4 is supported by the New Relic PHP agent in 2.7+ only. Previous versions of the agent will not work.

Python known issues

For information about Python known issues, see Status of Python agent.

Ruby known issues

For information about Ruby known issues since 2012, see:

Ruby version 1.9.3: The version 3.3.2 Ruby agent may not work well with Ruby version 1.9.3. New Relic's Beta newrelic_rpm gem may work better for you. (as of 7 Feb 2012)

Server monitor known issues

For information about server monitor known issues, see:

Other known issues

Chrome browsers: There is a known issue with the Chrome browser beta and developer editions that makes chart labels display incorrectly on many New Relic webpages. These pages look fine in the release version (17) of Chrome and in other browsers. More information about this issue is reported in the Chrome bug tracker and in the issue tracker for New Relic's Chart software.

For more help

To view the latest release information for agents, server monitors, and other New Relic product, refer to their Release Notes. Typically this is the first document in their individual Documentation category.


Server monitoring:

Other New Relic products:

If you need additional help, get support at