WebSphere Application Server: Re: NON-ASF in activation specification

[dWForums]

Author:
_neha_d

Message:
Matt, thanks for your reply.

Following are reasons to choose NON-ASF
1) strict ordering and 
2) higher throughput 

We have been using NON-ASF using listener ports with
Maximum sessions = 1
Maximum messages = 1

to 'get' msgs in exactly same order as 'put', if we rollback a 'get' we want to 
re-get the exact same message, thats how our retry mechanism works.

We are trying to migrate to activation spec.

Thanks for your help.


|\||)

/** In the face of ambiguity, refuse the temptation to guess */

To respond to this post, please click the following link:



Unsubscribe via the "binocular" icon on the web

WebSphere Application Server: Re: NON-ASF in activation specification

[dWForums]

Author:
mamwl1

Message:
Hi Neha,

Because of how non-ASF mode works it would have to be added to each activation 
spec provider for example the default messaging provider)separately. I am 
guessing you are asking for this on the WMQ messaging provider? If so it might 
be worth you bringing this up with your IBM representative so we can log a 
feature request - it will come through to me, or one of my colleagues. I would 
note that various customers have asked for this function, but IBM guidelines 
mean I can't say whether we will implement it or not or provide any sort of 
timeline.

Can you tell me why you want non-ASF activation specs? It might be possible to 
get the behavior you require without non-ASF mode being available.

Regards, Matt.

To respond to this post, please click the following link:



Unsubscribe via the "binocular" icon on the web