Well, if it is not "insane", then what should I do? I mean if the app only works correctly when logging is set to DEBUG then I would think that indicates a problems. I could run the app with DEBUG on all the time, but that would just be covering up what I would assume is a serious problem. What should I do next to debug this problem?
More info: Each time I update my project jar file, I do a recursive "touch" (which I have found forces tomcat to recompile all the jsp's and recognize the new jar file). After this, I restart tomcat. There was a problem with the webhost's configuration of tomcat caching static variables from the previous jar file into jsp static non-variables. I would *presume* this would clear out everything, but maybe not. On Feb 8, 2012, at 9:14 AM, Michael Gentry wrote: > On Tue, Feb 7, 2012 at 6:03 PM, Joe Baldwin <[email protected]> wrote: >> 2. So I found their log4j.properties file and inserted >> "log4j.logger.org.apache.cayenne.access.QueryLogger=DEBUG" (I hope this is >> what you were thinking of) > > I actually think you want INFO instead of DEBUG. > > >> 4. Rod Serling moment: when I tried to add the Product entity - for the >> first time it did not fail >> - detail: it added the Product, there was no Exception >> - I verified the Product by listing all of my products >> >> So, is this 1. Insane, or 2. totally Insane? > > I've seen AshwoodEntitySorter produce different insert orderings > before from different starts. Since you shutdown the application, AES > would have to produce a new dependency graph on startup. I'm not > saying this is responsible, but it is a possibility. So: 0. Maybe not > insane. :-) > > mrg
