Yes, that's basically it. Background thread exceptions are not being caught by
Tapestry application, so you need to take care of the logging yourself.
(Also, do not forget to do thread cleanup).
—
Sent from Mailbox
On Fri, Nov 20, 2015 at 12:30 PM, Nathan Quirynen
wrote:
> Or do you mean
Or do you mean I should just surround everything with a try catch to
catch any exception and then use the logger to log it?
On 20/11/15 11:22, Nathan Quirynen wrote:
Hey Ilya,
Hmm I'm not sure what you mean. It does log everything, but no
exceptions:
public class TestPage {
@Inject
Hey Ilya,
Hmm I'm not sure what you mean. It does log everything, but no exceptions:
public class TestPage {
@Inject
private ParallelExecutor parallelExecutor;
void setupRender() {
parallelExecutor.invoke(new SomeBackgroundTask());
}
public class SomeBackgroundTask
You may pass injected Logger instance to parallel execution, just like you
do normally.
On Thu, Nov 19, 2015 at 5:07 PM, Nathan Quirynen <
nat...@pensionarchitects.be> wrote:
> Hi,
>
> When using the ParallelExecutor exceptions thrown seem to be ignored in
> some way? The invokable just stops whe
Hi,
When using the ParallelExecutor exceptions thrown seem to be ignored in
some way? The invokable just stops when there's an error somewhere, but
no exception is being logged, making it hard to find the problem.
How can I get exceptions happening in the invokable getting logged?
Simple exam
