date:20170114

Re: [Dev] Help required

2017-01-14 Thread Malaka Silva

Hi Amit,

When you do toString in the class mediator it build the complete DOM into
the memory. In this case streaming does not make any sense.

ESB itself need memory for some additional tasks that maybe the reason your
java app worked without any issues.

To get more details on this better if you could profile the memory usage
when the file is processing and afterwards.

On Thu, Jan 12, 2017 at 3:06 PM, Amit Rajvanshi <
amit.rajvan...@eperiumindia.com> wrote:

> Hello WSO2 dev ,
>
>
>
> Thanks Malaka for your reply but streaming in Inbound endpoint did not
> work for my case.
>
> If I set JVM to *-Xms1024m -Xmx4096m -XX:MaxPermSize=2048m *under eclipse
> configuration then only it start processing of the file otherwise it
> failed to read message from Message context in Custom mediator.
>
>
>
> *Code in custom mediator :*
>
>
>
> public boolean mediate(MessageContext context) {
>
>   SOAPEnvelope envelope = context.getEnvelope();
>
>   SOAPBody soapBody = envelope.getBody();
>
>   OMElement omElement = soapBody.getFirstElement();
>
>   String xmlString = omElement.toString();
>
>   formEnrichedXml(xmlString, context);
>
>   return true;
>
> }
>
>
>
>
>
> My concern is that if we are following correct approach to process 140 MB
> XML file or increasing memory is wrong approach and something else is wrong
> with the code.
>
> I also tried with a sample application with iterate mediator to split this
> file on each instance of the element in the xml with default configuration
> but also it failed to execute and given me same error 
> *(*java.lang.OutOfMemoryError:
> Java heap space*) *and works fine if I increase memory limit to 4 GB.
>
> I have also tried with on simple java class to read this file and it
> worked fine without increasing any memory :
>
> DocumentBuilderFactory docFactory = DocumentBuilderFactory.newInstance();
>
> DocumentBuilder docBuilder;
>
> try
>
> {
>
> docBuilder = docFactory.newDocumentBuilder();
>
> Document doc = docBuilder.parse("G://
> 20170105_114800_PRODUCT.XML");
>
>
>
> NodeList rootChilds = doc.getDocumentElement().
> getChildNodes();
>
> System.out.println(rootChilds.getLength());
>
>
>
> for (int i = 0; i < rootChilds.getLength(); i++)
>
> {
>
> Node rootChild = rootChilds.item(i);
>
> System.out.println(rootChild.getNodeName());
>
> }
>
>
>
> System.out.println(111);
>
> }
>
> catch(Exception e)
>
> {
>
> // TODO Auto-generated catch block
>
> e.printStackTrace();
>
> }
>
>
>
> XML file contains 57000 instance of an object which size is around 140 MB
> which does not seems big file to me.
>
>
>
> Please suggest if memory increase is the only way to process this file.
>
>
>
> Best regards,
> *Amit Rajvanshi*
> Eperium Business Solutions (I) Pvt Ltd,
> B-13, Sector 57,
> Noida (U.P.) - 201301
> Phone: +91-120-4737401 <+91%20120%20473%207401>
> Web: www.eperiumindia.com
>
> *Shaping future commerce together*
>
> This message may contain confidential or legally privileged information.
> In the event of any error in transmission, unauthorized recipients are
> requested to contact the sender immediately and not to disclose or make use
> of this information. No warranties or assurance are made or given as to the
> accuracy of the information given or in relation to the safety of this
> e-mail and any attachments. No liability whatsoever is accepted for any
> consequences arising from this e-mail.
>
>
>
> *From:* Malaka Silva [mailto:mal...@wso2.com]
> *Sent:* 11 January 2017 09:12
> *To:* WSO2 Developers' List
> *Cc:* Amit Rajvanshi; Vivekananthan Sivanayagam
> *Subject:* Fwd: Help required
>
>
>
> Hi Amit,
>
>
>
> Have you tried the streaming with inbound endpoints?
>
>
>
> Also please send your queries to dev@wso2.org. You can cc me. That way
> more people from community can help you. :)
>
>
>
> [1] http://mrmalakasilva.blogspot.com/2016/03/streaming-large-files-using-
> wso2-esb.html
>
> [2] https://docs.wso2.com/display/ESB500/Tuning+the+VFS+Transport
>
> [3] https://docs.wso2.com/display/ESB500/File+Inbound+Protocol
>
>
>
> -- Forwarded message --
> From: *Amit Rajvanshi* 
> Date: Tue, Jan 10, 2017 at 7:05 PM
> Subject: Help required
> To: Malaka Silva 
>
> Hi Malaka,
>
>
>
> We again need your help :
>
>
>
> We are trying to process one xml which contains around 6 instance of
> an object and the size of XML is 140 MB.
>
> We are receiving this file through Inbound endpoint file location and
> doing some changes in custom mediator java code using DOM object.
>
> While we are processing small files around 30 MB it get processed
> successfully but for large files it is giving out of memory error:
>
>
>
> java.lang.OutOfMemoryError: Java heap space
>
>
>
> if we set our JVM to *-Xms2048m -Xmx2048m

