Hi Kyle,
We would like to increase the connection pool size in the WAS cluster (3machines) environment.
Server setup:
3 WAS 4.02 machines are clustered and one network dispatcher. DB2 (WAS40) is the used for the repository.
THe problem is when the connection pool size is increased and applied, it throws com.ibm.ejs.... exception and CORBA transaction exception. But when i applied the same on my local node its taking perfectly and the new connection pool size is applied after i restart that instance.
Can u help me in solving this problem.
I am listing the steps done below, if any step is wrong pl suggest and correct me:
1. Stop the HTTP Server service.
2. Go the WAS Console.
3. there are two nodes in the console.
4. Go to resources-JDBC->Datasources and give new values to the connection pool parameters and apply.
5. Error displaying "Attributes are not set properly" with com.ibm.ejs....exception.
6. then i stoped 3 instances running on the server, and did the step. 5. same error.
Can u tell me where i am making mistake? or is there any steps to be followed when the WAS servers are clustered.
When i did on my local
test machine (WAS 4.0Ad.ed), i didn even stop the instances, made changes in the connection pool size and applied. and restarted the particular instance. I saw the log, reflecting the latest connection pool parameters.
Please help me in solving the problem. Its quite urgent. Thanks in advance.
Rgds,
Prasad