Author FraOrolo
Recipients FraOrolo, jeff.allen, zyasoft
Date 2019-12-17.11:20:25
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Ok, had some time for experiments:
* I tried to use less PySystemStates, this makes it worse. One thread with Jython needs a separate SystemState
* Im still not sure how the synchronization in PyType.Registry.classToType.computeValue() can be missed.
  I see a problem in the fact, that there is no control for insertion into the classValue. I'm feeling unsure about the fact that multiple threads will re-create the PyType wrapping, because they are waiting in front of the lock and do not check if the first import and wrapping was successful.
But in principle this should be fine, just more PyJavaType wrappings are created.
* Interesting for me is: our Java Utitility classes are not referenced by other Java classes that would make them prone to concurrent recursive JavaType wrapping. The class that errors is not referenced by any other Java class.
Date User Action Args
2019-12-17 11:20:26FraOrolosetmessageid: <>
2019-12-17 11:20:26FraOrolosetrecipients: + FraOrolo, zyasoft, jeff.allen
2019-12-17 11:20:26FraOrololinkissue2834 messages
2019-12-17 11:20:25FraOrolocreate