This week's book giveaway is in the Java in General forum.
We're giving away four copies of Think Java: How to Think Like a Computer Scientist and have Allen B. Downey & Chris Mayfield on-line!
See this thread for details.
Win a copy of Think Java: How to Think Like a Computer Scientist this week in the Java in General forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

weblogic server crash

 
Ram prakash
Greenhorn
Posts: 11
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi all,
I am facing a problem with weblogic server.
Server crashes very often with the following
exception message.
Could you please give any suggestions to avoid this problem.
weblogic.common.ResourceException: No resources available at weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:568) at weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:400) at weblogic.common.internal.ResourceAllocator.reserveNoWait(ResourceAllocator.java:368) at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:166) at weblogic.jdbc.common.internal.ConnectionPool.reserveNoWait(ConnectionPool.java:127) at weblogic.jdbc.common.internal.RmiDataSource.getPoolConnection(RmiDataSource.java:194) at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:219)
Thanks,
Ram
 
Simon Brown
sharp shooter, and author
Ranch Hand
Posts: 1913
6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
This looks like:
(1) Your JDBC connection pool isn't large enough
(2) Your components aren't releasing connections back to the pool when they're finished
(3) Your transactions are too long meaning that the connections are being held open and nothing else can access those resources.
Moving to the BEA/WebLogic forum for further discussion...
Simon
 
Suresh Selvaraj
Ranch Hand
Posts: 104
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,
1.You may want to increase
the "CapacityIncrement" and "MaxCapacity"
attributes for Connection Pool in Weblogic
Server.
2.Similar changes need to be made in database also.
3.Simon Brown's "2"nd and "3"rd points need to be taken care. Ensure all OPEN Connections are closed in try-catch-finally {con.close();} blocks.
Suresh Selvaraj
 
Vikalp Singh
Ranch Hand
Posts: 50
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
For this check the con-current Connections open from the Database to use from the Client.
If we are having more than that connection in the Max connection in the weblogic server, it will give that error.
 
Himanshu Jhamb
Ranch Hand
Posts: 134
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi.
We have a similar situation on our side. Our app. is deployed in AIX/Weblogic 6.1 & we see these very exceptions.
We have already taken care of the following items in our app...
1) max weblogic threads paramater & the max DB connection parameters are already set appropriately... we have a 100 of each.
2) We are handling the open() and the close() of the connections properly in our stateless session beans that we use for accessing the DB(webserver vendor guarantees that a stateless session bean would not be swapped in memory in between processing - So this should not pose the situation where our bean gets swapped out and the connection remains active).
3) If we had any leaks in the application... we would have caught them since our application is a 24x7 app... and leaks usually worsen the system performance exponentially ... until the system comes on its knees.
One thought we had in mind was that maybe our OS (AIX) is swapping some weblogic threads while processing & thereby our connections are not closed properly... but, I would like to know if there is anything I am missing on the Weblogic side... before going with this theory.
Any help would be very much appreciated... since we are seeing these Resource Exceptions quite a bit... say, about 0.5% of the time.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic