Re: [jboss-dev] Reverted VFS to 2.2.0.M1 (& hudson madness)
So, you're saying that even after you fixed ts issues,
the 6715 is still there?
I don't see a race issue.
It must be something similar to what we already had,
something is not cleaning up properly behind itself.
That was the issue before -> due to overridden TempInfo,
nobody reset the parent VFSContext.
Jason T. Greene wrote:
Unfortunately the tempinfo TS fixes resurrects JBAS-6715, although in
a
slightly different manner (the VFS test created for 6715 passes). The
root problem still seems to be a race that leads to the deployers
somehow holding on to a stale ZipFileWrapper instance. This is going to
take awhile to track down.
Ales Justin wrote:
> VFS 2.2.0.M1 has .war cleanup bug
> VFS 2.2.0.M2 has TS issues + Iterator.remove bug
> VFS 2.2.0.M3 has TS issues
>
> Seam-int 5.2.0-SNAPSHOT excludes plugins/*.jar from scan
>
> If you could wait for some VFS 2.2.0-SNAPSHOT from Jason
> (it depends how fast he can provide it)
> that would be the best choice.
>
> Otherwise do your pick. :-)
>
> Shelly McGowan wrote:
>> Ales,
>>
>> So, we want to test with VFS 2.2.0.M1 and seam-int 5.2.0-SNAPSHOT?
>>
>>
>> Shelly
>>
>>
>> ----- Original Message -----
>> From: "Ales Justin" <ales.justin(a)gmail.com>
>> To: "JBoss.org development list"
<jboss-development(a)lists.jboss.org>
>> Sent: Monday, April 20, 2009 12:13:24 PM GMT -05:00 US/Canada Eastern
>> Subject: Re: [jboss-dev] Reverted VFS to 2.2.0.M1 (& hudson madness)
>>
>> Can we also change the Seam-int to 5.2.0-SNAPSHOT?
>> (Or Shelly, you already did this?)
>>
>> This should fix the performance issue EmbJopr is having with
>> VFSScanner going "into" plugins/*.jar files.
>>
>> Jason T. Greene wrote:
>>> Hi Everyone,
>>>
>>> Since this weekends hudson meltdown seems likely related to a memory
>>> leak, I have reverted VFS to M1. Recent updates to the VFS have been
>>> observed to leak (JBAS-6805). This is potentially caused by a thread
>>> safety issue introduced in M2. Shelly has kicked off another 5.1
>>> testrun with this update, and is checking to see see if M1 resolved
>>> 6805.
>>>
>>> In the meantime I am working on an update to the VFS that does not
>>> have the recent TS issues.
>>>
>> _______________________________________________
>> jboss-development mailing list
>> jboss-development(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-development
>> _______________________________________________
>> jboss-development mailing list
>> jboss-development(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-development
>>
> _______________________________________________
> jboss-development mailing list
> jboss-development(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development