99sono

Results 33 comments of 99sono

Patched eclipselink 2.7.6 Having blowups in ReadLockManager.removeReadLock(ReadLockManager.java:97) The implementation of CacheKey.equals(CacheKey.java:331 and CacheKey.HashCode are not safe

Let me summarize the types of null pointer exceptions that are patch should be addressing. This pattern A: ``` Caused by: java.lang.NullPointerException at org.eclipse.persistence.internal.identitymaps.CacheKey.equals(CacheKey.java:331) ~[eclipselink_2_7_6_hacked.jar] at org.eclipse.persistence.internal.identitymaps.CacheKey.equals(CacheKey.java:320) ~[eclipselink_2_7_6_hacked.jar] at java.util.Vector.indexOf(Vector.java:431)...

Patched eclipselink 2.7.6 Having blowups in ReadLockManager.removeReadLock(ReadLockManager.java:97) The implementation of CacheKey.equals(CacheKey.java:331 and CacheKey.HashCode are not safe

The project team tells me they are happy with the patched eclipselink, for the time being at least. They have not encountered issues of this nature since 2024.04.29. If the...

WARN n.liftweb.http.CoreRequestVarHandler - RequestVar net.liftmodules.ng.Angular$HeadRendered$_ was set but not read

likewise

Column-based filter widgets

I am quite curious about testing the data table once I have the time opportunity for it... I would just like to point, please be particularly mindful of any CSS...

Column-based filter widgets

One further suggestion, I would reccomend to consider a universal search field and not a search field by column... When well done, it normally much more user friendly to let...

New eclipselink dead lock scenario discovered the logic of the sessions.MergeManager.mergeChangesOfWorkingCopyIntoOriginal is not safe when it calls upon AbstractSession.getCacheKeyFromTargetSessionForMerge

Note: This bug will be existing on every version of eclipse link 2.7.6 and above. The version of eclipselink being used in this tracker is essential a 2.7.6 with patches....

New eclipselink dead lock scenario discovered the logic of the sessions.MergeManager.mergeChangesOfWorkingCopyIntoOriginal is not safe when it calls upon AbstractSession.getCacheKeyFromTargetSessionForMerge

Today I have been provided some data of a new event of this sort in a different project. This data will be provided via a private channel to the eclipselink...

New eclipselink dead lock scenario discovered the logic of the sessions.MergeManager.mergeChangesOfWorkingCopyIntoOriginal is not safe when it calls upon AbstractSession.getCacheKeyFromTargetSessionForMerge

I intend to share my current approach for minimizing the risk of encountering this deadlock pattern. However, I must emphasize that this solution falls short of my ideal vision. The...

New eclipselink dead lock scenario discovered the logic of the sessions.MergeManager.mergeChangesOfWorkingCopyIntoOriginal is not safe when it calls upon AbstractSession.getCacheKeyFromTargetSessionForMerge

Here, with this post, I am uploading my patch. It gives an overall idea of what I changed in the code. [0001-TRK-32421-Implement-an-attempt-to-fix-for-issue.patch](https://github.com/eclipse-ee4j/eclipselink/files/15139015/0001-TRK-32421-Implement-an-attempt-to-fix-for-issue.patch) I am also uploading all of the core...

New eclipselink dead lock scenario discovered the logic of the sessions.MergeManager.mergeChangesOfWorkingCopyIntoOriginal is not safe when it calls upon AbstractSession.getCacheKeyFromTargetSessionForMerge

In order to check the new code, I have had to heavily manipulate my debugger to override local variables so that I could finally get into the: org.eclipse.persistence.internal.sessions.AbstractSession.getCacheKeyFromTargetSessionForMergeScenarioMergeManagerNotNullAndCacheKeyOriginalStillNull(CacheKey, Object, ObjectBuilder,...