New version of SEC / DB connector does not provide proper logging information to troubleshoot/narrow down the issue

[s.gan...@gmail.com]

We installed the new version of SEC and DB connector as per RMP's suggestion as the older version was not stable and would crash very frequently.

1)When the new DB connector was starting up and issue was that the JDBC config file had an extra white space.
The error in the logs were
--------------------------
INFO: JDBC Adapter Started
java.lang.StringIndexOutOfBoundsException: String index out of range: 142
--------------------------
This error is generic and does not help at all. We worked for 3-4 days doing all trial and error methods to find out that the extra white space was causing the issue.

2)If the SQL query fails due to syntax its logged as INFO message in the log file rather than as ERROR:
------------
Jun 27, 2014 2:41:50 PM org.runmyprocess.sec.SECLogManager log
INFO: Executing query ...
Jun 27, 2014 2:41:50 PM org.runmyprocess.sec.SECLogManager log
INFO: Query execution failed
java.lang.Exception: java.sql.SQLSyntaxErrorException: ORA-00911: invalid character
------------

Please help us in updating the log for JDBC.jar as even minor issues are taking few days to fix and we always have to rely on trial and error methods.

Regards,
Ganesh Raj

[thoshino]

Hi Ganesh,

Thank you for the feedback.

Can you be more specific about how and what you think should be the solution for the 2 problems raised?

It will be good input for us.

Best regards,

Taka

[Shivaram, Ganesh]

Hi Taka,

 

For the 1^st when we worked we could not root cause the issue until we did some trial /error methods as it was a very generic exception thrown.

These errors should be caught and appropriate message thrown to user so we can narrow down the issue.

 

For 2^nd problem its more to do with error type, ideally that should be have been listed as “ERROR” rather than “INFO”.

 

 

 

Regards,

 

Ganesh Raj S

O: +1(215)-323-2007

M: +1(630)-456-8500

[thoshino]

Hi,

1st point:

I think that is a good idea. It would be impossible to cover for all error scenarios, helpful error message is good.

For the specific problem about the config file error, maybe you can write some code to check the syntax.

Key = value pairs,

value is JSON format, with keys "sqlDriver", "sqlSource", "sqlDriverPath",

The parameters are exactly same as if you would have done it through any Java application, so you could also add check DB connection during the verify code.

2nd point:

If the error type was simply ERROR, then it will be difficult to separate the error of the application (JDBC.jar) and error from Database.

Do you have any ideas around this?

Again, we appreciate your feedback.

And FYI, our SEC components are open source projects:

https://github.com/runmyprocess/

Best regards,

Taka