The ExecuteSql processor run to hang sometime when use dbcpconnectionpoollookup

[#1]

Hello,

I am working with 3 nodes CFM cluster. the version of CFM is 1.0.1.  

The below pic shows the steps:

the below pic is config of ExecuteSQL:

the below pic is lookup service:

the below is the config of dbcpconnetionpool:

The behavior is the ExcuteSQL processor will execute very slowly seem hanged.  but sometime execute very fast. I believe that is database issue. So my questions is:

1. what is the impact? is dbcp connections pool issue of config? or is the dbcp connections pool lookup wrong behavior?  

2. I'm afraid the impact of this will be magnified. when increased database connection pool to 500+.

Could help me to answer my questions?

Thanks

Paul

[#2]

I'm sorry. Correct the above description.

The behavior is the ExcuteSQL processor will execute very slowly seem hanged. but sometime execute very fast. I believe that is not database issue.

So my questions is:

1. what is the impact? is dbcp connections pool issue of config? or is the dbcp connections pool lookup wrong behavior?

2. I'm afraid the impact of this will be magnified when we face to increased database connection pool config to 500+. Is that the right thing to worry about?

Could help me to answer my questions?

Thanks Paul

[#3 · Accepted solution]

Oh, it is network connection issue. it gone away when i add oracle.jdbc.ReadTimeout=120000 and oracle.net.CONNECT_TIMEOUT=10000 to config of DBCPConnectionPool.