it could allow the creation of JDBC connection above the "max capacity" assigned to the pool
Wednesday, December 2, 2009
Subscribe to:
Post Comments (Atom)
skip to main |
skip to sidebar
Anything about Java, WebLogic, OSB, Linux etc.... this is my logbook of a navigation in the IT Technology ocean.
Search This Blog
popular posts
911truth.org
cars?
SyntaxHighlighter
Blog Archive
-
▼
2009
(163)
-
▼
December
(31)
- How to invoke an operation with WLST and with Java
- Session replication - a performance killer
- Tuning the Stateless Beans pool
- The doctor is in: anamneses of a JRA analysis
- A simple (and boring) list of SOA standard
- weblogic.management.utils.InvalidCursorException: ...
- Troubleshooting classloaders with JRockit
- XMing: in the log I find client 4 rejected by IP x...
- Above all, don't buy a Sony VAIO
- Classloaders implementations in WebLogic
- PoolDisabledSQLException, ResourceDisabledException
- The inner ugliness of beehive
- log4j: always use additivity=false
- WLI Worklists, quick introduction
- WebLogic WebServices, a quick tutorial
- On the performance of JMS Messaging Bridges
- Quick WLI tutorial
- Transaction "JDBC Internal" , "JMS Internal", "Mes...
- How to read a transaction error message
- Short tutorial on using Weblogic Diagnostics and w...
- Performance Checklist
- Thin locks, Fat Locks, contended thin lock etc
- Typical options for a JRA recording
- JRockit and Lock Profiling
- Quick WLST tutorial
- WLDF doesn't work in my Firefox, java.lang.NumberF...
- WLI quick tutorial: ADMIN
- Quick example on how to grep for Oracle errors usi...
- Excellent practical tutorial on Parsing XML in Java
- Careful with "pinned to thread" on the JDBC Connec...
- The infamous BEA-000627
-
▼
December
(31)
No comments:
Post a Comment