You'll want to just approach this as any other issue - can you open a JIRA showing the underlying stacktrace, the user/source query and sample data? TEIID-2437 and similar are caused when there is a type mismatch in data, which causes serialization to fail. Typically we should convert any mismatched data to the expected runtime type as we bring it into Teiid, but your issue may highlight something deficient.
> This would mean that to solve this issue I have to install EAP in place of 7.1.1
Are you adverse to ever moving to EAP or specifically concerned about the near term timing?
> could you plan to backport some patches (the critical ones) into 8.3 releasing a 8.3.x
The short answer is yes. On the download page you can see patch 2 for 8.3.x that addresses 4 critical/common issues. The long answer is that prior to subsequent final releases we'll take responsibility for producing patches for the latest final release. So if this gets addressed prior to final and is a critical/common issue, then it'll be added to that patch and the 8.3.x branch. Otherwise you can always stick with an older release, such as 8.3, longer by manually pulling in patches into your own git fork of the release branch 8.3.x.
Will open a jira, but I have no logs in the server.log (I'm in domain mode and maybe I have to acrtivate something more?) the error just comes up to squirrel
I'd like to pass to EAP, but for me changing a version of TEIID is quicker than changing the whole AS, that could call for bigger "change issue".