A DataContext exists without a live database connection. Only when you do
something with it (like run a query, or commit some objects) it opens a
connection, and then releases it immediately when the operation is done.
Andrus
On Mar 10, 2014, at 2:19 PM, Sampath Uppula wrote:
> Hi,
> I am rea
Hi,
I am really wondering even after getting the DataContext object why I am facing
the issue to connect the database.
Object Context :
>> org.apache.cayenne.access.DataContext@50ab9eed
The reason to disable the stack trace in live is to reduce the log size and
improve the performance.
Thanks ,
Then it is impossible to tell what really happened. This can be something
simple like a JDBC connection error, or anything else really. But we don’t
know.
Could you turn on logging of stack traces in a live environment? Why is it
disabled?
Andrus
On Mar 10, 2014, at 1:58 PM, Sampath Uppula
Hi Andrus,
Thanks for the quick update.
But I cannot provide the stack trace right now because this issue is occurring
in the live environment.
I am using the below jars related to Cayenne in the web application which is
deployed on Tomcat 7.
cayenne-client-3.0.2.jar
cayenne-modeler-3.0.2.jar
ca
Hi there, do you have a full stack trace of the exception? It should reveal
lots of useful details.
I am also confused with this class present in your logs:
org.apache.cayenne.modeler.util.ModelerLogger.
Andrus
On Mar 10, 2014, at 1:29 PM, Sampath Uppula wrote:
> Hi,
> I am using Cayenne 3.0
Hi,
I am using Cayenne 3.0.2 with Mysql database.
In my email scheduler, I am using the DataContext object to read the data from
the database.
I am getting the DataContext properly but when I am executing the below line I
am getting the Global exception.
dashboardfilterCreateObj =
DataObjectUt
Perfect! Thank you.
Note to others, I made a mistake with the order of the filters. It should
be:\
binder.bindList(Constants.SERVER_DOMAIN_FILTERS_LIST) //
.add(new AuditableFilter(new MyAuditableProcessor()))
.add(new ChangeSetFilter());
Now you can use: ChangeSetFilter.preCommi
