To all java expertise

Question

Dear All,
I hv database issue, first i made my database connection as a application session so can share among all the user in one web application. so, user will share same database connection for SQL query, update or edit.
Does anyone try this before and what is the impact would be?
I always receive this error before once a while and do you think it is related to the shared database connection?
java.sql.SQLException:
[Microsoft][SQLServer 2000 Driver for JDBC]Connection reset by peer: JVM_recv in Socket input stream read

Answer 1

>
well, let me start (again) by saying this is just my
OPINION (I have been flamed once too many on this
subject...).
I would say EJB technology is somewhat overrated, and
then mostly the container managed ones. There are two
types, container managed and bean managed enterprise
beans. The container managed beans tend to slow down
an application alot once the dataload increases and
the datamodel gets more complicated. The amount of
objects involved in database activities is huge. Using
bean managed beans could remedy this, because you've
got total control on how the data is being
loaded/written, but even then, the overhead caused by
the whole container thing is alot. Now don't get me
wrong, for the bigger projects it's perfectly OK to
use the beans and an application server, but for
smaller projects (like the one you're in right now),
I'd definitely stick to using your own 'framework'. If
the design is good, you'll end up with a extensible
web application (maybe not as easily extendable as an
J2EE application, but that's hardly a guarantee
anyways...). For the most part (and this is where
people start to flame me) I think resorting to EJBs is
nice if the developers on the project are of the
'point and click' type, rather than the
'dos-edit/javac' type. That's not to say that the
latter type is better, but they would be better able
to judge whether an application needs to be
implemented using EJBs or just a good framework.
Hope it helps ?
Rishiseems getting to learn some real experience frm Java consultant. But i know there are always a room for improvement for any system.
At this moment, i just concern about the sharing connection from session application layer. Logically, this could
1) Saving the open/close connection time. It should be significant better performance if each time user connect across WAN using sharing session connection compare to open/close connection each time of user query to database.
2) Coding will be much more simpler, especially exception handling for opening JDBC database.
3) one way of not putting the database ID and password into every JSP or servlet page whenever wanted to connect to database. Somehow i feel sharing connection from application session is much more safer cause database id and password is only initialised once.
Anyone got better ideas or correct my mistake..is welcome