Java agent release notesRSS

Improvements

• Spring 5

  The Java Agent now provides instrumentation for Spring 5 and Webflux. The agent will name transactions based on router functions as well as Spring controller and spring web annotations. The agent also provides support for Spring WebClient to capture external requests and timing.

  Spring 5 instrumentation works with Spring Boot, Tomcat, and Jetty.  

  Note if you have previously disabled Spring instrumentation: There is a new spring-4.3.0 instrumentation module that gets used in place of the previous spring-4.2.0 module for any customers running Spring 4.3.0 and above. If you had previously disabled support for spring-4.2.0 and you are running spring-4.3.0 you will want to change your class_transformer section in your newrelic.yml from:

  class_transformer:
    com.newrelic.instrumentation.spring-4.2.0:
      enabled: false

  Copiar

  to:

  class_transformer:
    com.newrelic.instrumentation.spring-4.3.0:
      enabled: false

  Copiar

Fixes

• Fixes an issue where the agent could cause an application deadlock when two tokens are created and linked from the other’s thread. This affects users of the New Relic token API and also users of the Hystrix framework.
• Fixes an issue where the agent would not capture JMX Datasource information from Tomcat when JDNI GlobalNamingResources is used.

Known Issues

Transaction reporting to New Relic may be delayed by up to 10 minutes when Spring WebClient is used to create http requests that never execute.

Improvements

• Apache HttpAsyncClient

  The Java agent now provides instrumentation for Apache HttpAsyncClient 4.1+. You will see your HttpAsyncClient calls as externals in New Relic.

• AsyncHttpClient

  The Java agent now provides instrumentation for AsyncHttpClient. You will now see the time spent in external service calls made using AsyncHttpClient in New Relic. If the external service is also running New Relic, you will see cross application tracing (CAT) details as well.

• Vert.x 3.5

  The Java agent now provides visibility into your applications built using the Vert.x 3.5. The agent instruments Vert.x Web, Vert.x Core, and Vert.x HTTP client. With this instrumentation, the agent will identify and name your transactions based on Vert.x web routing paths. The agent will also time web handlers, track async handlers, and external calls made with Vert.x HTTP client.

• JBoss EAP 7

  The Java Agent now provides instrumentation for JBoss EAP 7. You will now see the same visibility into your web transactions, app server stats, and frameworks that you have with previous versions of JBoss EAP.

• Play 2.7

  The Java Agent now provides instrumentation for Play 2.7. The previous Java agent release supports versions of Play up to 2.6.

• WebSphere Liberty

  Added ThreadPool metrics for WebSphere Liberty Profile. You will now see the active threads in the Threads tab of the JVM metrics page

Fixes

• Fixes an issue where OKHttp 3 was not tracking external total time correctly.
• Fixes an issue where for some JDBC drivers, the agent would execute additional getMetaData queries..
• Fixes an issue with the agent’s Scala instrumentation that could result in incorrect throughput, invalid or negative data in transaction segments, or inability to ignore status codes.
• Fixes an issue with the play-ws instrumentation that caused ClassNotFound exceptions to occur in the agent logs when withHeaders is used. This could result incomplete transactions and attributes in RPM.

Melhorias

• Java 10

O agente Java da New Relic agora é totalmente compatível com o Java 10. Para mais informações sobre a versão do JDK e o agente Java, consulte este tópico no Explorers Hub.

• Não compatível com Java 6

Para continuar a inovar e fornecer novos recursos de forma eficiente aos nossos clientes que executam na JVM, esta e as futuras versões do agente não são compatíveis com o Java 6. Caso esteja executando o Java 6, é possível continuar usando o agente Java 4.3.0 ou inferior. Para obter detalhes, consulte este tópico no Explorers Hub.

• Akka 2.5 e Akka HTTP 10.1

O agente Java agora suporta Akka 2.5.x e Akka HTTP 10.1.x. Será possível ver as chamadas Akka HTTP como transações do New Relic, ver as transferências entre os atores Akka e entender as chamadas para outros banco de dados e serviços.

• Solr 7

O agente Java agora oferece suporte ao Solr 7.x. O suporte ao Solr da New Relic relata chamadas de banco de dados para servidores Solr, bem como monitora o próprio servidor Solr.

Problema conhecido: a coleta de estatísticas JMX para o Solr 7 não é suportada a partir desta versão.

• Fonte de dados do WebLogic

O agente Java agora exibe dados de integridade sobre a fonte de dados do WebLogic na guia Datasource, na página da JVM.

Correções

• Corrigido um problema em que o agente Java 4.3.0 não relatava dados dependendo da configuração de localidade da JVM. Agente Java 4.3.0 falhou ao enviar dados de evento se a localidade da JVM estiver configurada para usar uma vírgula como decimal. Seria possível ver NumberFormatException no log do agente.
• Corrigido um problema raro em que o agente tentará incorretamente retransformar classes continuamente quando uma extensão com uma data de modificação no futuro for usada, causando um aumento significativo na carga da CPU.
• Corrigida uma ConcurrentModificationException causada pela instrumentação ning que se manifesta na instrumentação Mule, o que faz com que a solicitação afetada seja repetida e o agente Java não relate os dados de cabeçalho.
• Corrigido um problema em que, se enable_auto_app_naming fosse definido como true e distributed_tracing.enabled fosse definido como true, ele faria a amostragem de cada evento de distributed trace. Agora, se o agente tiver ambas as configurações habilitadas, ele não ativará o distributed tracing.

Improvements

• Distributed tracing

Distributed tracing lets you see the path that a request takes as it travels through your distributed system. By showing the distributed activity through a unified view, you can troubleshoot and understand a complex system better than ever before.

Distributed tracing is available with an APM Pro or equivalent subscription. To see a complete distributed trace, you need to enable the feature on a set of neighboring services. Enabling distributed tracing changes the behavior of some New Relic features, so carefully consult the transition guide before you enable this feature.

To enable distributed tracing, set enabled to true in the distributed_tracing section in the newrelic.yml config file.

distributed_tracing:
    enabled: true

• Added configuration option proxy_scheme to allow the agent to connect via https only proxies.

Fixes

• Fixed an issue where transaction throughput counts could be artificially inflated when using async servlets in Jersey.
• Fixed an issue where JBoss and Wildfly datasources could cause a LinkageError.

Bug fixes

• Fixed a bug where transactions were being kept alive for too long when application is under heavy GC, causing inaccurate throughput to be reported.
• Fixed a bug in which Akka routing instrumentation could cause extra memory usage. When this is the case, the transaction throughput will look significantly lower than anticipated.
• Fixed a rare bug in Play WS instrumentation where exceptions thrown by instrumentation were propagated out to the application code, potentially causing the request to error.
• Fixed a bug where Jersey Client and HttpUrlConnection could be double instrumented, resulting in inflated external call count.
• Fixed a bug where the total time and response time for a long running task could be misreported.

Improvements

• Configuration for custom_insights_events.max_samples_stored format in YAML has been changed. For agents 4.1.0 and above, the old .yml config setting will be ignored, which will result in the agent defaulting to max samples stored of 10,000 custom events. When you update your agent, please migrate to the new format:

custom_insights_events:
    enabled: true
    max_samples_stored: 5000

• The agent will log a warning message when it detects that the java.endorsed.dirs property is used. Classes in these directories cannot be instrumented by the agent because they are loaded by the bootstrap classloader.

Fixes

• Ensure that custom events added during a transaction do not get discarded if the transaction is ignored via a call to NewRelic.ignoreTransaction().
• A security update that corrects an issue affecting PostgreSQL that could occur if High-security mode was enabled (or record_sql was set to off) and a query ran slow enough to trigger an explain plan. If the above conditions were met the agent may not have properly stripped out all information from the query. For information on this fix, see the security bulletin.
• Addresses cases where the agent could not parse database statements that included the IGNORE and INTO keywords.

Fixes

• Fixes an issue Introduced in 3.48.0 with event sampling. The agent would only report the first max_samples_stored events in a given minute reporting period and disregard the remainder for that minute. With the fix, the agent randomly samples those events across the reporting period.

Improvements

• Removed the SSL configuration option: SSL is now always used in communication with New Relic servers. The newrelic.yml ssl configuration and -Dnewrelic.config.ssl system property are no longer used. Setting either value to anything other than true will result in logging a warning.
• Minimum version required for use in EU data center.

Fixes

• Fixes an issue where the thread profiler could fail to report. In this case, the agent logged a java.lang.StackOverflowError.