Our product uses an older version of the Shark workflow engine that itself uses an older version of Rhino (1.5). Under significant concurrent load we saw a sporadic, odd error that's identical to the one described at:
http://osdir.com/ml/mozilla.devel.jseng/2005-01/msg00154.html We were able to synchronize our call into Shark that in turn calls into Rhino and no longer saw this issue. However, in a newer version of our product we're using Rhino more extensively and directly against the latest version (1.7). We looked at whether the fix described in the link above (synchronizing access to the parent class loader in Rhino itself) was implemented in the latest version and it doesn't seem to be. Before we decide how to workaround/fix this in our own environment, I thought it was worth asking whether this issue has been fixed in Rhino already in a different fashion. Thanks in advance for any insights, Scott _______________________________________________ dev-tech-js-engine-rhino mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-js-engine-rhino
