Closed tomas-knap closed 7 years ago
I define new task, run it. Then, when observing logs in tomcat (catalina.out), I got the log as below. But from that, I do not know where the problem was. So ideally the service returning status of the execution should provide some more detail if there is an error state. Could be something low level (like the exception) to start with, so that consumer of such service can see what happened.
I agree, although the exception is eventually logged (albeit abridged as a part of reply message) when you attempt to get the result from the future that does the processing in its own thread.
I will investigate why the logging does not work for the separate processing thread, or if it is even done.
The problem is that TableMinerPlusFactory silently consumes any errors which occur - see TableMinerPlusFactory:99. Such exception must be propagated to REST API, so that it can be provided together with the /task/x/result in some "detail" field (so that the caller does not get only info that there was "ERROR".)
The problem is that TableMinerPlusFactory silently consumes any errors which occur - see TableMinerPlusFactory:99. Such exception must be propagated to REST API, so that it can be provided together with the /task/x/result in some "detail" field (so that the caller does not get only info that there was "ERROR".)
I have a bad feeling that is not the first time we encouter this error. Fixing right away.
The problem is that TableMinerPlusFactory silently consumes any errors which occur - see TableMinerPlusFactory:99. Such exception must be propagated to REST API, so that it can be provided together with the /task/x/result in some "detail" field (so that the caller does not get only info that there was "ERROR".)
I have a bad feeling that is not the first time we encouter this error. Fixing right away.
Should be fixed now. At least in the sense that the exceptions are not swallowed.
I define new task, run it. Then, when observing logs in tomcat (catalina.out), I got the log as below. But from that, I do not know where the problem was. So ideally the service returning status of the execution should provide some more detail if there is an error state. Could be something low level (like the exception) to start with, so that consumer of such service can see what happened.
Btw. the log of the Odalic Core execution disappeared from the consol (catalina.out), that was on purpose?