Great hint, Thanks a lot! Am 22.09.2015 um 09:28 schrieb Ahmad Emneina: > Forgot to note: Look for log4j-cloud.xml, and change the appropriate > components to trace. > > On Tue, Sep 22, 2015 at 12:26 AM, Ahmad Emneina <[email protected]> wrote: > >> Changing the log level in tomcat, to trace, should surface the DB >> calls. They'll contain the job ID as well so mapping shouldn't be an >> issue. Logs could grow quicker on trace, so if space is an issue, you >> wont want it running on trace for long. >> >>> On Sep 21, 2015, at 11:45 PM, Norbert Klein < >> [email protected]> wrote: >>> Hello everybody, >>> >>> is there a possibility to issolate certain mysql queries for error >> analysis? >>> I am unable to delete a storage pool, I see the exeception in the log >> file >>> and I looked in the code. But for me it is difficult to find out what >>> mysql query >>> is created inside the code. I would like to see what queries are run >>> by my api call. So I logged all queries in the database but there are >>> simply too much >>> to see which one belongs to the command to delete the storage pool. >>> >>> Regards >>> Norbert >>> -- >>> www.infosecprojects.net <http://www.infosecprojects.net/> >>>
-- www.infosecprojects.net <http://www.infosecprojects.net/>
