Its using jdbc prepared statements so you cannot see the actual SQL query. However I think there is some JDBC spy drivers you can use as proxy that can log the actual SQL. Or you can look at the database side which should have such information.
You can also try to turn on some DEBUG/TRACE logging on spring jdbc and the camel sql component as it may also log a bit more details that can get you more details. On Sat, Apr 22, 2017 at 4:16 AM, T.K <[email protected]> wrote: > Hi > > I am using servicemix 7.0.0, camel 2.16.3. > > I am using camel SQL Component as below- > > <to uri="sql:INSERT INTO transactions(txn_id, sender_org_unit_id, > receiver_org_unit_id, doc_type_id, bp_id, > route_id, txn_create_datetime, > txn_modified_datetime, doc_id, > bp_instance_id, technical_status_id, > source_doc, > target_doc) VALUES (:#transactionID, > :#senderID, :#receiverID, > :#docTypeID, > :#bpID, :#routeID, :#createDateTime, > :#modifiedDateTime, :#docID, > :#bpInstanceID, > :#statusID, :#sourceDoc, :#targetDoc);" /> > > I need to log actual INSERT sql statement into servicemix log file which get > triggered after all values has been set. > > I change PAX logging threshold to DEBUG, also added > > log4j.logger.org.apache.camel.component.sql=DEBUG > log4j.logger.org.apache.camel.component.sql.appender-ref=out > > but no luck. > > Rgds > T.K > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Log-end-SQL-statement-in-sql-component-tp5798079.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
