I dont think you can do this by configuration, AFAIK you need to log the statements (from code) befor you fire them. Alternatively you can use somethink like SQL Monitor but then you will not have the statements in your log4J log file.
If you decide to make the 1st option you can create a wrapper class for running SQL statements which logs these.