topic Re: "Non-proxy" from AuthNet SDK is spamming our logs! in Integration and Testing

"Non-proxy" from AuthNet SDK is spamming our logs!

lightwave365 — Thu, 07 May 2020 14:59:48 GMT

Could someone please tell me why this is spaming our logs from the AuthorizeNet Java SDK? This is very bothersome for our customers.

We use the AcceptHosted method and poll every 10 seconds for unsettled transactions.

[2020-05-07 10:44:47,089] [ WARN] Defaulting to non-proxy environment (pool-7-thread-1:net.authorize.util.HttpClient)
[2020-05-07 10:44:57,368] [ WARN] Defaulting to non-proxy environment (pool-8-thread-1:net.authorize.util.HttpClient)
[2020-05-07 10:45:07,693] [ WARN] Defaulting to non-proxy environment (pool-9-thread-1:net.authorize.util.HttpClient)
[2020-05-07 10:45:17,953] [ WARN] Defaulting to non-proxy environment (pool-10-thread-1:net.authorize.util.HttpClient)
[2020-05-07 10:45:28,223] [ WARN] Defaulting to non-proxy environment (pool-11-thread-1:net.authorize.util.HttpClient)

Also I tried to search "non-proxy" in the forums and it auto-corrected to "nonprofit". You might want to fix that.

Re: "Non-proxy" from AuthNet SDK is spamming our logs!

lightwave365 — Mon, 11 May 2020 13:45:53 GMT

Well since no one is responding to us I dug through their own code. Cringiness of variables begining with capital letters aside, (Just...why. Java conventions people. It's CS 101) it appears you must use a proxy if you don't want this message to be spammed?

Why is that? And how do you setup a proxy?

I really shouldn't have to debug your own code to solve my problem. I have my own job to do. Come on, guys.

if (UseProxy && ProxyHost != null) {
    // Use proxy	
} else {
    LogHelper.warn(logger, "Defaulting to non-proxy environment");
    httpClient = HttpClients.custom().setSSLSocketFactory(sslSocketFactory)
        .setDefaultRequestConfig(requestConfig).setRedirectStrategy(new 
        LaxRedirectStrategy()).build();
}

Re: "Non-proxy" from AuthNet SDK is spamming our logs!

lightwave365 — Mon, 18 May 2020 14:17:39 GMT

And it's been a week. Still no one helping us.

Re: "Non-proxy" from AuthNet SDK is spamming our logs!

lightwave365 — Tue, 26 May 2020 13:47:01 GMT

Two Weeks Later (spongebob announcer voice)

Re: "Non-proxy" from AuthNet SDK is spamming our logs!

lightwave365 — Tue, 02 Jun 2020 19:57:34 GMT

Alright, you guys are taking social distancing way too seriously. You're still allowed to talk to your customers through the computer. We aren't near each other.

Re: "Non-proxy" from AuthNet SDK is spamming our logs!

lightwave365 — Tue, 09 Jun 2020 14:32:28 GMT

Oh, you guys! Happy 4 week anniversary!

Sorry, I didn't get you anything. How about a pissed off customer? Aw crap, you already have that don't you? Eh, I can't really return it. But you might be able to exchange it for a happy one? I think there are some of those left.

Re: "Non-proxy" from AuthNet SDK is spamming our logs!

lightwave365 — Wed, 17 Jun 2020 14:35:56 GMT

Day 41: There doesn't seem to be an end it sight. The logs just keep coming and coming. Some of our devs have been driven mad. Others are starting to feel sorry for the AuthNet library:

"It doesn't know what it's doing. It was programmed that way. We shouldn't take it out on th - no, no. That's the Stockholm syndrome setting in. We'll get through this. We need to stand tough against this menace. We won't let it win. This is why I went to four years of college."

Re: "Non-proxy" from AuthNet SDK is spamming our logs!

lightwave365 — Mon, 22 Jun 2020 13:59:28 GMT

Yes, the SDK is spamming exactly like that. Just annoying and repetitve and giving me information i don't care about. Thanks buddy for the live demonstration.

Re: "Non-proxy" from AuthNet SDK is spamming our logs!

lightwave365 — Wed, 08 Jul 2020 16:21:46 GMT

Sorry guys, took a little vacation. Just needed some time away from the office for some rest, relaxation, and purging those AuthNet logs from my dreams. In those past few weeks we have maxed out our hard drives with 4.3 million lines of "Defaulting to non-proxy environment" in our logs. We'd delete those lines from our logs but they are clearly important since they are there with no explanation and they have a WARN prefix. Not to worry we are problem solvers. We have rented out a small warehouse and bought an additional 520 TB of server space to take on the load for the next few months. We should be able to store up to 2.7 billion lines of this important log now. We'll be sending you our electric bill.

Re: "Non-proxy" from AuthNet SDK is spamming our logs!

AlexPowers — Fri, 10 Jul 2020 20:14:30 GMT

Someone opened an issue for this on their GitHub at: https://github.com/AuthorizeNet/sdk-java/issues/172

Commenting there might get more attention, I'm not sure if the developers actually monitor these forums.

Re: "Non-proxy" from AuthNet SDK is spamming our logs!

lightwave365 — Mon, 13 Jul 2020 13:45:45 GMT

I have seen both "Administrators" and "Certified Developers" replying to threads around me for the past two months so clearly they are ignoring me - or they just want to see how far this creative story goes. But both are unacceptable. And ironically I have been spamming them about a spamming issue in their code while being slightly less annoying than actual spam. I'm looking at you above me RobuxFree. You need to up your game. I was so bored reading your comment. And how are bots getting by on these boards with this CAPTCHA at the bottom?

But thank you Alex for the link. Once again the customers help you more than the people who make the thing.

Re: "Non-proxy" from AuthNet SDK is spamming our logs!

allanrobert — Mon, 29 Jan 2024 08:38:29 GMT

From what I understand, it's like the SDK is trying to communicate without going through a proxy server, which can generate those warning messages in your logs. I'm not an expert, but have you tried tinkering with the SDK settings to see if you can switch it away from that default? It might help cut down on the noise in your logs. Also, thanks for the heads up about the forum's auto-correct mishap.