I'm trying to connect to salesforce using Mulesoft OOB connector - using OAuth jwt, but I intermittently get timeouts (connect timeout and read timeout both are set to 10 secs). Is there a way I can find out how much time it is taking to connect to Salesforce ?
So that the root cause for these timeouts can be found out?
Related
I am using a spring based application with MS SQL server and using hibernate or native sql to fetch data from the database. However one of the problems I am facing is session timeout after around 2 minutes. The session timeout configured for the application in web.xml is 20 minutes. Ideally if session is idle it does not get logged out. But whenever there is a database related operation that would take more than 2 minutes to execute the session is killed. Can someone help me with this?
Using Jboss 7.3
I am trying to implement Two factor authentication (2FA) on phpmyadmin. Conifguration Storage has been setup and corresponding user has been created. However, when I go to Settings > Two Factor Authentication and select the Authentication Application (2FA) option, phpmyadmin throws the following error :
Error in processing request
Error code: 500
Error text: error (rejected)
It seems that the connection to server has been lost. Please check your network connectivity and server status.
If anyone has implemented or faced the issue, kindly help me resolve the same.
Is there any active firewall rules? Once I had a phpmyadmin on AWS ec2 and I was using AWS security groups, by only letting 3306 open I wasn't able to activate 2fa.
I'm currently developing a project with python 3.7, Django 2.1, Mysql as database.
I'm deploying it in google cloud app engine standard environment and for the database I'm using a cloud SQL - MySql 2nd gen instance.
The application works well, however when I analyze the logs I see these errors:
"aborted connection - Got an error reading communication packets"
In this case the connection is being closed by my app (django).If I configure my app to have persistent connections and I put wait_timeout (i.e 60) in the config of the cloud sql, the error is:
"aborted connection - Got timeout reading communication packets".
I just determined that it's not a problem with sql cloud, or with the configuration of my application, but that it's an app engine problem. I came to this conclusion in the following way:
if I connect to the sql cloud instance through Mysql workbench, no connection is aborted
Similarly if I run my application on a local server, but connecting to cloud sql (through the cloud_sql_proxy), no error is generated and everything works perfect.
So my conclusion is that it is a problem of how the app engine connects to the cloud sql instance.
Why does this happen? How could it be solved?
The "Aborted connection" messages you're seeing, are usually triggered when a connection is closed improperly or there is a networking anomaly between the server and the client.
Sometimes Cloud SQL instances and GAE have long-live idle connections. In order to address this issue, it is recommended to set "wait_timeout' flag below 600 seconds - as you've already attempted to do so.
Another possible solution, is to implement application-level keepalives. SQLAlchemy provides “pre-ping” for this. Otherwise, generate activity on all open connections by sending a simple SQL statement such as "SELECT 1;" regularly, at least once every 5 minutes. Also consider using statements in your code like “with db.connect() as conn:” to control the connection’s lifetime.
I believe this is because requests from App Engine applications to Cloud SQL are subject to the following time and connection limits:
For apps running in the App Engine standard environment, all database requests must finish within the HTTP request timer, around 60 seconds. For apps running in the flexible environment, all database requests must finish within 60 minutes.
Offline requests like cron tasks have a time limit of 10 minutes.
Requests to Cloud SQL have limitations based on the scaling type of the App Engine module and how long an instance can remain in memory (residence).
Each App Engine instance running in a standard environment cannot have more than 60 concurrent connections to a Cloud SQL instance. For applications written in Java 8 or Go 1.8, the limit is 100.
Connection Issues: If you see errors containing "Aborted connection nnnn to db:", it usually indicates that your application is not terminating connections properly. It could also be caused by network issues. This error does not mean that there are problems with your Cloud SQL instance.
We are a Premier Account User in GoogleAppEngine. We have two front-end servers running on Google AppEngine developed using Java.
Front-end server A communicates with another front-end server B using URLFetch(java.net) request.
We have set the maximum connectionTimeOut and readTimeOuts (60000ms) also for URLFetch in server A.
All the requests from server A to B works successfully 70% of the time.
But we are finding weird scenarios like 30% of the time where server A would have given URLFetch request to Server B and throwing java.net.SocketTimeoutException: Timeout while fetching URL.
Note: The request from Server A to B remains dead air for 60 seconds and there aren't any request being received at Server B for the same. There are no instance restarts on both the servers.
But when the client retries the request again, it runs successfully.
We have 2 idle instances and instance classes configured to F4 on both the servers.
Can we please know why the request from Server A timeouts out without a request being received at the other server end (ie) Server B?
Thanks.
Regards,
Anantha Krishnan
Is there a way to send message or http request or send notification when SQL Azure data changes or when new data is inserted? I would like to send message/ http request/ notification to a non .NET web application. I have done that invoke an application of Tomcat server by send a http request from local SQL server when there is data change, but I can't with SQL Azure.
Can any one help me to solve this problem?
I hope it is ok to talk about our own Cotega service. IF you are interested in a finished solution for this, we are just finishing off the work to allow people to send Email and SMS notifications messages based on changes within their SQL Azure database so it would be interesting to see if we could extend this to suit your needs to call a .NET web app. Feel free to contact me from here if you are interested.