Failed to create com.microsoft.applicationinsights.channel.concrete.inprocess.InProcessTelemetryChannel, null about applicationinsights-java HOT 7 CLOSED

I'm having the same issue:

Failed to create com.microsoft.applicationinsights.channel.concrete.inprocess.InProcessTelemetryChannel, null

INFO | jvm 1 | 2017/01/02 21:59:19 | java.lang.NoClassDefFoundError: Could not initialize class org.apache.http.impl.conn.ManagedHttpClientConnectionFactory INFO | jvm 1 | 2017/01/02 21:59:19 | at org.apache.http.impl.conn.PoolingHttpClientConnectionManager$InternalConnectionFactory.<init>(PoolingHttpClientConnectionManager.java:493) INFO | jvm 1 | 2017/01/02 21:59:19 | at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.<init>(PoolingHttpClientConnectionManager.java:149) INFO | jvm 1 | 2017/01/02 21:59:19 | at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.<init>(PoolingHttpClientConnectionManager.java:138) INFO | jvm 1 | 2017/01/02 21:59:19 | at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.<init>(PoolingHttpClientConnectionManager.java:114) INFO | jvm 1 | 2017/01/02 21:59:19 | at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.<init>(PoolingHttpClientConnectionManager.java:105) INFO | jvm 1 | 2017/01/02 21:59:19 | at com.microsoft.applicationinsights.internal.channel.common.ApacheSender43.<init>(ApacheSender43.java:45) INFO | jvm 1 | 2017/01/02 21:59:19 | at com.microsoft.applicationinsights.internal.channel.common.ApacheSenderFactory.create(ApacheSenderFactory.java:40) INFO | jvm 1 | 2017/01/02 21:59:19 | at com.microsoft.applicationinsights.internal.channel.common.TransmissionNetworkOutput.<init>(TransmissionNetworkOutput.java:95) INFO | jvm 1 | 2017/01/02 21:59:19 | at com.microsoft.applicationinsights.internal.channel.common.TransmissionNetworkOutput.create(TransmissionNetworkOutput.java:85) INFO | jvm 1 | 2017/01/02 21:59:19 | at com.microsoft.applicationinsights.channel.concrete.inprocess.InProcessTelemetryChannelFactory.create(InProcessTelemetryChannelFactory.java:41) INFO | jvm 1 | 2017/01/02 21:59:19 | at com.microsoft.applicationinsights.channel.concrete.inprocess.InProcessTelemetryChannel.initialize(InProcessTelemetryChannel.java:263) INFO | jvm 1 | 2017/01/02 21:59:19 | at com.microsoft.applicationinsights.channel.concrete.inprocess.InProcessTelemetryChannel.<init>(InProcessTelemetryChannel.java:147) INFO | jvm 1 | 2017/01/02 21:59:19 | at com.microsoft.applicationinsights.internal.config.TelemetryConfigurationFactory.setChannel(TelemetryConfigurationFactory.java:396) INFO | jvm 1 | 2017/01/02 21:59:19 | at com.microsoft.applicationinsights.internal.config.TelemetryConfigurationFactory.initialize(TelemetryConfigurationFactory.java:102) INFO | jvm 1 | 2017/01/02 21:59:19 | at com.microsoft.applicationinsights.TelemetryConfiguration.getActive(TelemetryConfiguration.java:74) INFO | jvm 1 | 2017/01/02 21:59:19 | at com.microsoft.applicationinsights.web.internal.WebRequestTrackingFilter.init(WebRequestTrackingFilter.java:127) INFO | jvm 1 | 2017/01/02 21:59:19 | at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:295) INFO | jvm 1 | 2017/01/02 21:59:19 | at org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:422) INFO | jvm 1 | 2017/01/02 21:59:19 | at org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterConfig.java:115) INFO | jvm 1 | 2017/01/02 21:59:19 | at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:4071) INFO | jvm 1 | 2017/01/02 21:59:19 | at org.apache.catalina.core.StandardContext.start(StandardContext.java:4725) INFO | jvm 1 | 2017/01/02 21:59:19 | at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:799) INFO | jvm 1 | 2017/01/02 21:59:19 | at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:779) INFO | jvm 1 | 2017/01/02 21:59:19 | at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:601) INFO | jvm 1 | 2017/01/02 21:59:19 | at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1079) INFO | jvm 1 | 2017/01/02 21:59:19 | at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:1002) INFO | jvm 1 | 2017/01/02 21:59:19 | at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:506) INFO | jvm 1 | 2017/01/02 21:59:19 | at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1315) INFO | jvm 1 | 2017/01/02 21:59:19 | at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:324) INFO | jvm 1 | 2017/01/02 21:59:19 | at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142) INFO | jvm 1 | 2017/01/02 21:59:19 | at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1061) INFO | jvm 1 | 2017/01/02 21:59:19 | at org.apache.catalina.core.StandardHost.start(StandardHost.java:840) INFO | jvm 1 | 2017/01/02 21:59:19 | at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053) INFO | jvm 1 | 2017/01/02 21:59:19 | at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:463) INFO | jvm 1 | 2017/01/02 21:59:19 | at org.apache.catalina.core.StandardService.start(StandardService.java:525) INFO | jvm 1 | 2017/01/02 21:59:19 | at org.apache.catalina.core.StandardServer.start(StandardServer.java:754) INFO | jvm 1 | 2017/01/02 21:59:19 | at org.apache.catalina.startup.Catalina.start(Catalina.java:595) INFO | jvm 1 | 2017/01/02 21:59:19 | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) INFO | jvm 1 | 2017/01/02 21:59:19 | at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) INFO | jvm 1 | 2017/01/02 21:59:19 | at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) INFO | jvm 1 | 2017/01/02 21:59:19 | at java.lang.reflect.Method.invoke(Unknown Source)

from applicationinsights-java.

In the release 1.0.7, AI Core JAR was packaged with all dependencies (so-called shadow jar), so I would expect less issues with apache 43 connections creation. Please give it a try.

from applicationinsights-java.

@TheRubble and @JosJanssen were you able to try the fix recommended by @Dmitry-Matveev ?

from applicationinsights-java.

@beckylino

I remember we found another solution to get it working.
But we abandoned that project shortly afterwards, so we didn't needed another fix.

from applicationinsights-java.

@Dmitry-Matveev I have not seen this issue reproducing in the current version of the SDK.. Is it safe to close this issue now? I believe JosJanssen had also found a way to get it working according to his previous comment.

from applicationinsights-java.

@dhaval24, we've updated Http Client to version 4.5.3 since then and packaged it as a Shadow Jar dependencies with our own namespace. It might've helped, of course. If we have a repro with 1.0.6 and it goes away as soon as we update app onto 1.0.10 - that's a definite signal to close the bug.
However, we have enough reason to believe that the aforementioned fixes should've addressed the issue and we can close the bug as is (but with some lower confidence).

from applicationinsights-java.

@Dmitry-Matveev thanks for the update and closing the bug.

from applicationinsights-java.