ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 41603] - external jython classes are not thread-safe
Date Wed, 14 Feb 2007 14:25:27 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=41603>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=41603


josborne@exstream.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEEDINFO                    |NEW




------- Additional Comments From josborne@exstream.com  2007-02-14 06:25 -------
I was not sure if this was an ant issue or a jython issue so I am reporting the 
bug to both teams.   The interesting thing is that if the threadtester class is 
included directly in threadtest.xml then test is only printed once for each 
run.  Calling threadtest([]) does indeed remedy the problem, but I have run 
into several issues now where threads are overwriting one another's memory 
within scriptdef tasks and this definitely seems to be a problem.

I suppose the question is whether jython is to blame or the jvm implementation?

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Mime
View raw message