Martin Grotzke
Martin Grotzke
@davedennis Sorry for the late response here. Is this still relevant or can we close this issue?
Do you want to submit a pull request?
Without further checking I'd think that instead of `final ConcurrentMap attributes = _session.getAttributesFiltered();` this would be sufficient: `final Map attributes = new TreeMap(_session.getAttributesFiltered());`.
Can't you just pass the sorted attributes to `serializeAttributes` to get back `attributesData`?
You're right, we'd have to change `serializeAttributes` and everything "below" (descendent methods) to accept a `Map`. We'd also have to make sure that this sorted map is actually serialized, therefore...
I've not yet clearly understood the original observation: why the same session data was serialized differently. If we know what exactly caused this there might be another solution or workaround.
Another solution could be to use a `ConcurrentSkipListMap` for attributes instead of `ConcurrentHashMap`. This would require also some changes to replace previous usages of CHM, but it should be significantly...
Sorry, I can't follow you. Can you please rephrase what you want to say?
That's what we/you observed originally, and therfore is expected, isn't it? This should not happen with `ConcurrentSkipListMap`.
The referenced issue is now in github #197 ...