Splunk Dev

Splunk JAVA SDK Version issue

lsw6875
Engager

I am using JAVA SDK to display data on screen.

There was no error in version 1.6.0, which I initially used.

However, after updating to 1.6.3, the following error appeared.

This error is "java.lang.NumberFormatException: multiple points".

This happens randomly when a service connects or a job is performed.

2024-10-21 12:16:53.899 ERROR 2732 --- [nio-8090-exec-4] o.a.c.c.C.[.[.[/].[dispatcherServlet]    : Servlet.service() for servlet [dispatcherServlet] threw exception
 
java.lang.NumberFormatException: multiple points
at java.base/jdk.internal.math.FloatingDecimal.readJavaFormatString(FloatingDecimal.java:1890) ~[na:na]
Suppressed: reactor.core.publisher.FluxOnAssembly$OnAssemblyException: 
Assembly trace from producer [reactor.core.publisher.MonoCompletionStage] :
reactor.core.publisher.Mono.fromCompletionStage(Mono.java:549)
org.springframework.core.ReactiveAdapterRegistry$ReactorRegistrar.lambda$registerAdapters$4(ReactiveAdapterRegistry.java:241)
Error has been observed at the following site(s):
|_ Mono.fromCompletionStage ⇢ at org.springframework.core.ReactiveAdapterRegistry$ReactorRegistrar.lambda$registerAdapters$4(ReactiveAdapterRegistry.java:241)
Stack trace:
at java.base/jdk.internal.math.FloatingDecimal.readJavaFormatString(FloatingDecimal.java:1890) ~[na:na]
at java.base/jdk.internal.math.FloatingDecimal.parseDouble(FloatingDecimal.java:110) ~[na:na]
at java.base/java.lang.Double.parseDouble(Double.java:543) ~[na:na]
at java.base/java.text.DigitList.getDouble(DigitList.java:169) ~[na:na]
at java.base/java.text.DecimalFormat.parse(DecimalFormat.java:2126) ~[na:na]
at java.base/java.text.SimpleDateFormat.subParse(SimpleDateFormat.java:1933) ~[na:na]
at java.base/java.text.SimpleDateFormat.parse(SimpleDateFormat.java:1541) ~[na:na]
at java.base/java.text.DateFormat.parse(DateFormat.java:393) ~[na:na]
at com.splunk.Value.toDate(Value.java:109) ~[splunk-1.6.3.0.jar:1.6.3]
at com.splunk.Resource.load(Resource.java:166) ~[splunk-1.6.3.0.jar:1.6.3]
at com.splunk.Entity.load(Entity.java:356) ~[splunk-1.6.3.0.jar:1.6.3]
at com.splunk.Job.refresh(Job.java:940) ~[splunk-1.6.3.0.jar:1.6.3]
at com.splunk.JobCollection.create(JobCollection.java:90) ~[splunk-1.6.3.0.jar:1.6.3]
at com.splunk.JobCollection.create(JobCollection.java:108) ~[splunk-1.6.3.0.jar:1.6.3]
at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:218) ~[spring-core-5.3.4.jar:5.3.4]
at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:779) ~[spring-aop-5.3.4.jar:5.3.4]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163) ~[spring-aop-5.3.4.jar:5.3.4]
at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:750) ~[spring-aop-5.3.4.jar:5.3.4]
at org.springframework.aop.interceptor.AsyncExecutionInterceptor.lambda$invoke$0(AsyncExecutionInterceptor.java:115) ~[spring-aop-5.3.4.jar:5.3.4]
at org.springframework.aop.interceptor.AsyncExecutionAspectSupport.lambda$doSubmit$3(AsyncExecutionAspectSupport.java:276) ~[spring-aop-5.3.4.jar:5.3.4]
at java.base/java.util.concurrent.CompletableFuture$AsyncSupply.run$$$capture(CompletableFuture.java:1700) ~[na:na]
at java.base/java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java) ~[na:na

 

Has anyone solved this 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!

Accelerate Splunk App Development with AI

  Learn how to automate the repetitive parts of your build cycle.   Register to Attend   Join our Tech Talk ...

Meet the .conf26 AI Agent Buildathon Winners

At the .conf26 AI Agent Buildathon, Splunk users turned their operational expertise into working AI agents ...

Trusted Autonomy in the SOC: A Maturity Journey

AI is compressing attacker timelines and pushing SOC teams beyond human capacity thresholds. The next SOC ...