Re: [Dev] [Architecture] [VOTE] Release WSO2 API Manager 2.1.0 RC3

2017-01-14 Thread Chamalee De Silva

Hi,

Tested the following for both tenant and super tenant users.

   - Database functionalities with following databases.

  -  MySQL 5.6, 5.7
  -  Oracle 11g
  -  PostgreSQL  9.3
  -  MSSQL

   - API Invocation scenarios for new REST APIs including sample API.
   - API documentation functionalities
   - API visibility and versioning


[+]  Stable   -   go ahead and release


On Sun, Jan 15, 2017 at 9:33 AM, Nuwandi Wickramasinghe 
wrote:

> Tested following.
>
>- 3rd party key management for super tenant and tenant users
>- APIMANAGER-5530
>- APIMANAGER-5510
>- APIMANAGER-5370
>
> [+] Stable - go ahead and release
>
> On Fri, Jan 13, 2017 at 6:23 PM, Malintha Amarasinghe 
> wrote:
>
>> Hi All,
>>
>> This is the 3rd Release Candidate of WSO2 API Manager 2.1.0
>>
>> Please download, test the product and vote. The vote will be open for 72
>> hours or as needed.
>>
>> Source and distribution
>>
>> Run-time : https://github.com/wso2/product-apim/releases/download/v2.
>> 1.0-rc3/wso2am-2.1.0-RC3.zip
>> Analytics : https://github.com/wso2/anal
>> ytics-apim/releases/download/v2.1.0-rc2/wso2am-analytics-2.1.0-RC2.zip
>> Tooling : https://github.com/wso2/devstudio-tooling-apim/releases/ta
>> g/v2.1.0-rc2
>>
>>
>> This release fixes the following issues:
>> Runtime : https://wso2.org/jira/issues/?filter=13623
>> Analytics : https://wso2.org/jira/issues/?filter=13624
>> Tooling : https://wso2.org/jira/browse/DEVTOOLAPI-1
>>
>>
>> Please vote as follows.
>> [+] Stable - go ahead and release
>> [-] Broken - do not release (explain why)
>>
>>
>> Thanks,
>> - WSO2 API Manager Team -
>>
>> --
>> Malintha Amarasinghe
>> Software Engineer
>> *WSO2, Inc. - lean | enterprise | middleware*
>> http://wso2.com/
>>
>> Mobile : +94 712383306 <+94%2071%20238%203306>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> Best Regards,
>
> Nuwandi Wickramasinghe
>
> Software Engineer
>
> WSO2 Inc.
>
> Web : http://wso2.com
>
> Mobile : 0719214873
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
Thanks & Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. :http://wso2.com/

Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [VOTE] Release WSO2 IoT Server 3.0.0 RC1

2017-01-14 Thread Rasika Perera

Hi Devs,

*WSO2 IoT Server 3.0.0-RC1 Released*

This is the 1st Release Candidate of the WSO2
IoT Server

3
.0.0

Please download, test the product and vote. Vote will be open for 72 hours
or as needed.
**Known issues  :
 https://wso2.org/jira/issues/?filter=13634
Fixes provided :
https://wso2.org/jira/issues/?filter=13635

