How do I capture exception info for tMysqlInput component?

[Anonymous]

I've noticed that if anything goes wrong with my MySql queries, the only exception I ever see is NullPointerException. You can easily reproduce this by introducing a simple syntax error in the query.
Similar jobs running against Oracle tables returns the full error.
It's difficult to track down bugs in new jobs without the error info. Is this a bug in the component?
I'm using TOS 5.4.1.

[Anonymous]

hi beebell,
if you got a NullPointerException, it's not a sql error but a java error. You're trying to use a java method on a null value that doesn't manage that case.
It could be some connection parameters that 're not populate or you're using a varaible in your query that is null.

If your expectation is to catch some errors from sql engine, you've to uncheck batchsize in advanced parameters of your output DB componenent & use the reject flow.

hope it helps
regards
laurent

[Anonymous]

Hi,
Did you use tMySqlConnection component in your workflow?
Your job design sreenshots will be helpful for us to address your issue quickly.
Best regards
Sabrina