As we have been migrating from CUCM 8.6 to 9.1, we have been encountering issues with CUCM puking on AXL calls.
CUCM is returning a "Max connections for dbaxlweb at jdbcurl exceed. Connection not allowed". While I have seen a couple other threads talking about this issue. None of the actually get answered.
One thread here (AXL Error Code 0), David Staudt from Cisco, states that the HTTP session ID needs to be added to all subsequent requests and points people at another thread, which no longer exists.
Another thread here (Re: Max connections for dbaxlweb at jdbcurl exceed), points to a bug in Prime Collab, but then again talks about re-using a pre-existing connection ID. Later in the thread someone states that adding the session ID only handles reauthentication, and has no bearing on the failure of CUCM in handling database connection.
This issue is now causing us to reboot our CUCM servers once to twice a month, to release the DB connections. Even after opening a TAC case, the Cisco engineers tell us we need to re-use the session ID.
So since, Cisco has no documentation on how this is accomplished, is anyone doing this, and can they provide a code snip-it??
Secondly, why would a HTTP session, be tied to a DB connection? This seems to be a recipe for disaster. Since HTTP has no "real" connection/handshake between the client application and the server, how does the server determine when the client has closed the connection, therefore releasing the DB connection associated with it?
