This course will introduce you to SQL Server Core 2016, as well as teach you about SSMS, data tools, installation, server configuration, using Management Studio, and writing and executing queries.
connection ooling with tomcat
Hi, I understand that to get connection pooling to work with tomcat I need to modify some configuration files.
I have docs on how to do that , so thats fine.
My question is to do with whether the methods used to call the getConnection object should be synchronized or not.
Currently the getConnection method is called using synchronized methods. so that only one method can be dealing with it at one time.
Am i correct in htinking, once connection pooling is enabled, the methods which call cetConnection need not be synchronized?
The second part iof my question is what will happen if say, I have configured 15 connections to be in the pool and there comes a time when 16 are needed? will the last method to request a connection just have to wait its turn?
If so, how will i be able to test if it is working?
I have docs on how to do that , so thats fine.
My question is to do with whether the methods used to call the getConnection object should be synchronized or not.
Currently the getConnection method is called using synchronized methods. so that only one method can be dealing with it at one time.
Am i correct in htinking, once connection pooling is enabled, the methods which call cetConnection need not be synchronized?
The second part iof my question is what will happen if say, I have configured 15 connections to be in the pool and there comes a time when 16 are needed? will the last method to request a connection just have to wait its turn?
If so, how will i be able to test if it is working?
Asked:
5-
2
1 Solution
> > Am i correct in htinking, once connection pooling is enabled, the
> > methods which call cetConnection need not be synchronized?
> >
>
> I would keep the getConnection method synchronized.
I mean, if you call getConnection this should not be synchronized, but the implementation getConnection() of the pool is probably synchronized.
> > methods which call cetConnection need not be synchronized?
> >
>
> I would keep the getConnection method synchronized.
I mean, if you call getConnection this should not be synchronized, but the implementation getConnection() of the pool is probably synchronized.
> If so, how will i be able to test if it is working?
Just have a for loop that creates 16 connections, perform some long data processing and see the time it takes for each one.
Just have a for loop that creates 16 connections, perform some long data processing and see the time it takes for each one.
I have a load of DAO methods which currently are synchronized,
what I'll do is remove synchronization form them, and make the static method which wraps the getConnection method synchronized.
Is that what you would suggest?
what I'll do is remove synchronization form them, and make the static method which wraps the getConnection method synchronized.
Is that what you would suggest?
I think you could avoid synchronizing the call to getConnection since the container's implementation of the connection pool should be already synchronized. Maybe you want to take a look here to see how a conneciton pool is implemented: http://www.webdevelopersjournal.com/columns/connection_pool.html
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
Join & Write a Comment Already a member? Login.
Featured Post
This course will introduce you to SQL Server Core 2016, as well as teach you about SSMS, data tools, installation, server configuration, using Management Studio, and writing and executing queries.
Tackle projects and never again get stuck behind a technical roadblock.
Join Now
> Am i correct in htinking, once connection pooling is enabled, the
> methods which call cetConnection need not be synchronized?
>
I would keep the getConnection method synchronized.
> The second part iof my question is what will happen if say, I have
> configured 15 connections to be in the pool and there comes a time when
> 16 are needed? will the last method to request a connection just have
> to wait its turn?
It depends on the algorithm used with the conneciton pool. Many servers woudl just wait for a connection to be available before proceeding, others would just create a new connection after the limit is reached.
Regards