ColdFusion sql JDBC error

We are running coldfusion mx ver 7 and we connect to various MS sql 2000 servers running SP4 running on MS windows 2003 ENT.

The problem that we are having we we are getting the following error

[Macromedia][SQLServer JDBC Driver]Error establishing socket.
Address already in use: connect

I have not been able to reproduce this error on my pc but I have several other pc's that this is happening on a regular basis.  We are also having this same issue now with some of our clients.  In looking through the logs i am not finding anything of real value to help in diagnosing this issue.  Any Ideas?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Are the web servers and the DB servers in the same physical location?  If not this might be a permissions issue.  I am thinking of a similar issue I have seen with the 1433 port not being open on the firewall when the web and db server were not in the same location.
aimshelpdeskAuthor Commented:
The app dos have to connect through the firewall but it has been connecting through the firewall for some time now.  What is making this more diffucult is that it dosen't happen all the time.
Did this start happening after SP4 went on the server.  I googled this and found some refernces to that
Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

aimshelpdeskAuthor Commented:
Yes it seems to have been happening on the SP4 servers.  I havent found anything good searching on google.
There is not a lot of good info out there on this.  It seems to point to an issue with SP4.  I don't suppose that there is any chance of moving away from SP4.....  ALthough this is prolly not a good idea.

We use BlueDragon JX 2 and we do not have this issue with our sp4 server.

aimshelpdeskAuthor Commented:
Removing a major sp on MS SQL is not something I would dare try.
See if this helps...
----------------In case the above link goes bad, here is the original text from
The test suites of Geronimo and associated projects can open and close a large number of socket connections within a short period of time, causing Windows to exhaust its pool of ephemeral ports (default is port range 1024-5000). When each of these connections is closed, they will remain in TIME_WAIT for a period of time (default of 240 seconds) before the ephemeral port is available. Windows will not reuse a port until it has exhausted its pool of ephemeral ports. Therefore the Geronimo tests can easily utilise all the ports within 240 seconds.

You need to set the MaxUserPort to a larger value and reduce the TcpTimedWaitDelay in the registry settings. See the following for further details:

This problem has been encountered whilst running the OpenEJB itests suite.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Web Servers

From novice to tech pro — start learning today.

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.