[JBoss JIRA] Created: (TEIID-1388) Appears to be a limit of only one functional SalesForce connector in Teiid at a time.
9:12 p.m.
Appears to be a limit of only one functional SalesForce connector in Teiid at a time.
-------------------------------------------------------------------------------------
Key: TEIID-1388
URL: https://issues.jboss.org/browse/TEIID-1388
Project: Teiid
Issue Type: Bug
Components: Salesforce Connector
Affects Versions: 7.1.1
Environment: Teiid 7.1.1 in EDS ER5, JBDS Beta2, RHEL 5.1
Reporter: John Doyle
Assignee: John Doyle
Priority: Blocker
It appears they only one SalesForce connector can be run at a time. If you preview a
model from Designer and there are no SF connections in Teiid, it works. When you create a
DS for the VDB and deploy, the VDB cannot get connections from SalesForce. If you delete
the preview VDB and Datasource, then the deployed VDB begins working.
I originally suspected that the problem might be that we are running out of connections;
SalesForce limits you to 5 simultaneous connections per username/password. But I deployed
the two DataSources with different credentials, and the result did not change. Need to
investigate more.
Think that we do need to default the SF DS to a pool of 1 and then doc that it should be
bumped to 5 for production. The current default is 10, and that should never be. Even 5
will exhaust the limit with just a preview connection.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:19 p.m.
New subject: [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...
]
John Doyle commented on TEIID-1388:
-----------------------------------
Not sure why, but in the failure case the connection URL is
https://127.0.0.1:8443/services/Soap/u/17.0.
Bogus.
Appears to be a limit of only one functional SalesForce connector in
Teiid at a time.
-------------------------------------------------------------------------------------
Key: TEIID-1388
URL: https://issues.jboss.org/browse/TEIID-1388
Project: Teiid
Issue Type: Bug
Components: Salesforce Connector
Affects Versions: 7.1.1
Environment: Teiid 7.1.1 in EDS ER5, JBDS Beta2, RHEL 5.1
Reporter: John Doyle
Assignee: John Doyle
Priority: Blocker
It appears they only one SalesForce connector can be run at a time. If you preview a
model from Designer and there are no SF connections in Teiid, it works. When you create a
DS for the VDB and deploy, the VDB cannot get connections from SalesForce. If you delete
the preview VDB and Datasource, then the deployed VDB begins working.
I originally suspected that the problem might be that we are running out of connections;
SalesForce limits you to 5 simultaneous connections per username/password. But I deployed
the two DataSources with different credentials, and the result did not change. Need to
investigate more.
Think that we do need to default the SF DS to a pool of 1 and then doc that it should be
bumped to 5 for production. The current default is 10, and that should never be. Even 5
will exhaust the limit with just a preview connection.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:07 p.m.
New subject: [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...
]
John Doyle commented on TEIID-1388:
-----------------------------------
This is in the server log. I've tried turning off the ModifySOAPAddress attribute for
JBoss WS in the JMX console, but it has no effect.
15:00:46,312 INFO [ReflectionServiceFactoryBean] Creating Service
{urn:partner.soap.sforce.com}SforceService from WSDL:
vfszip:/NotBackedUp/jdoyle/soa-5.1-er5/jboss-soa-p-5/jboss-as/server/default/deploy/teiid/connectors/salesforce-api-7.1.1.jar/partner_v17.wsdl
15:00:46,538 INFO [AddressRewritingEndpointInfo] Setting new service endpoint address in
wsdl: https://www.salesforce.com/services/Soap/u/17.0
15:00:47,595 WARN [AbstractServerConfig] Unable to calculate
'WebServiceSecurePort', using default '8443'
15:00:47,595 INFO [AddressRewritingEndpointInfo] Setting new service endpoint address in
wsdl: https://127.0.0.1:8443/services/Soap/u/17.0
15:00:47,928 INFO [HttpsURLConnectionFactory] The cipher suites have not been configured,
falling back to cipher suite filters.
15:00:47,928 INFO [HttpsURLConnectionFactory] The cipher suite filters have not been
configured, falling back to default filters.
15:00:47,929 INFO [HttpsURLConnectionFactory] The cipher suites have been set to
SSL_RSA_WITH_RC4_128_MD5, SSL_RSA_WITH_RC4_128_SHA, TLS_RSA_WITH_AES_128_CBC_SHA,
TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_DSS_WITH_AES_128_CBC_SHA,
SSL_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA,
SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA, SSL_RSA_WITH_DES_CBC_SHA, SSL_DHE_RSA_WITH_DES_CBC_SHA,
SSL_DHE_DSS_WITH_DES_CBC_SHA, SSL_RSA_EXPORT_WITH_RC4_40_MD5,
SSL_RSA_EXPORT_WITH_DES40_CBC_SHA, SSL_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA,
SSL_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA, TLS_KRB5_WITH_RC4_128_SHA,
TLS_KRB5_WITH_RC4_128_MD5, TLS_KRB5_WITH_3DES_EDE_CBC_SHA, TLS_KRB5_WITH_3DES_EDE_CBC_MD5,
TLS_KRB5_WITH_DES_CBC_SHA, TLS_KRB5_WITH_DES_CBC_MD5, TLS_KRB5_EXPORT_WITH_RC4_40_SHA,
TLS_KRB5_EXPORT_WITH_RC4_40_MD5, TLS_KRB5_EXPORT_WITH_DES_CBC_40_SHA,
TLS_KRB5_EXPORT_WITH_DES_CBC_40_MD5.
15:00:52,364 INFO [ReflectionServiceFactoryBean] Creating Service
{urn:partner.soap.sforce.com}SforceService from WSDL:
vfszip:/NotBackedUp/jdoyle/soa-5.1-er5/jboss-soa-p-5/jboss-as/server/default/deploy/teiid/connectors/salesforce-api-7.1.1.jar/partner_v17.wsdl
15:00:52,395 INFO [AddressRewritingEndpointInfo] Setting new service endpoint address in
wsdl: https://127.0.0.1:8443/services/Soap/u/17.0
15:00:52,573 WARN [AbstractServerConfig] Unable to calculate
'WebServiceSecurePort', using default '8443'
15:00:52,573 INFO [AddressRewritingEndpointInfo] Setting new service endpoint address in
wsdl: https://127.0.0.1:8443/services/Soap/u/17.0
15:00:52,580 INFO [HttpsURLConnectionFactory] The cipher suites have not been configured,
falling back to cipher suite filters.
15:00:52,580 INFO [HttpsURLConnectionFactory] The cipher suite filters have not been
configured, falling back to default filters.
15:00:52,581 INFO [HttpsURLConnectionFactory] The cipher suites have been set to
SSL_RSA_WITH_RC4_128_MD5, SSL_RSA_WITH_RC4_128_SHA, TLS_RSA_WITH_AES_128_CBC_SHA,
TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_DSS_WITH_AES_128_CBC_SHA,
SSL_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA,
SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA, SSL_RSA_WITH_DES_CBC_SHA, SSL_DHE_RSA_WITH_DES_CBC_SHA,
SSL_DHE_DSS_WITH_DES_CBC_SHA, SSL_RSA_EXPORT_WITH_RC4_40_MD5,
SSL_RSA_EXPORT_WITH_DES40_CBC_SHA, SSL_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA,
SSL_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA, TLS_KRB5_WITH_RC4_128_SHA,
TLS_KRB5_WITH_RC4_128_MD5, TLS_KRB5_WITH_3DES_EDE_CBC_SHA, TLS_KRB5_WITH_3DES_EDE_CBC_MD5,
TLS_KRB5_WITH_DES_CBC_SHA, TLS_KRB5_WITH_DES_CBC_MD5, TLS_KRB5_EXPORT_WITH_RC4_40_SHA,
TLS_KRB5_EXPORT_WITH_RC4_40_MD5, TLS_KRB5_EXPORT_WITH_DES_CBC_40_SHA,
TLS_KRB5_EXPORT_WITH_DES_CBC_40_MD5.
15:00:52,589 WARNING [PhaseInterceptorChain] Interceptor for
{urn:partner.soap.sforce.com}SforceService#{urn:partner.soap.sforce.com}login has thrown
exception, unwinding now
org.apache.cxf.interceptor.Fault: Could not send Message.
at
org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:64)
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:243)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:484)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:310)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:262)
at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:73)
at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:124)
at $Proxy441.login(Unknown Source)
at
org.teiid.resource.adapter.salesforce.SalesforceConnectionImpl.login(SalesforceConnectionImpl.java:109)
at
org.teiid.resource.adapter.salesforce.SalesforceConnectionImpl.<init>(SalesforceConnectionImpl.java:76)
at
org.teiid.resource.adapter.salesforce.SalesForceManagedConnectionFactory$1.getConnection(SalesForceManagedConnectionFactory.java:102)
at
org.teiid.resource.adapter.salesforce.SalesForceManagedConnectionFactory$1.getConnection(SalesForceManagedConnectionFactory.java:99)
at
org.teiid.resource.spi.BasicManagedConnectionFactory.createManagedConnection(BasicManagedConnectionFactory.java:70)
at
org.jboss.resource.connectionmanager.InternalManagedConnectionPool.createConnectionEventListener(InternalManagedConnectionPool.java:639)
at
org.jboss.resource.connectionmanager.InternalManagedConnectionPool.fillToMin(InternalManagedConnectionPool.java:547)
at org.jboss.resource.connectionmanager.PoolFiller.run(PoolFiller.java:74)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:519)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:550)
at sun.net.NetworkClient.doConnect(NetworkClient.java:158)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:394)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:529)
at sun.net.www.protocol.https.HttpsClient.<init>(HttpsClient.java:272)
at sun.net.www.protocol.https.HttpsClient.New(HttpsClient.java:329)
at
sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(AbstractDelegateHttpsURLConnection.java:172)
at
sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:793)
at
sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:158)
at
sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:896)
at
sun.net.www.protocol.https.HttpsURLConnectionImpl.getOutputStream(HttpsURLConnectionImpl.java:230)
at
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleHeadersTrustCaching(HTTPConduit.java:1954)
at
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.onFirstWrite(HTTPConduit.java:1906)
at
org.apache.cxf.io.AbstractWrappedOutputStream.write(AbstractWrappedOutputStream.java:42)
at
org.apache.cxf.io.AbstractThresholdOutputStream.write(AbstractThresholdOutputStream.java:69)
at
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1972)
at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:66)
at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:640)
at
org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62)
... 16 more
Appears to be a limit of only one functional SalesForce connector in
Teiid at a time.
-------------------------------------------------------------------------------------
Key: TEIID-1388
URL: https://issues.jboss.org/browse/TEIID-1388
Project: Teiid
Issue Type: Bug
Components: Salesforce Connector
Affects Versions: 7.1.1
Environment: Teiid 7.1.1 in EDS ER5, JBDS Beta2, RHEL 5.1
Reporter: John Doyle
Assignee: John Doyle
Priority: Blocker
It appears they only one SalesForce connector can be run at a time. If you preview a
model from Designer and there are no SF connections in Teiid, it works. When you create a
DS for the VDB and deploy, the VDB cannot get connections from SalesForce. If you delete
the preview VDB and Datasource, then the deployed VDB begins working.
I originally suspected that the problem might be that we are running out of connections;
SalesForce limits you to 5 simultaneous connections per username/password. But I deployed
the two DataSources with different credentials, and the result did not change. Need to
investigate more.
Think that we do need to default the SF DS to a pool of 1 and then doc that it should be
bumped to 5 for production. The current default is 10, and that should never be. Even 5
will exhaust the limit with just a preview connection.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:29 p.m.
New subject: [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...
]
John Doyle commented on TEIID-1388:
-----------------------------------
Tried this in Teiid 7.2 running in JBoss AS, and there are no issues. This seems SOA
related.
Appears to be a limit of only one functional SalesForce connector in
Teiid at a time.
-------------------------------------------------------------------------------------
Key: TEIID-1388
URL: https://issues.jboss.org/browse/TEIID-1388
Project: Teiid
Issue Type: Bug
Components: Salesforce Connector
Affects Versions: 7.1.1
Environment: Teiid 7.1.1 in EDS ER5, JBDS Beta2, RHEL 5.1
Reporter: John Doyle
Assignee: John Doyle
Priority: Blocker
It appears they only one SalesForce connector can be run at a time. If you preview a
model from Designer and there are no SF connections in Teiid, it works. When you create a
DS for the VDB and deploy, the VDB cannot get connections from SalesForce. If you delete
the preview VDB and Datasource, then the deployed VDB begins working.
I originally suspected that the problem might be that we are running out of connections;
SalesForce limits you to 5 simultaneous connections per username/password. But I deployed
the two DataSources with different credentials, and the result did not change. Need to
investigate more.
Think that we do need to default the SF DS to a pool of 1 and then doc that it should be
bumped to 5 for production. The current default is 10, and that should never be. Even 5
will exhaust the limit with just a preview connection.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:01 p.m.
New subject: [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.
Appears to be a limit of only one functional SalesForce connector in
Teiid at a time.
-------------------------------------------------------------------------------------
Key: TEIID-1388
URL: https://issues.jboss.org/browse/TEIID-1388
Project: Teiid
Issue Type: Bug
Components: Salesforce Connector
Affects Versions: 7.1.1
Environment: Teiid 7.1.1 in EDS ER5, JBDS Beta2, RHEL 5.1
Reporter: John Doyle
Assignee: John Doyle
Priority: Blocker
It appears they only one SalesForce connector can be run at a time. If you preview a
model from Designer and there are no SF connections in Teiid, it works. When you create a
DS for the VDB and deploy, the VDB cannot get connections from SalesForce. If you delete
the preview VDB and Datasource, then the deployed VDB begins working.
I originally suspected that the problem might be that we are running out of connections;
SalesForce limits you to 5 simultaneous connections per username/password. But I deployed
the two DataSources with different credentials, and the result did not change. Need to
investigate more.
Think that we do need to default the SF DS to a pool of 1 and then doc that it should be
bumped to 5 for production. The current default is 10, and that should never be. Even 5
will exhaust the limit with just a preview connection.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:03 p.m.
New subject: [JBoss JIRA] Updated: (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 updated TEIID-1388:
--------------------------------
Attachment: SFTest.java
Sales Force Connection test
Appears to be a limit of only one functional SalesForce connector in
Teiid at a time.
-------------------------------------------------------------------------------------
Key: TEIID-1388
URL: https://issues.jboss.org/browse/TEIID-1388
Project: Teiid
Issue Type: Bug
Components: Salesforce Connector
Affects Versions: 7.1.1
Environment: Teiid 7.1.1 in EDS ER5, JBDS Beta2, RHEL 5.1
Reporter: John Doyle
Assignee: John Doyle
Priority: Blocker
Attachments: SFTest.java
It appears they only one SalesForce connector can be run at a time. If you preview a
model from Designer and there are no SF connections in Teiid, it works. When you create a
DS for the VDB and deploy, the VDB cannot get connections from SalesForce. If you delete
the preview VDB and Datasource, then the deployed VDB begins working.
I originally suspected that the problem might be that we are running out of connections;
SalesForce limits you to 5 simultaneous connections per username/password. But I deployed
the two DataSources with different credentials, and the result did not change. Need to
investigate more.
Think that we do need to default the SF DS to a pool of 1 and then doc that it should be
bumped to 5 for production. The current default is 10, and that should never be. Even 5
will exhaust the limit with just a preview connection.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:06 p.m.
New subject: [JBoss JIRA] Updated: (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 updated TEIID-1388:
--------------------------------
Fix Version/s: 7.1.1
Appears to be a limit of only one functional SalesForce connector in
Teiid at a time.
-------------------------------------------------------------------------------------
Key: TEIID-1388
URL: https://issues.jboss.org/browse/TEIID-1388
Project: Teiid
Issue Type: Bug
Components: Salesforce Connector
Affects Versions: 7.1.1
Environment: Teiid 7.1.1 in EDS ER5, JBDS Beta2, RHEL 5.1
Reporter: John Doyle
Assignee: John Doyle
Priority: Blocker
Fix For: 7.1.1
Attachments: SFTest.java
It appears they only one SalesForce connector can be run at a time. If you preview a
model from Designer and there are no SF connections in Teiid, it works. When you create a
DS for the VDB and deploy, the VDB cannot get connections from SalesForce. If you delete
the preview VDB and Datasource, then the deployed VDB begins working.
I originally suspected that the problem might be that we are running out of connections;
SalesForce limits you to 5 simultaneous connections per username/password. But I deployed
the two DataSources with different credentials, and the result did not change. Need to
investigate more.
Think that we do need to default the SF DS to a pool of 1 and then doc that it should be
bumped to 5 for production. The current default is 10, and that should never be. Even 5
will exhaust the limit with just a preview connection.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:58 a.m.
New subject: [JBoss JIRA] Resolved: (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 resolved TEIID-1388.
---------------------------------
Assignee: Ramesh Reddy (was: John Doyle)
Resolution: Done
The commited changes make use of user supplied URL from ds.xml as the endpoint. If in case
user did not supply the endpoint then a default endpoint is defined in the
"ra.xml" will be used.
Also, cleaned up some unused properties and added "isAlive" method to the
connection object to actually check if the connection is alive to be used by management
tools.
Appears to be a limit of only one functional SalesForce connector in
Teiid at a time.
-------------------------------------------------------------------------------------
Key: TEIID-1388
URL: https://issues.jboss.org/browse/TEIID-1388
Project: Teiid
Issue Type: Bug
Components: Salesforce Connector
Affects Versions: 7.1.1
Environment: Teiid 7.1.1 in EDS ER5, JBDS Beta2, RHEL 5.1
Reporter: John Doyle
Assignee: Ramesh Reddy
Priority: Blocker
Fix For: 7.1.1
Attachments: SFTest.java
It appears they only one SalesForce connector can be run at a time. If you preview a
model from Designer and there are no SF connections in Teiid, it works. When you create a
DS for the VDB and deploy, the VDB cannot get connections from SalesForce. If you delete
the preview VDB and Datasource, then the deployed VDB begins working.
I originally suspected that the problem might be that we are running out of connections;
SalesForce limits you to 5 simultaneous connections per username/password. But I deployed
the two DataSources with different credentials, and the result did not change. Need to
investigate more.
Think that we do need to default the SF DS to a pool of 1 and then doc that it should be
bumped to 5 for production. The current default is 10, and that should never be. Even 5
will exhaust the limit with just a preview connection.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:04 p.m.
New subject: [JBoss JIRA] Closed: (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...
]
Steven Hawkins closed TEIID-1388.
---------------------------------
Appears to be a limit of only one functional SalesForce connector in
Teiid at a time.
-------------------------------------------------------------------------------------
Key: TEIID-1388
URL: https://issues.jboss.org/browse/TEIID-1388
Project: Teiid
Issue Type: Bug
Components: Salesforce Connector
Affects Versions: 7.1.1
Environment: Teiid 7.1.1 in EDS ER5, JBDS Beta2, RHEL 5.1
Reporter: John Doyle
Assignee: Ramesh Reddy
Priority: Blocker
Fix For: 7.1.1
Attachments: SFTest.java
It appears they only one SalesForce connector can be run at a time. If you preview a
model from Designer and there are no SF connections in Teiid, it works. When you create a
DS for the VDB and deploy, the VDB cannot get connections from SalesForce. If you delete
the preview VDB and Datasource, then the deployed VDB begins working.
I originally suspected that the problem might be that we are running out of connections;
SalesForce limits you to 5 simultaneous connections per username/password. But I deployed
the two DataSources with different credentials, and the result did not change. Need to
investigate more.
Think that we do need to default the SF DS to a pool of 1 and then doc that it should be
bumped to 5 for production. The current default is 10, and that should never be. Even 5
will exhaust the limit with just a preview connection.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4937
days inactive
5081
days old
8 comments
3 participants
participants (3)
-
John Doyle (JIRA) -
Ramesh Reddy (JIRA)
-
Steven Hawkins (JIRA)