Hi all,

Any updates on issue?

Regards,
Dilshani

On Wed, Mar 2, 2016 at 3:18 PM, Dilshani Subasinghe <[email protected]>
wrote:

> Hi Malaka,
>
> Thank you and will try to proceed with that in mind. Still ESB having
> different behavior rather than normal JMS Client (Even though having same
> configurations). Will check on that.
>
> Regards,
> Dilshani
>
>
> On Wed, Mar 2, 2016 at 3:08 PM, Malaka Silva <[email protected]> wrote:
>
>>
>>
>> On Wed, Mar 2, 2016 at 2:55 PM, Dilshani Subasinghe <[email protected]>
>> wrote:
>>
>>> Hi Malaka,
>>>
>>> Thank you for explanations. I checked configurations and updated
>>> accordingly. And also there is a small point to clarify.
>>>
>>> When creating JMS Client use following function to create a session:
>>>
>>> *Session session = connection.createSession(false,
>>> Session.CLIENT_ACKNOWLEDGE);*
>>>
>>> JMS Inbound Endpoint will be using following parameter:
>>>
>>>
>>>
>>> *transport.jms.SessionAcknowledgement*
>>> Do both parameters refer same function of JMS ? Do ESB having special
>>> characteristics rather than normal JMS client ?
>>>
>> ​It's same.
>>
>>     protected Session createSession(Connection connection) {
>>         try {
>>             if (jmsSpec11) {
>>                 return connection.createSession(transactedSession,
>> sessionAckMode);
>>             } else {
>>                 if
>> (this.destinationType.equals(JMSConstants.JMSDestinationType.QUEUE)) {
>>                     return (QueueSession) ((QueueConnection)
>> (connection)).createQueueSession(
>>                             transactedSession, sessionAckMode);
>>                 } else if
>> (this.destinationType.equals(JMSConstants.JMSDestinationType.TOPIC)) {
>>                     return (TopicSession) ((TopicConnection)
>> (connection)).createTopicSession(
>>                             transactedSession, sessionAckMode);
>>                 }
>>             }
>>         } catch (JMSException e) {
>>             logger.error("JMS Exception while obtaining session for
>> factory '"
>>                     + this.connectionFactoryString + "' " +
>> e.getMessage());
>>         }
>>
>>         return null;
>>     }​
>>
>>
>>>
>>> Your support is highly appreciated.
>>>
>>> Regards,
>>> Dilshani
>>>
>>>
>>> On Tue, Mar 1, 2016 at 5:58 PM, Malaka Silva <[email protected]> wrote:
>>>
>>>> Hi Dilshani,
>>>>
>>>> Flow is very simple except following exceptions. Take message ->
>>>> execute mediation (sequence) -> ack the broker.
>>>>
>>>> If you want to rollback set SET_ROLLBACK_ONLY mc property to true in
>>>> fault sequence.
>>>>
>>>> Also in mediation flow non-blocking mediator should be used. eg:-
>>>> callout mediator not send mediator.
>>>>
>>>> On Tue, Mar 1, 2016 at 3:34 PM, Dilshani Subasinghe <[email protected]>
>>>> wrote:
>>>>
>>>>> Hi Malaka,
>>>>>
>>>>> In ESB, JMS Inbound endpoint can configure Acknowledgement Type with
>>>>> "transport.jms.SessionAcknowledgement". When it set as
>>>>> "Client_Acknowledge" , What will be the behavior of ESB ? Does it behave
>>>>> like normal JMS Client which enabled "Client_Acknowledgement" ?
>>>>>
>>>>> I'm using separate JMS Client with "Client_Acknowledge" mode and using
>>>>> it to test JMSX Delivery Count. But ESB Inbound endpoint doesn't behave
>>>>> like particular JMS Client (With "Client_Acknowledge" mode).
>>>>>
>>>>> Can you explain ESB behavior within the particular scenario ?
>>>>>
>>>>> Thank you.
>>>>>
>>>>> --
>>>>> Best Regards,
>>>>>
>>>>> Dilshani Subasinghe
>>>>> Software Engineer - QA
>>>>> WSO2, Inc.;http://wso2.com/
>>>>> <http://www.google.com/url?q=http%3A%2F%2Fwso2.com%2F&sa=D&sntz=1&usg=AFQjCNGJuLRux6KkJwXKVUCYOtEsNCmIAQ>
>>>>> lean.enterprise.middleware
>>>>>
>>>>> Mobile: +94773375185
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> Best Regards,
>>>>
>>>> Malaka Silva
>>>> Senior Tech Lead
>>>> M: +94 777 219 791
>>>> Tel : 94 11 214 5345
>>>> Fax :94 11 2145300
>>>> Skype : malaka.sampath.silva
>>>> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
>>>> Blog : http://mrmalakasilva.blogspot.com/
>>>>
>>>> WSO2, Inc.
>>>> lean . enterprise . middleware
>>>> http://www.wso2.com/
>>>> http://www.wso2.com/about/team/malaka-silva/
>>>> <http://wso2.com/about/team/malaka-silva/>
>>>> https://store.wso2.com/store/
>>>>
>>>> Save a tree -Conserve nature & Save the world for your future. Print
>>>> this email only if it is absolutely necessary.
>>>>
>>>
>>>
>>>
>>> --
>>> Best Regards,
>>>
>>> Dilshani Subasinghe
>>> Software Engineer - QA
>>> WSO2, Inc.;http://wso2.com/
>>> <http://www.google.com/url?q=http%3A%2F%2Fwso2.com%2F&sa=D&sntz=1&usg=AFQjCNGJuLRux6KkJwXKVUCYOtEsNCmIAQ>
>>> lean.enterprise.middleware
>>>
>>> Mobile: +94773375185
>>>
>>
>>
>>
>> --
>>
>> Best Regards,
>>
>> Malaka Silva
>> Senior Tech Lead
>> M: +94 777 219 791
>> Tel : 94 11 214 5345
>> Fax :94 11 2145300
>> Skype : malaka.sampath.silva
>> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
>> Blog : http://mrmalakasilva.blogspot.com/
>>
>> WSO2, Inc.
>> lean . enterprise . middleware
>> http://www.wso2.com/
>> http://www.wso2.com/about/team/malaka-silva/
>> <http://wso2.com/about/team/malaka-silva/>
>> https://store.wso2.com/store/
>>
>> Save a tree -Conserve nature & Save the world for your future. Print this
>> email only if it is absolutely necessary.
>>
>
>
>
> --
> Best Regards,
>
> Dilshani Subasinghe
> Software Engineer - QA
> WSO2, Inc.;http://wso2.com/
> <http://www.google.com/url?q=http%3A%2F%2Fwso2.com%2F&sa=D&sntz=1&usg=AFQjCNGJuLRux6KkJwXKVUCYOtEsNCmIAQ>
> lean.enterprise.middleware
>
> Mobile: +94773375185
>



-- 
Best Regards,

Dilshani Subasinghe
Software Engineer - QA
WSO2, Inc.;http://wso2.com/
<http://www.google.com/url?q=http%3A%2F%2Fwso2.com%2F&sa=D&sntz=1&usg=AFQjCNGJuLRux6KkJwXKVUCYOtEsNCmIAQ>
lean.enterprise.middleware

Mobile: +94773375185
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to