Forum Discussion

mneiferbag's avatar
mneiferbag
Contributor
3 years ago

Why MixpanelCustomEngine throws java.net.ConnectException ?

Hello everybody. I have upgraded to ReadyAPI-3.10.2 just yesterday. I run ReadyAPI on a Windows server VM without internet connection. While my projects run fine and the test cases pass, I have noticed the following exception in the logs. Could somebody please explain what "MixpanelCustomEngine" is and how to disable it. Thanks in advance!

 

04:55:47,787 ERROR [MixpanelCustomEngine] Connection timed out: connect
java.net.ConnectException: Connection timed out: connect
at sun.nio.ch.Net.connect0(Native Method) ~[?:?]
at sun.nio.ch.Net.connect(Net.java:576) ~[?:?]
at sun.nio.ch.Net.connect(Net.java:565) ~[?:?]
at sun.nio.ch.NioSocketImpl.connect(NioSocketImpl.java:588) ~[?:?]
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:333) ~[?:?]
at java.net.Socket.connect(Socket.java:645) ~[?:?]
at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:290) ~[?:?]
at sun.security.ssl.BaseSSLSocketImpl.connect(BaseSSLSocketImpl.java:174) ~[?:?]
at sun.net.NetworkClient.doConnect(NetworkClient.java:182) ~[?:?]
at sun.net.www.http.HttpClient.openServer(HttpClient.java:497) ~[?:?]
at sun.net.www.http.HttpClient.openServer(HttpClient.java:600) ~[?:?]
at sun.net.www.protocol.https.HttpsClient.<init>(HttpsClient.java:265) ~[?:?]
at sun.net.www.protocol.https.HttpsClient.New(HttpsClient.java:379) ~[?:?]
at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(AbstractDelegateHttpsURLConnection.java:189) ~[?:?]
at sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1232) ~[?:?]
at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:1120) ~[?:?]
at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:175) ~[?:?]
at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1653) ~[?:?]
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1577) ~[?:?]
at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:527) ~[?:?]
at sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:308) ~[?:?]
at com.smartbear.analytics.impl.addon.MixpanelCustomEngine.pingRemoveMixpanelManager(MixpanelCustomEngine.java:57) [analytics-core-2.6.41.jar:?]
at com.smartbear.analytics.impl.addon.MixpanelCustomEngine.importEvents(MixpanelCustomEngine.java:97) [analytics-core-2.6.41.jar:?]
at com.smartbear.analytics.impl.addon.MixpanelImporter.processEvents(MixpanelImporter.java:142) [analytics-core-2.6.41.jar:?]
at com.smartbear.analytics.impl.addon.MixpanelImporter.processEvents(MixpanelImporter.java:125) [analytics-core-2.6.41.jar:?]
at com.smartbear.analytics.impl.addon.MixpanelImporter$2.run(MixpanelImporter.java:89) [analytics-core-2.6.41.jar:?]
at java.lang.Thread.run(Thread.java:831) [?:?]
at com.smartbear.analytics.impl.addon.MixpanelImporter.sendInboxEvents(MixpanelImporter.java:92) [analytics-core-2.6.41.jar:?]
at com.smartbear.analytics.impl.addon.MixpanelImporter.trackEvent(MixpanelImporter.java:68) [analytics-core-2.6.41.jar:?]
at com.smartbear.analytics.impl.ReadyApiMixpanelProvider.sendEventData(ReadyApiMixpanelProvider.java:129) [analytics-core-2.6.41.jar:?]
at com.smartbear.analytics.impl.ReadyApiMixpanelProvider.trackAction(ReadyApiMixpanelProvider.java:59) [analytics-core-2.6.41.jar:?]
at com.smartbear.analytics.AnalyticsManager$2.run(AnalyticsManager.java:154) [analytics-core-2.6.41.jar:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130) [?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:630) [?:?]
at java.lang.Thread.run(Thread.java:831) [?:?]

 

2 Replies

  • OlgaB4's avatar
    OlgaB4
    Established Member

    I've got the same problem on 3.20.0. Does anyone know how to disable MixpanelCustomEngine ?

    • mneiferbag's avatar
      mneiferbag
      Contributor
      Unfortunately, after updating to 3.20.0, I'm still having this problem and haven't found a solution yet.