Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Connection Pooling in WebSphere 3.5

Status
Not open for further replies.

vbel4

Technical User
Aug 16, 2001
1
IN
We are using IBM WebSphere 3.5 with Oracle 8.1.5 Server as Database. In oracle, we have multiple schemas which is mapped to corresponding tablespace.

The application requires connection to multiple schemas at run time. We are using IBM WebSphere's DataSource (JDBC)connections in EJBs.

Some of these EJB's are calling oracle procedures. We are also using batch commit and single transaction commit [by using java.sql.Connection method setAutoCommit() ].

The schema names and password are stored in memory in a static instance of hash table.

Occassionaly we get the error "java.lang.InvalidStateException: Illegal operation" and the server cannot process the request.

in WebSphere we have set these parameters of datasourse

Min. Connection pool size - 10
Max " " - 20
Connection Time Out - 10
Idle Time Out - 180
Orphan Time Out - 300


Can anyone kindly help regarding this issue.

regs,
vbel4


 
We had a lot of problems trying that route.
We used persistence Builder in Visual Age to generate that layer and did not have any problems since then.
 
Change transaction for EJB to "TX_NOT_SUPPORTED" and transaction isolation to "TRANSACTION_SERIALIZABLE".
Be sure that ALL your code opens and closes connections, statement, resultsets etc. in the right order.
Also use commit and rollback the proper way.
The above works on sessions-beans.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top