Win a copy of Terraform in Action this week in the Cloud forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Tim Cooke
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • Liutauras Vilda
Sheriffs:
  • Jeanne Boyarsky
  • Rob Spoor
  • Bear Bibeault
Saloon Keepers:
  • Jesse Silverman
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
Bartenders:
  • Piet Souris
  • Al Hobbs
  • salvin francis

How to increase the WAS 4.0 Ad Ed Connection pool size in cluster environment

 
Ranch Hand
Posts: 39
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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
 
Ranch Hand
Posts: 102
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Can you please give the exception and what values are you trying to set it to !!!
Check the JDBC Provider Properties
Check on the nodes tab. Is the driver there on the both nodes.
I am not sure that this will solve ur problem but just a thought !!!
Kartik
 
You showed up just in time for the waffles! And this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
https://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton
reply
    Bookmark Topic Watch Topic
  • New Topic