Re: [Dev] [ESB 4.9.0] Different ESB configs for Message Processor.

2015-10-12 Thread Ajith Vitharana 
Hi Ravindra,



On Mon, Oct 12, 2015 at 1:07 AM, Ravindra Ranwala  wrote:

> Hi Ajith,
>
> This is not a bug in the MP, rather it is a configuration related issue.
> Here a getQuote request is sent which is a classical IN-OUT scenario.
> Therefore you are getting a response. If you are getting a response you
> need to define a reply sequence at the MP. Otherwise the MP has no way of
> handling the response.
>

Thank you  for the explanation. But this information is not available in
the doc [1].  Could you please document ,  then resolve the tickets ?

Reply sequence name (message.processor.reply.sequence)

The name of the sequence where the message reply should be sent.

No

[1]
https://docs.wso2.com/display/ESB490/Scheduled+Message+Forwarding+Processor

-Ajith



> Please define a simple reply sequence and point the MP to that. Also
> create a Documentation issue to include it in our documentation [1]. Also I
> guess we can resolve the jira issue [2] since it is not a bug in ESB,
> rather a documentation issue.
>
> A sample reply sequence config is given below.
>
>
> 
> http://ws.apache.org/ns/synapse"; name="replySequence">
>
>   
>
>
> 
>
>
>
>
>
>
> [1] https://docs.wso2.com/display/IntegrationPatterns/Durable+Subscriber
> [2] https://wso2.org/jira/browse/ESBJAVA-4263
>
>
> Thanks & Regards,
>
> On Sun, Oct 11, 2015 at 3:26 AM, Ajith Vitharana  wrote:
>
>> Hi All.
>>
>> Created JIRAs for above issues.
>>
>> [1] https://wso2.org/jira/browse/DOCUMENTATION-2524
>> [2] https://wso2.org/jira/browse/ESBJAVA-4263
>>
>> -Ajith
>>
>> On Wed, Oct 7, 2015 at 12:48 AM, Ajith Vitharana  wrote:
>>
>>>
>>>
>>> On Wed, Oct 7, 2015 at 12:43 AM, Yasassri Ratnayake 
>>> wrote:
>>>
 According to [1]  "*The deactivate sequence that will be executed when
 the processor is deactivated automatically. Automatic deactivation occurs
 when the maximum delivery attempts is exceeded and the Drop message after
 maximum delivery attempts parameter is disabled.*"

 [1] - https://docs.wso2.com/display/ESB490/Message+Forwarding+Processor

>>>
>>>
>>> The backed is available *BEFORE* exceed the max delivery attempts. But
>>> still message processor going to deactivate ?
>>>
>>> -Ajith
>>>

 On Wed, Oct 7, 2015 at 10:06 AM, Ajith Vitharana 
 wrote:

> Other issue is,
>
> 1. According to the sample I'm shutting down the backend-1  and send a
> request.
> 2. Now I can see the message store has one message.
> 3. Before 50 delivery attempts , start the backend-1
> 4. Now I  can see the message processor executed and message delivered
>  to backed-1
>
> But just after sending the message, the  message processor going to
> deactivate state and printing following exception.
>
> [2015-10-07 00:25:03,987]  WARN - ForwardingService Failed to send the
> message through the fault sequence. Sequence name does not Exist.
> *[2015-10-07 00:25:05,335]  WARN - ForwardingService Failed to send
> the message through the deactivate sequence. Sequence name does not 
> Exist.*
> [2015-10-07 00:25:05,340]  INFO - ScheduledMessageProcessor
> Successfully deactivated the message processor [send_pending_message]
> *[2015-10-07 00:25:05,341] ERROR - ForwardingService Failed to send
> the out message. Reply sequence does not Exist. Deactivated the message
> processor*
>
>
> 1. According to the WARN log , what is the deactivate sequence should
> define ?
> 2. Why message processor is deactivate just after sending message to
> back end ?
>
> -Ajith
>
>
> On Tue, Oct 6, 2015 at 11:39 PM, Ajith Vitharana 
> wrote:
>
>> Hi Yasassri.
>>
>> Yes. According to the carbon commits it has renamed. Then those
>> configs never tested after 2012 :)
>>
>> [1] https://wso2.org/jira/browse/CARBON-13114
>>
>> -Ajith
>>
>>
>> Author: ishan
>> Date: Fri Jun 15 02:00:53 2012
>> New Revision: 130164
>> URL: http://wso2.org/svn/browse/wso2?view=rev&revision=130164
>>
>> Log:
>> Fixing CARBON-13114 with the patch of CharithaM.
>>
>> Modified:
>>carbon/platform/trunk/components/mediation/message-
>> processor/org.wso2.carbon.message.processor.ui/src/main/
>> resources/org/wso2/carbon/message/processor/ui/i18n/
>> Resources.properties
>>carbon/platform/trunk/components/mediation/message-
>> processor/org.wso2.carbon.message.processor.ui/src/main/
>> resources/web/message_processor/index.jsp
>>carbon/platform/trunk/components/mediation/message-
>> processor/org.wso2.carbon.message.processor.ui/src/main/
>> resources/web/message_processor/manageMessageForwardingProcessor.jsp
>>
>> Modified: carbon/platform/trunk/components/mediation/message-
>> processor/org.wso2.carbon.message.processor.ui/src/main/
>> resources/org/wso2/carbon/message/processor/ui/i18n/
>

Re: [Dev] [ESB 4.9.0] Different ESB configs for Message Processor.

2015-10-11 Thread Ravindra Ranwala 
Hi Ajith,

This is not a bug in the MP, rather it is a configuration related issue.
Here a getQuote request is sent which is a classical IN-OUT scenario.
Therefore you are getting a response. If you are getting a response you
need to define a reply sequence at the MP. Otherwise the MP has no way of
handling the response. Please define a simple reply sequence and point the
MP to that. Also create a Documentation issue to include it in our
documentation [1]. Also I guess we can resolve the jira issue [2] since it
is not a bug in ESB, rather a documentation issue.

