This content has been marked as final.
Show 3 replies
-
1. Re: No ManagedConnections available within configured blocki
jaikiran May 28, 2009 3:51 AM (in response to muneeb_baig)No ManagedConnections available within configured blocking timeout --
See this http://www.jboss.org/community/wiki/WhatDoesTheMessageNoManagedConnectionsAvailableMean -
2. Re: No ManagedConnections available within configured blocki
muneeb_baig May 28, 2009 6:30 AM (in response to muneeb_baig)First of all I thank you very much for your time and response. So far I did the same thing as mentioned in the article and elevated the limits, and yet haven't encountered the problem.
Furthermore, I would like you or some other experts to please shed some light upon the difference of JVM for 32-bit and 64-bit in this scenario.
Thank you once again for the help and regards,
--muneeb -
3. Re: No ManagedConnections available within configured blocki
peterj May 28, 2009 11:16 AM (in response to muneeb_baig)please shed some light upon the difference of JVM for 32-bit and 64-bit
There is no difference from a Java application perspective. The only noticeable difference is that with a 64-bit JVM you can allocate larger heaps because you are not constrained to a 4GB memory address. Another issue would be if your Java app makes use of any DLLs (or shared libraries) - you would need a 32-bit version of the DLL to run with a 32-bit JVM and a 64-bit version of the DLL to run with a 64-bit JVM.
I typically run the same apps on a 64-bit JVM and a 32-bit JVM without any issues.
If you want to track down the connection issue, you might want to use the tools SQL Server provides to monitor database activity. Perhaps there is a query that is taking too long.