*Source and binary distribution files:*
https://github.com/wso2/product-iots/releases/tag/v3.0.0-RC

*The tag to be voted upon:*
https://github.com/wso2/product-iots/tree/v3.0.0-RC

Please vote as follows.
[+] Stable - go ahead and release
[-] Broken - do not release (explain why)

Thanks,
~WSO2 IoT Team~

-- 
With Regards,

*Rasika Perera*
Software Engineer
LinkedIn: http://lk.linkedin.com/in/rasika90



WSO2 Inc. www.wso2.com
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 API Manager 2.1.0 RC3

2017-01-14 Thread Nuwandi Wickramasinghe

Tested following.

   - 3rd party key management for super tenant and tenant users
   - APIMANAGER-5530
   - APIMANAGER-5510
   - APIMANAGER-5370

[+] Stable - go ahead and release

On Fri, Jan 13, 2017 at 6:23 PM, Malintha Amarasinghe 
wrote:

> Hi All,
>
> This is the 3rd Release Candidate of WSO2 API Manager 2.1.0
>
> Please download, test the product and vote. The vote will be open for 72
> hours or as needed.
>
> Source and distribution
>
> Run-time : https://github.com/wso2/product-apim/releases/
> download/v2.1.0-rc3/wso2am-2.1.0-RC3.zip
> Analytics : https://github.com/wso2/analytics-apim/releases/download/
> v2.1.0-rc2/wso2am-analytics-2.1.0-RC2.zip
> Tooling : https://github.com/wso2/devstudio-tooling-apim/releases/
> tag/v2.1.0-rc2
>
>
> This release fixes the following issues:
> Runtime : https://wso2.org/jira/issues/?filter=13623
> Analytics : https://wso2.org/jira/issues/?filter=13624
> Tooling : https://wso2.org/jira/browse/DEVTOOLAPI-1
>
>
> Please vote as follows.
> [+] Stable - go ahead and release
> [-] Broken - do not release (explain why)
>
>
> Thanks,
> - WSO2 API Manager Team -
>
> --
> Malintha Amarasinghe
> Software Engineer
> *WSO2, Inc. - lean | enterprise | middleware*
> http://wso2.com/
>
> Mobile : +94 712383306 <+94%2071%20238%203306>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

Best Regards,

Nuwandi Wickramasinghe

Software Engineer

WSO2 Inc.

Web : http://wso2.com

Mobile : 0719214873
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [IS6 M1] LDAP Userstore implementation and documentation

2017-01-14 Thread Samuel Gnaniah

I checked the readme in Github and it doesn't have any content added. Is it
possible to provide tested steps for this for documentation?

Also, will this be common to all C5 products or is it only for IS?

*Samuel Gnaniah*
Lead Technical Writer

WSO2 (pvt.) Ltd.
Colombo, Sri Lanka
(+94) 773131798

On Sat, Jan 14, 2017 at 10:41 PM, KasunG Gajasinghe  wrote:

>
>
> On Sat, Jan 14, 2017 at 9:29 PM, Ishara Karunarathna 
> wrote:
>
>> Hi Kasun,
>>
>> On Sat, Jan 14, 2017 at 6:58 PM, KasunG Gajasinghe 
>> wrote:
>>
>>> Hi,
>>>
>>> Opening this thread to keep track of the LDAP userstore feature that
>>> goes into the M1. We are on the final stage of this implementation which is
>>> maintained at [1]. @Ishara is working on this.
>>>
>> Are we going to track all the features via mails ?
>> I think all should be tracked with users stories.
>>
>
> Yes. User stories and mails serve for two different purposes, isn't it?
> This is to have discussions, make sure that everyone is on the same page.
>
>
>
>>
>>> We need to get the PR for carbon-jndi merged [2] since the current JNDI
>>> impl does not load JNDI provides coming from the JRE.
>>>
>>> @Samuel, please note on docs.
>>>
>>> [1] https://github.com/wso2-extensions/carbon-security-user-store-ldap
>>> [2] https://github.com/wso2/carbon-jndi/pull/32
>>>
>>> --
>>>
>>> *Kasun Gajasinghe*Associate Technical Lead, WSO2 Inc.
>>> email: kasung AT spamfree wso2.com
>>> linked-in: http://lk.linkedin.com/in/gajasinghe
>>> blog: http://kasunbg.org
>>> phone: +1 650-745-4499 <(650)%20745-4499>, 77 678 0813
>>>
>>>
>>
>>
>>
>> --
>> Ishara Karunarathna
>> Associate Technical Lead
>> WSO2 Inc. - lean . enterprise . middleware |  wso2.com
>>
>> email: isha...@wso2.com,   blog: isharaaruna.blogspot.com,   mobile:
>> +94717996791 <071%20799%206791>
>>
>>
>>
>
>
> --
>
> *Kasun Gajasinghe*Associate Technical Lead, WSO2 Inc.
> email: kasung AT spamfree wso2.com
> linked-in: http://lk.linkedin.com/in/gajasinghe
> blog: http://kasunbg.org
> phone: +1 650-745-4499 <(650)%20745-4499>, 77 678 0813
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [IS6 M1] LDAP Userstore implementation and documentation

