You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
strongloop/loopback-next NodeJS-Oracle DB - NJS-040 Connection Timeout using oracle driver with Lopback with in the ICP (loopback-connector-oracle)
#7253
I am seeking some information using loopback-connector-oracle version 4.1.1 on the issue I am facing on. The analysis as this: We have the DB connection configuration to connect to oracle DB data source using oracle connector in json file format using attributes. "maxConn": 20, "host": DB_HOST, "port": DB_PORT, "database": DB_NAME, "password": DB_PASSWORD, "user": DB_USER, "connector": "oracle",
There are two process/pod are running on and each has its own pool used by oracle connector. What happened was in one instance the oracle is able to connect and process the requests but one the second pod/process I have noticed the NJS-040 error connection times out. As both the running on the same environment, so connectivity will not be an issue. I am seeking your help or input to know the reason could be connection pool exhausted? As I seen the number of connection/session on DB was less in number that was configured. When I re-start the pod/process every thing come back to normal. Some Qs that come in to my though process, for which I am seeking your help on, if you can guide and give your valuable input on.
If the connection pool is used (oracle connector )it should release the objects as well and exhaustion will have the less chances on?
After the process/pod is started and get the connection object in data source via connector ( oracle), and network issue happened and connectivity is lost between the process and db, does the connector recover that? As my observation, it seems it should what I have noticed in other process that was recovered, What could cause it in one process when it is running with the scope?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I am seeking some information using loopback-connector-oracle version 4.1.1 on the issue I am facing on. The analysis as this: We have the DB connection configuration to connect to oracle DB data source using oracle connector in json file format using attributes. "maxConn": 20, "host": DB_HOST, "port": DB_PORT, "database": DB_NAME, "password": DB_PASSWORD, "user": DB_USER, "connector": "oracle",
There are two process/pod are running on and each has its own pool used by oracle connector. What happened was in one instance the oracle is able to connect and process the requests but one the second pod/process I have noticed the NJS-040 error connection times out. As both the running on the same environment, so connectivity will not be an issue. I am seeking your help or input to know the reason could be connection pool exhausted? As I seen the number of connection/session on DB was less in number that was configured. When I re-start the pod/process every thing come back to normal. Some Qs that come in to my though process, for which I am seeking your help on, if you can guide and give your valuable input on.
If the connection pool is used (oracle connector )it should release the objects as well and exhaustion will have the less chances on?
After the process/pod is started and get the connection object in data source via connector ( oracle), and network issue happened and connectivity is lost between the process and db, does the connector recover that? As my observation, it seems it should what I have noticed in other process that was recovered, What could cause it in one process when it is running with the scope?
Beta Was this translation helpful? Give feedback.
All reactions