Re: [Dev] Setting JMS Version gloably
Hi Manu, Vijitha's comment is valid. As per the offline discussion I had with ErandaR and PrabathAR, JMS 2.0 shared subscription feature is not implemented for JMS Proxy services (in axis2 transport listener side) since it will be deprecated in future. Therefore it is available for JMS Inbound Endpoints only. If you have lots of JMS proxies we may need to migrate them into JMS Inbound Endpoints. Thanks & Regards, On Wed, Jun 8, 2016 at 11:00 AM, Vijitha Ekanayake wrote: > Hi Manu/Dilshani, > > According to the current implementation It seems, we haven't done any > changes in JMSTransportListener side. JMS 2.0 listener implementation is > supported as JMS inbound endpoint and sender implementation support on JMS > transport sender. You can refer mail thread[1] for more details. > > [1]. [Architecture] [GSoC] JMS 2.0 support for WSO2 ESB JMS Inbound > Endpoint and JMS Transport > > Thanks. > > On Wed, Jun 8, 2016 at 8:58 AM, Dilshani Subasinghe > wrote: > >> Hi Manuranga, >> >> According to documentation, Yes we can set that. But I notice that, it >> doesn't validate through the value given globally. For example, even I set >> up JMS Version as 2.0 globally, it doesn't take that value. >> >> Within the source (ServiceTaskManager.java) it seem to hard coded. >> >> >> */** Should this service use JMS 1.1 ? (when false, defaults to 1.0.2b) >> */private boolean jmsSpec11 = true;* >> >> @Vijitha - Hope you may explain the actual scenario ? >> >> Regards, >> Dilshani >> >> >> On Wed, Jun 8, 2016 at 1:25 AM, Manuranga Perera wrote: >> >>> Hi Ravindra/Dilshani, >>> Can we set transport.jms.JMSSpecVersion globally (ie: via axis2.xml)? >>> >>> -- >>> With regards, >>> *Manu*ranga Perera. >>> >>> phone : 071 7 70 20 50 >>> mail : m...@wso2.com >>> >> >> >> >> -- >> 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 >> Blog: dilshanilive.blogspot.com >> > > > > -- > Vijitha Ekanayake > Software Engineer*, *WSO2, Inc.; http://wso2.com/ > Mobile : +94 777 24 73 39 | +94 718 74 44 08 > lean.enterprise.middleware > -- Ravindra Ranwala Software Engineer WSO2, Inc: http://wso2.com <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> Mobile: +94714198770 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] ESB 5 Beta - Shared subscriber doesn't connect
.internal.Reason.createException(Reason.java:214)
> at
> com.ibm.msg.client.wmq.internal.WMQMessageConsumer.checkJmqiCallSuccess(WMQMessageConsumer.java:212)
> at
> com.ibm.msg.client.wmq.internal.WMQMessageConsumer.checkJmqiCallSuccess(WMQMessageConsumer.java:112)
> at
> com.ibm.msg.client.wmq.internal.WMQConsumerShadow.initialize(WMQConsumerShadow.java:1038)
> at
> com.ibm.msg.client.wmq.internal.WMQSyncConsumerShadow.initialize(WMQSyncConsumerShadow.java:134)
> at
> com.ibm.msg.client.wmq.internal.WMQMessageConsumer.(WMQMessageConsumer.java:470)
> at
> com.ibm.msg.client.wmq.internal.WMQSession.createDurableSubscriber(WMQSession.java:897)
> at
> com.ibm.msg.client.jms.internal.JmsSessionImpl.createDurableSubscriber(JmsSessionImpl.java:1166)
> at com.ibm.mq.jms.MQSession.createDurableSubscriber(MQSession.java:539)
> at
> org.apache.axis2.transport.jms.JMSUtils.createConsumer(JMSUtils.java:794)
> at
> org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.createConsumer(ServiceTaskManager.java:924)
> at
> org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.getMessageConsumer(ServiceTaskManager.java:785)
> at
> org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.receiveMessage(ServiceTaskManager.java:535)
> at
> org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.run(ServiceTaskManager.java:447)
> at
> org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed
> with compcode '2' ('MQCC_FAILED') reason '2429'
> ('MQRC_SUBSCRIPTION_IN_USE').
> at
> com.ibm.msg.client.wmq.common.internal.Reason.createException(Reason.java:202)
> ... 17 more
> --
> With regards,
> *Manu*ranga Perera.
>
> phone : 071 7 70 20 50
> mail : m...@wso2.com
>
--
Ravindra Ranwala
Software Engineer
WSO2, Inc: http://wso2.com
<http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg>
Mobile: +94714198770
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [ESB500]Error in Clustering Mode - JMS 2.0 Feature:Shared Topic Subscription
Hi Dilshani,
AFAIK there's no special configuration for this in ESB side. Have you
copied all the libraries to the workers properly? If so we have to debug
and see the root cause of the issue.
Thanks & Regards,
On Thu, Feb 25, 2016 at 8:14 AM, Dilshani Subasinghe
wrote:
> Hi Malaka,
>
> This issue about clustering. Multiple subscribers do not affect to the
> error.
>
> Yes, I am using M2 pack.
>
> Regards,
> Dilshani
>
>
> On Wed, Feb 24, 2016 at 8:38 PM, Malaka Silva wrote:
>
>> Hi Dilshani,
>>
>> Just to be clear is this issue related to clustering or issue persist
>> when there are multiple subscribers?
>>
>> Also you must be using esb 5 milestone pack?
>>
>> On Wed, Feb 24, 2016 at 7:09 PM, Dilshani Subasinghe
>> wrote:
>>
>>> Hi ESB Team,
>>>
>>> I am testing new fearure called "JMS 2.0.0 Support"[1] and found an
>>> error in "JMS 2.0 Feature:Shared Topic Subscription". Feature will
>>> successfully functioning in Standalone mode. But it clustering mode, it
>>> will provide an error as follows;
>>>
>>> TID: [-1234] [] [2016-02-24 15:30:13,451] WARN
>>> {org.wso2.carbon.inbound.endpoint.protocol.jms.JMSPollingConsumer} -
>>> Inbound JMS endpoint unable to get a connection.
>>> {org.wso2.carbon.inbound.endpoint.protocol.jms.JMSPollingConsumer}
>>> TID: [-1234] [] [2016-02-24 15:30:14,451] ERROR
>>> {org.wso2.carbon.inbound.endpoint.protocol.jms.factory.JMSConnectionFactory}
>>> - Connection cannot bb establish to the broke. Plese check the broker libs
>>> provided.
>>> {org.wso2.carbon.inbound.endpoint.protocol.jms.factory.JMSConnectionFactory}
>>>
>>> This error will pop up from worker nodes. When clustering mode disabled,
>>> it will work properly.
>>>
>>> Is there any special configuration for HornetQ when ESB in clustering
>>> mode?
>>>
>>> As I found out, HornetQ "run.sh" script must modify to bind its' host
>>> name. Likewise is there any special configurations for ESB cluster ?
>>>
>>> Thank you in advance.
>>>
>>> [1] - https://redmine.wso2.com/issues/4121
>>>
>>>
>>> --
>>> Best Regards,
>>>
>>> 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
>
--
Ravindra Ranwala
Software Engineer
WSO2, Inc: http://wso2.com
<http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg>
Mobile: +94714198770
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Committers += Prabath Ariyarathna
Congratulations Prabath ! On Tue, Oct 13, 2015 at 11:50 AM, Chanaka Fernando wrote: > Congratulations Prabath !!! Keep up the good work. > > On Tue, Oct 13, 2015 at 11:44 AM, Kasun Indrasiri wrote: > >> Hi devs, >> >> Its my pleasure to welcome Prabath Ariyarathna as a WSO2 Committer. >> Prabath, welcome aboard and keep up the good work! >> >> Thanks. >> >> -- >> Kasun Indrasiri >> Software Architect >> WSO2, Inc.; http://wso2.com >> lean.enterprise.middleware >> >> cell: +94 77 556 5206 >> Blog : http://kasunpanorama.blogspot.com/ >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > -- > Chanaka Fernando > Senior Technical Lead > WSO2, Inc.; http://wso2.com > lean.enterprise.middleware > > mobile: +94 773337238 > Blog : http://soatutorials.blogspot.com > LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0 > Twitter:https://twitter.com/chanakaudaya > > > > > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Ravindra Ranwala Software Engineer WSO2, Inc: http://wso2.com <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> Mobile: +94714198770 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [ESB 4.9.0] Different ESB configs for Message Processor.
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.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/manageMessageForwardingProcessor.jsp
>>>>>(original)
>>>>> +++ carbon/platform/trunk/components/mediation/message-
>>>>> processor/org.wso2.carbon.message.processor.ui/src/main/
>>>>> resources/web/message_processor/manageMessageForwardingProcessor.jsp
>>>>>Fri Jun 15 02:00:53 2012
>>>>> @@ -92,7 +92,7 @@
>>>>>
>>>>> function addServiceParams() {
>>>>> addServiceParameter("interval", document.getElementById('
>>>>> retry_interval').value);
>>>>> -addServiceParameter("max.deliver.attempts",
>>>>> document.getElementById('max_delivery_attempts').value);
>>>>> +addServiceParameter("max.delivery.attempts",
>>>>> document.getElementById('max_delivery_attempts').value);
>>>>> addServiceParameter("axis2.repo", document.getElementById('
>>>>> axis2_repo').value);
>>>>> addServiceParameter("axis2.config", document.getElementById('
>>>>> axis2_config').value);
>>>>> addServiceParameter("message.processor.reply.sequence",
>>>>> document.getElementById('message_processor_reply_sequence').value);
>>>>> @@ -292,10 +292,10 @@
>>>>>
>>>>>
>>>>>
>>>>> -
>>>>> +
>>>>> >>>> id="max_delivery_attempts" name="max_delivery_attempts"
>>>>> value="<%=((null!=processorData)&&
>>>>> processorData.getParams() != null
>>>>> -&& !processorData.getParams().
>>>>> isEmpty()&&(processorData.getParams().get("max.deliver.attempts
>>>>> ")!=null))?processorData.getParams().get("max.deliver.attempts"):""%>"
>>>>> +&& !processorData.getParams().
>>>>> isEmpty()&&(processorData.getParams().get("max.delivery.attempts
>>>>> ")!=null))?processorData.getParams().get("max.delivery.attempts
>>>>> "):""%>"
>>>>> />
>>>>>
>>>>>
>>>>> ___
>>>>> Commits mailing list
>>>>> comm...@wso2.org
>>>>> http://wso2.org/cgi-bin/mailman/listinfo/commits
>>>>>
>>>>>
>>>>> On Tue, Oct 6, 2015 at 11:28 PM, Yasassri Ratnayake >>>> > wrote:
>>>>>
>>>>>> Hi Ajith,
>>>>>>
>>>>>> It seems the configs are not correct in the sample, Also in your
>>>>>> second step the parameter name is *>>>>> name="max.delivery.attempts">4 *which is correct, but in
>>>>>> the sample the Property is given *>>>>> name="max.deliver.attempts">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
>>>>>>>>>>>>> name="target.endpoint">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 <%2B94715933168>*
>>>>>> *Blogs : http://yasassriratnayake.blogspot.com
>>>>>> <http://yasassriratnayake.blogspot.com/>*
>>>>>> *http://wso2logs.blogspot.com
>>>>>> <http://wso2logs.blogspot.com>*
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Ajith Vitharana.
>>>>>
>>>>> WSO2 Inc. - http://wso2.com
>>>>> Email : aji...@wso2.com
>>>>> Blog: http://vitharana.org
>>>>> Mobile : +1-812-360-5335
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> 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 <%2B94715933168>*
>>> *Blogs : http://yasassriratnayake.blogspot.com
>>> <http://yasassriratnayake.blogspot.com/>*
>>> *http://wso2logs.blogspot.com <http://wso2logs.blogspot.com>*
>>>
>>
>>
>>
>> --
>> Ajith Vitharana.
>>
>> WSO2 Inc. - http://wso2.com
>> Email : aji...@wso2.com
>> Blog: http://vitharana.org
>> Mobile : +1-812-360-5335
>>
>>
>
>
> --
> 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
>
>
--
Ravindra Ranwala
Software Engineer
WSO2, Inc: http://wso2.com
<http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg>
Mobile: +94714198770
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [VOTE] Release WSO2 ESB 4.9.0 RC6
Hi All, I have tested below functionalities in the RC6 pack. Message Processor Coordination support = Standalone Mode - Message forwarding - Deactivation/Activation scenarios - Cron expressions - Deletion and Editing Cluster Mode - Basic Message Forwarding with single task (i.e. taskCount=1) - Activation/Deactivation/Editing MP with taskCount = 1 - Activation/Deactivation/Editing MP with taskCount = 2 - Changing between task counts, from 1 to 2 and from 2 back to 1 - Deletion MP with different member counts - Checked number of JMS consumers for each scenario and verified - Message Processor with reply sequence RabbitMQ Transport = - ESB acts as RabbitMQ AMQP Producer - ESB acts as RabbitMQ AMQP Consumer [X] Stable - go ahead and release Thanks & Regards, On Thu, Sep 10, 2015 at 1:16 AM, Chanaka Fernando wrote: > Hi Devs, > > WSO2 ESB 4.9.0 RC6 Release Vote > > This release fixes the following issues: > https://wso2.org/jira/issues/?filter=12393 > > Please download ESB 4.9.0 RC6 and test the functionality and vote. Vote > will be open for 72 hours or as needed. > > Source & binary distribution files: > > http://maven.wso2.org/nexus/content/repositories/orgwso2esb-068/org/wso2/esb/wso2esb/4.9.0/ > > Maven staging repository: > http://maven.wso2.org/nexus/content/repositories/orgwso2esb-068/ > > The tag to be voted upon : > https://github.com/wso2/product-esb/tree/esb-parent-4.9.0-RC6 > > > [-] Broken - do not release (explain why) > [+] Stable - go ahead and release > > Thanks and Regards, > ~ WSO2 ESB Team ~ > > -- > -- > Chanaka Fernando > Senior Technical Lead > WSO2, Inc.; http://wso2.com > lean.enterprise.middleware > > mobile: +94 773337238 > Blog : http://soatutorials.blogspot.com > LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0 > Twitter:https://twitter.com/chanakaudaya > > > > > > _______ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Ravindra Ranwala Software Engineer WSO2, Inc: http://wso2.com <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> Mobile: +94714198770 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] cron job on MessageProcessor?
Hi John, Message Processor Max Delivery attempt parameter is clearly documented here [1]. Anyway in ESB 4.9.0 version we have deactivateSequence, which can be triggered when the Message Processor is deactivated after reaching max-delivery-attempts. In that sequence you may implement DLC pattern. Also I understand that your requirement is valid, and you may create a public jira to track that. We may incorporate it in to the product in a future release. [1] https://docs.wso2.com/display/ESB481/Message+Forwarding+Processor Thanks & Regards, On Wed, Sep 9, 2015 at 4:07 PM, John Hawkins wrote: > Hi Ravindra, > I'm thinking about this a lot now > max.delivery.attempts is not documented anywhere nor is it in the > MessageProcessor wizard (but it is in a few JIRA's and blog entries). Is > this deliberate do you know - are we hiding it for some reason? > > Personally I would expect some kind of 'retries fail' sequence to be an > optional thing I can set. Then I could do what I wanted with the message > and the MessageProcessor can continue. Are you aware of any thoughts like > this at all? If not then I think I need to create a JIRA to at least > document this feature as-is. > > cheers, > john. > > John Hawkins > Director: Solutions Architecture > > > On Wed, Sep 9, 2015 at 11:03 AM, Ravindra Ranwala > wrote: > >> Hi John, >> >> There is no DLC behaviour after reaching the max-retry-count at the >> moment. >> >> >> Thanks & Regards, >> >> On Wed, Sep 9, 2015 at 3:23 PM, John Hawkins wrote: >> >>> Another question - is there no Dead Letter Queue behaviour then if a >>> message fails to get sent after max_retry is done? >>> >>> John Hawkins >>> Director: Solutions Architecture >>> >>> >>> On Thu, Sep 3, 2015 at 4:41 PM, Ravindra Ranwala >>> wrote: >>> >>>> Hi John, >>>> >>>> The Cron expression in MP is used to create firing schedules such as >>>> "At 8:00am every Monday through Friday" [1]. If it is set the MP will run >>>> according to that. Otherwise MP will poll the queue with the specified >>>> interval value continuously. >>>> >>>> Also the MP has a parameter called max_delivery_attempts (defaults to >>>> 4), which defines the maximum retry attempts in case of a failure in end >>>> point. By default if the MP could not send the message to the end point >>>> after this number of retry count, it deactivates itself. But that message >>>> remains in the queue. After that you have to activate the MP explicitly to >>>> make the next schedule to be effective. Otherwise it will remain >>>> deactivated. >>>> >>>> If you need to override the above behaviour, you need to enable >>>> max-delivery-drop parameter, so that if the MP could not send the message >>>> after this number of attempts, it merely drops the message and continues. >>>> Here you loose the message if the endpoint is down. >>>> >>>> >>>> [1] >>>> http://www.quartz-scheduler.org/documentation/quartz-1.x/tutorials/crontrigger >>>> >>>> >>>> Thanks & Regards, >>>> >>>> On Thu, Sep 3, 2015 at 8:05 PM, John Hawkins wrote: >>>> >>>>> Hi All, >>>>> >>>>> I'm trying to figure out when does the "cron schedule" get used that >>>>> I can configure on the MessageProcessor? >>>>> >>>>> The logic that I think is happening is - if the message fails to get >>>>> sent 'retry' number of times then it's put to the dead letter queue (or >>>>> DLC >>>>> as its called in qpid) . The Message Processor then looks at the DLC based >>>>> on when the cron job tells it to? >>>>> >>>>> If this logic is correct (?) then I have a number of other questions >>>>> please: >>>>> >>>>> 1) what if this cron job is not set - does the message remain on the >>>>> DLQ? >>>>> 2) Where is the DLQ defined to synapse/the message processor so that >>>>> it knows where to go? >>>>> 3) What if the message gets removed from the DLC for some reason >>>>> (manually or otherwise)? Do we fail quietly or log it somewhere? >>>>> 4) What if other messages from other parts of the ESB get put to the >>>>> DLQ ? How does the MessageProcesso
Re: [Dev] cron job on MessageProcessor?
Hi John, There is no DLC behaviour after reaching the max-retry-count at the moment. Thanks & Regards, On Wed, Sep 9, 2015 at 3:23 PM, John Hawkins wrote: > Another question - is there no Dead Letter Queue behaviour then if a > message fails to get sent after max_retry is done? > > John Hawkins > Director: Solutions Architecture > > > On Thu, Sep 3, 2015 at 4:41 PM, Ravindra Ranwala > wrote: > >> Hi John, >> >> The Cron expression in MP is used to create firing schedules such as "At >> 8:00am every Monday through Friday" [1]. If it is set the MP will run >> according to that. Otherwise MP will poll the queue with the specified >> interval value continuously. >> >> Also the MP has a parameter called max_delivery_attempts (defaults to 4), >> which defines the maximum retry attempts in case of a failure in end point. >> By default if the MP could not send the message to the end point after this >> number of retry count, it deactivates itself. But that message remains in >> the queue. After that you have to activate the MP explicitly to make the >> next schedule to be effective. Otherwise it will remain deactivated. >> >> If you need to override the above behaviour, you need to enable >> max-delivery-drop parameter, so that if the MP could not send the message >> after this number of attempts, it merely drops the message and continues. >> Here you loose the message if the endpoint is down. >> >> >> [1] >> http://www.quartz-scheduler.org/documentation/quartz-1.x/tutorials/crontrigger >> >> >> Thanks & Regards, >> >> On Thu, Sep 3, 2015 at 8:05 PM, John Hawkins wrote: >> >>> Hi All, >>> >>> I'm trying to figure out when does the "cron schedule" get used that I >>> can configure on the MessageProcessor? >>> >>> The logic that I think is happening is - if the message fails to get >>> sent 'retry' number of times then it's put to the dead letter queue (or DLC >>> as its called in qpid) . The Message Processor then looks at the DLC based >>> on when the cron job tells it to? >>> >>> If this logic is correct (?) then I have a number of other questions >>> please: >>> >>> 1) what if this cron job is not set - does the message remain on the >>> DLQ? >>> 2) Where is the DLQ defined to synapse/the message processor so that it >>> knows where to go? >>> 3) What if the message gets removed from the DLC for some reason >>> (manually or otherwise)? Do we fail quietly or log it somewhere? >>> 4) What if other messages from other parts of the ESB get put to the DLQ >>> ? How does the MessageProcessor know which messages are for it? >>> >>> >>> many thanks for your help ! >>> john. >>> >>> >>> John Hawkins >>> Director: Solutions Architecture >>> >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> Ravindra Ranwala >> Software Engineer >> WSO2, Inc: http://wso2.com >> <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> >> Mobile: +94714198770 >> >> > -- Ravindra Ranwala Software Engineer WSO2, Inc: http://wso2.com <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> Mobile: +94714198770 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [VOTE] Release WSO2 ESB 4.9.0 RC4
Hi All, I have tested scenarios [1]. No issues found. [X] Stable - go ahead and release [1] https://docs.google.com/a/wso2.com/document/d/1WaRiVRrzDIaKLQU4zXcYj0SFN4PFT6J0wV253sE_dmA/edit?usp=sharing Thanks & Regards, On Tue, Sep 8, 2015 at 1:08 AM, Jagath Sisirakumara Ariyarathne < jaga...@wso2.com> wrote: > Hi Devs, > > WSO2 ESB 4.9.0 RC4 Release Vote > > This release fixes the following issues: > *https://wso2.org/jira/issues/?filter=12393 > <https://wso2.org/jira/issues/?filter=12393>* > > Please download ESB 4.9.0 RC4 and test the functionality and vote. Vote will > be open for 72 hours or as needed. > > *Source & binary distribution files:* > *http://maven.wso2.org/nexus/content/repositories/orgwso2esb-058/org/wso2/esb/wso2esb/4.9.0-RC4/ > <http://maven.wso2.org/nexus/content/repositories/orgwso2esb-058/org/wso2/esb/wso2esb/4.9.0-RC4/>* > > *Maven staging repository:* > *http://maven.wso2.org/nexus/content/repositories/orgwso2esb-058/ > <http://maven.wso2.org/nexus/content/repositories/orgwso2esb-058/>* > > *The tag to be voted upon :* > *https://github.com/wso2/product-esb/tree/esb-parent-4.9.0-RC4 > <https://github.com/wso2/product-esb/tree/esb-parent-4.9.0-RC4>* > > > [+] Stable - go ahead and release > [-] Broken - do not release (explain why) > > > Thanks and Regards, > ~ WSO2 ESB Team ~ > > -- > Jagath Ariyarathne > Technical Lead > WSO2 Inc. http://wso2.com/ > Email: jaga...@wso2.com > Mob : +94 77 386 7048 > > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Ravindra Ranwala Software Engineer WSO2, Inc: http://wso2.com <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> Mobile: +94714198770 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [VOTE] Release WSO2 ESB 4.9.0 RC3
Hi Devs, WSO2 ESB 4.9.0 RC3 Release Vote This release fixes the following issues: https://wso2.org/jira/browse/ESBJAVA-4138?filter=12385 Please download ESB 4.9.0 RC3 and test the functionality and vote. Vote will be open for 72 hours or as needed. Source & binary distribution files: http://maven.wso2.org/nexus/content/repositories/orgwso2esb-041/org/wso2/esb/wso2esb/4.9.0-RC3/ Maven staging repository: http://maven.wso2.org/nexus/content/repositories/orgwso2esb-041/ The tag to be voted upon : https://github.com/wso2/product-esb/tree/esb-parent-4.9.0-RC3 [ ] Broken - do not release (explain why) [ ] Stable - go ahead and release Thanks and Regards, ~ WSO2 ESB Team ~ -- Ravindra Ranwala Software Engineer WSO2, Inc: http://wso2.com <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> Mobile: +94714198770 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] cron job on MessageProcessor?
Hi John, The Cron expression in MP is used to create firing schedules such as "At 8:00am every Monday through Friday" [1]. If it is set the MP will run according to that. Otherwise MP will poll the queue with the specified interval value continuously. Also the MP has a parameter called max_delivery_attempts (defaults to 4), which defines the maximum retry attempts in case of a failure in end point. By default if the MP could not send the message to the end point after this number of retry count, it deactivates itself. But that message remains in the queue. After that you have to activate the MP explicitly to make the next schedule to be effective. Otherwise it will remain deactivated. If you need to override the above behaviour, you need to enable max-delivery-drop parameter, so that if the MP could not send the message after this number of attempts, it merely drops the message and continues. Here you loose the message if the endpoint is down. [1] http://www.quartz-scheduler.org/documentation/quartz-1.x/tutorials/crontrigger Thanks & Regards, On Thu, Sep 3, 2015 at 8:05 PM, John Hawkins wrote: > Hi All, > > I'm trying to figure out when does the "cron schedule" get used that I > can configure on the MessageProcessor? > > The logic that I think is happening is - if the message fails to get sent > 'retry' number of times then it's put to the dead letter queue (or DLC as > its called in qpid) . The Message Processor then looks at the DLC based on > when the cron job tells it to? > > If this logic is correct (?) then I have a number of other questions > please: > > 1) what if this cron job is not set - does the message remain on the DLQ? > 2) Where is the DLQ defined to synapse/the message processor so that it > knows where to go? > 3) What if the message gets removed from the DLC for some reason (manually > or otherwise)? Do we fail quietly or log it somewhere? > 4) What if other messages from other parts of the ESB get put to the DLQ ? > How does the MessageProcessor know which messages are for it? > > > many thanks for your help ! > john. > > > John Hawkins > Director: Solutions Architecture > > > _______ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Ravindra Ranwala Software Engineer WSO2, Inc: http://wso2.com <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> Mobile: +94714198770 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [VOTE] Release WSO2 ESB 4.9.0 RC2
Hi All, Please find the correct filter for the issues fixed for this release. https://wso2.org/jira/browse/ESBJAVA-4138?filter=12385 Also the correct staging repo can be found here. http://maven.wso2.org/nexus/content/repositories/orgwso2esb-029/ Thanks & Regards, On Wed, Sep 2, 2015 at 10:38 PM, Ravindra Ranwala wrote: > Hi All, > > Please find the correct link to the issues fixed for this release. > > https://wso2.org/jira/secure/ReleaseNote.jspa?projectId=10023&version=11540 > > Thanks & Regards, > > On Wed, Sep 2, 2015 at 10:32 PM, Ravindra Ranwala > wrote: > >> Hi Devs, >> >> WSO2 ESB 4.9.0 RC2 Release Vote >> >> This release fixes the following issues: >> >> https://wso2.org/jira/secure/ReleaseNote.jspa?projectId=10023&version=11540 >> <https://wso2.org/jira/browse/ESBJAVA-4093?filter=12363> >> >> Please download ESB 4.9.0 RC2 and test the functionality and vote. Vote >> will be open for 72 hours or as needed. >> >> *Source & binary distribution files:* >> >> <http://maven.wso2.org/nexus/content/repositories/orgwso2esb-051/org/wso2/esb/wso2esb/4.9.0-RC1/> >> http://maven.wso2.org/nexus/content/repositories/orgwso2esb-029/org/wso2/esb/wso2esb/4.9.0-RC2/ >> >> *Maven staging repository:* >> http://maven.wso2.org/nexus/content/repositories/orgwso2esb-029/ >> <http://maven.wso2.org/nexus/content/repositories/orgwso2esb-051/> >> >> *The tag to be voted upon :* >> https://github.com/wso2/product-esb/tree/esb-parent-4.9.0-RC2 >> <https://github.com/wso2/product-esb/tree/esb-parent-4.9.0-RC1> >> >> >> [ ] Broken - do not release (explain why) >> [ ] Stable - go ahead and release >> >> >> Thanks and Regards, >> ~ WSO2 ESB Team ~ >> >> >> -- >> Ravindra Ranwala >> Software Engineer >> WSO2, Inc: http://wso2.com >> <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> >> Mobile: +94714198770 >> >> > > > -- > Ravindra Ranwala > Software Engineer > WSO2, Inc: http://wso2.com > <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> > Mobile: +94714198770 > > -- Ravindra Ranwala Software Engineer WSO2, Inc: http://wso2.com <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> Mobile: +94714198770 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [VOTE] Release WSO2 ESB 4.9.0 RC2
Hi All, Please find the correct link to the issues fixed for this release. https://wso2.org/jira/secure/ReleaseNote.jspa?projectId=10023&version=11540 Thanks & Regards, On Wed, Sep 2, 2015 at 10:32 PM, Ravindra Ranwala wrote: > Hi Devs, > > WSO2 ESB 4.9.0 RC2 Release Vote > > This release fixes the following issues: > https://wso2.org/jira/secure/ReleaseNote.jspa?projectId=10023&version=11540 > <https://wso2.org/jira/browse/ESBJAVA-4093?filter=12363> > > Please download ESB 4.9.0 RC2 and test the functionality and vote. Vote > will be open for 72 hours or as needed. > > *Source & binary distribution files:* > > <http://maven.wso2.org/nexus/content/repositories/orgwso2esb-051/org/wso2/esb/wso2esb/4.9.0-RC1/> > http://maven.wso2.org/nexus/content/repositories/orgwso2esb-029/org/wso2/esb/wso2esb/4.9.0-RC2/ > > *Maven staging repository:* > http://maven.wso2.org/nexus/content/repositories/orgwso2esb-029/ > <http://maven.wso2.org/nexus/content/repositories/orgwso2esb-051/> > > *The tag to be voted upon :* > https://github.com/wso2/product-esb/tree/esb-parent-4.9.0-RC2 > <https://github.com/wso2/product-esb/tree/esb-parent-4.9.0-RC1> > > > [ ] Broken - do not release (explain why) > [ ] Stable - go ahead and release > > > Thanks and Regards, > ~ WSO2 ESB Team ~ > > > -- > Ravindra Ranwala > Software Engineer > WSO2, Inc: http://wso2.com > <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> > Mobile: +94714198770 > > -- Ravindra Ranwala Software Engineer WSO2, Inc: http://wso2.com <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> Mobile: +94714198770 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [VOTE] Release WSO2 ESB 4.9.0 RC2
Hi Devs, WSO2 ESB 4.9.0 RC2 Release Vote This release fixes the following issues: https://wso2.org/jira/secure/ReleaseNote.jspa?projectId=10023&version=11540 <https://wso2.org/jira/browse/ESBJAVA-4093?filter=12363> Please download ESB 4.9.0 RC2 and test the functionality and vote. Vote will be open for 72 hours or as needed. *Source & binary distribution files:* <http://maven.wso2.org/nexus/content/repositories/orgwso2esb-051/org/wso2/esb/wso2esb/4.9.0-RC1/> http://maven.wso2.org/nexus/content/repositories/orgwso2esb-029/org/wso2/esb/wso2esb/4.9.0-RC2/ *Maven staging repository:* http://maven.wso2.org/nexus/content/repositories/orgwso2esb-029/ <http://maven.wso2.org/nexus/content/repositories/orgwso2esb-051/> *The tag to be voted upon :* https://github.com/wso2/product-esb/tree/esb-parent-4.9.0-RC2 <https://github.com/wso2/product-esb/tree/esb-parent-4.9.0-RC1> [ ] Broken - do not release (explain why) [ ] Stable - go ahead and release Thanks and Regards, ~ WSO2 ESB Team ~ -- Ravindra Ranwala Software Engineer WSO2, Inc: http://wso2.com <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> Mobile: +94714198770 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [VOTE] Release WSO2 ESB 4.9.0 RC1
Hi All, I have tested scenarios [1]. No issues found. [X] Stable - go ahead and release [1] https://docs.google.com/document/d/1UpXN3SJvXOzp5UH6eF0lkO_vXTnvko7ruY5VMs9bDDI/edit Thanks & Regards, On Wed, Aug 26, 2015 at 7:29 AM, Prabath Ariyarathna wrote: > HI All. > > I have tested basic security scenarios on the Java7 and Java8. No issues > found. > [X] Stable - go ahead and release. > > Thanks. > > On Tue, Aug 25, 2015 at 9:20 PM, Viraj Senevirathne > wrote: > >> Hi all, >> >> I have tested VFS inbound and transport use cases for file, ftp and sftp >> protocols. No issues found. >> [X] Stable - go ahead and release >> >> Thanks. >> >> On Tue, Aug 25, 2015 at 8:28 PM, Nadeeshaan Gunasinghe < >> nadeesh...@wso2.com> wrote: >> >>> Hi, >>> >>> I tested JMS use cases and MSMP fail over use cases. No issues found. >>> >>> [X] Stable - go ahead and release >>> >>> Regards. >>> >>> >>> *Nadeeshaan Gunasinghe* >>> Software Engineer, WSO2 Inc. http://wso2.com >>> +94770596754 | nadeesh...@wso2.com | Skype: nadeeshaan.gunasinghe >>> <#14f67bb67ffa1168_14f658e48984972a_14f655ebf8b0b7e4_> >>> <http://www.facebook.com/nadeeshaan.gunasinghe> >>> <http://lk.linkedin.com/in/nadeeshaan> <http://twitter.com/Nadeeshaan> >>> <http://nadeeshaan.blogspot.com/> >>> Get a signature like this: Click here! >>> <http://ws-promos.appspot.com/r?rdata=eyJydXJsIjogImh0dHA6Ly93d3cud2lzZXN0YW1wLmNvbS9lbWFpbC1pbnN0YWxsP3dzX25jaWQ9NjcyMjk0MDA4JnV0bV9zb3VyY2U9ZXh0ZW5zaW9uJnV0bV9tZWRpdW09ZW1haWwmdXRtX2NhbXBhaWduPXByb21vXzU3MzI1Njg1NDg3Njk3OTIiLCAiZSI6ICI1NzMyNTY4NTQ4NzY5NzkyIn0=> >>> >>> On Tue, Aug 25, 2015 at 6:01 PM, Jagath Sisirakumara Ariyarathne < >>> jaga...@wso2.com> wrote: >>> >>>> Hi, >>>> >>>> I executed performance tests for basic scenarios with this pack. No >>>> issues observed. >>>> >>>> [X] Stable - go ahead and release >>>> >>>> Thanks. >>>> >>>> On Mon, Aug 24, 2015 at 10:27 PM, Chanaka Fernando >>>> wrote: >>>> >>>>> Hi Devs, >>>>> >>>>> WSO2 ESB 4.9.0 RC1 Release Vote >>>>> >>>>> This release fixes the following issues: >>>>> https://wso2.org/jira/browse/ESBJAVA-4093?filter=12363 >>>>> >>>>> Please download ESB 490 RC1 and test the functionality and vote. Vote >>>>> will be open for 72 hours or as needed. >>>>> >>>>> *Source & binary distribution files:* >>>>> >>>>> http://maven.wso2.org/nexus/content/repositories/orgwso2esb-051/org/wso2/esb/wso2esb/4.9.0-RC1/ >>>>> >>>>> *Maven staging repository:* >>>>> http://maven.wso2.org/nexus/content/repositories/orgwso2esb-051/ >>>>> >>>>> *The tag to be voted upon :* >>>>> https://github.com/wso2/product-esb/tree/esb-parent-4.9.0-RC1 >>>>> >>>>> >>>>> [ ] Broken - do not release (explain why) >>>>> [ ] Stable - go ahead and release >>>>> >>>>> >>>>> Thanks and Regards, >>>>> ~ WSO2 ESB Team ~ >>>>> >>>>> -- >>>>> -- >>>>> Chanaka Fernando >>>>> Senior Technical Lead >>>>> WSO2, Inc.; http://wso2.com >>>>> lean.enterprise.middleware >>>>> >>>>> mobile: +94 773337238 >>>>> Blog : http://soatutorials.blogspot.com >>>>> LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0 >>>>> Twitter:https://twitter.com/chanakaudaya >>>>> Wordpress:http://chanakaudaya.wordpress.com >>>>> >>>>> >>>>> >>>>> >>>>> ___ >>>>> Dev mailing list >>>>> Dev@wso2.org >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> Jagath Ariyarathne >>>> Technical Lead >>>> WSO2 Inc. http://wso2.com/ >>>> Email: jaga...@wso2.com >>>> Mob : +94 77 386 7048 >>>> >>>> >>>> ___ >>>> Dev mailing list >>>> Dev@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> Viraj Senevirathne >> Software Engineer; WSO2, Inc. >> >> Mobile : +94 71 818 4742 <%2B94%20%280%29%20773%20451194> >> Email : vir...@wso2.com >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > > *Prabath Ariyarathna* > > *Associate Technical Lead* > > *WSO2, Inc. * > > *lean . enterprise . middleware * > > > *Email: prabat...@wso2.com * > > *Blog: http://prabu-lk.blogspot.com <http://prabu-lk.blogspot.com>* > > *Flicker : https://www.flickr.com/photos/47759189@N08 > <https://www.flickr.com/photos/47759189@N08>* > > *Mobile: +94 77 699 4730 * > > > > > > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Ravindra Ranwala Software Engineer WSO2, Inc: http://wso2.com <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> Mobile: +94714198770 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Build failure when running mvn release:rollback
Hi Jagath, I tried with release plugin 2.3.2 as stated in [1], and that worked for me. [1] http://stackoverflow.com/questions/15166781/mvn-releaseprepare-not-committing-changes-to-pom-xml Thanks & Regards, On Fri, Aug 21, 2015 at 12:55 AM, Jagath Sisirakumara Ariyarathne < jaga...@wso2.com> wrote: > Hi, > > We encountered below failure when running "mvn release:rollback" after > running a successful dry run of release preparation. Full console output > is attached. Any help to resolve this? > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-release-plugin:2.5.1:rollback (default-cli) > on project esb-parent: Unable to commit files > [ERROR] Provider message: > [ERROR] The git-commit command failed. > [ERROR] Command output: > [ERROR] -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > goal org.apache.maven.plugins:maven-release-plugin:2.5.1:rollback > (default-cli) on project esb-parent: Unable to commit files > Provider message: > The git-commit command failed. > ... > > Caused by: org.apache.maven.plugin.MojoFailureException: Unable to commit > files > Provider message: > The git-commit command failed. > Command output: > > at > org.apache.maven.plugins.release.RollbackReleaseMojo.execute(RollbackReleaseMojo.java:63) > . > Caused by: org.apache.maven.shared.release.scm.ReleaseScmCommandException: > Unable to commit files > Provider message: > The git-commit command failed. > Command output: > > at > org.apache.maven.shared.release.phase.AbstractScmCommitPhase.checkin(AbstractScmCommitPhase.java:165) > at > org.apache.maven.shared.release.phase.AbstractScmCommitPhase.performCheckins(AbstractScmCommitPhase.java:145) > > > Thanks. > > -- > Jagath Ariyarathne > Technical Lead > WSO2 Inc. http://wso2.com/ > Email: jaga...@wso2.com > Mob : +94 77 386 7048 > > -- Ravindra Ranwala Software Engineer WSO2, Inc: http://wso2.com <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> Mobile: +94714198770 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Committers += ​Kalpa Welivitigoda
Congratulations Kalpa ! On Tue, Aug 18, 2015 at 11:55 AM, Madhawa Gunasekara wrote: > Congratulations kalpa > > On Tue, Aug 18, 2015 at 11:38 AM, Aruna Karunarathna > wrote: > >> Congratzz Kalpa...!!! >> >> On Tue, Aug 18, 2015 at 11:35 AM, Supun Malinga wrote: >> >>> Congrats Kalpa! Keep up the good work..! >>> >>> On Tue, Aug 18, 2015 at 11:31 AM, KasunG Gajasinghe >>> wrote: >>> >>>> >>>> Congratulations Kalpa! A well deserved one! :-) >>>> >>>> On Tue, Aug 18, 2015 at 10:29 AM, Sameera Perera >>>> wrote: >>>> >>>>> Hi, >>>>> >>>>> It is with great pleasure we welcome ​Kalpa Welivitigoda​ as a WSO2 >>>>> Committer. >>>>> @Kalpa, congratulations and keep up the good work! >>>>> >>>>> -- >>>>> >>>>> -- >>>>> >>>>> *Sameera Perera* >>>>> Director of Engineering >>>>> gtalk: samee...@wso2.com >>>>> Tel : 94 11 214 5345 >>>>> Fax :94 11 2145300 >>>>> *WSO2, Inc.* <http://wso2.com/> >>>>> lean.enterprise.middleware >>>>> >>>>> >>>>> >>>>> ___ >>>>> Dev mailing list >>>>> Dev@wso2.org >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> >>>> *Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc. >>>> email: kasung AT spamfree wso2.com >>>> linked-in: http://lk.linkedin.com/in/gajasinghe >>>> blog: http://kasunbg.org >>>> >>>> >>>> >>>> ___ >>>> Dev mailing list >>>> Dev@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> Supun Malinga, >>> >>> Senior Software Engineer, >>> WSO2 Inc. >>> http://wso2.com >>> email: sup...@wso2.com >>> mobile: +94 (0)71 56 91 321 >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> >> *Aruna Sujith Karunarathna *| Software Engineer >> WSO2, Inc | lean. enterprise. middleware. >> #20, Palm Grove, Colombo 03, Sri Lanka >> Mobile: +94 71 9040362 | Work: +94 112145345 >> Email: ar...@wso2.com | Web: www.wso2.com >> >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > *Madhawa Gunasekara* > Software Engineer > WSO2 Inc.; http://wso2.com > lean.enterprise.middleware > > mobile: +94 719411002 <+94+719411002> > blog: *http://madhawa-gunasekara.blogspot.com > <http://madhawa-gunasekara.blogspot.com>* > linkedin: *http://lk.linkedin.com/in/mgunasekara > <http://lk.linkedin.com/in/mgunasekara>* > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Ravindra Ranwala Software Engineer WSO2, Inc: http://wso2.com <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> Mobile: +94714198770 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Next carbon-deployment release is 4.5.0
Hi KasunG, I have tested module-mgt feature for ESB and that was working as expected. Thanks & Regards, On Tue, Aug 18, 2015 at 3:59 PM, KasunG Gajasinghe wrote: > [+Krishantha] > > New staging repo with fixes for module-mgt and AS application mgt - > http://maven.wso2.org/nexus/content/repositories/orgwso2carbondeployment-032/ > > > On Tue, Aug 18, 2015 at 12:53 AM, KasunG Gajasinghe > wrote: > >> >> carbon-deployment is has been added to staging repo - >> http://maven.wso2.org/nexus/content/repositories/orgwso2carbondeployment-030/ >> >> Please use this repo and verify the downstream projects. Planning to >> promote the staging repo to public by EOD Tuesday. >> >> Thanks >> >> >> >> On Fri, Aug 14, 2015 at 1:45 PM, Priyadarssini Kishokumar < >> priyadarss...@wso2.com> wrote: >> >>> Thanks. >>> >>> On Fri, Aug 14, 2015 at 1:44 PM, KasunG Gajasinghe >>> wrote: >>> >>>> Merged. >>>> >>>> On Fri, Aug 14, 2015 at 11:02 AM, Priyadarssini Kishokumar < >>>> priyadarss...@wso2.com> wrote: >>>> >>>>> Hi, >>>>> >>>>> Please verify & merge PR[1] for the improvement [2] >>>>> >>>>> [1] https://github.com/wso2/carbon-deployment/pull/104 >>>>> >>>>> [2] https://wso2.org/jira/browse/ESBJAVA-3858 >>>>> >>>>> Thanks, >>>>> >>>>> On Thu, Aug 13, 2015 at 2:47 PM, KasunG Gajasinghe >>>>> wrote: >>>>> >>>>>> >>>>>> The release date is this Friday. So, make sure to send all the >>>>>> fixes if any EOD today. >>>>>> >>>>>> Thanks. >>>>>> >>>>>> On Tue, Aug 11, 2015 at 6:40 PM, KasunG Gajasinghe >>>>>> wrote: >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> This is to update that the next carbon-deployment release is 4.5.0. >>>>>>> >>>>>>> AS will need a Jaggery release on top of carbon-deployment 4.5.0 for >>>>>>> the AS 5.3.0 beta release. >>>>>>> >>>>>>> Thanks, >>>>>>> KasunG >>>>>>> >>>>>>> -- >>>>>>> >>>>>>> *Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc. >>>>>>> email: kasung AT spamfree wso2.com >>>>>>> linked-in: http://lk.linkedin.com/in/gajasinghe >>>>>>> blog: http://kasunbg.org >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> >>>>>> *Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc. >>>>>> email: kasung AT spamfree wso2.com >>>>>> linked-in: http://lk.linkedin.com/in/gajasinghe >>>>>> blog: http://kasunbg.org >>>>>> >>>>>> >>>>>> >>>>>> ___ >>>>>> Dev mailing list >>>>>> Dev@wso2.org >>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Priya Kishok >>>>> Software Engineer >>>>> WSO2, Inc : http://wso2.com >>>>> Mob : +94774457404 >>>>> >>>> >>>> >>>> >>>> -- >>>> >>>> *Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc. >>>> email: kasung AT spamfree wso2.com >>>> linked-in: http://lk.linkedin.com/in/gajasinghe >>>> blog: http://kasunbg.org >>>> >>>> >>>> >>> >>> >>> >>> -- >>> Priya Kishok >>> Software Engineer >>> WSO2, Inc : http://wso2.com >>> Mob : +94774457404 >>> >> >> >> >> -- >> >> *Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc. >> email: kasung AT spamfree wso2.com >> linked-in: http://lk.linkedin.com/in/gajasinghe >> blog: http://kasunbg.org >> >> >> > > > > -- > > *Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc. > email: kasung AT spamfree wso2.com > linked-in: http://lk.linkedin.com/in/gajasinghe > blog: http://kasunbg.org > > > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Ravindra Ranwala Software Engineer WSO2, Inc: http://wso2.com <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> Mobile: +94714198770 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] carbon-mediation 4.4.3 Released !
Hi All, org.wso2.carbon.mediation version 4.4.3 was released. org.wso2.carbon.mediation carbon-mediation 4.4.3 Thanks & Regards, -- Ravindra Ranwala Software Engineer WSO2, Inc: http://wso2.com <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> Mobile: +94714198770 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Wso2-commons-vfs 2.0-wso2v11 Released !
Hi All, Wso2-commons-vfs version 2.0-wso2v11 Released. org.apache.commons commons-vfs2-project 2.0-wso2v11 Thanks & Regards, -- Ravindra Ranwala Software Engineer WSO2, Inc: http://wso2.com <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> Mobile: +94714198770 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] DepSync failure in ESB 4.9.0
nizerServiceImpl.java:97) >>> ... 9 more >>> [2015-08-03 12:05:42,235] INFO - NioSelectorPool Using a shared >>> selector for servlet write/read >>> [2015-08-03 12:05:42,342] INFO - TaskServiceImpl Task service starting >>> in CLUSTERED mode... >>> [2015-08-03 12:05:42,384] INFO - NTaskTaskManager Initialized task >>> manager on manager node. Tenant [-1234] >>> [2015-08-03 12:05:42,399] INFO - RegistryEventingServiceComponent >>> Successfully Initialized Eventing on Registry >>> [2015-08-03 12:05:42,487] INFO - JMXServerManager JMX Service URL : >>> service:jmx:rmi://localhost:2/jndi/rmi://localhost:1/jmxrmi >>> [2015-08-03 12:05:42,488] INFO - StartupFinalizerServiceComponent >>> Server : WSO2 Enterprise Service Bus-4.9.0 >>> [2015-08-03 12:05:42,488] INFO - StartupFinalizerServiceComponent WSO2 >>> Carbon started in 36 sec >>> [2015-08-03 12:05:42,749] INFO - CarbonUIServiceComponent Mgt Console >>> URL : https://mgt.esb.wso2.com:9444/carbon/ >>> [2015-08-03 12:05:57,216] ERROR - CarbonDeploymentSchedulerTask >>> Deployment synchronization update for tenant -1234 failed >>> java.lang.RuntimeException: >>> org.wso2.carbon.deployment.synchronizer.DeploymentSynchronizerException: No >>> Repository found for type svn >>> at >>> org.wso2.carbon.deployment.synchronizer.internal.DeploymentSynchronizerServiceImpl.update(DeploymentSynchronizerServiceImpl.java:90) >>> at >>> org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.deploymentSyncUpdate(CarbonDeploymentSchedulerTask.java:179) >>> at >>> org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.run(CarbonDeploymentSchedulerTask.java:137) >>> at >>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) >>> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:309) >>> at >>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) >>> at >>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) >>> at >>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1143) >>> at >>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:618) >>> at java.lang.Thread.run(Thread.java:785) >>> Caused by: >>> org.wso2.carbon.deployment.synchronizer.DeploymentSynchronizerException: No >>> Repository found for type svn >>> at >>> org.wso2.carbon.deployment.synchronizer.repository.CarbonRepositoryUtils.getDeploymentSyncConfigurationFromConf(CarbonRepositoryUtils.java:167) >>> at >>> org.wso2.carbon.deployment.synchronizer.repository.CarbonRepositoryUtils.getActiveSynchronizerConfiguration(CarbonRepositoryUtils.java:97) >>> at >>> org.wso2.carbon.deployment.synchronizer.internal.DeploymentSynchronizerServiceImpl.update(DeploymentSynchronizerServiceImpl.java:61) >>> ... 9 more >>> [2015-08-03 12:05:57,219] ERROR - CarbonDeploymentSchedulerTask >>> Deployment synchronization commit for tenant -1234 failed >>> java.lang.RuntimeException: >>> org.wso2.carbon.deployment.synchronizer.DeploymentSynchronizerException: No >>> Repository found for type svn >>> at >>> org.wso2.carbon.deployment.synchronizer.internal.DeploymentSynchronizerServiceImpl.commit(DeploymentSynchronizerServiceImpl.java:117) >>> at >>> org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.deploymentSyncCommit(CarbonDeploymentSchedulerTask.java:298) >>> at >>> org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.run(CarbonDeploymentSchedulerTask.java:142) >>> at >>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) >>> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:309) >>> at >>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) >>> at >>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) >>> at >>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1143) >>> at >>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:618) >>> at java.lang.Thread.run(Thread.java:785) >>> Caused by: >>> org.wso2.carbon.deployment.synchronizer.DeploymentSynchronizerException: No >>> Repository found for type svn >>> at >>> org.wso2.carbon.deployment.synchronizer.repository.CarbonRepositoryUtils.getDeploymentSyncConfigurationFromConf(CarbonRepositoryUtils.java:167) >>> at >>> org.wso2.carbon.deployment.synchronizer.repository.CarbonRepositoryUtils.getActiveSynchronizerConfiguration(CarbonRepositoryUtils.java:97) >>> at >>> org.wso2.carbon.deployment.synchronizer.internal.DeploymentSynchronizerServiceImpl.commit(DeploymentSynchronizerServiceImpl.java:97) >>> ... 9 more >>> >>> >>> >>> >> >> >> -- >> -- >> Chanaka Fernando >> Senior Technical Lead >> WSO2, Inc.; http://wso2.com >> lean.enterprise.middleware >> >> mobile: +94 773337238 >> Blog : http://soatutorials.blogspot.com >> LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0 >> Twitter:https://twitter.com/chanakaudaya >> Wordpress:http://chanakaudaya.wordpress.com >> >> >> >> > > > -- > > *Aruna Sujith Karunarathna *| Software Engineer > WSO2, Inc | lean. enterprise. middleware. > #20, Palm Grove, Colombo 03, Sri Lanka > Mobile: +94 71 9040362 | Work: +94 112145345 > Email: ar...@wso2.com | Web: www.wso2.com > > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Ravindra Ranwala Software Engineer WSO2, Inc: http://wso2.com <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> Mobile: +94714198770 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Testing Kafka Inbound in ESB cluster mode.
Hi Kathees, I'm not sure which ESB pack are you using. Anyway the M8 pack [1] was working fine for me. Could you please try that out and let us know. [1] https://svn.wso2.org/repos/wso2/people/chanakaf/Alpha-Release/ Thanks & Regards, On Mon, Apr 6, 2015 at 2:53 PM, Chanaka Fernando wrote: > Hi Kathees, > > Can you setup a cluster without ELB and check on that? > > Thanks, > Chanaka > > On Mon, Apr 6, 2015 at 2:50 PM, Kathees Rajendram > wrote: > >> Hi Chanaka,Ravindra, >> >> I have the setup with a elb,a manager node and a worker node. As Chanaka >> mentioned I changed taskServerCount parameter value to 1 in both manager >> and worker node. Still I am getting the same error in both manager and >> worker node. >> >> Thanks, >> Kathees >> >> On Mon, Apr 6, 2015 at 2:24 PM, Chanaka Fernando >> wrote: >> >>> [Adding Kathees] >>> >>> On Mon, Apr 6, 2015 at 2:23 PM, Ravindra Ranwala >>> wrote: >>> >>>> Hi Chanaka, >>>> >>>> Yes, I have encountered with this error while I was testing MSMP tasks >>>> in cluster mode. It was an intermittent issue. >>>> >>>> @Kathees: Could you please restart the manager node again and make sure >>>> that you have started one or more workers in the meantime as Chanaka >>>> mentioned. AFAIK, manager node collects them as pending tasks and schedules >>>> later once workers joined the cluster. >>>> >>>> >>>> >>>> Thanks & Regards, >>>> >>>> On Mon, Apr 6, 2015 at 2:12 PM, Chanaka Fernando >>>> wrote: >>>> >>>>> Hi Ravindra/Maheeka, >>>>> >>>>> Have you observed such an issue when you were testing tasks in cluster >>>>> mode? >>>>> >>>>> Thanks, >>>>> Chanaka >>>>> >>>>> -- Forwarded message -- >>>>> From: Chanaka Fernando >>>>> Date: Mon, Apr 6, 2015 at 1:42 PM >>>>> Subject: Re: Testing Kafka Inbound in ESB cluster mode. >>>>> To: Kathees Rajendram >>>>> Cc: DEV , Kasun Indrasiri >>>>> >>>>> >>>>> Hi Kathees, >>>>> >>>>> Have you started the worker nodes? By theory, Tasks are running on >>>>> worker nodes. You need to have at least 1 worker node to start executing >>>>> the tasks. Also there is another configuration file which controls the >>>>> minimum number of instances to start executing the tasks. This can be >>>>> configured in the *ESB_HOME/repository/conf/etc/tasks-config.xml* >>>>> file with the below parameter. >>>>> >>>>> 2 >>>>> >>>>> The value of 2 means that cluster will wait until 2 worker nodes are >>>>> started for the execution of tasks. >>>>> >>>>> Thanks, >>>>> Chanaka >>>>> >>>>> On Mon, Apr 6, 2015 at 12:49 PM, Kathees Rajendram >>>>> wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> I tested Kafka inbound in esb cluster mode. I have added required >>>>>> patches and inbound configuration in manager node. When I start the >>>>>> manger >>>>>> node I am getting following error. >>>>>> >>>>>> Am I missing anything? >>>>>> >>>>>> [2015-04-06 12:32:55,977] INFO - NTaskTaskManager Initialized task >>>>>> manager on manager node. Tenant [-1234] >>>>>> [2015-04-06 12:32:56,089] ERROR - NTaskTaskManager Scheduling task >>>>>> [[NTask::-1234::MyKAFKAListenerEP-KAFKA-EP]::KAFKA-EP] FAILED. Error: No >>>>>> available task nodes for resolving a task location >>>>>> org.wso2.carbon.ntask.common.TaskException: No available task nodes >>>>>> for resolving a task location >>>>>> at >>>>>> org.wso2.carbon.ntask.core.impl.clustered.ClusteredTaskManager.getTaskLocation(ClusteredTaskManager.java:224) >>>>>> at >>>>>> org.wso2.carbon.ntask.core.impl.clustered.ClusteredTaskManager.locateMemberForTask(ClusteredTaskManager.java:201) >>>>>> at >>>>>> org.wso2.carbon.ntask.core.impl.clustered.ClusteredTaskManager.getMemberIdFromTaskName(Clustere
Re: [Dev] Testing Kafka Inbound in ESB cluster mode.
t; org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771) >> at >> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130) >> at >> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214) >> at >> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433) >> at >> org.eclipse.equinox.http.servlet.internal.Activator.registerHttpService(Activator.java:81) >> at >> org.eclipse.equinox.http.servlet.internal.Activator.addProxyServlet(Activator.java:60) >> at >> org.eclipse.equinox.http.servlet.internal.ProxyServlet.init(ProxyServlet.java:40) >> at >> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.init(DelegationServlet.java:38) >> at >> org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1279) >> at >> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1192) >> at >> org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1087) >> at >> org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5210) >> at >> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5493) >> at >> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) >> at >> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559) >> at >> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549) >> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) >> at java.util.concurrent.FutureTask.run(FutureTask.java:138) >> at >> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) >> at >> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) >> at java.lang.Thread.run(Thread.java:662) >> >> >> Thanks, >> Kathees >> >> -- >> Kathees >> Software Engineer, >> email: kath...@wso2.com >> mobile: +94772596173 >> > > > > -- > -- > Chanaka Fernando > Technical Lead > WSO2, Inc.; http://wso2.com > lean.enterprise.middleware > > mobile: +94 773337238 > Blog : http://soatutorials.blogspot.com > LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0 > Twitter:https://twitter.com/chanakaudaya > Wordpress:http://chanakaudaya.wordpress.com > > > > > > > -- > -- > Chanaka Fernando > Technical Lead > WSO2, Inc.; http://wso2.com > lean.enterprise.middleware > > mobile: +94 773337238 > Blog : http://soatutorials.blogspot.com > LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0 > Twitter:https://twitter.com/chanakaudaya > Wordpress:http://chanakaudaya.wordpress.com > > > > -- Ravindra Ranwala Software Engineer WSO2, Inc: http://wso2.com <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> Mobile: +94714198770 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Sending an Arraylist using a SOAP mesage
Hi Pubudu,
Could you please try to send it as an array of Objects instead of an Array
list.
Thanks & Regards,
On Wed, Mar 18, 2015 at 11:36 AM, Pubudu Dodangoda wrote:
> How can I perform $subject ?
>
> I can send other data(string, int, objects etc)
> But when I try to send an Arraylist, I get the following value at the
> debugger
>
> {OMElementmpl@10789}"http://data.admin.dashboard.analytics.carbon.wso2.org/xsd";>my
> role"
>
> this is the soap message I sent
>
> http://schemas.xmlsoap.org/soap/envelope/";
> xmlns:adm="http://admin.dashboard.analytics.carbon.wso2.org"; xmlns:xsd="
> http://data.admin.dashboard.analytics.carbon.wso2.org/xsd";>
>
>
>
>
> myId
> my role
> my role2
>
>
>
>
>
> Thank You and kind Regards
> --
> Pubudu Dodangoda
> BSc Engineering(Hon's) Undergraduate
> Department of Computer Science Engineering
> University of Moratuwa
> 0716053681 / 0775192994
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
--
Ravindra Ranwala
Software Engineer
WSO2, Inc: http://wso2.com
<http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg>
Mobile: +94714198770
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Committers += Dinesh J Weerakkody
Congratulations Dinesh ! On Thu, Mar 12, 2015 at 8:30 AM, Chamalee De Silva wrote: > congrats! > > On Thu, Mar 12, 2015 at 8:24 AM, Abimaran Kugathasan > wrote: > >> Congrats! >> >> On Thu, Mar 12, 2015 at 8:17 AM, Nuwan Dias wrote: >> >>> Hi, >>> >>> It is with great pleasure we welcome DineshW as a WSO2 Committer. >>> @Dinesh, congratulations and keep up the good work! >>> >>> Thanks, >>> NuwanD. >>> >>> -- >>> Nuwan Dias >>> >>> Associate Tech Lead - WSO2, Inc. http://wso2.com >>> email : nuw...@wso2.com >>> Phone : +94 777 775 729 >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> Thanks >> Abimaran Kugathasan >> >> Software Engineer | WSO2 Inc >> Data & APIs Technologies Team >> Mobile : +94 773922820 >> >> <http://stackoverflow.com/users/515034> >> <http://lk.linkedin.com/in/abimaran> >> <http://www.lkabimaran.blogspot.com/> <https://github.com/abimaran> >> <https://twitter.com/abimaran> >> >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > > Chamalee De Silva > > Software Engineer | WSO2 > > E:chama...@wso2.com > M :0711540738| http://wso2.com <http://wso2.com/> > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Ravindra Ranwala Software Engineer WSO2, Inc: http://wso2.com <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> Mobile: +94714198770 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] NTask coordination issue while cleaning up a Task
Hi Malaka, We are closing the JMS connection from the message processor indeed. But the user deactivates it via manager nodes web interface, hence the deactivate method executes in the manager node. But there the JMS connection is null and nothing to close. The JMS connection is created in the worker node which is responsible to serve requests. This JMS connection is not getting closed once the deactivation is done via manager nodes ui. Thanks & Regards, On Sat, Feb 28, 2015 at 10:58 PM, Malaka Silva wrote: > Hi Ravindra, > > The deactivation happens from Message Processor. User won't be > deactivating the task. > > Can't we close the connection at MP level rather than Task level? > > > On Sat, Feb 28, 2015 at 3:16 PM, Anjana Fernando wrote: > >> Hi Ravindra, >> >> As I mentioned in our earlier f2f chat also, there is no such listener >> mechanism supported in ntask, even though it is supported in Quartz, for >> local servers. NTask has a very specific set of features, for distributed >> task scheduling, nothing else. And your requirement wasn't one of them. So >> we may consider implementing it in the future if it makes sense for >> multiple users of the feature, but not now, specially not in a hurry. >> Because we have to carefully check the usage and implement/test it >> properly. So for now at least, implement your scenario using cluster >> messaging, by notifying the required nodes of the state change. >> >> Cheers, >> Anjana. >> >> On Fri, Feb 27, 2015 at 5:57 PM, Ravindra Ranwala >> wrote: >> >>> >>> Hi Anjana, >>> >>> Currently we are implementing Message store - Message processor >>> coordination support for ESB in worker-manager cluster mode. When a task is >>> deactivated some housekeeping work needs to be done. For an example >>> cleaning up JMS consumers etc. Quartz supports several types of Listeners >>> which can be registered to get the notifications. But we could not see such >>> a listener in our ntask core implementation. An example scenario which >>> emphasizes this requirement is given below. >>> >>> >>> Suppose that the cluster has one manager and two worker nodes at the >>> moment where one message processor is running in one worker. This task is >>> having a JMS connection in order to consume JMS messages from a queue. When >>> the deactivation occurs in the manager node, the JMS connection is not >>> teared off properly in all worker nodes where it runs. Even Though the task >>> is deactivated this shows that there is one JMS consumer for the queue and >>> which is not the expected behaviour. Is there any support/hook in your >>> platform to get this done. >>> >>> >>> >>> >>> >>> Thanks & Regards, >>> -- >>> Ravindra Ranwala >>> Software Engineer >>> WSO2, Inc: http://wso2.com >>> <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> >>> Mobile: +94714198770 >>> >>> >> >> >> -- >> *Anjana Fernando* >> Senior Technical Lead >> WSO2 Inc. | http://wso2.com >> lean . enterprise . middleware >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > > 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/> > > Save a tree -Conserve nature & Save the world for your future. Print this > email only if it is absolutely necessary. > -- Ravindra Ranwala Software Engineer WSO2, Inc: http://wso2.com <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> Mobile: +94714198770 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] NTask coordination issue while cleaning up a Task
Hi Anjana, Currently we are implementing Message store - Message processor coordination support for ESB in worker-manager cluster mode. When a task is deactivated some housekeeping work needs to be done. For an example cleaning up JMS consumers etc. Quartz supports several types of Listeners which can be registered to get the notifications. But we could not see such a listener in our ntask core implementation. An example scenario which emphasizes this requirement is given below. Suppose that the cluster has one manager and two worker nodes at the moment where one message processor is running in one worker. This task is having a JMS connection in order to consume JMS messages from a queue. When the deactivation occurs in the manager node, the JMS connection is not teared off properly in all worker nodes where it runs. Even Though the task is deactivated this shows that there is one JMS consumer for the queue and which is not the expected behaviour. Is there any support/hook in your platform to get this done. Thanks & Regards, -- Ravindra Ranwala Software Engineer WSO2, Inc: http://wso2.com <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> Mobile: +94714198770 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 ESB Message processor activation from management console
Hi All, Currently when the Message Processor states are changed via ESB management console in a cluster mode, the states are synchronized using the dep-sync mechanism. Automatic deactivation is the only scenario where the dep-sync is not used to synchronize the states of the message processor across the worker nodes of the cluster. If we are avoiding dep-sync, we need to have an event based support in ntask core (platform) so that we can subscribe to state transition events of a given task. The other alternative is to have a Polling based scheme, which will be a costly solution and consumes more CPU cycles. AFAIK, currently there is no such an event driven support in ntask core and what we have is a polling based scheme. @Anjana: Could you please let us know whether this is feasible. Thanks & Regards, On Wed, Feb 18, 2015 at 3:22 PM, Chanaka Fernando wrote: > Hi All, > > We are currently revamping the Message Processor implementation to provide > coordination support in a clustered environment using ntask implementation. > During this process we are planning to resolve a long running issue in the > Message Processor usage. The issue is that, when we deploy a Message > processor in the ESB and try to change the status (activate/deactivate), it > will change the xml file and persist that state in to that file. This > behavior causing issues when we deploy MP using a CAR file since it does > not deploy the xml file in to deployment directory by default. When this > happens, if we change the MP from management console, it will save the xml > and throw errors when restarting the server and the status is not persisted. > > Our initial plan was to not persist the active/deactive state in the file > but keep that state in the memory. When a user change the status from the > management console, it will not persist in the xml file but change the > status in the memory and MP will change the status accordingly. The > drawback with this model is that we cannot persist the state of the MP > (which we have changed) after a server restart. > > Another option is to check whether the artifact is coming from a CAR file > or not and persist the state only if it is not coming from a CAR file. But > even with this approach, we can only persist the state of the processor for > artifacts which are not deployed from the CAR file. > > Given the above options, I think the first option is more consistent since > it would not behave differently for artifacts coming from different paths. > The drawback with that is we can't persist the state of the MP (which has > changed during the server runtime) after server restart. If some user needs > to persist the status, he may need to change the CAR file with the desired > state. > > Any suggestions would be welcomed. > > > Thanks, > Chanaka > > -- > -- > Chanaka Fernando > Technical Lead > WSO2, Inc.; http://wso2.com > lean.enterprise.middleware > > mobile: +94 773337238 > Blog : http://soatutorials.blogspot.com > LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0 > Twitter:https://twitter.com/chanakaudaya > Wordpress:http://chanakaudaya.wordpress.com > > > > -- Ravindra Ranwala Software Engineer WSO2, Inc: http://wso2.com <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> Mobile: +94714198770 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Tenant loading with coordination="false" inbound endpoints
Hi Malaka, How about using an Observer, which will then be notified when the tenant needs to be loaded. Thanks & Regards, On Tue, Feb 17, 2015 at 10:00 PM, Malaka Silva wrote: > Hi, > > In polling inbound with coordination="true" tenant is loaded when the > ntask is executed. (at adapter level) > > However when coordination="false" we will not be using ntask. It'll run as > a background thread. > > So we need some way to load the tenant in this case. > > One way is to have a dummy task and schedule it with different > dispatchers. Same is done for MSMP with coordination. This task is just to > load tenants. > @Ravindra & Priyadarshini Can you give some info onthis how this was done? > > Any other way to address this issue? > > 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/> > > Save a tree -Conserve nature & Save the world for your future. Print this > email only if it is absolutely necessary. > -- Ravindra Ranwala Software Engineer WSO2, Inc: http://wso2.com <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> Mobile: +94714198770 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Find running tasks in a worker-manager cluster via nTask component
Hi All, I am implementing Message Store/Message Processor coordination support [1] in a worker-manager cluster mode. I used nTask task manager to manipulate the cluster. The nTask task manager contains methods (getRunningTaskList. isTaskRunning, getRunningTaskCount) to get the running tasks. But instead of returning the number of currently running tasks, these methods return all the tasks available in task repository. Also after analyzing and debugging the code I noted that you have made a check in all these methods as below. taskManager.getTaskState(name) .equals(org.wso2.carbon.ntask.core.TaskManager.TaskState.NORMAL) Due to this bug, the number of running tasks could not be calculated in the cluster and has become a blocker to this implementation. Any help would be appreciated. [1] https://redmine.wso2.com/issues/2923 Thanks & Regards, -- Ravindra Ranwala Software Engineer WSO2, Inc: http://wso2.com <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> Mobile: +94714198770 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Committers += Tharindu Edirisinghe
>>>>>>>>>>> Dev mailing list >>>>>>>>>>> Dev@wso2.org >>>>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> ___ >>>>>>>>>> Dev mailing list >>>>>>>>>> Dev@wso2.org >>>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Buddhima Wijeweera >>>>>>>>> Software Engineer; WSO2 Inc.; http://wso2.com , >>>>>>>>> >>>>>>>>> Mobile: +94 71 427 9966 >>>>>>>>> Email: buddh...@wso2.com >>>>>>>>> Blog: https://buddhimawijeweera.wordpress.com >>>>>>>>> GitHub Profile: https://github.com/Buddhima >>>>>>>>> >>>>>>>>> ___ >>>>>>>>> Dev mailing list >>>>>>>>> Dev@wso2.org >>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Vijitha Ekanayake >>>>>>>> Software Engineer*, *WSO2, Inc.; http://wso2.com/ >>>>>>>> Mobile : +94 777 24 73 39 | +94 718 74 44 08 >>>>>>>> lean.enterprise.middleware >>>>>>>> >>>>>>>> ___ >>>>>>>> Dev mailing list >>>>>>>> Dev@wso2.org >>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> *Chamin Nalinda* >>>>>>> >>>>>>> Intern - Engineering >>>>>>> WSO2 Inc. http://www.wso2.com >>>>>>> lean.enterprise.middleware >>>>>>> >>>>>>> Mobile: (+94) 77 241 66 04 >>>>>>> Linkedin: https://www.linkedin.com/in/chaminnalinda >>>>>>> Web: http://www.ckreativity.com >>>>>>> Blog: http://techspiro.blogspot.com/ >>>>>>> >>>>>>> >>>>>>> ___ >>>>>>> Dev mailing list >>>>>>> Dev@wso2.org >>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>> >>>>>>> >>>>>> ___ >>>>>> Dev mailing list >>>>>> Dev@wso2.org >>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Pumudu Ruhunage >>>>> Associate Software Engineer | WSO2 Inc >>>>> M: +94 779 664493 | http://wso2.com >>>>> >>>>> ___ >>>>> Dev mailing list >>>>> Dev@wso2.org >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> Thanks & Regards >>>> -- >>>> Srisunmugaraja Paraparan >>>> Software Engineer, >>>> WSO2 Inc. - lean . enterprise . middleware | wso2.com >>>> >>>> email : parapa...@wso2.com, mobile : +94 77 0362151 >>>> >>>> ___ >>>> Dev mailing list >>>> Dev@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> -- >>> Sithumini Senevirathne >>> Software Engineer >>> WSO2 Inc. - lean . enterprise . middleware | wso2.com >>> >>> email: sithumi...@wso2.com, mobile: +94 756977999 >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> Milinda Perera >> Software Engineer; >> WSO2 Inc. http://wso2.com , >> Mobile: (+94) 714 115 032 >> >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Gayan Gunawardana > Software Engineer; WSO2 Inc.; http://wso2.com/ > Email: ga...@wso2.com > Mobile: +94 (71) 8020933 > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Ravindra Ranwala Software Engineer WSO2, Inc: http://wso2.com <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> Mobile: +94714198770 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Committers += Amalka Subasinghe
>>>>>> -- >>>>>>>>>>> *Gayashan Amarasinghe* >>>>>>>>>>> Software Engineer | Platform TG >>>>>>>>>>> WSO2, Inc. | http://wso2.com >>>>>>>>>>> lean. enterprise. middleware >>>>>>>>>>> >>>>>>>>>>> Mobile : +94718314517 >>>>>>>>>>> Blog : gayashan-a.blogspot.com >>>>>>>>>>> >>>>>>>>>>> ___ >>>>>>>>>>> Dev mailing list >>>>>>>>>>> Dev@wso2.org >>>>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> *Supun Sethunga* >>>>>>>>>> Software Engineer >>>>>>>>>> WSO2, Inc. >>>>>>>>>> lean | enterprise | middleware >>>>>>>>>> Mobile : +94 716546324 >>>>>>>>>> >>>>>>>>>> ___ >>>>>>>>>> Dev mailing list >>>>>>>>>> Dev@wso2.org >>>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> *Lasindu Charith* >>>>>>>>> Software Engineer, WSO2 Inc. >>>>>>>>> Mobile: +94714427192 >>>>>>>>> Web: blog.lasindu.com >>>>>>>>> >>>>>>>>> ___ >>>>>>>>> Dev mailing list >>>>>>>>> Dev@wso2.org >>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> ___ >>>>>>>> Dev mailing list >>>>>>>> Dev@wso2.org >>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Harsha Kumara >>>>>>> Software Engineer, WSO2 Inc. >>>>>>> Mobile: +94775505618 >>>>>>> Blog:harshcreationz.blogspot.com >>>>>>> >>>>>>> ___ >>>>>>> Dev mailing list >>>>>>> Dev@wso2.org >>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> ___ >>>>>> Dev mailing list >>>>>> Dev@wso2.org >>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> -- >>>>> Sithumini Senevirathne >>>>> Software Engineer >>>>> WSO2 Inc. - lean . enterprise . middleware | wso2.com >>>>> >>>>> email: sithumi...@wso2.com, mobile: +94 756977999 >>>>> >>>>> ___ >>>>> Dev mailing list >>>>> Dev@wso2.org >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> Regards, >>>> Manula Chathurika Thantriwatte >>>> Software Engineer >>>> WSO2 Inc. : http://wso2.com >>>> lean . enterprise . middleware >>>> >>>> email : manu...@wso2.com / man...@apache.org >>>> phone : +94 772492511 >>>> blog : http://manulachathurika.blogspot.com/ >>>> >>>> >>>> >>>> >>>> ___ >>>> Dev mailing list >>>> Dev@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> *Dinithi De Silva* >>> Associate Software Engineer, WSO2 Inc. >>> m:+94716667655 | e:dinit...@wso2.com | w: www.wso2.com >>> | a: #20, Palm Grove, Colombo 03 >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> Denuwanthi De Silva >> Software Engineer; >> WSO2 Inc.; http://wso2.com, >> Email: denuwan...@wso2.com >> Blog: https://denuwanthi.wordpress.com/ >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Ravindra Ranwala Software Engineer WSO2, Inc: http://wso2.com <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> Mobile: +94714198770 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Please Review and Merge the pull request
Hi Malaka,
I formatted the newly added code using the wso2 formatters [1]. But I am
confused why this pull request distorts that. In my source it shows inline
with the existing source.
[1]
https://sites.google.com/a/wso2.com/engineering/Home/eclipsecodeformattingtemplatesforwso2developers?pli=1
Thanks & Regards,
On Sat, Jan 24, 2015 at 10:47 AM, Malaka Silva wrote:
> Hi Ravindra,
>
> There seems to be some formatting issues please fix. eg:- newCtx =
> MessageHelper.cloneMessageContextForAggregateMediator(synCtx);- } catch (
> AxisFault axisFault) {+ destinationStatRecord =+ (StatisticsRecord) newCtx
> .getProperty(SynapseConstants.STATISTICS_STACK);+ if
> (destinationStatRecord != null &&
>
> On Sat, Jan 24, 2015 at 10:01 AM, Ravindra Ranwala
> wrote:
>
>> Hi ESBTeam,
>>
>> Please review and merge the pull request [1] to the issue [2].
>>
>>
>> [1] https://github.com/wso2-dev/wso2-synapse/pull/207/
>> [2] https://wso2.org/jira/browse/ESBJAVA-3498
>>
>>
>>
>> Thanks & Regards,
>>
>> --
>> Ravindra Ranwala
>> Software Engineer
>> WSO2, Inc: http://wso2.com
>> <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg>
>> Mobile: +94714198770
>>
>>
>
>
> --
>
> 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/>
>
> Save a tree -Conserve nature & Save the world for your future. Print this
> email only if it is absolutely necessary.
>
--
Ravindra Ranwala
Software Engineer
WSO2, Inc: http://wso2.com
<http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg>
Mobile: +94714198770
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] "Sample 152: Switching Transports and Message Format from SOAP to REST POX" doesn't make sence
ok, that's great. Thanks & Regards, On Wed, Jan 21, 2015 at 1:38 AM, Manuranga Perera wrote: > Hi Ravindra, > > >> Since ESB is a generic product we have given the customer the opportunity >> to configure that. But in one end it does not make sense. But if the >> behaviour you mentioned is really important, we can consider creating a >> public jira and solving that in a future release. >> > > Thanks for the explanation. I but I think we should at least correct the > doc to have , > so it does what is said in the title of the doc. I will create a public doc > jira for this. > > -- > With regards, > *Manu*ranga Perera. > > phone : 071 7 70 20 50 > mail : m...@wso2.com > -- Ravindra Ranwala Software Engineer WSO2, Inc: http://wso2.com <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> Mobile: +94714198770 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Committers += Kasun De Silva
94 718 74 44 08 >>>>>>>>> lean.enterprise.middleware >>>>>>>>> >>>>>>>>> ___ >>>>>>>>> Dev mailing list >>>>>>>>> Dev@wso2.org >>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> >>>>>>>> Thanks & regards, >>>>>>>> Nirmal >>>>>>>> >>>>>>>> Senior Software Engineer- Platform Technologies Team, WSO2 Inc. >>>>>>>> Mobile: +94715779733 >>>>>>>> Blog: http://nirmalfdo.blogspot.com/ >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> ___ >>>>>>>> Dev mailing list >>>>>>>> Dev@wso2.org >>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Thanks >>>>>>> Abimaran Kugathasan >>>>>>> >>>>>>> Software Engineer | WSO2 Inc >>>>>>> Data & APIs Technologies Team >>>>>>> Mobile : +94 773922820 >>>>>>> >>>>>>> <http://stackoverflow.com/users/515034> >>>>>>> <http://lk.linkedin.com/in/abimaran> >>>>>>> <http://www.lkabimaran.blogspot.com/> <https://github.com/abimaran> >>>>>>> <https://twitter.com/abimaran> >>>>>>> >>>>>>> >>>>>>> ___ >>>>>>> Dev mailing list >>>>>>> Dev@wso2.org >>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Regards, >>>>>> Manula Chathurika Thantriwatte >>>>>> Software Engineer >>>>>> WSO2 Inc. : http://wso2.com >>>>>> lean . enterprise . middleware >>>>>> >>>>>> email : manu...@wso2.com / man...@apache.org >>>>>> phone : +94 772492511 >>>>>> blog : http://manulachathurika.blogspot.com/ >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> ___ >>>>>> Dev mailing list >>>>>> Dev@wso2.org >>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> >>>>> Danesh Kuruppu >>>>> Software Engineer >>>>> WSO2 Inc, >>>>> Mobile: +94 (77) 1690552 >>>>> >>>>> ___ >>>>> Dev mailing list >>>>> Dev@wso2.org >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> >>>> *Tharindu Dharmarathna*Associate Software Engineer >>>> WSO2 Inc.; http://wso2.com >>>> lean.enterprise.middleware >>>> >>>> mobile: *+94779109091 <%2B94779109091>* >>>> >>>> ___ >>>> Dev mailing list >>>> Dev@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> *Chamin Nalinda* >>> >>> Intern - Engineering >>> WSO2 Inc. http://www.wso2.com >>> lean.enterprise.middleware >>> >>> Mobile: (+94) 77 241 66 04 >>> Linkedin: https://www.linkedin.com/in/chaminnalinda >>> Web: http://www.ckreativity.com >>> Blog: http://techspiro.blogspot.com/ >>> >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> Shashika Prabath Karunatilaka, >> Software Engineer, >> WSO2, Inc: http://wso2.com/ >> mobile : +94 77 7487792 >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > *Jerad Rutnam* > *Software Engineer - UI* > > WSO2 Inc. > lean | enterprise | middleware > M : +94 77 959 1609 | E : je...@wso2.com | W : www.wso2.com > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Ravindra Ranwala Software Engineer WSO2, Inc: http://wso2.com <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> Mobile: +94714198770 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Committers += Buddhima Wijeweera
Congrats Buddhima ! Regards, On Mon, Dec 29, 2014 at 8:28 PM, Chamin Nalinda wrote: > Congratulations Buddhima !!! > > On Mon, Dec 29, 2014 at 6:38 PM, Ravi Undupitiya wrote: > >> Congratulations Buddhima!! >> >> On Mon, Dec 29, 2014 at 7:55 AM, Kasun Indrasiri wrote: >> >>> Hi devs, >>> >>> Its my pleasure to welcome Buddhima Wijeweera as a WSO2 Committer. >>> >>> Buddhima, welcome aboard and keep up the good work. >>> >>> Thanks. >>> >>> -- >>> Kasun Indrasiri >>> Software Architect >>> WSO2, Inc.; http://wso2.com >>> lean.enterprise.middleware >>> >>> cell: +94 77 556 5206 >>> Blog : http://kasunpanorama.blogspot.com/ >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> *Ravi Undupitiya* >> Senior Software Engineer; WSO2 http://wso2.com >> >> >> *E-mail: r...@wso2.com <http://wso2.com>**M: **+94 772 930 712 >> <%2B94%C2%A0772%20930%20712>* >> >> Lean . Enterprise . Middleware >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > *Chamin Nalinda* > > Intern - Engineering > WSO2 Inc. http://www.wso2.com > lean.enterprise.middleware > > Mobile: (+94) 77 241 66 04 > Linkedin: https://www.linkedin.com/in/chaminnalinda > Web: http://www.ckreativity.com > Blog: http://techspiro.blogspot.com/ > > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Ravindra Ranwala Software Engineer WSO2, Inc: http://wso2.com <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> Mobile: +94714198770 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Committers += Sandamal Weerasinghe
Congrats Sandamal ! Regards, On Mon, Dec 29, 2014 at 10:25 PM, Chanuka Dissanayake wrote: > Congratulations Sandamal.. :) > > On Mon, Dec 29, 2014 at 6:33 PM, Ravi Undupitiya wrote: > >> Congratulations Sandamal!! >> >> On Mon, Dec 29, 2014 at 7:54 AM, Kasun Indrasiri wrote: >> >>> Hi devs, >>> >>> Its my pleasure to welcome Sandamal Weerasinghe as a WSO2 Committer. >>> >>> Sandamal, welcome aboard and keep up the good work. >>> >>> Thanks. >>> >>> -- >>> Kasun Indrasiri >>> Software Architect >>> WSO2, Inc.; http://wso2.com >>> lean.enterprise.middleware >>> >>> cell: +94 77 556 5206 >>> Blog : http://kasunpanorama.blogspot.com/ >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> *Ravi Undupitiya* >> Senior Software Engineer; WSO2 http://wso2.com >> >> >> *E-mail: r...@wso2.com <http://wso2.com>**M: **+94 772 930 712 >> <%2B94%C2%A0772%20930%20712>* >> >> Lean . Enterprise . Middleware >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Chanuka Dissanayake > *Software Engineer | **WSO2 Inc.*; http://wso2.com > > Mobile: +94 71 33 63 596 > Email: chan...@wso2.com > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Ravindra Ranwala Software Engineer WSO2, Inc: http://wso2.com <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> Mobile: +94714198770 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Committers += Isuru Ranawaka
t;>>>>>>>> Dev mailing list >>>>>>>>>>>>> Dev@wso2.org >>>>>>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> ___ >>>>>>>>>>>> Dev mailing list >>>>>>>>>>>> Dev@wso2.org >>>>>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> Thanks >>>>>>>>>>> Abimaran Kugathasan >>>>>>>>>>> >>>>>>>>>>> Software Engineer | WSO2 Inc >>>>>>>>>>> Data & APIs Technologies Team >>>>>>>>>>> Mobile : +94 773922820 >>>>>>>>>>> >>>>>>>>>>> <http://stackoverflow.com/users/515034> >>>>>>>>>>> <http://lk.linkedin.com/in/abimaran> >>>>>>>>>>> <http://www.lkabimaran.blogspot.com/> >>>>>>>>>>> <https://github.com/abimaran> <https://twitter.com/abimaran> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> ___ >>>>>>>>>>> Dev mailing list >>>>>>>>>>> Dev@wso2.org >>>>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> *Chamin Nalinda* >>>>>>>>>> >>>>>>>>>> Intern - Engineering >>>>>>>>>> WSO2 Inc. http://www.wso2.com >>>>>>>>>> lean.enterprise.middleware >>>>>>>>>> >>>>>>>>>> Mobile: (+94) 77 241 66 04 >>>>>>>>>> Linkedin: https://www.linkedin.com/in/chaminnalinda >>>>>>>>>> Web: http://www.ckreativity.com >>>>>>>>>> Blog: http://techspiro.blogspot.com/ >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> ___ >>>>>>>>>> Dev mailing list >>>>>>>>>> Dev@wso2.org >>>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Milinda Perera >>>>>>>>> Software Engineer; >>>>>>>>> WSO2 Inc. http://wso2.com , >>>>>>>>> Mobile: (+94) 714 115 032 >>>>>>>>> >>>>>>>>> >>>>>>>>> ___ >>>>>>>>> Dev mailing list >>>>>>>>> Dev@wso2.org >>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Prasanna Dangalla >>>>>>>> Software Engineer, WSO2, Inc.; http://wso2.com/ >>>>>>>> lean.enterprise.middleware >>>>>>>> >>>>>>>> cell: +94 777 55 80 30 | +94 718 11 27 51 >>>>>>>> twitter: @prasa77 >>>>>>>> >>>>>>>> ___ >>>>>>>> Dev mailing list >>>>>>>> Dev@wso2.org >>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> ___ >>>>>>> Dev mailing list >>>>>>> Dev@wso2.org >>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Shashika Prabath Karunatilaka, >>>>>> Software Engineer, >>>>>> WSO2, Inc: http://wso2.com/ >>>>>> mobile : +94 77 7487792 >>>>>> >>>>>> ___ >>>>>> Dev mailing list >>>>>> Dev@wso2.org >>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Priya Kishok >>>>> Software Engineer >>>>> WSO2, Inc : http://wso2.com >>>>> Mob : +94774457404 >>>>> >>>>> ___ >>>>> Dev mailing list >>>>> Dev@wso2.org >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> *Niranda Perera* >>>> Software Engineer, WSO2 Inc. >>>> Mobile: +94-71-554-8430 >>>> Twitter: @n1r44 <https://twitter.com/N1R44> >>>> >>>> ___ >>>> Dev mailing list >>>> Dev@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> Harsha Kumara >>> Software Engineer, WSO2 Inc. >>> Mobile: +94775505618 >>> Blog:harshcreationz.blogspot.com >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> *Ravi Undupitiya* >> Senior Software Engineer; WSO2 http://wso2.com >> >> >> *E-mail: r...@wso2.com <http://wso2.com>**M: **+94 772 930 712 >> <%2B94%C2%A0772%20930%20712>* >> >> Lean . Enterprise . Middleware >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Ravindra Ranwala Software Engineer WSO2, Inc: http://wso2.com <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> Mobile: +94714198770 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Committers += Hasitha Amal De Silva
Congrats Hasitha !!! On Tue, Dec 23, 2014 at 12:55 PM, Prasanna Dangalla wrote: > Congratulations... > > On Tue, Dec 23, 2014 at 12:38 PM, Pulasthi Mahawithana > wrote: > >> Congrats Hasitha ! >> >> On Tue, Dec 23, 2014 at 10:35 AM, Inosh Perera wrote: >> >>> Congrats Hasitha! >>> >>> On Tue, Dec 23, 2014 at 10:29 AM, Samith Dassanayake >>> wrote: >>> >>>> Congratz Hasitha! >>>> >>>> On Mon, Dec 22, 2014 at 5:12 PM, Kalpa Welivitigoda >>>> wrote: >>>> >>>>> Congratulations Hasitha ! >>>>> >>>>> On Mon, Dec 22, 2014 at 5:11 PM, Ramith Jayasinghe >>>>> wrote: >>>>> >>>>>> Hi Hasitha, >>>>>> Congratulations! >>>>>> It is with great pleasure that we welcome you as a WSO2 committer. >>>>>> Keep up the good work! >>>>>> >>>>>> >>>>>> -- >>>>>> Ramith Jayasinghe >>>>>> Technical Lead >>>>>> WSO2 Inc., http://wso2.com >>>>>> lean.enterprise.middleware >>>>>> >>>>>> E: ram...@wso2.com >>>>>> >>>>>> >>>>>> ___ >>>>>> Dev mailing list >>>>>> Dev@wso2.org >>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Best Regards, >>>>> >>>>> Kalpa Welivitigoda >>>>> Software Engineer, WSO2 Inc. http://wso2.com >>>>> Email: kal...@wso2.com >>>>> Mobile: +94776509215 >>>>> >>>>> ___ >>>>> Dev mailing list >>>>> Dev@wso2.org >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> Best Regards >>>> >>>> Samith Dassanayake >>>> Software Engineer, WSO2 Inc. >>>> >>>> >>>> ___ >>>> Dev mailing list >>>> Dev@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> Inosh Perera >>> Software Engineer, WSO2 Inc. >>> Tel: 0785293686 >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> *Pulasthi Mahawithana* >> Software Engineer >> WSO2 Inc., http://wso2.com/ >> Mobile: +94-71-5179022 >> Blog: http://blog.pulasthi.org >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Prasanna Dangalla > Software Engineer, WSO2, Inc.; http://wso2.com/ > lean.enterprise.middleware > > cell: +94 777 55 80 30 | +94 718 11 27 51 > twitter: @prasa77 > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Ravindra Ranwala Software Engineer WSO2, Inc: http://wso2.com <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> Mobile: +94714198770 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Committers += Firzhan Naqash
Congrats Firzhan !!! On Tue, Dec 23, 2014 at 4:32 PM, Thanuja Jayasinghe wrote: > Congratz Firzhan. > > On Tue, Dec 23, 2014 at 5:42 AM, Dakshika Jayathilaka > wrote: > >> Congratulations !! >> >> *Dakshika Jayathilaka* >> Software Engineer >> WSO2, Inc. >> lean.enterprise.middleware >> 0771100911 >> >> On Tue, Dec 23, 2014 at 2:27 PM, Manoj Kumara wrote: >> >>> Congratulations !! >>> >>> >>> *Manoj Kumara* >>> Software Engineer >>> WSO2 Inc. http://wso2.com/ >>> *lean.enterprise.middleware* >>> Mobile: +94713448188 >>> >>> On Tue, Dec 23, 2014 at 2:26 PM, Sajini De Silva >>> wrote: >>> >>>> Congratulations Firzhan!!! >>>> >>>> On Tue, Dec 23, 2014 at 2:25 PM, Lasitha Wattaladeniya < >>>> lasit...@wso2.com> wrote: >>>> >>>>> Congratulations ! >>>>> >>>>> On Tue, Dec 23, 2014 at 11:48 AM, Kasun De Silva >>>>> wrote: >>>>> >>>>>> Congratz Firzan !!! >>>>>> >>>>>> *Kasun de Silva* >>>>>> Software Engineer | *WSO2 Inc.*; http://wso2.com >>>>>> lean.enterprise.middleware >>>>>> >>>>>> email : kas...@wso2.com >>>>>> mobile : +94 77 794 4260 >>>>>> >>>>>> >>>>>> On Tue, Dec 23, 2014 at 11:46 AM, Nandika Jayawardana < >>>>>> nand...@wso2.com> wrote: >>>>>> >>>>>>> Hi All, >>>>>>> >>>>>>> It is my pleasure to welcome Firzhan as a WSO2 committer. Firzhan is >>>>>>> a key member of Business Process Server Team and has contributed to Both >>>>>>> BPS and IS. >>>>>>> Welcome aboard and week up the good work ! >>>>>>> >>>>>>> Regards >>>>>>> Nandika >>>>>>> >>>>>>> -- >>>>>>> Nandika Jayawardana >>>>>>> Senior Technical Lead >>>>>>> WSO2 Inc ; http://wso2.com >>>>>>> lean.enterprise.middleware >>>>>>> >>>>>>> ___ >>>>>>> Dev mailing list >>>>>>> Dev@wso2.org >>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>> >>>>>>> >>>>>> >>>>>> ___ >>>>>> Dev mailing list >>>>>> Dev@wso2.org >>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Lasitha Wattaladeniya >>>>> Software Engineer >>>>> WSO2, Inc. | http://wso2.com >>>>> lean. enterprise. middleware >>>>> >>>>> Mobile : +94719397528 >>>>> Blog : techreadme.blogspot.com >>>>> >>>>> ___ >>>>> Dev mailing list >>>>> Dev@wso2.org >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> Sajini De SIlva >>>> Software Engineer; WSO2 Inc.; http://wso2.com , >>>> Email: saj...@wso2.com >>>> Blog: http://sajinid.blogspot.com/ >>>> Git hub profile: https://github.com/sajinidesilva >>>> >>>> Phone: +94 712797729 >>>> >>>> >>>> ___ >>>> Dev mailing list >>>> Dev@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > *Thanuja Lakmal* > Software Engineer > WSO2 Inc. http://wso2.com/ > *lean.enterprise.middleware* > Mobile: +94715979891 +94758009992 > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Ravindra Ranwala Software Engineer WSO2, Inc: http://wso2.com <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> Mobile: +94714198770 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Committers += Roshan Deniyage
Congrats Roshan ! On Fri, Dec 19, 2014 at 8:02 AM, Shiroshica Kulatilake wrote: > > Congrats !!! > > On Fri, Dec 19, 2014 at 8:01 AM, Anuruddha Premalal > wrote: >> >> Congratulation Roshan!! >> >> On Fri, Dec 19, 2014 at 6:44 AM, Kasun De Silva wrote: >>> >>> Congratz Roshan!!! >>> >>> *Kasun de Silva* >>> Software Engineer | *WSO2 Inc.*; http://wso2.com >>> lean.enterprise.middleware >>> >>> email : kas...@wso2.com >>> mobile : +94 77 794 4260 >>> >>> >>> On Fri, Dec 19, 2014 at 1:29 AM, Thanuja Jayasinghe >>> wrote: >>>> >>>> Congratz Roshan!!! >>>> >>>> On Thu, Dec 18, 2014 at 12:59 PM, Prabath Ariyarathna < >>>> prabat...@wso2.com> wrote: >>>>> >>>>> Congratulations Roshan >>>>> >>>>> On Thu, Dec 18, 2014 at 11:23 PM, Harsha Kumara >>>>> wrote: >>>>>> >>>>>> Congratulations Roshan! >>>>>> >>>>>> On Thu, Dec 18, 2014 at 10:24 PM, Vijitha Ekanayake < >>>>>> vijit...@wso2.com> wrote: >>>>>>> >>>>>>> Congratulations Roshan >>>>>>> >>>>>>> On Thu, Dec 18, 2014 at 10:10 PM, Dimuthu Leelarathne < >>>>>>> dimut...@wso2.com> wrote: >>>>>>> >>>>>>>> Hi all, >>>>>>>> >>>>>>>> WSO2 welcomes Roshan Deniyage as WSO2 committer! >>>>>>>> >>>>>>>> Congratulations! >>>>>>>> >>>>>>>> thanks, >>>>>>>> dimuthu >>>>>>>> >>>>>>>> -- >>>>>>>> Dimuthu Leelarathne >>>>>>>> Architect & Product Lead of App Factory >>>>>>>> >>>>>>>> WSO2, Inc. (http://wso2.com) >>>>>>>> email: dimut...@wso2.com >>>>>>>> Mobile : 0773661935 >>>>>>>> >>>>>>>> Lean . Enterprise . Middleware >>>>>>>> >>>>>>>> ___ >>>>>>>> Dev mailing list >>>>>>>> Dev@wso2.org >>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Vijitha Ekanayake >>>>>>> Software Engineer*, *WSO2, Inc.; http://wso2.com/ >>>>>>> Mobile : +94 777 24 73 39 | +94 718 74 44 08 >>>>>>> lean.enterprise.middleware >>>>>>> >>>>>>> ___ >>>>>>> Dev mailing list >>>>>>> Dev@wso2.org >>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>> >>>>>>> >>>>>> >>>>>> -- >>>>>> Harsha Kumara >>>>>> Software Engineer, WSO2 Inc. >>>>>> Mobile: +94775505618 >>>>>> Blog:harshcreationz.blogspot.com >>>>>> >>>>>> ___ >>>>>> Dev mailing list >>>>>> Dev@wso2.org >>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>> >>>>>> >>>>> >>>>> -- >>>>> >>>>> *Prabath Ariyarathna* >>>>> >>>>> *Associate Technical Lead* >>>>> >>>>> *WSO2, Inc. * >>>>> >>>>> *lean . enterprise . middleware * >>>>> >>>>> >>>>> *Email: prabat...@wso2.com * >>>>> >>>>> *Blog: http://prabu-lk.blogspot.com <http://prabu-lk.blogspot.com>* >>>>> >>>>> *Flicker : https://www.flickr.com/photos/47759189@N08 >>>>> <https://www.flickr.com/photos/47759189@N08>* >>>>> >>>>> *Mobile: +94 77 699 4730 * >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> ___ >>>>> Dev mailing list >>>>> Dev@wso2.org >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>>> >>>> >>>> -- >>>> *Thanuja Lakmal* >>>> Software Engineer >>>> WSO2 Inc. http://wso2.com/ >>>> *lean.enterprise.middleware* >>>> Mobile: +94715979891 +94758009992 >>>> >>>> ___ >>>> Dev mailing list >>>> Dev@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> -- >> *Anuruddha Premalal* >> Software Eng. | WSO2 Inc. >> Mobile : +94710461070 >> Web site : www.regilandvalley.com >> >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > -- > Shiroshica Kulatilake > > Architect, > WSO2, Inc. http://wso2.com/ > Phone: +94 776523867 > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Ravindra Ranwala Software Engineer WSO2, Inc: http://wso2.com <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> Mobile: +94714198770 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] SSLHandShake issue when invoking https endpoint from ESB
ated keystore. >>>> 3. exported public certificate to .crt file >>>> 4. added .crt to wso2carbon.jks and client-truststore.jks >>>> 5. change axis2.xml parameter as >>> name="HostnameVerifier">AllowAll >>>> >>>> Can anyone help me to sort out this issue? >>>> >>>> following exception printed out in the terminal >>>> >>>> [2014-12-15 08:40:04,243] ERROR - SourceHandler I/O error: null cert >>>> chain >>>> >>>> javax.net.ssl.SSLHandshakeException: null cert chain >>>> >>>> at >>>> com.sun.net.ssl.internal.ssl.Handshaker.checkThrown(Handshaker.java:1015) >>>> >>>> at >>>> com.sun.net.ssl.internal.ssl.SSLEngineImpl.checkTaskThrown(SSLEngineImpl.java:485) >>>> >>>> at >>>> com.sun.net.ssl.internal.ssl.SSLEngineImpl.writeAppRecord(SSLEngineImpl.java:1108) >>>> >>>> at >>>> com.sun.net.ssl.internal.ssl.SSLEngineImpl.wrap(SSLEngineImpl.java:1080) >>>> >>>> at javax.net.ssl.SSLEngine.wrap(SSLEngine.java:452) >>>> >>>> at >>>> org.apache.http.nio.reactor.ssl.SSLIOSession.doWrap(SSLIOSession.java:220) >>>> >>>> at >>>> org.apache.http.nio.reactor.ssl.SSLIOSession.doHandshake(SSLIOSession.java:254) >>>> >>>> at >>>> org.apache.http.nio.reactor.ssl.SSLIOSession.isAppInputReady(SSLIOSession.java:380) >>>> >>>> at >>>> org.apache.http.impl.nio.reactor.AbstractIODispatch.inputReady(AbstractIODispatch.java:118) >>>> >>>> at >>>> org.apache.http.impl.nio.reactor.BaseIOReactor.readable(BaseIOReactor.java:160) >>>> >>>> at >>>> org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:342) >>>> >>>> at >>>> org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents(AbstractIOReactor.java:320) >>>> >>>> at >>>> org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:280) >>>> >>>> at >>>> org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:106) >>>> >>>> at >>>> org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:604) >>>> >>>> at java.lang.Thread.run(Thread.java:695) >>>> >>>> Caused by: javax.net.ssl.SSLHandshakeException: null cert chain >>>> >>>> at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:174) >>>> >>>> at >>>> com.sun.net.ssl.internal.ssl.SSLEngineImpl.fatal(SSLEngineImpl.java:1447) >>>> >>>> at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:243) >>>> >>>> at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:231) >>>> >>>> at >>>> com.sun.net.ssl.internal.ssl.ServerHandshaker.clientCertificate(ServerHandshaker.java:1372) >>>> >>>> at >>>> com.sun.net.ssl.internal.ssl.ServerHandshaker.processMessage(ServerHandshaker.java:160) >>>> >>>> at >>>> com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Handshaker.java:593) >>>> >>>> at com.sun.net.ssl.internal.ssl.Handshaker$1.run(Handshaker.java:533) >>>> >>>> at java.security.AccessController.doPrivileged(Native Method) >>>> >>>> at >>>> com.sun.net.ssl.internal.ssl.Handshaker$DelegatedTask.run(Handshaker.java:952) >>>> >>>> at >>>> org.apache.http.nio.reactor.ssl.SSLIOSession.doRunTask(SSLIOSession.java:238) >>>> >>>> at >>>> org.apache.http.nio.reactor.ssl.SSLIOSession.doHandshake(SSLIOSession.java:270) >>>> [1] >>>> http://sahanlm.blogspot.com/2013/10/wso2-esb-exposing-secure-backend.html >>>> >>>> -- >>>> Vijitha Ekanayake >>>> Software Engineer*, *WSO2, Inc.; http://wso2.com/ >>>> Mobile : +94 777 24 73 39 | +94 718 74 44 08 >>>> lean.enterprise.middleware >>>> >>>> ___ >>>> Dev mailing list >>>> Dev@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> -- >>> Waruna Perera >>> Senior Software Engineer - Test Automation >>> Mobile: +94 77 3867037 >>> WSO2, Inc.; http://wso2.com/ >>> lean . enterprise . middlewear. >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> -- >> >> 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/> >> >> Save a tree -Conserve nature & Save the world for your future. Print this >> email only if it is absolutely necessary. >> > > > -- > Vijitha Ekanayake > Software Engineer*, *WSO2, Inc.; http://wso2.com/ > Mobile : +94 777 24 73 39 | +94 718 74 44 08 > lean.enterprise.middleware > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Ravindra Ranwala Software Engineer WSO2, Inc: http://wso2.com <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> Mobile: +94714198770 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] HTTP Core Reverse Proxy SSL ERROR
Hi All, When using a connection pool on the client side to manage outgoing connections one needs to ensure that the connection factory used by the pool to create new connection objects is SSL capable. Thanks & Regards, On Sat, Dec 13, 2014 at 9:12 AM, Ravindra Ranwala wrote: > > Hi All, > > The issue was solved by injecting the SSL Connection Factory through the > ProxyConnPool constructor as follows. > > > > > > > > > *clientSSLContext = > SSLUtil.createClientSSLContext(TRUST_STORE_LOCATION, > TRUST_STORE_PASSWORD); > BasicNIOConnFactory sslClientConnectionFactory = >new > BasicNIOConnFactory(clientSSLContext, null, > > ConnectionConfig.DEFAULT);ProxyConnPool connPool = new > ProxyConnPool(connectingIOReactor, sslClientConnectionFactory, 5000);* > > > > > Thanks &Regards, > > On Sat, Dec 6, 2014 at 12:34 PM, Ravindra Ranwala > wrote: >> >> Hi All, >> >> I am developing a reverse proxy using http core and need to connect to a >> Secure/HTTPS endpoint via the proxy. I took the reverse proxy[1] and added >> SSL support as shown below. >> >> clientSSLContext = >> >> SSLUtil.createClientSSLContext(TRUST_STORE_LOCATION, >> >> TRUST_STORE_PASSWORD); >> >> final IOEventDispatch connectingEventDispatch = >> new >> DefaultHttpClientIODispatch( >> >> >> clientHandler, >> >> >> clientSSLContext, >> >> >> ConnectionConfig.DEFAULT); >> ... >> connectingIOReactor.execute(connectingEventDispatch); >> >> >> I am trying to connect to HTTPS endpoint of SimpleStockQuoteService which >> is deployed in axis2 server. But when I send the request(getQuote), I am >> getting this error in the server console. >> >> 14/12/06 11:16:54 ERROR nhttp.ServerHandler: I/O error: Received >> close_notify during handshake >> javax.net.ssl.SSLException: Received close_notify during handshake >> at sun.security.ssl.Alerts.getSSLException(Alerts.java:208) >> at sun.security.ssl.SSLEngineImpl.fatal(SSLEngineImpl.java:1446) >> at sun.security.ssl.SSLEngineImpl.fatal(SSLEngineImpl.java:1414) >> at sun.security.ssl.SSLEngineImpl.recvAlert(SSLEngineImpl.java:1552) >> at sun.security.ssl.SSLEngineImpl.readRecord(SSLEngineImpl.java:1018) >> at >> sun.security.ssl.SSLEngineImpl.readNetRecord(SSLEngineImpl.java:853) >> at sun.security.ssl.SSLEngineImpl.unwrap(SSLEngineImpl.java:727) >> at javax.net.ssl.SSLEngine.unwrap(SSLEngine.java:624) >> >> >> I enabled SSL debug logs as well, but still could not figure out the >> issue. >> >> Any help would be appreciated. >> >> >> [1] https://hc.apache.org/httpcomponents-core-ga/examples.html >> >> >> >> Thanks & Regards, >> >> -- >> Ravindra Ranwala >> Software Engineer >> WSO2, Inc: http://wso2.com >> <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> >> Mobile: +94714198770 >> >> > > -- > Ravindra Ranwala > Software Engineer > WSO2, Inc: http://wso2.com > <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> > Mobile: +94714198770 > > -- Ravindra Ranwala Software Engineer WSO2, Inc: http://wso2.com <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> Mobile: +94714198770 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] HTTP Core Reverse Proxy SSL ERROR
Hi All, The issue was solved by injecting the SSL Connection Factory through the ProxyConnPool constructor as follows. *clientSSLContext = SSLUtil.createClientSSLContext(TRUST_STORE_LOCATION, TRUST_STORE_PASSWORD); BasicNIOConnFactory sslClientConnectionFactory = new BasicNIOConnFactory(clientSSLContext, null, ConnectionConfig.DEFAULT);ProxyConnPool connPool = new ProxyConnPool(connectingIOReactor, sslClientConnectionFactory, 5000);* Thanks &Regards, On Sat, Dec 6, 2014 at 12:34 PM, Ravindra Ranwala wrote: > > Hi All, > > I am developing a reverse proxy using http core and need to connect to a > Secure/HTTPS endpoint via the proxy. I took the reverse proxy[1] and added > SSL support as shown below. > > clientSSLContext = > > SSLUtil.createClientSSLContext(TRUST_STORE_LOCATION, > > TRUST_STORE_PASSWORD); > > final IOEventDispatch connectingEventDispatch = > new > DefaultHttpClientIODispatch( > > > clientHandler, > > > clientSSLContext, > > > ConnectionConfig.DEFAULT); > ... > connectingIOReactor.execute(connectingEventDispatch); > > > I am trying to connect to HTTPS endpoint of SimpleStockQuoteService which > is deployed in axis2 server. But when I send the request(getQuote), I am > getting this error in the server console. > > 14/12/06 11:16:54 ERROR nhttp.ServerHandler: I/O error: Received > close_notify during handshake > javax.net.ssl.SSLException: Received close_notify during handshake > at sun.security.ssl.Alerts.getSSLException(Alerts.java:208) > at sun.security.ssl.SSLEngineImpl.fatal(SSLEngineImpl.java:1446) > at sun.security.ssl.SSLEngineImpl.fatal(SSLEngineImpl.java:1414) > at sun.security.ssl.SSLEngineImpl.recvAlert(SSLEngineImpl.java:1552) > at sun.security.ssl.SSLEngineImpl.readRecord(SSLEngineImpl.java:1018) > at sun.security.ssl.SSLEngineImpl.readNetRecord(SSLEngineImpl.java:853) > at sun.security.ssl.SSLEngineImpl.unwrap(SSLEngineImpl.java:727) > at javax.net.ssl.SSLEngine.unwrap(SSLEngine.java:624) > > > I enabled SSL debug logs as well, but still could not figure out the issue. > > Any help would be appreciated. > > > [1] https://hc.apache.org/httpcomponents-core-ga/examples.html > > > > Thanks & Regards, > > -- > Ravindra Ranwala > Software Engineer > WSO2, Inc: http://wso2.com > <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> > Mobile: +94714198770 > > -- Ravindra Ranwala Software Engineer WSO2, Inc: http://wso2.com <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> Mobile: +94714198770 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] HTTP Core Reverse Proxy SSL ERROR
Hi All, I am developing a reverse proxy using http core and need to connect to a Secure/HTTPS endpoint via the proxy. I took the reverse proxy[1] and added SSL support as shown below. clientSSLContext = SSLUtil.createClientSSLContext(TRUST_STORE_LOCATION, TRUST_STORE_PASSWORD); final IOEventDispatch connectingEventDispatch = new DefaultHttpClientIODispatch( clientHandler, clientSSLContext, ConnectionConfig.DEFAULT); ... connectingIOReactor.execute(connectingEventDispatch); I am trying to connect to HTTPS endpoint of SimpleStockQuoteService which is deployed in axis2 server. But when I send the request(getQuote), I am getting this error in the server console. 14/12/06 11:16:54 ERROR nhttp.ServerHandler: I/O error: Received close_notify during handshake javax.net.ssl.SSLException: Received close_notify during handshake at sun.security.ssl.Alerts.getSSLException(Alerts.java:208) at sun.security.ssl.SSLEngineImpl.fatal(SSLEngineImpl.java:1446) at sun.security.ssl.SSLEngineImpl.fatal(SSLEngineImpl.java:1414) at sun.security.ssl.SSLEngineImpl.recvAlert(SSLEngineImpl.java:1552) at sun.security.ssl.SSLEngineImpl.readRecord(SSLEngineImpl.java:1018) at sun.security.ssl.SSLEngineImpl.readNetRecord(SSLEngineImpl.java:853) at sun.security.ssl.SSLEngineImpl.unwrap(SSLEngineImpl.java:727) at javax.net.ssl.SSLEngine.unwrap(SSLEngine.java:624) I enabled SSL debug logs as well, but still could not figure out the issue. Any help would be appreciated. [1] https://hc.apache.org/httpcomponents-core-ga/examples.html Thanks & Regards, -- Ravindra Ranwala Software Engineer WSO2, Inc: http://wso2.com <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> Mobile: +94714198770 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [EIP-Dead Letter Channel] Timout Exception while resending the dead message
Hi Zamly, If the message sending fails, the message processor keeps on retrying until the max delivery attempt is reached. Once the max delivery attempt is reached the message processor deactivates. You have to give the endpoint to the message processor. I think you would NOT have given the endpoint so that it is unable to send the message to the backend. You may refer this article[1] for more information. Target endpoint can be given as targetendpoint="sampleEndpoint" in the message processor configuration. [1] http://wso2.com/library/articles/2014/01/guaranteed-delivery-with-Message-Store-Message-Processor%20/ Thanks & Regards, On Wed, Nov 12, 2014 at 2:57 PM, Zamly Thaha wrote: > Hi all, > I have been trying the Dead letter Message Channel Example in the EIP > Guide [1]. > > As per the documentation if message sending fails, the client should get > the response when the back end service is alive within the message > processor's retry attempts. The back end service seems to be receiving the > message from the message processor once the back end server is restarted. > > But the intended client gets the following error : > "org.apache.axis2.AxisFault: Read timed out" instead of the response. > > Please note : > The message processor keeps attempting all its retry attempts even if the > back service is alive. > When creating a message processor in ESB 4.8.1, it requires an additional > endpoint parameter (compulsory field). The current documentation doesn't > specify about the endpoint parameter. > > Is this an issue with the configuration? any help would be appreciated. > > [1] https://docs.wso2.com/display/IntegrationPatterns/Dead+Letter+Channel > > Regards. > -- > *ZAMLY|THAHA* > Associate Software Engineer | WSO2 Inc. > > M: +94 717179055 > > _______ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Ravindra Ranwala Software Engineer WSO2, Inc: http://wso2.com <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> Mobile: +94714198770 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] How to create a new ESB mediator
Hi Lahiru, WSO2 Carbon is based on OSGi. To extend the framework you need to drop an OSGi bundle. What you are having at the moment is an external jar file. Once you place the jar file in to $CARBON_HOME/repository/components/dropins directory, the platform converts the legacy jar file into an OSGi bundle at run time. Refer this article [1] for more details. [1] http://wso2.com/library/knowledgebase/add-external-jar-libraries-wso2-carbon-based-products/ Thanks & Regards, On Wed, Oct 29, 2014 at 8:27 PM, Udara Liyanage wrote: > Hi, > > This post might help you. > > > http://wso2.com/library/tutorials/2014/03/understanding-the-carbon-component-architecture/ > > > > Touched, not typed. Erroneous words are a feature, not a typo. > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Ravindra Ranwala Software Engineer WSO2, Inc: http://wso2.com <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> Mobile: +94714198770 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [BAM][API-Manager] issue in updating API Manager statistics dashboard with BAM
invoke the api. That is the reason for the missing requests in >>>>>>>>>>>>>> statistics >>>>>>>>>>>>>> dashboard. >>>>>>>>>>>>>> >>>>>>>>>>>>>> I tried debugging the APIMgtUsageDataBridgeDataPublisher >>>>>>>>>>>>>> class since it has publishEvent method to publish data. >>>>>>>>>>>>>> APIMgtUsageDataBridgeDataPublisher class uses >>>>>>>>>>>>>> LoadBalancingDataPublisher as >>>>>>>>>>>>>> the dataPublisher in this case. >>>>>>>>>>>>>> >>>>>>>>>>>>>> I found that every time when I invoke the api via rest >>>>>>>>>>>>>> client, this method will execute. but randomly some requests are >>>>>>>>>>>>>> not >>>>>>>>>>>>>> publishing in Cassandra database. I used the >>>>>>>>>>>>>> latest org.wso2.carbon.databridge.agent.thrift jar. but the >>>>>>>>>>>>>> problem is >>>>>>>>>>>>>> still there. >>>>>>>>>>>>>> >>>>>>>>>>>>>> if requests come to publishEvent method, should they publish >>>>>>>>>>>>>> in Cassandra database?and is there any known reason for data get >>>>>>>>>>>>>> not >>>>>>>>>>>>>> published in cassendra database. if not where I can find the >>>>>>>>>>>>>> data publisher >>>>>>>>>>>>>> to cassendra in BAM from API Manager. >>>>>>>>>>>>>> >>>>>>>>>>>>>> Thanks >>>>>>>>>>>>>> -- >>>>>>>>>>>>>> Lakshman Udayakantha >>>>>>>>>>>>>> WSO2 Inc. www.wso2.com >>>>>>>>>>>>>> lean.enterprise.middleware >>>>>>>>>>>>>> Mobile: *0711241005 <0711241005>* >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> ___ >>>>>>>>>>>>>> Dev mailing list >>>>>>>>>>>>>> Dev@wso2.org >>>>>>>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> -- >>>>>>>>>>>>> W.G. Gihan Anuruddha >>>>>>>>>>>>> Senior Software Engineer | WSO2, Inc. >>>>>>>>>>>>> M: +94772272595 >>>>>>>>>>>>> >>>>>>>>>>>>> ___ >>>>>>>>>>>>> Dev mailing list >>>>>>>>>>>>> Dev@wso2.org >>>>>>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> Manoj Gunawardena >>>>>>>>>>>> Tech Lead >>>>>>>>>>>> WSO2, Inc.: http://wso2.com >>>>>>>>>>>> lean.enterprise.middleware >>>>>>>>>>>> Mobile : +94 77 2291643 >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> Lakshman Udayakantha >>>>>>>>>>> WSO2 Inc. www.wso2.com >>>>>>>>>>> lean.enterprise.middleware >>>>>>>>>>> Mobile: *0711241005 <0711241005>* >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> W.G. Gihan Anuruddha >>>>>>>>>> Senior Software Engineer | WSO2, Inc. >>>>>>>>>> M: +94772272595 >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Lakshman Udayakantha >>>>>>>>> WSO2 Inc. www.wso2.com >>>>>>>>> lean.enterprise.middleware >>>>>>>>> Mobile: *0711241005* >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Regards, >>>>>>>> >>>>>>>> Inosh Goonewardena >>>>>>>> Associate Technical Lead- WSO2 Inc. >>>>>>>> Mobile: +94779966317 >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Lakshman Udayakantha >>>>>>> WSO2 Inc. www.wso2.com >>>>>>> lean.enterprise.middleware >>>>>>> Mobile: *0711241005* >>>>>>> >>>>>>> >>>>>> >>>>>> -- >>>>>> Regards, >>>>>> >>>>>> Inosh Goonewardena >>>>>> Associate Technical Lead- WSO2 Inc. >>>>>> Mobile: +94779966317 >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Lakshman Udayakantha >>>>> WSO2 Inc. www.wso2.com >>>>> lean.enterprise.middleware >>>>> Mobile: *0711241005* >>>>> >>>>> >>>> >>>> >>>> -- >>>> Lakshman Udayakantha >>>> WSO2 Inc. www.wso2.com >>>> lean.enterprise.middleware >>>> Mobile: *0711241005* >>>> >>>> >>>> ___ >>>> Dev mailing list >>>> Dev@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> Manoj Gunawardena >>> Tech Lead >>> WSO2, Inc.: http://wso2.com >>> lean.enterprise.middleware >>> Mobile : +94 77 2291643 >>> >> >> >> >> -- >> Lakshman Udayakantha >> WSO2 Inc. www.wso2.com >> lean.enterprise.middleware >> Mobile: *0711241005* >> >> > > > -- > Lakshman Udayakantha > WSO2 Inc. www.wso2.com > lean.enterprise.middleware > Mobile: *0711241005* > > -- Ravindra Ranwala Software Engineer WSO2, Inc: http://wso2.com <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> Mobile: +94714198770 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [ESB] How does content aware mediators behave with nhttp transport ?
Hi Rushmin, Yes indeed. We call this as Conditional canonicalization in Passthrough transport architecture. Refer this article[1] for further information. [1] http://wso2.com/library/articles/2013/12/demystifying-wso2-esb-pass-thru-transport-part-ii/ Thanks & Regards, On Fri, Oct 24, 2014 at 8:53 AM, Rushmin Fernando wrote: > Thanks Ravindra. > > Does it mean that the message won't get built till the mediation engine > reaches the first content aware mediator in the sequence ? > > Rushmin > > On Thu, Oct 23, 2014 at 11:18 PM, Ravindra Ranwala > wrote: > >> Hi Rushmin, >> >> If the mediator is a content aware one, the Axis2 Engine should build the >> message using a message builder into our internal canonical form before >> passing it to the mediate method of the content aware mediator. The mediate >> method accepts that internal canonical format and conducts the mediation on >> it. Building the message is NOT a responsibility of the mediator. For an >> example instance a Filter mediator with a regular xpath expression which >> accesses message content can be considered as a content aware mediator. >> >> >> >> Thanks & Regards, >> >> On Thu, Oct 23, 2014 at 11:04 PM, Rushmin Fernando >> wrote: >> >>> Thanks isuru for the detailed reply! >>> >>> So when a message is passed to the mediate() method, is it prebuilt if >>> the mediator is a content aware one? Or is it the respinsibility of the >>> mediator to build the message? >>> On Oct 23, 2014 1:04 PM, "Isuru Ranawaka" wrote: >>> >>>> Hi Rushmin, >>>> >>>> According to the nhttp architecture it uses two buffers for request >>>> read(Input Stream) and request write to BE(output stream). But those two >>>> buffers has raw byte stream.But in the mediation layer requests are >>>> represent as OMElements.So InputStream is need to convert OMElement and >>>> again to OutputStream so that is handle by Axis2 Level message builders >>>> and formatters. Message builders create OMElement from input stream and >>>> formatters again serialized it. So before moving to mediation layer >>>> messages are converted to OMElement but this not fully build of the message >>>> this is only partially build because it uses Steaming API (Stax parser) how >>>> ever it has significant build overhead comparing to raw byte stream. >>>> >>>> If mediators are content aware then message is actually fully read to >>>> the memory by Streaming API. But if you used binary relay in nhttp >>>> transport then messages are processed as byte streams with out partially or >>>> fully building of the message.But it can not be used with content aware >>>> mediators. >>>> >>>> thanks >>>> IsuruR >>>> >>>> On Thu, Oct 23, 2014 at 9:30 PM, Rushmin Fernando >>>> wrote: >>>> >>>>> Does the framework build the message before it submits a message for >>>>> mediation to a content aware mediator >>>>> >>>>> or >>>>> >>>>> does it build the message upfront if there is a content mediator in >>>>> possible sequence paths ? >>>>> >>>>> Thanks >>>>> Rushmin >>>>> >>>>> >>>>> >>>>> -- >>>>> *Rushmin Fernando* >>>>> *Technical Lead* >>>>> >>>>> WSO2 Inc. <http://wso2.com/> - Lean . Enterprise . Middleware >>>>> >>>>> email : rush...@wso2.com >>>>> mobile : +94772310855 >>>>> >>>>> >>>>> >>>>> ___ >>>>> Dev mailing list >>>>> Dev@wso2.org >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> Best Regards >>>> Isuru Ranawaka >>>> M: +94714629880 >>>> Blog : http://isurur.blogspot.com/ >>>> >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> Ravindra Ranwala >> Software Engineer >> WSO2, Inc: http://wso2.com >> <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> >> Mobile: +94714198770 >> >> > > > -- > *Rushmin Fernando* > *Technical Lead* > > WSO2 Inc. <http://wso2.com/> - Lean . Enterprise . Middleware > > email : rush...@wso2.com > mobile : +94772310855 > > > -- Ravindra Ranwala Software Engineer WSO2, Inc: http://wso2.com <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> Mobile: +94714198770 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [ESB] How does content aware mediators behave with nhttp transport ?
Hi Rushmin, If the mediator is a content aware one, the Axis2 Engine should build the message using a message builder into our internal canonical form before passing it to the mediate method of the content aware mediator. The mediate method accepts that internal canonical format and conducts the mediation on it. Building the message is NOT a responsibility of the mediator. For an example instance a Filter mediator with a regular xpath expression which accesses message content can be considered as a content aware mediator. Thanks & Regards, On Thu, Oct 23, 2014 at 11:04 PM, Rushmin Fernando wrote: > Thanks isuru for the detailed reply! > > So when a message is passed to the mediate() method, is it prebuilt if the > mediator is a content aware one? Or is it the respinsibility of the > mediator to build the message? > On Oct 23, 2014 1:04 PM, "Isuru Ranawaka" wrote: > >> Hi Rushmin, >> >> According to the nhttp architecture it uses two buffers for request >> read(Input Stream) and request write to BE(output stream). But those two >> buffers has raw byte stream.But in the mediation layer requests are >> represent as OMElements.So InputStream is need to convert OMElement and >> again to OutputStream so that is handle by Axis2 Level message builders >> and formatters. Message builders create OMElement from input stream and >> formatters again serialized it. So before moving to mediation layer >> messages are converted to OMElement but this not fully build of the message >> this is only partially build because it uses Steaming API (Stax parser) how >> ever it has significant build overhead comparing to raw byte stream. >> >> If mediators are content aware then message is actually fully read to >> the memory by Streaming API. But if you used binary relay in nhttp >> transport then messages are processed as byte streams with out partially or >> fully building of the message.But it can not be used with content aware >> mediators. >> >> thanks >> IsuruR >> >> On Thu, Oct 23, 2014 at 9:30 PM, Rushmin Fernando >> wrote: >> >>> Does the framework build the message before it submits a message for >>> mediation to a content aware mediator >>> >>> or >>> >>> does it build the message upfront if there is a content mediator in >>> possible sequence paths ? >>> >>> Thanks >>> Rushmin >>> >>> >>> >>> -- >>> *Rushmin Fernando* >>> *Technical Lead* >>> >>> WSO2 Inc. <http://wso2.com/> - Lean . Enterprise . Middleware >>> >>> email : rush...@wso2.com >>> mobile : +94772310855 >>> >>> >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> Best Regards >> Isuru Ranawaka >> M: +94714629880 >> Blog : http://isurur.blogspot.com/ >> > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Ravindra Ranwala Software Engineer WSO2, Inc: http://wso2.com <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> Mobile: +94714198770 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Write integration test for new osgi service.
Hi Danesh, The way you write an integration tests depend on your product. Based on that you have to extend a specific class and write integration tests. For an instance if the product is ESB you have to extend the ESBIntegrationTest class. Also you have to patch the product with the new artifact to test that functionality. If you have a module where integration tests have already been written then you can merely add the necessary test cases to that module. For more information please refer this documentation [1]. [1.] https://docs.wso2.com/display/TA430/WSO2+Test+Automation+Documentation Thanks & Regards, On Tue, Oct 21, 2014 at 7:33 AM, Danesh Kuruppu wrote: > Hi all, > > I wrote new osgi service to expose configuration context. Need to write > integration test case for that. what is the best way I could follow. > > Please help > > Thanks > -- > > Danesh Kuruppu > Software Engineer > WSO2 Inc, > Mobile: +94 (77) 1690552 > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Ravindra Ranwala Software Engineer WSO2, Inc: http://wso2.com <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> Mobile: +94714198770 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Google Spreadsheet connector OAuth2 Authorization support
Hi Malaka, We neither store new tokens for consequent calls nor obtain a new token for each task execution. We obtain tokens only once when the connection is created and it is stored. We pass Access token and refresh token (stored previously) to the Google spreadsheet API (gdata spreadsheet) which internally handles token expiration related stuffs. Spreadsheet API conducts an offline access to the protected resource using the given tokens. Thanks & Regards, On Fri, Oct 17, 2014 at 10:38 AM, Malaka Silva wrote: > Hi Ravindra, > > When the access token is expired, using the refresh token we can obtain a > new token. Are we storing back the new token for the consequent calls? or > are we getting a new token for each execution cycle? > > Best Regards, > Malaka > > On Fri, Oct 17, 2014 at 8:55 AM, Ravindra Ranwala > wrote: > >> Hi Manoj, >> >> I have given this proxy configuration just for testing purposes. But you >> can use our iPAAS recipe app to fetch the access tokens and refresh tokens. >> Here we are using refresh tokens for offline access to a protected >> resource. If the Access token is expired, we may use the refresh token to >> obtain a new one. User should have access and refresh tokens obtained >> beforehand to use this. The connector uses those tokens to access >> resources. For an example read set of Tweets from a tweeter account and >> write them back to a Google spreadsheet. You may parametrize this and >> trigger an ESB task to get the work done. >> >> >> Thanks & Regards, >> >> On Fri, Oct 17, 2014 at 8:20 AM, Manoj Gunawardena >> wrote: >> >>> Hi Ravindra, >>> >>> proxy contains oauth acess token and refresh token, How those tokens >>> fetch? Is there a service to fetch those token. Once the tokens expires, >>> how new tokens add to the proxy? This proxy creates dynamically? >>> >>> >>> Thanks >>> >>> On Thu, Oct 16, 2014 at 8:33 AM, Ravindra Ranwala >>> wrote: >>> >>>> Hi All, >>>> >>>> I have added OAuth 2 Authorization support for Google spreadsheet >>>> connector. Using that now we can create a proxy/recipe which filters out >>>> set of tweets from the twitter connector and writes back to a Google >>>> spreadsheet via Google spreadsheet OAuth 2 connector support. I have given >>>> the git repo location here. >>>> >>>> >>>> https://github.com/ravindraranwala/esb-connectors/tree/googlespreadsheet-OAuth2 >>>> >>>> When you create the proxy/recipe please build the above project and use >>>> the Google spreadsheet connector created under the target directory and >>>> upload it to the ESB.Make sure to explicitly enable the connector once >>>> uploaded since it is disabled by default. >>>> >>>> A sample Proxy Configuration to read set of Tweets and write it back to >>>> a Google spread sheet is given below. The changes compared to the Google >>>> spreadsheet OAuth 1.0 configuration is highlighted here. >>>> >>>> >>>> >>>> http://ws.apache.org/ns/synapse"; >>>>name=" >>>> twitterToGoogleSpreadsheetProxy" >>>>transports="https,http" >>>>statistics="disable" >>>>trace="disable" >>>>startOnLoad="true"> >>>> >>>> >>>> >>>> TWITTER_CONSUMER_KEY >>>> TWITTER_CONSUMER_SECRET >>>> TWITTER_ACCESS_TOKEN >>>> >>>> TWITTER_ACCESS_TOKEN_SECRET >>>> >>>> >>>> tuesday >>>> en >>>> >>>> >>>> >>>> ** >>>> GOOGLE_CONSUMER_KEY >>>> <http://212972391932-3thmh0maoodoin7t116vb0adpjjvckv0.apps.googleusercontent.com> >>>> >>>> >>>> GOOGLE_CONSUMER_SECRET >>>> >>>> * >>>> GOOGLE_ACCESS_TOKEN >>>> GOOGLE_REFRESH_TOKEN* >>>> ** >>>> >>>> Tweets >>>> Sheet1 >>>> true >>>> 100 >>>> >>>> >>>> >>>> >>>> >>>> >>>>
Re: [Dev] Google Spreadsheet connector OAuth2 Authorization support
Hi Manoj, I have given this proxy configuration just for testing purposes. But you can use our iPAAS recipe app to fetch the access tokens and refresh tokens. Here we are using refresh tokens for offline access to a protected resource. If the Access token is expired, we may use the refresh token to obtain a new one. User should have access and refresh tokens obtained beforehand to use this. The connector uses those tokens to access resources. For an example read set of Tweets from a tweeter account and write them back to a Google spreadsheet. You may parametrize this and trigger an ESB task to get the work done. Thanks & Regards, On Fri, Oct 17, 2014 at 8:20 AM, Manoj Gunawardena wrote: > Hi Ravindra, > > proxy contains oauth acess token and refresh token, How those tokens > fetch? Is there a service to fetch those token. Once the tokens expires, > how new tokens add to the proxy? This proxy creates dynamically? > > > Thanks > > On Thu, Oct 16, 2014 at 8:33 AM, Ravindra Ranwala > wrote: > >> Hi All, >> >> I have added OAuth 2 Authorization support for Google spreadsheet >> connector. Using that now we can create a proxy/recipe which filters out >> set of tweets from the twitter connector and writes back to a Google >> spreadsheet via Google spreadsheet OAuth 2 connector support. I have given >> the git repo location here. >> >> >> https://github.com/ravindraranwala/esb-connectors/tree/googlespreadsheet-OAuth2 >> >> When you create the proxy/recipe please build the above project and use >> the Google spreadsheet connector created under the target directory and >> upload it to the ESB.Make sure to explicitly enable the connector once >> uploaded since it is disabled by default. >> >> A sample Proxy Configuration to read set of Tweets and write it back to a >> Google spread sheet is given below. The changes compared to the Google >> spreadsheet OAuth 1.0 configuration is highlighted here. >> >> >> >> http://ws.apache.org/ns/synapse"; >>name=" >> twitterToGoogleSpreadsheetProxy" >>transports="https,http" >>statistics="disable" >>trace="disable" >>startOnLoad="true"> >> >> >> >> TWITTER_CONSUMER_KEY >> TWITTER_CONSUMER_SECRET >> TWITTER_ACCESS_TOKEN >> >> TWITTER_ACCESS_TOKEN_SECRET >> >> >> tuesday >> en >> >> >> >> ** >> GOOGLE_CONSUMER_KEY >> <http://212972391932-3thmh0maoodoin7t116vb0adpjjvckv0.apps.googleusercontent.com> >> >> >> GOOGLE_CONSUMER_SECRET >> >> * >> GOOGLE_ACCESS_TOKEN >> GOOGLE_REFRESH_TOKEN* >> ** >> >> Tweets >> Sheet1 >> true >> 100 >> >> >> >> >> >> >> >> >> Thanks & Regards, >> >> >> -- >> Ravindra Ranwala >> Software Engineer >> WSO2, Inc: http://wso2.com >> <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> >> Mobile: +94714198770 >> >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Manoj Gunawardena > Tech Lead > WSO2, Inc.: http://wso2.com > lean.enterprise.middleware > Mobile : +94 77 2291643 > -- Ravindra Ranwala Software Engineer WSO2, Inc: http://wso2.com <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> Mobile: +94714198770 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Google Spreadsheet connector OAuth2 Authorization support
Hi All,
I have added OAuth 2 Authorization support for Google spreadsheet
connector. Using that now we can create a proxy/recipe which filters out
set of tweets from the twitter connector and writes back to a Google
spreadsheet via Google spreadsheet OAuth 2 connector support. I have given
the git repo location here.
https://github.com/ravindraranwala/esb-connectors/tree/googlespreadsheet-OAuth2
When you create the proxy/recipe please build the above project and use the
Google spreadsheet connector created under the target directory and upload
it to the ESB.Make sure to explicitly enable the connector once uploaded
since it is disabled by default.
A sample Proxy Configuration to read set of Tweets and write it back to a
Google spread sheet is given below. The changes compared to the Google
spreadsheet OAuth 1.0 configuration is highlighted here.
http://ws.apache.org/ns/synapse";
name="
twitterToGoogleSpreadsheetProxy"
transports="https,http"
statistics="disable"
trace="disable"
startOnLoad="true">
TWITTER_CONSUMER_KEY
TWITTER_CONSUMER_SECRET
TWITTER_ACCESS_TOKEN
TWITTER_ACCESS_TOKEN_SECRET
tuesday
en
**
GOOGLE_CONSUMER_KEY
<http://212972391932-3thmh0maoodoin7t116vb0adpjjvckv0.apps.googleusercontent.com>
GOOGLE_CONSUMER_SECRET
*
GOOGLE_ACCESS_TOKEN
GOOGLE_REFRESH_TOKEN*
**
Tweets
Sheet1
true
100
Thanks & Regards,
--
Ravindra Ranwala
Software Engineer
WSO2, Inc: http://wso2.com
<http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg>
Mobile: +94714198770
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] What is the standard way of handling exceptions
Hi Dinesh,
The way you handle an Exception is subjective and depends on the context.
But there is one important thing to note. That is never ever do something
like this unless you have an extremely valid reason.
try{
// Some code goes here
//
} catch (Exception ignored) {
// Do Nothing Just IGNORE
}
This is called as swallowing an Exception and will make your day today life
very difficult since it hides the exception. It neither logs the exception
nor throws it. So It is very difficult to find errors with these sort of
codes in your code base.
Thanks &Regards,
On Fri, Oct 10, 2014 at 10:16 AM, Waruna Perera wrote:
> Hi Danesh,
>
> In integration tests we used to log the exception and throw it. The reason
> is the result will be included in the testng reports.
>
> Thanks
>
> On Wed, Oct 8, 2014 at 9:24 AM, Danesh Kuruppu wrote:
>
>> One more question, why we do both log exception and throw it inside
>> handleException?. It will result in multiple log messages in log file, for
>> a single problem in the code.
>>
>> On Thu, Oct 2, 2014 at 9:32 AM, Dinesh J Weerakkody
>> wrote:
>>
>>> Hi,
>>>
>>> I'm just curious about the stranded way of handling exceptions in WSO2
>>> products. When I go through source code, I found that we use
>>> handleException method in some places (in some places use deferent method
>>> such as create new exceptions, catch, log and ignore, etc.) Can someone
>>> explain the standard exception handling mechanism in WSO2 products and it
>>> will be very helpful for newcomers also. (use cases for each case like when
>>> to use what method).
>>>
>>>
>>> When it comes to handleException method, I have another question.
>>>
>>>
>>> *Current handle exception method*
>>> public void handleException(String msg, Exception e) throws
>>> ProductException{
>>> log.error(msg, e);
>>> throw new ProductException(msg, e);
>>> }
>>>
>>> *Problem*
>>> class One{
>>> public void methodOne() {
>>> try {
>>> Two two = new Two();
>>> two.methodTwo();
>>> } catch (WhateverException e) {
>>> handleException("Whatever exception message", e);
>>> }
>>> }
>>> }
>>>
>>> class Two{
>>> public void methodTwo() {
>>> try {
>>> // Database manipulation code goes here
>>> } catch (SQLException e) {
>>> handleException("Cannot complete the transaction", e);
>>> }
>>> }
>>> }
>>>
>>> In handleException method we always create a new Exception. When we have
>>> multiple method calls, there will be duplicate stacktraces and the actual
>>> exception is printed in very latter part of the stack trace. Sometimes it
>>> is bit difficult to trace an error. Is there any specific reason to create
>>> new exceptions inside handleException method, instead of throwing same
>>> exception object if the exceptions is an instance of ProductException like
>>> below sample.
>>>
>>> public void handleException(String msg, Exception e) throws
>>> ProductException{
>>> log.error(msg, e);
>>> if(e instanceof ProductException)
>>>throw e;
>>> throw new ProductException(msg, e);
>>> }
>>>
>>> Thank you.
>>>
>>>
>>> --
>>>
>>> *Dinesh J. Weerakkody*
>>> Software Engineer
>>> WSO2 Inc.
>>> lean | enterprise | middleware
>>> M : +94 727 361788 | E : dine...@wso2.com | W : www.wso2.com
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>> Danesh Kuruppu
>> Software Engineer
>> WSO2 Inc,
>> Mobile: +94 (77) 1690552
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Waruna Perera
> Senior Software Engineer - Test Automation
> Mobile: +94 77 3867037
> WSO2, Inc.; http://wso2.com/
> lean . enterprise . middlewear.
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
--
Ravindra Ranwala
Software Engineer
WSO2, Inc: http://wso2.com
<http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg>
Mobile: +94714198770
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] ESB build error
Hi Chamin, >From which location are you building this project. Try it with -e switch and see. Regards, On Thu, Oct 9, 2014 at 11:45 AM, Chamin Nalinda wrote: > Error message says fails to collect dependencies for jars > > -- start - > > [INFO] > > [INFO] Reactor Summary: > [INFO] > [INFO] WSO2 ESB - Aggregator Module .. SUCCESS [0.317s] > [INFO] WSO2 ESB - Styles Parent .. SUCCESS [0.012s] > [INFO] WSO2 ESB - Styles . SUCCESS [4.901s] > [INFO] WSO2 Stratos ESB - Styles . SUCCESS [0.210s] > [INFO] WSO2 ESB - Samples Parent . SUCCESS [0.011s] > [INFO] WSO2 ESB - Samples FAILURE [4.441s] > [INFO] WSO2 Stratos ESB - Samples SKIPPED > [INFO] WSO2 ESB - Features Parent SKIPPED > [INFO] WSO2 ESB - Features Aggregator Module . SKIPPED > [INFO] WSO2 ESB - Styles Features SKIPPED > [INFO] WSO2 ESB - Samples Features ... SKIPPED > [INFO] WSO2 Stratos ESB - Login User Interface ... SKIPPED > [INFO] WSO2 Stratos ESB - Features Aggregator Module . SKIPPED > [INFO] WSO2 Stratos ESB - Login UI Feature ... SKIPPED > [INFO] WSO2 Stratos ESB - Styles Features SKIPPED > [INFO] WSO2 Stratos ESB - Samples Features ... SKIPPED > [INFO] WSO2 ESB - P2 Profile Generation .. SKIPPED > [INFO] WSO2 ESB - Distribution ... SKIPPED > [INFO] WSO2 ESB - Integration Parent . SKIPPED > [INFO] ESB Test Service Module ... SKIPPED > [INFO] Integration Commons Module - ESB test Module .. SKIPPED > [INFO] WSO2 ESB Integration Test Core SKIPPED > [INFO] ESB Mediators Test Module - 1 . SKIPPED > [INFO] ESB Mediators Test Module - 2 . SKIPPED > [INFO] ESB test Module - Sample .. SKIPPED > [INFO] ESB test Module-Transport . SKIPPED > [INFO] ESB test Module-Other . SKIPPED > [INFO] ESB test Module-Service ... SKIPPED > [INFO] ESB UI Test Module SKIPPED > [INFO] Integration Test Reporting SKIPPED > [INFO] WSO2 Carbon - Releases - products - Aggregator Module SKIPPED > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 11.365s > [INFO] Finished at: Thu Oct 09 11:24:57 IST 2014 > [INFO] Final Memory: 20M/736M > [INFO] > > [ERROR] Failed to execute goal on project org.wso2.esb.samples: Could not > resolve dependencies for project > org.wso2.esb:org.wso2.esb.samples:bundle:4.8.1: Failed to collect > dependencies for [org.apache.synapse:synapse-core:jar:2.1.2-wso2v1 > (compile), org.apache.synapse:synapse-commons:jar:2.1.2-wso2v1 (compile), > org.apache.ws.security.wso2:wss4j:jar:1.5.11.wso2v3 (compile), > org.apache.rampart.wso2:rampart-core:jar:1.6.1.wso2v10 (compile), > org.apache.geronimo.specs.wso2:geronimo-jms_1.1_spec:jar:1.1.0.wso2v1 > (compile)]: Failed to read artifact descriptor for > org.apache.ws.security.wso2:wss4j:jar:1.5.11.wso2v3: Could not find > artifact org.wso2.carbon:carbon-parent:pom:4.0.0-SNAPSHOT in wso2-nexus ( > http://maven.wso2.org/nexus/content/groups/wso2-public/) -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the > -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, > please read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException > [ERROR] > [ERROR] After correcting the problems, you can resume the build with the > command > [ERROR] mvn -rf :org.wso2.esb.samples > > > -- end -- > > > -- > *Chamin Nalinda* > > Intern - Engineering > WSO2 Inc. http://www.wso2.com > lean.enterprise.middleware > > Mobile: (+94) 77 241 66 04 > Linkedin: https://www.linkedin.com/in/chaminnalinda > Web: http://www.ckreativity.com > Blog: http://techspiro.blogspot.com/ > > > ___
Re: [Dev] Error when running Cassandra: java.lang.ClassNotFoundException
Hi Bhathiya, That is based on the assumption that you are using a Cassandra version 2.* or later. If it a really older version as you mentioned 1.* it may not be the case. For further information refer to[1]. I have encountered with the same issue when I was doing my project using Cassandra version 2.0.8. Here I am referring to recent versions. [1.] https://wiki.apache.org/cassandra/GettingStarted Regards, On Tue, Oct 7, 2014 at 3:05 PM, Bhathiya Jayasekara wrote: > Hi Ravindra, > > On Tue, Oct 7, 2014 at 8:49 AM, Ravindra Ranwala > wrote: > >> Hi Vishanth, >> >> Can you please copy Cassandra into some directory under your $HOME >> directory and execute *./cassandra* command after moving to the >> *$CASSANDRA_HOME/bin* directory. Also make sure to switch your JVM to >> some jdk 1.7 version prior to run the above command since Cassandra needs >> jdk 1.7or later version. >> > > You can't say so without knowing the Cassandra version. Cassandra 1.* does > not need java 1.7. > > @Vishanth, > Regarding the original issue: As some pointed out, this can be a > permission issue. Try unzipping Cassandra into a different location (home, > may be) and check. Or try running as root in your current installation. > (Just to check if it's a permission issue.) > > Thanks, > Bhathiya > > >> As Niranda mentioned this could be a permission issue. Setting the >> $CASSANDRA_HOME environment variable is also optional. >> >> >> Thanks & Regards, >> >> On Mon, Oct 6, 2014 at 5:58 PM, Niranda Perera wrote: >> >>> Hi Vishanth, >>> >>> this might be a permission issue since you have installed in the /opt/ >>> directory. alter the permissions of the directory (perform with care!!!) or >>> try manually downloading a cassandra release as mentioned here [1]. >>> >>> [1] http://wiki.apache.org/cassandra/GettingStarted >>> >>> cheers >>> >>> On Mon, Oct 6, 2014 at 5:10 PM, Dimuthu De Lanerolle >>> wrote: >>> >>>> Reported a similar error here. [1] >>>> >>>> [1] >>>> http://stackoverflow.com/questions/16851308/i-am-getting-this-error-when-i-am-starting-cassandra-server >>>> >>>> >>>> Regards >>>> >>>> On Mon, Oct 6, 2014 at 4:54 PM, Vishanth Balasubramaniam < >>>> vishan...@wso2.com> wrote: >>>> >>>>> Hi, >>>>> >>>>> Getting this following error when I run Cassandra. >>>>> >>>>> root@instance-0001:/opt/cassandra/bin# cassandra >>>>> root@instance-0001:/opt/cassandra/bin# Exception in thread "main" >>>>> java.lang.NoClassDefFoundError: >>>>> org/apache/cassandra/service/CassandraDaemon >>>>> Caused by: java.lang.ClassNotFoundException: >>>>> org.apache.cassandra.service.CassandraDaemon >>>>> at java.net.URLClassLoader$1.run(URLClassLoader.java:202) >>>>> at java.security.AccessController.doPrivileged(Native Method) >>>>> at java.net.URLClassLoader.findClass(URLClassLoader.java:190) >>>>> at java.lang.ClassLoader.loadClass(ClassLoader.java:307) >>>>> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) >>>>> at java.lang.ClassLoader.loadClass(ClassLoader.java:248) >>>>> Could not find the main class: >>>>> org.apache.cassandra.service.CassandraDaemon. Program will exit. >>>>> >>>>> I tried the commands cassandra, cassandra -f, cassandra -f start, >>>>> which all prompted me the same error. >>>>> >>>>> I believe this could be because of incorrect Classpath, I would like >>>>> to know how to set the Classpath correctly. >>>>> >>>>> Thank you, >>>>> >>>>> -- >>>>> *Vishanth Balasubramaniam* >>>>> Software Engineer >>>>> WSO2 Inc.; http://wso2.com >>>>> lean.enterprise.middleware >>>>> >>>>> mobile: *+94771737718* >>>>> about me: *http://about.me/vishanth <http://about.me/vishanth>* >>>>> >>>>> >>>>> ___ >>>>> Dev mailing list >>>>> Dev@wso2.org >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> Dimuthu De Lanerolle >&g
Re: [Dev] Error when running Cassandra: java.lang.ClassNotFoundException
Hi Vishanth, Can you please copy Cassandra into some directory under your $HOME directory and execute *./cassandra* command after moving to the *$CASSANDRA_HOME/bin* directory. Also make sure to switch your JVM to some jdk 1.7 version prior to run the above command since Cassandra needs jdk 1.7or later version. As Niranda mentioned this could be a permission issue. Setting the $CASSANDRA_HOME environment variable is also optional. Thanks & Regards, On Mon, Oct 6, 2014 at 5:58 PM, Niranda Perera wrote: > Hi Vishanth, > > this might be a permission issue since you have installed in the /opt/ > directory. alter the permissions of the directory (perform with care!!!) or > try manually downloading a cassandra release as mentioned here [1]. > > [1] http://wiki.apache.org/cassandra/GettingStarted > > cheers > > On Mon, Oct 6, 2014 at 5:10 PM, Dimuthu De Lanerolle > wrote: > >> Reported a similar error here. [1] >> >> [1] >> http://stackoverflow.com/questions/16851308/i-am-getting-this-error-when-i-am-starting-cassandra-server >> >> >> Regards >> >> On Mon, Oct 6, 2014 at 4:54 PM, Vishanth Balasubramaniam < >> vishan...@wso2.com> wrote: >> >>> Hi, >>> >>> Getting this following error when I run Cassandra. >>> >>> root@instance-0001:/opt/cassandra/bin# cassandra >>> root@instance-0001:/opt/cassandra/bin# Exception in thread "main" >>> java.lang.NoClassDefFoundError: org/apache/cassandra/service/CassandraDaemon >>> Caused by: java.lang.ClassNotFoundException: >>> org.apache.cassandra.service.CassandraDaemon >>> at java.net.URLClassLoader$1.run(URLClassLoader.java:202) >>> at java.security.AccessController.doPrivileged(Native Method) >>> at java.net.URLClassLoader.findClass(URLClassLoader.java:190) >>> at java.lang.ClassLoader.loadClass(ClassLoader.java:307) >>> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) >>> at java.lang.ClassLoader.loadClass(ClassLoader.java:248) >>> Could not find the main class: >>> org.apache.cassandra.service.CassandraDaemon. Program will exit. >>> >>> I tried the commands cassandra, cassandra -f, cassandra -f start, which >>> all prompted me the same error. >>> >>> I believe this could be because of incorrect Classpath, I would like to >>> know how to set the Classpath correctly. >>> >>> Thank you, >>> >>> -- >>> *Vishanth Balasubramaniam* >>> Software Engineer >>> WSO2 Inc.; http://wso2.com >>> lean.enterprise.middleware >>> >>> mobile: *+94771737718* >>> about me: *http://about.me/vishanth <http://about.me/vishanth>* >>> >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> Dimuthu De Lanerolle >> Software Engineer >> WSO2 Inc. >> lean . enterprise . middlewear. >> http://wso2.com/ >> Tel. : +94 11 2145345 Fax : +94 11 2145300 email : dimut...@wso2.com >> >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > *Niranda Perera* > Software Engineer, WSO2 Inc. > Mobile: +94-71-554-8430 > Twitter: @n1r44 <https://twitter.com/N1R44> > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Ravindra Ranwala Software Engineer WSO2, Inc: http://wso2.com <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> Mobile: +94714198770 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
