Splunk Dev

Accessing HEC with Java getting error Failed to connect to hecdevsplunk.company.com/11.54.0.234:8088

steveIMS
Engager

Using Java Class HttpEventCollectorLoggingHandler, with properties file, implementing the HttpEventCollectorErrorHandler.

The Reply; Error Code and Error text from HttpEventCollectorErrorHandler is:

Reply: Failed to connect to hecdevsplunk.company.com/11.54.0.234:8088
ErrorCode: -1
ErrorText: com.google.gson.stream.MalformedJsonException: Use JsonReader.setLenient(true) to accept malformed JSON at line 1 column 9 path $
Failed write of Log Event: Failed to connect to hecdevsplunk.company.com/11.54.0.234:8088
HttpEventCollectorErrorHandler

Any assistance would be appreciated, Thanks Steve.

Tags (1)

struffieux
Engager

Hi,

I have the same error.:

om.splunk.logging.HttpEventCollectorErrorHandler$ServerErrorException: com.google.gson.stream.MalformedJsonException: Use JsonReader.setLenient(true) to accept malformed JSON at line 1 column 7 path $

Something new about it?

0 Karma

struffieux
Engager

It seems in case of error by send event that HttpEventCollectorSender will instantiate a ServerErrorException:

 HttpEventCollectorErrorHandler.error(events, new ServerErrorException(ex.getMessage()));

And ServerErrorException try to parse the message as JSON (!):

        public ServerErrorException(String serverReply) {
            this.reply = serverReply;

            try {
                JsonObject json = JsonParser.parseString(serverReply).getAsJsonObject();
                this.errorCode = json.get("code").getAsLong();
                this.errorText = json.get("text").getAsString();
            } catch (Exception var3) {
                this.errorText = var3.getMessage();
            }

        }

So this error is not the original error.

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Build resilience for the agentic era: Join us at Splunk Go San Jose

AI is changing how organizations build, operate, and secure digital services. As teams adopt AI agents and ...

Manage Edge Processor pipelines end to end with APIs

This guide uses the Data Management APIs to create an Edge Processor, onboard one instance, deploy a pipeline ...