A sample reply sequence config is given below.



http://ws.apache.org/ns/synapse"; name="replySequence">
   
  
   
   







[1] https://docs.wso2.com/display/IntegrationPatterns/Durable+Subscriber
[2] https://wso2.org/jira/browse/ESBJAVA-4263


Thanks & Regards,

On Sun, Oct 11, 2015 at 3:26 AM, Ajith Vitharana  wrote:

> Hi All.
>
> Created JIRAs for above issues.
>
> [1] https://wso2.org/jira/browse/DOCUMENTATION-2524
> [2] https://wso2.org/jira/browse/ESBJAVA-4263
>
> -Ajith
>
> On Wed, Oct 7, 2015 at 12:48 AM, Ajith Vitharana  wrote:
>
>>
>>
>> On Wed, Oct 7, 2015 at 12:43 AM, Yasassri Ratnayake 
>> wrote:
>>
>>> According to [1]  "*The deactivate sequence that will be executed when
>>> the processor is deactivated automatically. Automatic deactivation occurs
>>> when the maximum delivery attempts is exceeded and the Drop message after
>>> maximum delivery attempts parameter is disabled.*"
>>>
>>> [1] - https://docs.wso2.com/display/ESB490/Message+Forwarding+Processor
>>>
>>
>>
>> The backed is available *BEFORE* exceed the max delivery attempts. But
>> still message processor going to deactivate ?
>>
>> -Ajith
>>
>>>
>>> On Wed, Oct 7, 2015 at 10:06 AM, Ajith Vitharana 
>>> wrote:
>>>
 Other issue is,

 1. According to the sample I'm shutting down the backend-1  and send a
 request.
 2. Now I can see the message store has one message.
 3. Before 50 delivery attempts , start the backend-1
 4. Now I  can see the message processor executed and message delivered
  to backed-1

 But just after sending the message, the  message processor going to
 deactivate state and printing following exception.

 [2015-10-07 00:25:03,987]  WARN - ForwardingService Failed to send the
 message through the fault sequence. Sequence name does not Exist.
 *[2015-10-07 00:25:05,335]  WARN - ForwardingService Failed to send the
 message through the deactivate sequence. Sequence name does not Exist.*
 [2015-10-07 00:25:05,340]  INFO - ScheduledMessageProcessor
 Successfully deactivated the message processor [send_pending_message]
 *[2015-10-07 00:25:05,341] ERROR - ForwardingService Failed to send the
 out message. Reply sequence does not Exist. Deactivated the message
 processor*


 1. According to the WARN log , what is the deactivate sequence should
 define ?
 2. Why message processor is deactivate just after sending message to
 back end ?

 -Ajith


 On Tue, Oct 6, 2015 at 11:39 PM, Ajith Vitharana 
 wrote:

> Hi Yasassri.
>
> Yes. According to the carbon commits it has renamed. Then those
> configs never tested after 2012 :)
>
> [1] https://wso2.org/jira/browse/CARBON-13114
>
> -Ajith
>
>
> Author: ishan
> Date: Fri Jun 15 02:00:53 2012
> New Revision: 130164
> URL: http://wso2.org/svn/browse/wso2?view=rev&revision=130164
>
> Log:
> Fixing CARBON-13114 with the patch of CharithaM.
>
> Modified:
>carbon/platform/trunk/components/mediation/message-
> processor/org.wso2.carbon.message.processor.ui/src/main/
> resources/org/wso2/carbon/message/processor/ui/i18n/
> Resources.properties
>carbon/platform/trunk/components/mediation/message-
> processor/org.wso2.carbon.message.processor.ui/src/main/
> resources/web/message_processor/index.jsp
>carbon/platform/trunk/components/mediation/message-
> processor/org.wso2.carbon.message.processor.ui/src/main/
> resources/web/message_processor/manageMessageForwardingProcessor.jsp
>
> Modified: carbon/platform/trunk/components/mediation/message-
> processor/org.wso2.carbon.message.processor.ui/src/main/
> resources/org/wso2/carbon/message/processor/ui/i18n/
> Resources.properties
> URL:
> http://wso2.org/svn/browse/wso2/carbon/platform/trunk/components/mediation/message-processor/org.wso2.carbon.message.processor.ui/src/main/resources/org/wso2/carbon/message/processor/ui/i18n/Resources.properties?rev=130164&r1=130163&r2=130164&view=diff
> 
> ==
> --- carbon/platform/trunk/components/mediation/message-
> processor/org.wso2.carbon.message.processor.ui/src/main/
> resources/org/wso2/carbon/message/processor/ui/i18n/Resources.properties
> (origin

Re: [Dev] [ESB 4.9.0] Different ESB configs for Message Processor.

2015-10-10 Thread Ajith Vitharana 
Hi All.

Created JIRAs for above issues.

[1] https://wso2.org/jira/browse/DOCUMENTATION-2524
[2] https://wso2.org/jira/browse/ESBJAVA-4263

-Ajith

On Wed, Oct 7, 2015 at 12:48 AM, Ajith Vitharana  wrote:

>
>
> On Wed, Oct 7, 2015 at 12:43 AM, Yasassri Ratnayake 
> wrote:
>
>> According to [1]  "*The deactivate sequence that will be executed when
>> the processor is deactivated automatically. Automatic deactivation occurs
>> when the maximum delivery attempts is exceeded and the Drop message after
>> maximum delivery attempts parameter is disabled.*"
>>
>> [1] - https://docs.wso2.com/display/ESB490/Message+Forwarding+Processor
>>
>
>
> The backed is available *BEFORE* exceed the max delivery attempts. But
> still message processor going to deactivate ?
>
> -Ajith
>
>>
>> On Wed, Oct 7, 2015 at 10:06 AM, Ajith Vitharana  wrote:
>>
>>> Other issue is,
>>>
>>> 1. According to the sample I'm shutting down the backend-1  and send a
>>> request.
>>> 2. Now I can see the message store has one message.
>>> 3. Before 50 delivery attempts , start the backend-1
>>> 4. Now I  can see the message processor executed and message delivered
>>>  to backed-1
>>>
>>> But just after sending the message, the  message processor going to
>>> deactivate state and printing following exception.
>>>
>>> [2015-10-07 00:25:03,987]  WARN - ForwardingService Failed to send the
>>> message through the fault sequence. Sequence name does not Exist.
>>> *[2015-10-07 00:25:05,335]  WARN - ForwardingService Failed to send the
>>> message through the deactivate sequence. Sequence name does not Exist.*
>>> [2015-10-07 00:25:05,340]  INFO - ScheduledMessageProcessor Successfully
>>> deactivated the message processor [send_pending_message]
>>> *[2015-10-07 00:25:05,341] ERROR - ForwardingService Failed to send the
>>> out message. Reply sequence does not Exist. Deactivated the message
>>> processor*
>>>
>>>
>>> 1. According to the WARN log , what is the deactivate sequence should
>>> define ?
>>> 2. Why message processor is deactivate just after sending message to
>>> back end ?
>>>
>>> -Ajith
>>>
>>>
>>> On Tue, Oct 6, 2015 at 11:39 PM, Ajith Vitharana 
>>> wrote:
>>>
 Hi Yasassri.

 Yes. According to the carbon commits it has renamed. Then those configs
 never tested after 2012 :)

 [1] https://wso2.org/jira/browse/CARBON-13114

 -Ajith


 Author: ishan
 Date: Fri Jun 15 02:00:53 2012
 New Revision: 130164
 URL: http://wso2.org/svn/browse/wso2?view=rev&revision=130164

 Log:
 Fixing CARBON-13114 with the patch of CharithaM.

 Modified:
