On Tuesday 12 October 2010 09:40 PM, Adam Bien wrote:
> Hi,
>
> it is a general problem with @Named. It also happens if you bind a @Stateless bean directly to JSF. Interestingly: if you expose a @Stateless bean via REST and injects CDI managed beans into the @Stateless bean, everything works as expected - no leaks.
> Its actually a massive bug. All 3.0.1 JSF 2 - CDI apps are affected...
> Could the fixed WELD be used in Glassfish v 3.0.1 as well?
Weld 1.1 has some major changes in their SPI and unless the glassfish
integration code is backported as well, Weld 1.1 may not work with
GlassFish 3.0.1.
Thanks
--Siva.
> thanks for the fast response!,
>
> adam
> On 12.10.2010, at 17:38, Sivakumar Thyagarajan wrote:
>
>> Hi Adam
>>
>> On Tuesday 12 October 2010 08:15 PM, Alexis Moussine-Pouchkine wrote:
>>> Please make sure you also file this against Weld (and share the issue I'd). Let's hope the version we're about to integrate has a fix...
>>
>> Thanks for reporting this.
>>
>> This has already been filed in WELD issue tracker as https://jira.jboss.org/browse/WELD-570 and https://jira.jboss.org/browse/WELD-476. I heard today from the Weld lead that this has been fixed in their trunk and WELD 1.1 BETA2 promotion would happen this week or the next. So, when we integrate it in GlassFish 3.1, this should be fixed.
>>
>> This is also tracked in GlassFish as issue 12368.
>>
>> Thanks
>> --Siva.
>>>
>>> Adam Bien<abien_at_adam-bien.com> wrote:
>>>
>>>> Hi All,
>>>>
>>>> I even filed an issue. A simple binding between JSF and CDI causes memory leaks - everything (NetBeans Project, Profiler snapshot, JMeter load script) is attached: https://glassfish.dev.java.net/issues/show_bug.cgi?id=13928
>>>> It is an weld issue - JBoss6m5 behaves the same way.
>>>>
>>>> Any thoughts?
>>>>
>>>> thanks in advance!,
>>>>
>>>> adam