[teiid-issues] [JBoss JIRA] Assigned: (TEIID-100) Salesforce connector should explicitly handle InvalidQueryLocatorFault
Tim Walsh (JIRA)
jira-events at lists.jboss.org
Tue Apr 21 00:03:22 EDT 2009
[ https://jira.jboss.org/jira/browse/TEIID-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tim Walsh reassigned TEIID-100:
-------------------------------
Assignee: Tim Walsh (was: John Doyle)
> Salesforce connector should explicitly handle InvalidQueryLocatorFault
> ----------------------------------------------------------------------
>
> Key: TEIID-100
> URL: https://jira.jboss.org/jira/browse/TEIID-100
> Project: Teiid
> Issue Type: Bug
> Components: Salesforce Connector
> Affects Versions: 6.x
> Environment: SFDC 5.5GA Connector; MM Designer 5.5.2 0037 Linux
> Reporter: Greg Haber
> Assignee: Tim Walsh
> Fix For: 6.x
>
>
> There is a hard limit of 5 on the number of handles a single Salesforce user can have to server side result sets - see http://www.salesforce.com/us/developer/docs/api100/Content/sforce_api_calls_query_querylocator.htm
> This means, that in cases where a customer is doing a lot of queries that return large result sets (larger than SF will return in a single SOAP response), it is very possible that they will run into this limit. This limit should manifest itself as an InvalidQueryLocatorFault thrown when the Salesforce queryMore() operation is called.
> I see in the current code (queryMore method of com.metamatrix.connector.salesforce.connection.impl.ConnectionImpl) that we don't explicitly catch this fault. We should catch this fault and throw a ConnectorException that clearly explains what is happening (if the message SFDC returns here isn't clear enough).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the teiid-issues
mailing list