carbon/platform/trunk/components/mediation/message-
 processor/org.wso2.carbon.message.processor.ui/src/main/
 resources/org/wso2/carbon/message/processor/ui/i18n/
 Resources.properties
carbon/platform/trunk/components/mediation/message-
 processor/org.wso2.carbon.message.processor.ui/src/main/
 resources/web/message_processor/index.jsp
carbon/platform/trunk/components/mediation/message-
 processor/org.wso2.carbon.message.processor.ui/src/main/
 resources/web/message_processor/manageMessageForwardingProcessor.jsp

 Modified: carbon/platform/trunk/components/mediation/message-
 processor/org.wso2.carbon.message.processor.ui/src/main/
 resources/org/wso2/carbon/message/processor/ui/i18n/
 Resources.properties
 URL:
 http://wso2.org/svn/browse/wso2/carbon/platform/trunk/components/mediation/message-processor/org.wso2.carbon.message.processor.ui/src/main/resources/org/wso2/carbon/message/processor/ui/i18n/Resources.properties?rev=130164&r1=130163&r2=130164&view=diff
 
 ==
 --- carbon/platform/trunk/components/mediation/message-
 processor/org.wso2.carbon.message.processor.ui/src/main/
 resources/org/wso2/carbon/message/processor/ui/i18n/Resources.properties
 (original)
 +++ carbon/platform/trunk/components/mediation/message-
 processor/org.wso2.carbon.message.processor.ui/src/main/
 resources/org/wso2/carbon/message/processor/ui/i18n/Resources.properties
 Fri Jun 15 02:00:53 2012
 @@ -24,7 +24,9 @@
  size=Size
  action=Actions
  deactivate=Deactivate
 -activate=activate
 +activate=Activate
 +inactive=Inactive
 +active=Active
  no.messageProcessors.are.currently.defined=No Message Processors are
 currently defined.
  message.Processor= Message Processor
  name=Name
 @@ -104,7 +106,7 @@
  message.sampling.processor.parameters=Message Sampling Processor
 Parameters
  message.context.properties=Message Context Properties
  interval=Message retry interval (Millis)


 *-max.deliver.attempts=Maximum delivery 
 attempts+max.delivery.attempts=Maximum delivery attempts*
  axis2.repo=Axis2 Client repository
  axis2.config=Axis2 Configuration
  message.processor.rep

Re: [Dev] [ESB 4.9.0] Different ESB configs for Message Processor.

2015-10-06 Thread Ajith Vitharana 
On Wed, Oct 7, 2015 at 12:43 AM, Yasassri Ratnayake 
wrote:

> According to [1]  "*The deactivate sequence that will be executed when
> the processor is deactivated automatically. Automatic deactivation occurs
> when the maximum delivery attempts is exceeded and the Drop message after
> maximum delivery attempts parameter is disabled.*"
>
> [1] - https://docs.wso2.com/display/ESB490/Message+Forwarding+Processor
>


The backed is available *BEFORE* exceed the max delivery attempts. But
still message processor going to deactivate ?

-Ajith

