makes the difference, it improved the exception handling by logging a severe message
before throwing JsonbException.
For some reason in JsonBindingProvider,
org.eclipse.yasson.internal.Unmarshaller Invalid token=EOF
----------------------------------------------------------
Key: WFLY-13079
URL:
https://issues.redhat.com/browse/WFLY-13079
Project: WildFly
Issue Type: Bug
Components: REST
Affects Versions: 19.0.0.Beta2
Reporter: Cheng Fang
Assignee: Alessio Soldano
Priority: Major
When running the batch sample application {{numbers-chunk}}
(
https://github.com/jberet/numbers-chunk.git), log shows the following severe message.
The same app runs fine with previous versions of WildFly:
{code}
23:30:45,307 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 29)
WFLYUT0021: Registered web context: '/numbers-chunk' for server
'default-server'
23:30:45,404 INFO [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0010:
Deployed "numbers-chunk.war" (runtime-name : "numbers-chunk.war")
23:31:00,750 SEVERE [org.eclipse.yasson.internal.Unmarshaller] (default task-1) Invalid
token=EOF at (line no=1, column no=0, offset=-1). Expected tokens are: [CURLYOPEN,
SQUAREOPEN, STRING, NUMBER, TRUE, FALSE, NULL]
{code}