[
https://issues.jboss.org/browse/JBESB-3803?page=com.atlassian.jira.plugin...
]
Tom Cunningham resolved JBESB-3803.
-----------------------------------
Assignee: Tom Cunningham
Fix Version/s: 4.11 CP1
Resolution: Done
org.jboss.soa.esb.listeners.gateway.SqlTableGatewayListener class
needs to log DEBUG statements
-----------------------------------------------------------------------------------------------
Key: JBESB-3803
URL:
https://issues.jboss.org/browse/JBESB-3803
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.11
Environment: ESB as used by SOA-P.
Reporter: Rick Wagner
Assignee: Tom Cunningham
Priority: Minor
Fix For: 4.11 CP1
Description of problem:
SqlTableGatewayListener class in general has virtually not enough debug statements for
trouble shooting when a problem arises. Recently we ran into an issue with the SQL that
was built by SqlTableGatewayListener. Since there was no debug logging on the sql that got
built, we had to use byteman scripts to figure out the SQL.
The following three methods should at least log the SQL that it built before returning
from the method.
protected String scanStatement();
protected String updateStatement();
protected String deleteStatement();
Version-Release number of selected component (if applicable):
JBossESB 4.10
How reproducible:
Does not apply.
Steps to Reproduce:
Does not apply.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira