|
EJB's are really meant for when you want to spread processing and HA
across multiple app servers/LPARs (as I understand them). If you
aren't doing that or don't have multiple servers then not much is
being gained outside of a good amount of EJB complexity. How many
transactions are you expecting per minute?
It sounds like a Java servlet with Axis running on Tomcat with
connections pooled is all that is warranted here. See how I configure
connection pooling with my Tomcat server below.
C:/Program Files/Apache Software Foundation/Tomcat
5.5/webapps/MyServletContext/META-INF/context.xml
<Context path="/MyServletContext" docBase="/MyServletContext"
debug="0" reloadable="false">
<Resource
name="jdbc/myresourcename"
auth="Container"
type="javax.sql.DataSource"
factory="
org.apache.tomcat.dbcp.dbcp.BasicDataSourceFactory"
maxActive="100"
maxIdle="30"
minIdle="10"
maxWait="15000"
username="myuser"
password="mypassword"
driverClassName="com.mysql.jdbc.Driver"
url="jdbc:mysql://localhost:3306/mydbschema"
removeAbandoned="true"
removeAbandonedTimeout="300"
validationQuery="select 1"
logAbandoned="true"
testOnBorrow="true"
testOnReturn="true"
testWhileIdle="true"
/>
</Context>
HTH,
Aaron Bartell
http://mowyourlawn.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.