Connection pool in Java
Overall: 


Are you sure that you want to keep a static number of connections? Why not keep a minimum set of connections and create new ones when needed? 
ConnectionPool shouldn't have static fields as signalpillar said. 
You don't check if the connections have timed out after a period of wait
Loggers are nice -> you don't necessary have to remove all useful debug output when going to production
You might want to have some sort of a timeout for the blocking queue depending on the application. Then you would poll rather than take from the queue. 


Static initializer: 


Is it sensible to catch exceptions per makeConnection - There's probably something wrong if any of them fail.
You don't check if there really are 10 connections in the pool after initialization. 
What tt34 said. 


Method getConnection: 


return is not a method, parenthesis are not needed
do you really want to throw an InterruptedException from your ConnectionPool?


Method releaseConnection:


The same as getConnection


Method makeConnection: 


this could be perhaps renamed as connect or openConnection
It would be better that the connection parameters are given as parameters rather hard-coding - you'll probably just testing at the moment but still 
You should not just ignore the ClassNotFoundException in Class.forName(...): The program will fail again on the next instruction. Rethrow the exception or wrap it as a run-time exception if you do not want to show the ClassNotFoundException in the method signature
Rather than concatenating multiple strings, consider using String.format