>
> On Wed, Oct 7, 2015 at 10:06 AM, Ajith Vitharana  wrote:
>
>> Other issue is,
>>
>> 1. According to the sample I'm shutting down the backend-1  and send a
>> request.
>> 2. Now I can see the message store has one message.
>> 3. Before 50 delivery attempts , start the backend-1
>> 4. Now I  can see the message processor executed and message delivered
>>  to backed-1
>>
>> But just after sending the message, the  message processor going to
>> deactivate state and printing following exception.
>>
>> [2015-10-07 00:25:03,987]  WARN - ForwardingService Failed to send the
>> message through the fault sequence. Sequence name does not Exist.
>> *[2015-10-07 00:25:05,335]  WARN - ForwardingService Failed to send the
>> message through the deactivate sequence. Sequence name does not Exist.*
>> [2015-10-07 00:25:05,340]  INFO - ScheduledMessageProcessor Successfully
>> deactivated the message processor [send_pending_message]
>> *[2015-10-07 00:25:05,341] ERROR - ForwardingService Failed to send the
>> out message. Reply sequence does not Exist. Deactivated the message
>> processor*
>>
>>
>> 1. According to the WARN log , what is the deactivate sequence should
>> define ?
>> 2. Why message processor is deactivate just after sending message to back
>> end ?
>>
>> -Ajith
>>
>>
>> On Tue, Oct 6, 2015 at 11:39 PM, Ajith Vitharana  wrote:
>>
>>> Hi Yasassri.
>>>
>>> Yes. According to the carbon commits it has renamed. Then those configs
>>> never tested after 2012 :)
>>>
>>> [1] https://wso2.org/jira/browse/CARBON-13114
>>>
>>> -Ajith
>>>
>>>
>>> Author: ishan
>>> Date: Fri Jun 15 02:00:53 2012
>>> New Revision: 130164
>>> URL: http://wso2.org/svn/browse/wso2?view=rev&revision=130164
>>>
>>> Log:
>>> Fixing CARBON-13114 with the patch of CharithaM.
>>>
>>> Modified:
>>>carbon/platform/trunk/components/mediation/message-
>>> processor/org.wso2.carbon.message.processor.ui/src/main/
>>> resources/org/wso2/carbon/message/processor/ui/i18n/Resources.properties
>>>carbon/platform/trunk/components/mediation/message-
>>> processor/org.wso2.carbon.message.processor.ui/src/main/
>>> resources/web/message_processor/index.jsp
>>>carbon/platform/trunk/components/mediation/message-
>>> processor/org.wso2.carbon.message.processor.ui/src/main/
>>> resources/web/message_processor/manageMessageForwardingProcessor.jsp
>>>
>>> Modified: carbon/platform/trunk/components/mediation/message-
>>> processor/org.wso2.carbon.message.processor.ui/src/main/
>>> resources/org/wso2/carbon/message/processor/ui/i18n/Resources.properties
>>> URL:
>>> http://wso2.org/svn/browse/wso2/carbon/platform/trunk/components/mediation/message-processor/org.wso2.carbon.message.processor.ui/src/main/resources/org/wso2/carbon/message/processor/ui/i18n/Resources.properties?rev=130164&r1=130163&r2=130164&view=diff
>>> 
>>> ==
>>> --- carbon/platform/trunk/components/mediation/message-
>>> processor/org.wso2.carbon.message.processor.ui/src/main/
>>> resources/org/wso2/carbon/message/processor/ui/i18n/Resources.properties
>>> (original)
>>> +++ carbon/platform/trunk/components/mediation/message-
>>> processor/org.wso2.carbon.message.processor.ui/src/main/
>>> resources/org/wso2/carbon/message/processor/ui/i18n/Resources.properties
>>> Fri Jun 15 02:00:53 2012
>>> @@ -24,7 +24,9 @@
>>>  size=Size
>>>  action=Actions
>>>  deactivate=Deactivate
>>> -activate=activate
>>> +activate=Activate
>>> +inactive=Inactive
>>> +active=Active
>>>  no.messageProcessors.are.currently.defined=No Message Processors are
>>> currently defined.
>>>  message.Processor= Message Processor
>>>  name=Name
>>> @@ -104,7 +106,7 @@
>>>  message.sampling.processor.parameters=Message Sampling Processor
>>> Parameters
>>>  message.context.properties=Message Context Properties
>>>  interval=Message retry interval (Millis)
>>>
>>>
>>> *-max.deliver.attempts=Maximum delivery 
>>> attempts+max.delivery.attempts=Maximum delivery attempts*
>>>  axis2.repo=Axis2 Client repository
>>>  axis2.config=Axis2 Configuration
>>>  message.processor.reply.sequence=Reply sequence name
>>> @@ -112,4 +114,4 @@
>>>  quartz.conf=Quartz configuration file path
>>>  cronExpression=Cron Expression
>>>  target.endpoint=Address Endpoint name
>>> -out_only=Out-only message
>>> \ No newline at end of file
>>> +out_only=Out-only message
>>>
>>> Modified: carbon/platform/trunk/components/mediation/message-
>>> pr

Re: [Dev] [ESB 4.9.0] Different ESB configs for Message Processor.

2015-10-06 Thread Yasassri Ratnayake 
And also If you are receiving a reply you need to define a on-reply
sequence.

On Wed, Oct 7, 2015 at 10:13 AM, Yasassri Ratnayake 
wrote:

> According to [1]  "*The deactivate sequence that will be executed when
> the processor is deactivated automatically. Automatic deactivation occurs
> when the maximum delivery attempts is exceeded and the Drop message after
> maximum delivery attempts parameter is disabled.*"
>
> [1] - https://docs.wso2.com/display/ESB490/Message+Forwarding+Processor
>
> On Wed, Oct 7, 2015 at 10:06 AM, Ajith Vitharana  wrote:
>
>> Other issue is,
>>
>> 1. According to the sample I'm shutting down the backend-1  and send a
>> request.
>> 2. Now I can see the message store has one message.
>> 3. Before 50 delivery attempts , start the backend-1
>> 4. Now I  can see the message processor executed and message delivered
>>  to backed-1
>>
>> But just after sending the message, the  message processor going to
>> deactivate state and printing following exception.
>>
>> [2015-10-07 00:25:03,987]  WARN - ForwardingService Failed to send the
>> message through the fault sequence. Sequence name does not Exist.
>> *[2015-10-07 00:25:05,335]  WARN - ForwardingService Failed to send the
>> message through the deactivate sequence. Sequence name does not Exist.*
>> [2015-10-07 00:25:05,340]  INFO - ScheduledMessageProcessor Successfully
>> deactivated the message processor [send_pending_message]
>> *[2015-10-07 00:25:05,341] ERROR - ForwardingService Failed to send the
>> out message. Reply sequence does not Exist. Deactivated the message
>> processor*
>>
>>
>> 1. According to the WARN log , what is the deactivate sequence should
>> define ?
>> 2. Why message processor is deactivate just after sending message to back
>> end ?
>>
>> -Ajith
>>
>>
>> On Tue, Oct 6, 2015 at 11:39 PM, Ajith Vitharana  wrote:
>>
>>> Hi Yasassri.
>>>
>>> Yes. According to the carbon commits it has renamed. Then those configs
>>> never tested after 2012 :)
>>>
>>> [1] https://wso2.org/jira/browse/CARBON-13114
>>>
>>> -Ajith
>>>
>>>
>>> Author: ishan
>>> Date: Fri Jun 15 02:00:53 2012
>>> New Revision: 130164
>>> URL: http://wso2.org/svn/browse/wso2?view=rev&revision=130164
>>>
>>> Log:
>>> Fixing CARBON-13114 with the patch of CharithaM.
>>>
>>> Modified:
>>>carbon/platform/trunk/components/mediation/message-
>>> processor/org.wso2.carbon.message.processor.ui/src/main/
>>> resources/org/wso2/carbon/message/processor/ui/i18n/Resources.properties
>>>carbon/platform/trunk/components/mediation/message-
>>> processor/org.wso2.carbon.message.processor.ui/src/main/
>>> resources/web/message_processor/index.jsp
>>>carbon/platform/trunk/components/mediation/message-
>>> processor/org.wso2.carbon.message.processor.ui/src/main/
>>> resources/web/message_processor/manageMessageForwardingProcessor.jsp
>>>
>>> Modified: carbon/platform/trunk/components/mediation/message-
>>> processor/org.wso2.carbon.message.processor.ui/src/main/
>>> resources/org/wso2/carbon/message/processor/ui/i18n/Resources.properties
>>> URL:
>>> http://wso2.org/svn/browse/wso2/carbon/platform/trunk/components/mediation/message-processor/org.wso2.carbon.message.processor.ui/src/main/resources/org/wso2/carbon/message/processor/ui/i18n/Resources.properties?rev=130164&r1=130163&r2=130164&view=diff
>>> 
>>> ==
>>> --- carbon/platform/trunk/components/mediation/message-
>>> processor/org.wso2.carbon.message.processor.ui/src/main/
>>> resources/org/wso2/carbon/message/processor/ui/i18n/Resources.properties
>>> (original)
>>> +++ carbon/platform/trunk/components/mediation/message-
>>> processor/org.wso2.carbon.message.processor.ui/src/main/
>>> resources/org/wso2/carbon/message/processor/ui/i18n/Resources.properties
>>> Fri Jun 15 02:00:53 2012
>>> @@ -24,7 +24,9 @@
>>>  size=Size
>>>  action=Actions
>>>  deactivate=Deactivate
>>> -activate=activate
>>> +activate=Activate
>>> +inactive=Inactive
>>> +active=Active
>>>  no.messageProcessors.are.currently.defined=No Message Processors are
>>> currently defined.
>>>  message.Processor= Message Processor
>>>  name=Name
>>> @@ -104,7 +106,7 @@
>>>  message.sampling.processor.parameters=Message Sampling Processor
>>> Parameters
>>>  message.context.properties=Message Context Properties
>>>  interval=Message retry interval (Millis)
>>>
>>>
>>> *-max.deliver.attempts=Maximum delivery 
>>> attempts+max.delivery.attempts=Maximum delivery attempts*
>>>  axis2.repo=Axis2 Client repository
>>>  axis2.config=Axis2 Configuration
>>>  message.processor.reply.sequence=Reply sequence name
>>> @@ -112,4 +114,4 @@
>>>  quartz.conf=Quartz configuration file path
>>>  cronExpression=Cron Expression
>>>  target.endpoint=Address Endpoint name
>>> -out_only=Out-only message
>>> \ No newline at end of file
>>> +out_only=Out-only message
>>>
>>> Modified: carbon/platform/trunk/components/mediation/message-
>>> processor/org.wso2.carbon.message.processor.ui/src/ma

Re: [Dev] [ESB 4.9.0] Different ESB configs for Message Processor.

2015-10-06 Thread Yasassri Ratnayake 
According to [1]  "*The deactivate sequence that will be executed when the
processor is deactivated automatically. Automatic deactivation occurs when
the maximum delivery attempts is exceeded and the Drop message after
maximum delivery attempts parameter is disabled.*"

[1] - https://docs.wso2.com/display/ESB490/Message+Forwarding+Processor

On Wed, Oct 7, 2015 at 10:06 AM, Ajith Vitharana  wrote:

