On Feb 8, 2012, at 9:37 PM, Joe Baldwin wrote:
> Does anyone have a clue as to what happened here, or should I just pour
> myself a beer a call it "done". :)
I am fairy sure Cayenne logging being on or off has nothing to do with it. My
guess (not knowing much about your deployment environment
Problem Statement: Seemingly misleading FK exception from MySQL on production
server
Repeatability: 100% on the production server, 0% on the dev server
Status: It appears the theory of multiple universes could be part of the
solution set :)
** New Test:
1. After setting Cayenne logging to D
I will look into P6Spy, and post the results.
Thanks
Joe
On Feb 8, 2012, at 11:58 AM, Mike Kienenberger wrote:
> I was just trying to restate what other people said. I don't have
> anything original to add, unfortunately.
>
> One thing you can do is to insert the P6Spy database driver into
> One thing you can do is to insert the P6Spy database driver into your app
> -- this jdbc driver wrapper will provide logging at the jdbc level, which
> would let you see what's going on without having to enable java logging.
To see what part of the application is issuing the request, you could t
I was just trying to restate what other people said. I don't have
anything original to add, unfortunately.
One thing you can do is to insert the P6Spy database driver into your
app -- this jdbc driver wrapper will provide logging at the jdbc
level, which would let you see what's going on without
> And your next step is to determine how the sort orderings are different (by
> looking at the log results), determine why a certain sort causes a problem,
OK, but I have absolutely no idea what you are talking about. :) More
importantly, I am not sure if I have described the test results well
Oops. Didn't finish.
And your next step is to determine how the sort orderings are
different (by looking at the log results), determine why a certain
sort causes a problem, and then subclass the sorter to insure it sorts
in a consistently-valid manner each time.
On Wed, Feb 8, 2012 at 11:15 AM,
I think what Michael is saying is that the ashwood sorter isn't
guaranteed to return the same results for the same commit operation on
the next run after the application is restarted. So setting the
logging wasn't what caused the change -- it was restarting the app.
On Wed, Feb 8, 2012 at 11:02
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. Wh
On Tue, Feb 7, 2012 at 6:03 PM, Joe Baldwin 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
So does that mean that the logging works now? That would be a good outcome in
itself :)
> Before I deleted the log file, I noticed an entry that said something about
> not properly closing the JDBC something-R-other. But it has not re-appeared.
> This is curious because I had theorized that th
Hey Andrus,
Did you ever see the Twilight Zone? Well get ready for this one.
1. It took me a while to figure out out to get the logging running, and it
turns out the the webhost already has it in the tomcat path (but it is sort of
hidden, and they don't, of course, tell you anything about it)
The simplest thing you can do is add log4J jar to your app, and add this
somewhere on app startup (e.g. a filter or servlet init method, etc) :
BasicConfigurator.configure();
To fine-tune logging you may switch to PropertyConfigurator. But start with
BasicConfigurator - it should log every
I would do it, if I understood it. However, I tried to tackle Cayenne logging
about a year ago and could never figure it out. I couldn't even figure out how
to turn it off. It just continued to perform the default behavior.
If you give me the exact commands and tell me exactly where to place
Can you enable Cayenne SQL logging? You'll see all the SQL executed prior to
the exception.
http://cayenne.apache.org/doc30/configuring-logging.html
On Feb 7, 2012, at 8:49 PM, Joe Baldwin wrote:
> Michael,
>
> I have new info that makes this problem look even screwier. (Please refer to
> t
Michael,
I have new info that makes this problem look even screwier. (Please refer to
the error msgs below).
So, you might say: "so what, ... this looks like the same error". Yes, it
does! However, I just got this error after I restarted tomcat and tried to
login to my app. There is ABSOLUT
Bryan & Michael,
It sounds to me like the scenario that you are describing has to do with
committing multiple entities and that the *order* can be re-set from what was
intended.
Since I have no idea what the problem is, I am open to suggestions. However, I
checked the code, and it appears tha
Hi Bryan,
I can confirm that the commit order varies. We were seeing the issue
on the same environment, though. When the AshwoodEntitySorter built
the object graph, it would vary from run-to-run. Once built, it is
cached. If it happens to build a proper order, you are good to go at
least until
geTypeOid`) REFERENCES `packagetype` (`oid`))
>>>
>>> Thanks
>>> Joe
>>>
>>>
>>>
>>> On Feb 5, 2012, at 2:29 AM, Andrus Adamchik wrote:
>>>
>>>> While I don't know what the cause of the error is, my recommend
;>
>>
>> On Feb 5, 2012, at 2:29 AM, Andrus Adamchik wrote:
>>
>>> While I don't know what the cause of the error is, my recommendation would
>>> be to put all Cayenne files in CLASSPATH (e.g. WEB-INF/classes or in a jar
>>> under WEB-INF/li
` (`oid`))
>>
>> Thanks
>> Joe
>>
>>
>>
>> On Feb 5, 2012, at 2:29 AM, Andrus Adamchik wrote:
>>
>>> While I don't know what the cause of the error is, my recommendation would
>>> be to put all Cayenne files in CLASSPATH (
This error reminds me of something we see in our shop. If multiple related
entities are being committed together, Cayenne can sometimes commit them
out of order which can cause FK constraint violations. The commit order
seems to be indeterminate; it can work as expected on a dev machine and
fail
gt;> under WEB-INF/lib). This is much more portable across any Java environments.
>>
>> Andrus
>>
>> On Feb 4, 2012, at 7:40 PM, Joe Baldwin wrote:
>>
>>> Here is more research on my "odd error".
>>>
>>> Production Server Env
TH (e.g. WEB-INF/classes or in a jar under
> WEB-INF/lib). This is much more portable across any Java environments.
>
> Andrus
>
> On Feb 4, 2012, at 7:40 PM, Joe Baldwin wrote:
>
>> Here is more research on my "odd error".
>>
>> Production Server
Here is more research on my "odd error".
>
> Production Server Env
> Tomcat, linux, MySQL 5.1, Java 1.6
> I only have control of tomcat config files & start/stop operations
> I am using a *temp* configuration for installation and only have
> a
Here is more research on my "odd error".
Production Server Env
Tomcat, linux, MySQL 5.1, Java 1.6
I only have control of tomcat config files & start/stop operations
I am using a *temp* configuration for installation and only have
an IP which I aliase
I am manually mirroring a test app (successfully tested on my dev tomcat), onto
a remote server. I am getting an odd error and am having trouble tracking it
down. (an excerpt is listed below)
While it is possible that I have made a mistake in my coding, it is not likely
since the associated
27 matches
Mail list logo
