Posted: Fri Mar 14, 2003 12:47 am Post subject: connections and sessions on Web applications
Novice
Joined: 15 Oct 2002 Posts: 10
We have build a Web application that uses jms over mq. Our application is using right now an only connection for the whole application an one session for each thread.
I have read that creating connections is resource hungry and there should be only one connection per client.
The only problem with this solution is that is the connection falis for some reason, the application does not recover.
In your opinion, witch solution is best. One connection/app and one session/thread or one connection/thread and let server's connection pooling do its work??
We have a small wrapper around all of our JMS calls that detects errors and reconnects. That said, I'm thinking of creating some sort of pool object to manage all of this.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum