2000, shared by many other CF servers and apps on the same network that
have no problem whatsoever.
MX6.1, using the latest MM provided datadirect JDBC drivers. After a
month of working without a single peep (server was migrated a month ago,
the same app worked for years before this), today any query to one of
the datasources returns this:
--
[Macromedia][SQLServer JDBC Driver]Error establishing socket. No buffer
space available (maximum connections reached?): JVM_Bind
--
There are 3 datasources on the machine, 2 to the same server, and only 1
returns this error. So I restart CF services, but after the 4th
connection to the datasource (but not to other datasource on the exact
same sql server), I get this:
--
[]java.sql.SQLException: [Macromedia][SQLServer JDBC Driver]Error
establishing socket. Address already in use: connect
The root cause was that: java.sql.SQLException: [Macromedia][SQLServer
JDBC Driver]Error establishing socket. Address already in use: connect
--
I repeat this many times to make sure it's not coincidental. On a
suggestion, I set the datasource to limit connections to 3 (a
semi-abitrary number based on the connection failing at 4). The
datasource won't let me do this, instantly returning the original
JVM_Bind error. Even if I restart CF services, any connection to that
datasource returns the JVM_bind error. But now we have something new.
One of the _other_ datasources on the machine, that connects to a
different sql server on a different machine, now returns the JVM_bind
error as well. Fascinated in a car-crash sort of way, I throw my
hands up in the air and reboot the server.
The server comes back up, and now it all works.
The confidence I now have in this (production) server is overwhelming.
While it seems to work for now, I'm sure I havne't seen the last of this
error.... so if there's any insight into these errors, it will be
greatly appreciated.
-Jeff
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