> Other issue is,
>
> 1. According to the sample I'm shutting down the backend-1  and send a
> request.
> 2. Now I can see the message store has one message.
> 3. Before 50 delivery attempts , start the backend-1
> 4. Now I  can see the message processor executed and message delivered  to
> backed-1
>
> But just after sending the message, the  message processor going to
> deactivate state and printing following exception.
>
> [2015-10-07 00:25:03,987]  WARN - ForwardingService Failed to send the
> message through the fault sequence. Sequence name does not Exist.
> *[2015-10-07 00:25:05,335]  WARN - ForwardingService Failed to send the
> message through the deactivate sequence. Sequence name does not Exist.*
> [2015-10-07 00:25:05,340]  INFO - ScheduledMessageProcessor Successfully
> deactivated the message processor [send_pending_message]
> *[2015-10-07 00:25:05,341] ERROR - ForwardingService Failed to send the
> out message. Reply sequence does not Exist. Deactivated the message
> processor*
>
>
> 1. According to the WARN log , what is the deactivate sequence should
> define ?
> 2. Why message processor is deactivate just after sending message to back
> end ?
>
> -Ajith
>
>
> On Tue, Oct 6, 2015 at 11:39 PM, Ajith Vitharana  wrote:
>
>> Hi Yasassri.
>>
>> Yes. According to the carbon commits it has renamed. Then those configs
>> never tested after 2012 :)
>>
>> [1] https://wso2.org/jira/browse/CARBON-13114
>>
>> -Ajith
>>
>>
>> Author: ishan
>> Date: Fri Jun 15 02:00:53 2012
>> New Revision: 130164
>> URL: http://wso2.org/svn/browse/wso2?view=rev&revision=130164
>>
>> Log:
>> Fixing CARBON-13114 with the patch of CharithaM.
>>
>> Modified:
>>carbon/platform/trunk/components/mediation/message-
>> processor/org.wso2.carbon.message.processor.ui/src/main/
>> resources/org/wso2/carbon/message/processor/ui/i18n/Resources.properties
>>carbon/platform/trunk/components/mediation/message-
>> processor/org.wso2.carbon.message.processor.ui/src/main/
>> resources/web/message_processor/index.jsp
>>carbon/platform/trunk/components/mediation/message-
>> processor/org.wso2.carbon.message.processor.ui/src/main/
>> resources/web/message_processor/manageMessageForwardingProcessor.jsp
>>
>> Modified: carbon/platform/trunk/components/mediation/message-
>> processor/org.wso2.carbon.message.processor.ui/src/main/
>> resources/org/wso2/carbon/message/processor/ui/i18n/Resources.properties
>> URL:
>> http://wso2.org/svn/browse/wso2/carbon/platform/trunk/components/mediation/message-processor/org.wso2.carbon.message.processor.ui/src/main/resources/org/wso2/carbon/message/processor/ui/i18n/Resources.properties?rev=130164&r1=130163&r2=130164&view=diff
>> 
>> ==
>> --- carbon/platform/trunk/components/mediation/message-
>> processor/org.wso2.carbon.message.processor.ui/src/main/
>> resources/org/wso2/carbon/message/processor/ui/i18n/Resources.properties
>> (original)
>> +++ carbon/platform/trunk/components/mediation/message-
>> processor/org.wso2.carbon.message.processor.ui/src/main/
>> resources/org/wso2/carbon/message/processor/ui/i18n/Resources.properties
>> Fri Jun 15 02:00:53 2012
>> @@ -24,7 +24,9 @@
>>  size=Size
>>  action=Actions
>>  deactivate=Deactivate
>> -activate=activate
>> +activate=Activate
>> +inactive=Inactive
>> +active=Active
>>  no.messageProcessors.are.currently.defined=No Message Processors are
>> currently defined.
>>  message.Processor= Message Processor
>>  name=Name
>> @@ -104,7 +106,7 @@
>>  message.sampling.processor.parameters=Message Sampling Processor
>> Parameters
>>  message.context.properties=Message Context Properties
>>  interval=Message retry interval (Millis)
>>
>>
>> *-max.deliver.attempts=Maximum delivery 
>> attempts+max.delivery.attempts=Maximum delivery attempts*
>>  axis2.repo=Axis2 Client repository
>>  axis2.config=Axis2 Configuration
>>  message.processor.reply.sequence=Reply sequence name
>> @@ -112,4 +114,4 @@
>>  quartz.conf=Quartz configuration file path
>>  cronExpression=Cron Expression
>>  target.endpoint=Address Endpoint name
>> -out_only=Out-only message
>> \ No newline at end of file
>> +out_only=Out-only message
>>
>> Modified: carbon/platform/trunk/components/mediation/message-
>> processor/org.wso2.carbon.message.processor.ui/src/main/
>> resources/web/message_processor/index.jsp
>> URL:
>> http://wso2.org/svn/browse/wso2/carbon/platform/trunk/components/mediation/message-processor/org.wso2.carbon.message.processor.ui/src/main/resources/web/message_processor/index.jsp?rev=130164&r1=130163&r2=1

Re: [Dev] [ESB 4.9.0] Different ESB configs for Message Processor.

2015-10-06 Thread Ajith Vitharana 
Other issue is,

1. According to the sample I'm shutting down the backend-1  and send a
request.
2. Now I can see the message store has one message.
3. Before 50 delivery attempts , start the backend-1
4. Now I  can see the message processor executed and message delivered  to
backed-1

But just after sending the message, the  message processor going to
deactivate state and printing following exception.

[2015-10-07 00:25:03,987]  WARN - ForwardingService Failed to send the
message through the fault sequence. Sequence name does not Exist.
*[2015-10-07 00:25:05,335]  WARN - ForwardingService Failed to send the
message through the deactivate sequence. Sequence name does not Exist.*
[2015-10-07 00:25:05,340]  INFO - ScheduledMessageProcessor Successfully
deactivated the message processor [send_pending_message]
*[2015-10-07 00:25:05,341] ERROR - ForwardingService Failed to send the out
message. Reply sequence does not Exist. Deactivated the message processor*


1. According to the WARN log , what is the deactivate sequence should
define ?
2. Why message processor is deactivate just after sending message to back
end ?

-Ajith


On Tue, Oct 6, 2015 at 11:39 PM, Ajith Vitharana  wrote:

