[teiid-issues] [JBoss JIRA] Commented: (TEIID-1388) Appears to be a limit of only one functional SalesForce connector in Teiid at a time.

[ https://issues.jboss.org/browse/TEIID-1388?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-1388: ------------------------------------- According to the test attached at least in the demo/developer Salesforce connections, SF only grant at most one "session" at any given time. Yes, you can call "login" as many times, but it will return the same session-id, whether it is from same VM or different VMs. However, once you call the "logout" all the connections which are of the same session are closed. So, it may not appropriate actually do a "logout " of a session any time from the connection pool as it will invalidate all the connection objects. Luckily Teiid is not doing any "logout" right now, so we need keep this way. Now, to the actual problem of not creating more than single connection, and why it is working in 7.2 and not in SOA. The variable here is CXF 7.2 - CXF may not be in use, and default JAX-WS in use, this one uses the default endpoint from Service class, that is in the WSDL. SOA - CXF is in use, first time the endpoint is correctly set from the WSDL, however after that it set to default location, that will resolve to "127.0.0.1:8443" that will fail to make connection. Resolution: Set the end point on port binding from user configuration. User is already been asked to supply the endpoint but it was not being used. Like ((BindingProvider)sfSoap).getRequestContext().put(BindingProvider.ENDPOINT_ADDRESS_PROPERTY, "https://www.salesforce.com/services/Soap/u/17.0"); then issue login. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira