hange outside of the VO object.
--Alex
> -Original Message-
> From: Daan Hoogland [mailto:dhoogl...@schubergphilis.com]
> Sent: Wednesday, June 12, 2013 4:36 PM
> To: dev@cloudstack.apache.org
> Subject: RE: help on db code wanted
>
> Dear readers,
>
> I
16
Who has got the magic word for me?
Regards,
-Original Message-
From: Daan Hoogland [mailto:dhoogl...@schubergphilis.com]
Sent: donderdag 13 juni 2013 1:08
To: dev@cloudstack.apache.org
Subject: RE: help on db code wanted
Ok,
2013-06-13 00:54:21,841 INFO [cloud.utils.LogUtils] (main:n
-
From: Alex Huang [mailto:alex.hu...@citrix.com]
Sent: donderdag 13 juni 2013 1:04
To: dev@cloudstack.apache.org
Subject: RE: help on db code wanted
When you're debugging, you should modify the log4j-cloud.xml that jetty is
reading. I can't remember where it is by default. I ha
om]
> Sent: Wednesday, June 12, 2013 3:48 PM
> To: dev@cloudstack.apache.org
> Subject: RE: help on db code wanted
>
> Glad to be teaching for a change;) quite common greeting in dutch if you
> don't know how to start.
>
> About the log4j-cloud file. There is a lot of
those?
-Original Message-
From: Alex Huang [mailto:alex.hu...@citrix.com]
Sent: donderdag 13 juni 2013 0:44
To: dev@cloudstack.apache.org
Subject: RE: help on db code wanted
Nice...learn something new every day.
--Alex
> -Original Message-
> From: Daan Hoogland [ma
Nice...learn something new every day.
--Alex
> -Original Message-
> From: Daan Hoogland [mailto:dhoogl...@schubergphilis.com]
> Sent: Wednesday, June 12, 2013 3:36 PM
> To: dev@cloudstack.apache.org
> Subject: RE: help on db code wanted
>
> Thanks Alex,
>
> I
juni 2013 0:31
To: dev@cloudstack.apache.org
Subject: RE: help on db code wanted
Daan,
You can enable trace logging on the category
"com.cloud.utils.db.Transaction.Statement" in log4j-cloud.xml. It will log
every SQL statement sent to the DB. Look for update to the specific table,
tha
Daan,
You can enable trace logging on the category
"com.cloud.utils.db.Transaction.Statement" in log4j-cloud.xml. It will log
every SQL statement sent to the DB. Look for update to the specific table,
that will give you an indication what the db layer thinks is being set. The
logs grow very
