-
Bug
-
Resolution: Done
-
Major
-
None
-
None
-
None
-
None
In fresh BPM Suite 6.3.0 + Tomcat installation, there can be exceptions observed in the log
https://gist.github.com/agiertli/f7032f3a7641d121dbbfa4ffc954f767
Maciej explained these as follows:
these are warnings only as they code failed to look up EJB version of these services and thus fallbaks to default ones. It’s mainly about the JEE containers being strick on thread management and access to JEE resources such as transaction.
I believe they should not have any impact on the overall functionality of the system. Easy to verify - just change a drl and see if that triggers incremental build.
If we do not want to suppress these exceptions on our code level, then I think we should document it, so users won't be concerned.