Bug 808529 - org.jboss.soa.esb.listeners.gateway.SqlTableGatewayListener class needs to log DEBUG statements
Summary: org.jboss.soa.esb.listeners.gateway.SqlTableGatewayListener class needs to lo...
Keywords:
Status: VERIFIED
Alias: None
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: JBossESB
Version: 5.3.0 GA
Hardware: All
OS: All
medium
medium
Target Milestone: ER4
: 5.3.0 GA
Assignee: Kevin Conner
QA Contact: Jiri Pechanec
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-30 15:48 UTC by Taneem Ibrahim
Modified: 2015-03-12 11:24 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBESB-3803 0 Minor Closed org.jboss.soa.esb.listeners.gateway.SqlTableGatewayListener class needs to log DEBUG statements 2013-10-28 09:56:06 UTC

Description Taneem Ibrahim 2012-03-30 15:48:16 UTC 
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.
Comment 1 Rick Wagner 2012-03-30 15:51:45 UTC 
GSS prioritizes this 'medium'.  This should be a very fast / low risk change, it would be nice to have it in SOA-P 5.3 if possible.
Comment 2 JBoss JIRA Server 2012-05-30 19:26:13 UTC 
Tom Cunningham <tcunning> updated the status of jira JBESB-3803 to Resolved
Comment 3 JBoss JIRA Server 2012-05-30 19:26:30 UTC 
Tom Cunningham <tcunning> updated the status of jira JBESB-3803 to Closed
Comment 4 JBoss JIRA Server 2012-05-30 19:26:30 UTC 
Tom Cunningham <tcunning> made a comment on jira JBESB-3803

Added debug statements to scan/update/deleteStatement.
Comment 5 Suz 2012-06-13 02:55:57 UTC 
I have set the technical note field to negative as this appears to have been detected and fixed in the same version, so users will not have seen it.
Comment 6 Jiri Pechanec 2012-06-27 07:39:05 UTC 
Verified in ER4
Note You need to log in before you can comment on or make changes to this bug.