cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Freeman Fang <freeman.f...@gmail.com>
Subject Re: can we use asyn way for jms transport
Date Tue, 26 Aug 2008 08:55:54 GMT
Hi Ulhas,

Thanks.

How about we introduce Spring JmsTemplate to cxf jms transport, is it 
helpful? I'm not familar with spring JmsTemplate but I wanna get more 
ideas about it .

Thanks again

Freeman

Ulhas Bhole wrote:
> Hi Freeman,
>
> I was looking at code and here are two main problems that we will need 
> to tackle.
>
> 1. By default, we create separate TemporaryQueue for repsonse so we 
> will need receiver per tempqueue waiting on reply. (so that many threds.)
> 2. to propogate the JMS response headers back we use JAXWS 
> responseContext which I assume is threadlocal so we need to find out 
> how it will react when the response goes on different thread.
>
> If we ignore for moment point 2 we will either need to use one 
> TemporaryQueue for all responses if no replyDestination is defined. 
> Also will neeed to have separate pool of listeners for scalability.(I 
> don't know how the JMS callback works  so will need to  look into it 
> more)
>
> Regards,
>
> Ulhas Bhole
> Freeman Fang wrote:
>> Any thoughts?
>>
>> Cheers
>> Freeman
>>
>>
>> Freeman Fang wrote:
>>> Hi,
>>>
>>> Currently we are using sync way for jms transport which means the 
>>> thread get blocked until response messsage is coming or the client 
>>> side timeout, see the handleResponse() method of JMSConduit?  Is it 
>>> possible that we use non-block way for JMSConduit, something like 
>>> implement JMS MessageListener API? Or any special reason we need 
>>> this sync invocation for JMS conduit?
>>>
>>> Thanks
>>> Freeman
>>>
>>>
>>>
>
> ----------------------------
> IONA Technologies PLC (registered in Ireland)
> Registered Number: 171387
> Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland
>


Mime
View raw message