I have seen that and if I remember correctly it can be caused by
sorting with a custom
comparator that works inconsistently (i.e. one that can say A > B and
B > A). I could be wrong
as it's been a while but I would check your comparator classes if you
have any.
Alan
On Jan 29, 2008, at 3:28 PM, [EMAIL PROTECTED] wrote:
Has anyone ever received a strange WebObjects error when sorting
related to an internal Apple "K2Sort" funky state?
Here's the error:
java.lang.IllegalStateException: Internal Inconsistency in K2Sort
Here's the stack trace:
_NSCollectionPrimitives.java 312 K2SortArray
com.webobjects.foundation
EOSortOrdering.java 202
_sortUsingKeyOrderArray com.webobjects.eocontrol
EOSortOrdering.java 238
sortedArrayUsingKeyOrderArray com.webobjects.eocontrol
From what I can tell, when our app starts up this error either
never happens or it happens each time we try to perform a sort.
Almost like playing the slots... at app launch time we don't know
if things are going to sort correctly for the life of the app.
It's concievable that something else is going on, that some user
hits a branch of code that leaves the K2 algorithm in a broken
state... but we haven't identified a series of steps that causes this.
Anyone experience problems with the K2Sort?
-- Aaron
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/award%
40apple.com
This email sent to [EMAIL PROTECTED]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
