How can I stop the catalina.out from being filled with "java.text.ParseException: Unparseable date:"

Tibor Dudas

Every week 1GB of logs is written in the form:

java.text.ParseException: Unparseable date: "08.02.2021 07:58"
at java.text.DateFormat.parse(DateFormat.java:366)
at com.thed.zephyr.je.rest.delegate.impl.ScheduleResourceDelegateImpl.getSerializeSchedule(ScheduleResourceDelegateImpl.java:3382)
at com.thed.zephyr.je.rest.delegate.impl.ScheduleResourceDelegateImpl.extractSchedulesForIssue(ScheduleResourceDelegateImpl.java:569)
at com.thed.zephyr.je.rest.delegate.impl.ScheduleResourceDelegateImpl.getExecutions(ScheduleResourceDelegateImpl.java:491)
at com.thed.zephyr.je.rest.ScheduleResource.getExecutions(ScheduleResource.java:351)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.atlassian.plugins.rest.common.interceptor.impl.DispatchProviderHelper$ResponseOutInvoker.lambda$_dispatch$0(DispatchProviderHelper.java:181)
at com.atlassian.plugins.rest.common.interceptor.impl.DispatchProviderHelper.lambda$invokeMethodWithInterceptors$0(DispatchProviderHelper.java:81)
at com.atlassian.plugins.rest.common.interceptor.impl.DefaultMethodInvocation.invoke(DefaultMethodInvocation.java:53)
at com.atlassian.plugins.rest.common.expand.interceptor.ExpandInterceptor.intercept(ExpandInterceptor.java:42)
at com.atlassian.plugins.rest.common.interceptor.impl.DefaultMethodInvocation.invoke(DefaultMethodInvocation.java:53)
at com.atlassian.plugins.rest.common.interceptor.impl.DispatchProviderHelper.invokeMethodWithInterceptors(DispatchProviderHelper.java:106)
at com.atlassian.plugins.rest.common.interceptor.impl.DispatchProviderHelper$ResponseOutInvoker._dispatch(DispatchProviderHelper.java:180)
at com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
at com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
at com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
at com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)

...

Nic Brough -Adaptavist-

You've got something in your testing routines or reporting that is sending Jira or, more accurately, the Zephyr app you have installed on Jira, a duff date, or there's broken data in your database, with a date being misrepresented somewhere.  (The fact it gives you a valid looking date suggests the former possibility, as a broken date in the database probably wouldn't be able to render in the error)