> Hi Yasassri.
>
> Yes. According to the carbon commits it has renamed. Then those configs
> never tested after 2012 :)
>
> [1] https://wso2.org/jira/browse/CARBON-13114
>
> -Ajith
>
>
> Author: ishan
> Date: Fri Jun 15 02:00:53 2012
> New Revision: 130164
> URL: http://wso2.org/svn/browse/wso2?view=rev&revision=130164
>
> Log:
> Fixing CARBON-13114 with the patch of CharithaM.
>
> Modified:
>carbon/platform/trunk/components/mediation/message-
> processor/org.wso2.carbon.message.processor.ui/src/main/
> resources/org/wso2/carbon/message/processor/ui/i18n/Resources.properties
>carbon/platform/trunk/components/mediation/message-
> processor/org.wso2.carbon.message.processor.ui/src/main/
> resources/web/message_processor/index.jsp
>carbon/platform/trunk/components/mediation/message-
> processor/org.wso2.carbon.message.processor.ui/src/main/
> resources/web/message_processor/manageMessageForwardingProcessor.jsp
>
> Modified: carbon/platform/trunk/components/mediation/message-
> processor/org.wso2.carbon.message.processor.ui/src/main/
> resources/org/wso2/carbon/message/processor/ui/i18n/Resources.properties
> URL:
> http://wso2.org/svn/browse/wso2/carbon/platform/trunk/components/mediation/message-processor/org.wso2.carbon.message.processor.ui/src/main/resources/org/wso2/carbon/message/processor/ui/i18n/Resources.properties?rev=130164&r1=130163&r2=130164&view=diff
> 
> ==
> --- carbon/platform/trunk/components/mediation/message-
> processor/org.wso2.carbon.message.processor.ui/src/main/
> resources/org/wso2/carbon/message/processor/ui/i18n/Resources.properties
> (original)
> +++ carbon/platform/trunk/components/mediation/message-
> processor/org.wso2.carbon.message.processor.ui/src/main/
> resources/org/wso2/carbon/message/processor/ui/i18n/Resources.properties
> Fri Jun 15 02:00:53 2012
> @@ -24,7 +24,9 @@
>  size=Size
>  action=Actions
>  deactivate=Deactivate
> -activate=activate
> +activate=Activate
> +inactive=Inactive
> +active=Active
>  no.messageProcessors.are.currently.defined=No Message Processors are
> currently defined.
>  message.Processor= Message Processor
>  name=Name
> @@ -104,7 +106,7 @@
>  message.sampling.processor.parameters=Message Sampling Processor
> Parameters
>  message.context.properties=Message Context Properties
>  interval=Message retry interval (Millis)
>
>
> *-max.deliver.attempts=Maximum delivery 
> attempts+max.delivery.attempts=Maximum delivery attempts*
>  axis2.repo=Axis2 Client repository
>  axis2.config=Axis2 Configuration
>  message.processor.reply.sequence=Reply sequence name
> @@ -112,4 +114,4 @@
>  quartz.conf=Quartz configuration file path
>  cronExpression=Cron Expression
>  target.endpoint=Address Endpoint name
> -out_only=Out-only message
> \ No newline at end of file
> +out_only=Out-only message
>
> Modified: carbon/platform/trunk/components/mediation/message-
> processor/org.wso2.carbon.message.processor.ui/src/main/
> resources/web/message_processor/index.jsp
> URL:
> http://wso2.org/svn/browse/wso2/carbon/platform/trunk/components/mediation/message-processor/org.wso2.carbon.message.processor.ui/src/main/resources/web/message_processor/index.jsp?rev=130164&r1=130163&r2=130164&view=diff
> 
> ==
> --- carbon/platform/trunk/components/mediation/message-
> processor/org.wso2.carbon.message.processor.ui/src/main/
> resources/web/message_processor/index.jsp(original)
> +++ carbon/platform/trunk/components/mediation/message-
> processor/org.wso2.carbon.message.processor.ui/src/main/
> resources/web/message_processor/index.jspFri Jun 15 02:00:53 2012
> @@ -290,11 +290,14 @@
> id="delete_link" class

Re: [Dev] [ESB 4.9.0] Different ESB configs for Message Processor.

2015-10-06 Thread Ajith Vitharana 
Hi Yasassri.

Yes. According to the carbon commits it has renamed. Then those configs
never tested after 2012 :)

[1] https://wso2.org/jira/browse/CARBON-13114

-Ajith


Author: ishan
Date: Fri Jun 15 02:00:53 2012
New Revision: 130164
URL: http://wso2.org/svn/browse/wso2?view=rev&revision=130164

Log:
Fixing CARBON-13114 with the patch of CharithaM.

Modified:
   carbon/platform/trunk/components/mediation/message-
processor/org.wso2.carbon.message.processor.ui/src/main/
resources/org/wso2/carbon/message/processor/ui/i18n/Resources.properties
   carbon/platform/trunk/components/mediation/message-
processor/org.wso2.carbon.message.processor.ui/src/main/
resources/web/message_processor/index.jsp
   carbon/platform/trunk/components/mediation/message-
processor/org.wso2.carbon.message.processor.ui/src/main/
resources/web/message_processor/manageMessageForwardingProcessor.jsp

Modified: carbon/platform/trunk/components/mediation/message-
processor/org.wso2.carbon.message.processor.ui/src/main/
resources/org/wso2/carbon/message/processor/ui/i18n/Resources.properties
URL:
http://wso2.org/svn/browse/wso2/carbon/platform/trunk/components/mediation/message-processor/org.wso2.carbon.message.processor.ui/src/main/resources/org/wso2/carbon/message/processor/ui/i18n/Resources.properties?rev=130164&r1=130163&r2=130164&view=diff

==
--- carbon/platform/trunk/components/mediation/message-
processor/org.wso2.carbon.message.processor.ui/src/main/
resources/org/wso2/carbon/message/processor/ui/i18n/Resources.properties
(original)
+++ carbon/platform/trunk/components/mediation/message-
processor/org.wso2.carbon.message.processor.ui/src/main/
resources/org/wso2/carbon/message/processor/ui/i18n/Resources.properties
Fri Jun 15 02:00:53 2012
@@ -24,7 +24,9 @@
 size=Size
 action=Actions
 deactivate=Deactivate
-activate=activate
+activate=Activate
+inactive=Inactive
+active=Active
 no.messageProcessors.are.currently.defined=No Message Processors are
currently defined.
 message.Processor= Message Processor
 name=Name
@@ -104,7 +106,7 @@
 message.sampling.processor.parameters=Message Sampling Processor Parameters
 message.context.properties=Message Context Properties
 interval=Message retry interval (Millis)

*-max.deliver.attempts=Maximum delivery
attempts+max.delivery.attempts=Maximum delivery attempts*
 axis2.repo=Axis2 Client repository
 axis2.config=Axis2 Configuration
 message.processor.reply.sequence=Reply sequence name
@@ -112,4 +114,4 @@
 quartz.conf=Quartz configuration file path
 cronExpression=Cron Expression
 target.endpoint=Address Endpoint name
-out_only=Out-only message
\ No newline at end of file
+out_only=Out-only message

