Anselm,

That's definitely a bug, along with #1602. Thanks for bringing it to our attention! Obviously we want Jython to be a robust platform for concurrent Python.

Fixed in r7049

- Jim

On Mon, Apr 26, 2010 at 3:14 AM, Anselm Kruis <a.kruis@science-computing.de> wrote:
Hi,

during the investigation of http://bugs.jython.org/issue1602 I had a look at
org.python.core.PyObject#getJavaProxy():

    protected Object getJavaProxy() {
        if (javaProxy == null) {
            proxyInit();
        }
        return javaProxy;
    }

The current implementation is obviously not thread safe, but I'm not sure, if
this is a real problem. The only problematic case is javaProxy == null and
proxyInit() creating a new javaProxy. I do not yet understand the post jython
2.1 internals well enough, to decide if this case is possible at all.

Regards
   Anselm

--
 Dipl. Phys. Anselm Kruis                       science + computing ag
 Senior Solutions Engineer                      Ingolstädter Str. 22
 email A.Kruis@science-computing.de             80807 München, Germany
 phone +49 89 356386 874                        www.science-computing.de
 fax   +49 89 356386 737

--
Vorstand/Board of Management:
Dr. Bernd Finkbeiner, Dr. Roland Niemeier,
Dr. Arno Steitz, Dr. Ingrid Zech
Vorsitzender des Aufsichtsrats/
Chairman of the Supervisory Board:
Michel Lepert
Sitz/Registered Office: Tuebingen
Registergericht/Registration Court: Stuttgart
Registernummer/Commercial Register No.: HRB 382196



------------------------------------------------------------------------------
_______________________________________________
Jython-dev mailing list
Jython-dev@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jython-dev