2017-01-14 Thread KasunG Gajasinghe

On Sat, Jan 14, 2017 at 9:29 PM, Ishara Karunarathna 
wrote:

> Hi Kasun,
>
> On Sat, Jan 14, 2017 at 6:58 PM, KasunG Gajasinghe 
> wrote:
>
>> Hi,
>>
>> Opening this thread to keep track of the LDAP userstore feature that goes
>> into the M1. We are on the final stage of this implementation which is
>> maintained at [1]. @Ishara is working on this.
>>
> Are we going to track all the features via mails ?
> I think all should be tracked with users stories.
>

Yes. User stories and mails serve for two different purposes, isn't it?
This is to have discussions, make sure that everyone is on the same page.



>
>> We need to get the PR for carbon-jndi merged [2] since the current JNDI
>> impl does not load JNDI provides coming from the JRE.
>>
>> @Samuel, please note on docs.
>>
>> [1] https://github.com/wso2-extensions/carbon-security-user-store-ldap
>> [2] https://github.com/wso2/carbon-jndi/pull/32
>>
>> --
>>
>> *Kasun Gajasinghe*Associate Technical Lead, WSO2 Inc.
>> email: kasung AT spamfree wso2.com
>> linked-in: http://lk.linkedin.com/in/gajasinghe
>> blog: http://kasunbg.org
>> phone: +1 650-745-4499 <(650)%20745-4499>, 77 678 0813
>>
>>
>
>
>
> --
> Ishara Karunarathna
> Associate Technical Lead
> WSO2 Inc. - lean . enterprise . middleware |  wso2.com
>
> email: isha...@wso2.com,   blog: isharaaruna.blogspot.com,   mobile:
> +94717996791 <071%20799%206791>
>
>
>


-- 

*Kasun Gajasinghe*Associate Technical Lead, WSO2 Inc.
email: kasung AT spamfree wso2.com
linked-in: http://lk.linkedin.com/in/gajasinghe
blog: http://kasunbg.org
phone: +1 650-745-4499, 77 678 0813
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [IS6 M1] LDAP Userstore implementation and documentation

2017-01-14 Thread Ishara Karunarathna

Hi Kasun,

On Sat, Jan 14, 2017 at 6:58 PM, KasunG Gajasinghe  wrote:

> Hi,
>
> Opening this thread to keep track of the LDAP userstore feature that goes
> into the M1. We are on the final stage of this implementation which is
> maintained at [1]. @Ishara is working on this.
>
Are we going to track all the features via mails ?
I think all should be tracked with users stories.

>
> We need to get the PR for carbon-jndi merged [2] since the current JNDI
> impl does not load JNDI provides coming from the JRE.
>
> @Samuel, please note on docs.
>
> [1] https://github.com/wso2-extensions/carbon-security-user-store-ldap
> [2] https://github.com/wso2/carbon-jndi/pull/32
>
> --
>
> *Kasun Gajasinghe*Associate Technical Lead, WSO2 Inc.
> email: kasung AT spamfree wso2.com
> linked-in: http://lk.linkedin.com/in/gajasinghe
> blog: http://kasunbg.org
> phone: +1 650-745-4499 <(650)%20745-4499>, 77 678 0813
>
>