Modified: carbon/platform/trunk/components/mediation/message-
processor/org.wso2.carbon.message.processor.ui/src/main/
resources/web/message_processor/index.jsp
URL:
http://wso2.org/svn/browse/wso2/carbon/platform/trunk/components/mediation/message-processor/org.wso2.carbon.message.processor.ui/src/main/resources/web/message_processor/index.jsp?rev=130164&r1=130163&r2=130164&view=diff

==
--- carbon/platform/trunk/components/mediation/message-
processor/org.wso2.carbon.message.processor.ui/src/main/
resources/web/message_processor/index.jsp(original)
+++ carbon/platform/trunk/components/mediation/message-
processor/org.wso2.carbon.message.processor.ui/src/main/
resources/web/message_processor/index.jspFri Jun 15 02:00:53 2012
@@ -290,11 +290,14 @@
id="delete_link" class="icon-link"
style="background-image:url(..
/admin/images/delete.gif);">
-
+
+ [
+
+]
+
 
 <%
 } else if ("Scheduled Message Forwarding Processor".
@@ -308,11 +311,14 @@
id="delete_link" class="icon-link"
style="background-image:url(..
/admin/images/delete.gif);">
-
+
+ [
+
+]
+
 
 <%
 } else if ("Message Sampling Processor".
@@ -326,11 +332,15 @@
id="delete_link" class="icon-link"
style="background-image:url(..
/admin/images/delete.gif);">
-
+ 
+ [
+
+]
+
 
 <%} else { %>
 
-
\ No newline at end of file
+

Modified: carbon/platform/trunk/components/mediation/message-
processor/org.wso2.carbon.message.processor.ui/src/main/
resources/web/message_processor/manageMessageForwardingProcessor.jsp
URL:
http://wso2.org/svn/browse/wso2/carbon/platform/trunk/components/mediation/message-processor/org.wso2.carbon.message.processor.ui/src/main/resources/web/message_processor/manageMessageForwardingProcessor.j

Re: [Dev] [ESB 4.9.0] Different ESB configs for Message Processor.

2015-10-06 Thread Yasassri Ratnayake 
Hi Ajith,

It seems the configs are not correct in the sample, Also in your second
step the parameter name is *4 *which is correct, but in the
sample the Property is given *50. *This must be causing the
inconsistent behavior.

With Regards,

On Wed, Oct 7, 2015 at 8:27 AM, Ajith Vitharana  wrote:

> Hi All,
>
> I updated source view from the configuration mentioned in sample [1].
>
> i) When I double check the message processor configs from source view, I
>  noticed same config as the sample (expected behavior).
>
>  class="org.apache.synapse.message.processor.impl.forwarder.ScheduledMessageForwardingProcessor"
> messageStore="*pending_subscriptions*" name="send_pending_message"
> targetEndpoint="DurableSubscriberEndpoint">
> 1000
> false
>  name="target.endpoint">DurableSubscriberEndpoint
> *50*
> 
>
> ii) When I go to the "Message Processors" UI and edit the config (wrong
> configurations)
>
>  class="org.apache.synapse.message.processor.impl.forwarder.ScheduledMessageForwardingProcessor"
> targetEndpoint="DurableSubscriberEndpoint" messageStore="
> *pending_subscriptions*" xmlns="http://ws.apache.org/ns/synapse";>
>1000
>1000
>   * 4*
>true
>Disabled
>1
> 
>
> iii) According to the sample ,  I noticed  the message processor is
> deactivating after the 4 attempts, that means the second config executing
> at mediation.
>
>
> iv) When I check the file in synapse-configs/default/message-processors
> that is updated with my new configs.
>
> 
> http://ws.apache.org/ns/synapse";
>
> class="org.apache.synapse.message.processor.impl.forwarder.ScheduledMessageForwardingProcessor"
>   name="*send_pending_message*"
>   targetEndpoint="DurableSubscriberEndpoint"
>   messageStore="pending_subscriptions">
>1000
>false
>DurableSubscriberEndpoint
>   * 50*
> 
>
>
> [1] https://docs.wso2.com/display/IntegrationPatterns/Durable+Subscriber
>
> --
> Ajith Vitharana.
>
> WSO2 Inc. - http://wso2.com
> Email  : aji...@wso2.com
> Blog: http://vitharana.org
> Mobile : +1-812-360-5335
>
>


-- 
Yasassri Ratnayake
Software Engineer - QA
WSO2 Inc ; http://wso2.com
lean.enterprise.middleware
*Mobile : +94715933168*
*Blogs : http://yasassriratnayake.blogspot.com
*
*http://wso2logs.blogspot.com *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [ESB 4.9.0] Different ESB configs for Message Processor.

2015-10-06 Thread Ajith Vitharana 
Hi All,

I updated source view from the configuration mentioned in sample [1].

i) When I double check the message processor configs from source view, I
 noticed same config as the sample (expected behavior).


1000
false
DurableSubscriberEndpoint
*50*


ii) When I go to the "Message Processors" UI and edit the config (wrong
configurations)

http://ws.apache.org/ns/synapse";>
   1000
   1000
  * 4*
   true
   Disabled
   1


iii) According to the sample ,  I noticed  the message processor is
deactivating after the 4 attempts, that means the second config executing
at mediation.


iv) When I check the file in synapse-configs/default/message-processors
that is updated with my new configs.


http://ws.apache.org/ns/synapse";

class="org.apache.synapse.message.processor.impl.forwarder.ScheduledMessageForwardingProcessor"
  name="*send_pending_message*"
  targetEndpoint="DurableSubscriberEndpoint"
  messageStore="pending_subscriptions">
   1000
   false
   DurableSubscriberEndpoint
  * 50*



[1] https://docs.wso2.com/display/IntegrationPatterns/Durable+Subscriber

-- 
Ajith Vitharana.

WSO2 Inc. - http://wso2.com
Email  : aji...@wso2.com
Blog: http://vitharana.org
Mobile : +1-812-360-5335
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev