[jboss-dev] EJB 3.1 @Asynchronous Support in M4

[Jaikiran Pai]

r106914 of AS trunk now contains 0.2.0-alpha-8 of EJB3 AS6 bom. This 
includes the fixes that Andrew did for allowing async invocations 
through local business interfaces of EJB3 beans. Other related 
changes/fixes (like in Singleton component) have also been taken care of 
and released.

This completes the EJB3 planned releases for M4. Unless we run into any 
bugs during QA, we don't have any more planned releases for M4.

-Jaikiran

On Tuesday 20 July 2010 01:13 PM, Andrew Lee Rubinger wrote:
> Update:
>
> The issue I describe is reflected by this ticket:
>
> https://jira.jboss.org/browse/EJBTHREE-2132
>
> I put the required support in place and verified now that @Local
> asynchronous views are working, along with AS smoke-tests and the async
> integration test.
>
> Jaikiran is gonna take over now and do the requisite releases and AS
> integration patches.
>
> EJB3 Team will ping back this list with a "go for launch" when we've
> cleared all Hudsons.
>
> S,
> ALR
>
> On 07/20/2010 12:20 AM, Andrew Lee Rubinger wrote:
>> Update on the @Asynchronous support for AS 6.0.0.M4:
>>
>> Last week we made a design change in the asynchronous component of EJB3
>> to move to client-side interceptors instead of server-side.  The reason was:
>>
>> 1) For the server to push the result to the client, we'd need
>> bidirectional communication (ie. R2 bisocket impl) of some type, which
>> is bound to not play nicely with firewalls
>> 2) If the client were to poll the server for results, we'd be making a
>> result store (which is a memory leak by design unless we implemented
>> some serialization or expiry policy, added complexity).
>>
>> The unit tests for the client-side async model have been working fine,
>> as have the integration tests in the AS testsuite.
>>
>> I have, however, made an Embedded test to reliably ensure that
>> @Asynchronous invocations do indeed occur in a separate Thread.  What
>> I've discovered is that for @Remote business interfaces, all is firing
>> as expected.  In @Local business interfaces however, this is not the case.
>>
>> I've discovered the root of this is because EJB local proxies do not
>> have client-side interceptors at all.  I'm halfway through patching the
>> impl to support this notion.
>>
>> For M4 launch we can:
>>
>> 1) Continue along and provide @Asynchronous support for remote business
>> interfaces only
>> 2) Get the proper fixes into the EJB3 proxy mechanism to support
>> client-side interception
>>
>> Aside from this issue, EJB3 team is go for M4 (Jaikiran's components
>> were integrated today).
>>
>> I'm on #jboss-dev tomorrow to discuss.
>>
>> S,
>> ALR
>> _______________________________________________
>> jboss-development mailing list
>> jboss-development at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-development
> _______________________________________________
> jboss-development mailing list
> jboss-development at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development