Mailing-List: contact user-help@cayenne.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cayenne.apache.org
Received-SPF: pass (nike.apache.org: domain of mkienenb@gmail.com designates
 74.125.82.41 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAM1yOjaesZcJLi9ggFbbYcwedS3HpT4SeQWmHr4rjGoKx_wQPg@mail.gmail.com>
References: <1CAF0260-43A3-409E-9833-3A551EC5208A@earthlink.net>
 <B2241A4C-B03B-4C45-979D-64D05C9C0659@earthlink.net>
 <C777D02B-AFDD-43F5-9A7D-6D48772793CD@objectstyle.org>
 <605526E6-72CF-4B2D-97A7-76766A951E74@earthlink.net>
 <CAFYr+8bqnQTpPmywyXdFy7OOFfzXhHjM0fWo3oa3ubfZzxSmgw@mail.gmail.com>
 <CAA-upzo_nQrp+O=ggsy9q9SK0PkKpV8HaORxsBGfYNt-bgR-_A@mail.gmail.com>
 <858FBC75-700C-46A6-8471-357EEF122265@earthlink.net>
 <B8F795D3-AC32-4345-937B-C4156E7B379A@objectstyle.org>
 <E3F687D3-7BA9-4588-800F-4D7BF0309891@earthlink.net>
 <3A20F2B5-4E0D-4AD6-A539-CB11611CA7E3@objectstyle.org>
 <822D6D6A-C017-452F-A667-D9EAD60FCD37@earthlink.net>
 <CAA-upzpTfCU-AyMww90_v3VU80Dj14pjTw=3OLW8LU6HbFFUqw@mail.gmail.com>
 <EF7B28CC-4482-4E91-8B01-565EC64FD3C8@earthlink.net>
 <CAM1yOjaesZcJLi9ggFbbYcwedS3HpT4SeQWmHr4rjGoKx_wQPg@mail.gmail.com>
From: Mike Kienenberger <mkienenb@gmail.com>
Date: Wed, 8 Feb 2012 11:18:01 -0500
Message-ID: 
 <CAM1yOjagXr0=Onz1AnhLj0CZ42WWeLpVbSzZnQQaUpM6JJzMxg@mail.gmail.com>
Subject: Re: Odd error
To: user@cayenne.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

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, Mike Kienenberger <mkienenb@gmail.com> wro=
te:
> 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. =A0 So setting the
> logging wasn't what caused the change -- it was restarting the app.
>
> On Wed, Feb 8, 2012 at 11:02 AM, Joe Baldwin <jfbaldwin@earthlink.net> wr=
ote:
>> Well, if it is not "insane", then what should I do? =A0I mean if the app=
 only works correctly when logging is set to DEBUG then I would think that =
indicates a problems. =A0I could run the app with DEBUG on all the time, bu=
t that would just be covering up what I would assume is a serious problem. =
=A0What 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). =A0After this, I restart tomcat. =A0There was a problem with th=
e webhost's configuration of tomcat caching static variables from the previ=
ous jar file into jsp static non-variables. =A0 I would *presume* this woul=
d 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 <jfbaldwin@earthlink.net> w=
rote:
>>>> 2. So I found their log4j.properties file and inserted "log4j.logger.o=
rg.apache.cayenne.access.QueryLogger=3DDEBUG" =A0(I hope this is what you w=
ere thinking of)
>>>
>>> I actually think you want INFO instead of DEBUG.
>>>
>>>
>>>> 4. Rod Serling moment: when I tried to add the Product entity - for th=
e first time it did not fail
>>>> =A0 =A0 =A0 =A0- detail: it added the Product, there was no Exception
>>>> =A0 =A0 =A0 =A0- 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. =A0Since you shutdown the application, AE=
S
>>> would have to produce a new dependency graph on startup. =A0I'm not
>>> saying this is responsible, but it is a possibility. =A0So: 0. Maybe no=
t
>>> insane. =A0:-)
>>>
>>> mrg
>>