-- 
Ishara Karunarathna
Associate Technical Lead
WSO2 Inc. - lean . enterprise . middleware |  wso2.com

email: isha...@wso2.com,   blog: isharaaruna.blogspot.com,   mobile:
+94717996791
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [devicemgt-plugins] Nexus: Promotion Completed

2017-01-14 Thread KasunG Gajasinghe

Hi Rasika,

Why don't we setup Continuous Delivery for this repo? :-)

Thanks.

On Sat, Jan 14, 2017 at 7:08 PM, Nexus Repository Manager 
wrote:

> Message from: https://maven.wso2.org/nexus/
>
> *Description:*
>
> releasing cdm plugins 1020
>
>
>
> *Deployer properties:*
>
>- "userAgent" = "Apache-Maven/3.0.5 (Java 1.7.0_51; Linux
>3.13.0-24-generic)"
>- "userId" = "rasi...@wso2.com"
>- "ip" = "172.19.1.133"
>
>
> *Details:*
>
> The following artifacts have been promoted to the "Releases" [id=releases]
>  repository
>
> /org/wso2/carbon/devicemgt-plugins/org.wso2.carbon.
> device.mgt.iot.analytics/3.0.6/org.wso2.carbon.device.mgt.
> iot.analytics-3.0.6.zip
> 
> (SHA1: 0acce7efc9c21fc4484b42b11df44a222108172c)
> /org/wso2/carbon/devicemgt-plugins/org.wso2.carbon.
> device.mgt.iot.analytics/3.0.6/org.wso2.carbon.device.mgt.
> iot.analytics-3.0.6.pom
> 
> (SHA1: 6fe7da342a235957fbb6b6144b4838af843b4e38)
> /org/wso2/carbon/devicemgt-plugins/org.wso2.carbon.
> device.mgt.iot.raspberrypi.analytics/3.0.6/org.wso2.carbon.device.mgt.iot.
> raspberrypi.analytics-3.0.6.pom
> 
> (SHA1: 2ca56e779ec00ae262a012bac1f7b9e05a41b5eb)
> /org/wso2/carbon/devicemgt-plugins/org.wso2.carbon.
> device.mgt.iot.raspberrypi.analytics/3.0.6/org.wso2.carbon.device.mgt.iot.
> raspberrypi.analytics-3.0.6.zip
> 
> (SHA1: f22eb1df7fc7147cdaf8cd0eb234bcef04415253)
> /org/wso2/carbon/devicemgt-plugins/mb-extensions/3.0.6/
> mb-extensions-3.0.6.pom
> 
> (SHA1: 53f7dd41a37254d95c1404ac6785116a1dca5711)
> /org/wso2/carbon/devicemgt-plugins/org.wso2.carbon.
> device.mgt.mobile.windows.feature/3.0.6/org.wso2.carbon.
> device.mgt.mobile.windows.feature-3.0.6.zip
> 
> (SHA1: 44d7e619c880fc6fd10612c201921d56698dd753)
> /org/wso2/carbon/devicemgt-plugins/org.wso2.carbon.
> device.mgt.mobile.windows.feature/3.0.6/org.wso2.carbon.
> device.mgt.mobile.windows.feature-3.0.6.pom
> 
> (SHA1: 045391bcad6a0b47a02c75259ec44d4553cb4f5e)
> /org/wso2/carbon/devicemgt-plugins/windows-plugin/3.0.6/
> windows-plugin-3.0.6.pom
> 
> (SHA1: f01c0fc5dc21d0021435fd91ac45c2c9e0f26faf)
> /org/wso2/carbon/devicemgt-plugins/org.wso2.carbon.device.mgt.iot.
> virtualfirealarm.api/3.0.6/org.wso2.carbon.device.mgt.
> iot.virtualfirealarm.api-3.0.6-sources.jar
> 
> (SHA1: d342b5d2c2d3abf9bc8df07ac16ce3cad552dd00)
> /org/wso2/carbon/devicemgt-plugins/org.wso2.carbon.device.mgt.iot.
> virtualfirealarm.api/3.0.6/org.wso2.carbon.device.mgt.
> iot.virtualfirealarm.api-3.0.6-javadoc.jar
> 
> (SHA1: dd44f059fd99bee41dbfb4cba432af43c222b359)
> /org/wso2/carbon/devicemgt-plugins/org.wso2.carbon.device.mgt.iot.
> virtualfirealarm.api/3.0.6/org.wso2.carbon.device.mgt.
> iot.virtualfirealarm.api-3.0.6.pom
> 
> (SHA1: 76282ae3f8aa28e51d75d45e808a4e2119884ce2)
>

Re: [Dev] [IS6 M1] LDAP Userstore implementation and documentation

2017-01-14 Thread Samuel Gnaniah

Noted.

*Samuel Gnaniah*
Lead Technical Writer

WSO2 (pvt.) Ltd.
Colombo, Sri Lanka
(+94) 773131798

On Sat, Jan 14, 2017 at 6:58 PM, KasunG Gajasinghe  wrote:

> Hi,
>
> Opening this thread to keep track of the LDAP userstore feature that goes
> into the M1. We are on the final stage of this implementation which is
> maintained at [1]. @Ishara is working on this.
>
> We need to get the PR for carbon-jndi merged [2] since the current JNDI
> impl does not load JNDI provides coming from the JRE.
>
> @Samuel, please note on docs.
>
> [1] https://github.com/wso2-extensions/carbon-security-user-store-ldap
> [2] https://github.com/wso2/carbon-jndi/pull/32
>
> --
>
> *Kasun Gajasinghe*Associate Technical Lead, WSO2 Inc.
> email: kasung AT spamfree wso2.com
> linked-in: http://lk.linkedin.com/in/gajasinghe
> blog: http://kasunbg.org
> phone: +1 650-745-4499 <(650)%20745-4499>, 77 678 0813
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [IS6 M1] LDAP Userstore implementation and documentation

2017-01-14 Thread KasunG Gajasinghe

Hi,

Opening this thread to keep track of the LDAP userstore feature that goes
into the M1. We are on the final stage of this implementation which is
maintained at [1]. @Ishara is working on this.

We need to get the PR for carbon-jndi merged [2] since the current JNDI
impl does not load JNDI provides coming from the JRE.

@Samuel, please note on docs.

[1] https://github.com/wso2-extensions/carbon-security-user-store-ldap
[2] https://github.com/wso2/carbon-jndi/pull/32

-- 

*Kasun Gajasinghe*Associate Technical Lead, WSO2 Inc.
email: kasung AT spamfree wso2.com
linked-in: http://lk.linkedin.com/in/gajasinghe
blog: http://kasunbg.org
phone: +1 650-745-4499, 77 678 0813
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Salesforce connector supports for complex queries

2017-01-14 Thread Chanuka Dissanayake

>
> According to the logs there is an error in the query string [1]. It should
> be SELECT Id,Contact_Us_First_Submission_Date__c FROM Lead WHERE Status
> != 'Disqualified' AND Participant_Type__c != 'Partner' AND
> Participant_Type__c != 'Other' AND Contact_Us_First_Submission_Date__c !=
> Null.
>
>
Thanks Kesavan, didn't notice that. It's working now :)


On Sat, Jan 14, 2017 at 11:30 AM, Kesavan Yogarajah 
wrote:

> Hi Chanuka,
>
> According to the logs there is an error in the query string [1]. It should
> be SELECT Id,Contact_Us_First_Submission_Date__c FROM Lead WHERE Status
> != 'Disqualified' AND Participant_Type__c != 'Partner' AND
> Participant_Type__c != 'Other' AND Contact_Us_First_Submission_Date__c !=
> Null.
>
> [1] -
> 
> Id,SELECT Contact_Us_First_Submission_Date__c FROM Lead WHERE Status !=
> 'Disqualified' AND Participant_Type__c != 'Partner' AND Participant_Type__c
> != 'Other' AND Contact_Us_First_Submission_Date__c !=
> Null
>
> Thanks
>
> Kesavan Yogarajah
> Software Engineer
> Mobile :+94 (0) 779 758021 <+94%2077%20975%208021>
> kesav...@wso2.com
> WSO2, Inc.
> lean . enterprise . middleware
>
> On Sat, Jan 14, 2017 at 10:16 AM, Chanuka Dissanayake 
> wrote:
>
>> Hi Malaka,
>>
>> Also are you using latest ESB?
>>>
>>
>> Yes it's, ESB 5.0 and tooling.
>>
>> Maybe issue is related to TLS version?
>>
>>
>> Don't know, whether it have an effect, because it didn't work before they
>> have update to the new version.
>>
>> I have attached the wire log, after invoking the query, it's basically
>> not responding.
>>
>>
>> Thanks,
>> Chanuka.
>>
>> On Fri, Jan 13, 2017 at 8:16 PM, Malaka Silva  wrote:
>>
>>> Hi Chanuka,
>>>
>>> Since we are simple invoking the api it should work.
>>>
>>> Can you share wire logs for further investigation.
>>>
>>> Also are you using latest ESB? Maybe issue is related to TLS version? [1]
>>>
>>> [1] https://help.salesforce.com/servlet/servlet.FileDownload
>>> ?file=0150M03KgGkQAK
>>>
>>> +Dev List
>>> -- Forwarded message --
>>> From: Chanuka Dissanayake 
>>> Date: Fri, Jan 13, 2017 at 6:53 PM
>>> Subject: Salesforce connector supports for complex queries
>>> To: kesavany Yogarajah , Keerthika Mahendralingam <
>>> keerth...@wso2.com>
>>> Cc: Malaka Silva , Shevan Goonetilleke ,
>>> Yasith Tharindu , Suhan Dharmasuriya ,
>>> Nirodha Pramod 
>>>
>>>
>>> Hi Kesavan,
>>>
>>> I have come across that, when querying data from Salesforce connector it
>>> does not retrieving the data, instead it kept waiting. Have you done
>>> anything related to $subject?. Following is the query which is not working
>>> through the connector.
>>>
>>> SELECT Id,Contact_Us_First_Submission_Date__c FROM Lead WHERE Status !=
>>> 'Disqualified' AND Participant_Type__c != 'Partner' AND Participant_Type__c
>>> != 'Other' AND Contact_Us_First_Submission_Date__c != Null
>>> Regards,
>>> Chanuka.
>>> --
>>> Chanuka Dissanayake
>>> *Software Engineer | **WSO2 Inc.*; http://wso2.com
>>>
>>> Mobile: +94 71 33 63 596
>>> Email: chan...@wso2.com
>>>
>>>
>>>
>>> --
>>>
>>> Best Regards,
>>>
>>> Malaka Silva
>>> Senior Technical Lead
>>> M: +94 777 219 791 <+94%2077%20721%209791>
>>> 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
>>> https://wso2.com/signature
>>> http://www.wso2.com/about/team/malaka-silva/
>>> 
>>> https://store.wso2.com/store/
>>>
>>> Don't make Trees rare, we should keep them with care
>>>
>>
>>
>>
>> --
>> Chanuka Dissanayake
>> *Software Engineer | **WSO2 Inc.*; http://wso2.com
>>
>> Mobile: +94 71 33 63 596
>> Email: chan...@wso2.com
>>
>
>


-- 
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

Re: [Dev] Help required

Re: [Dev] [Architecture] [VOTE] Release WSO2 API Manager 2.1.0 RC3

[Dev] [VOTE] Release WSO2 IoT Server 3.0.0 RC1

Re: [Dev] [VOTE] Release WSO2 API Manager 2.1.0 RC3

Re: [Dev] [IS6 M1] LDAP Userstore implementation and documentation

Re: [Dev] [IS6 M1] LDAP Userstore implementation and documentation

Re: [Dev] [IS6 M1] LDAP Userstore implementation and documentation

[Dev] [devicemgt-plugins] Nexus: Promotion Completed

Re: [Dev] [IS6 M1] LDAP Userstore implementation and documentation

[Dev] [IS6 M1] LDAP Userstore implementation and documentation

Re: [Dev] Salesforce connector supports for complex queries

11 matches

Site Navigation

Mail list logo

Footer information