]
Tim Walsh resolved TEIID-100.
-----------------------------
Resolution: Done
/teiid/connectors/connector-salesforce/src/main/java/com/metamatrix/connector/salesforce/connection/impl/ConnectionImpl.java
added exception case.
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_cal...
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: