topic Re: Subsequent requests: Jdbcurl error Max connections in Management

Subsequent requests: Jdbcurl error Max connections

dkartio20 — Tue, 14 Apr 2015 16:02:46 GMT

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?

Re: Subsequent requests: Jdbcurl error Max connections

npetrele — Tue, 14 Apr 2015 18:33:08 GMT

This is a known defect in the 9.1 line (CSCup43923). There is an engineering special (ES) with a fix for this defect. I recommend opening a support ticket, after which we can make the ES available to you for download.

Here's the link to open a ticket:

Cisco DevNet Support

Re: Subsequent requests: Jdbcurl error Max connections

endamcm79 — Wed, 15 Apr 2015 13:19:28 GMT

Is there any URL that lists these known defects?

Re: Subsequent requests: Jdbcurl error Max connections

npetrele — Wed, 15 Apr 2015 16:59:58 GMT

You can go to bug search here:

https://tools.cisco.com/bugsearch

Here's a link for this particular defect:

https://tools.cisco.com/bugsearch/bug/CSCup43923

I know that some defects are not exposed to the outside world, so if you can't get to the information, that's why. There's not much information there, anyway. Here's the info on that page:

Symptom:

error message coming in response

Max connections for dbaxlweb at jdbcurl exceed. Connection not allowed

Conditions:

execute large number of axl requests

Workaround:

restart the tomcat

Known Fixed Releases:

(9)

10.5(1.11011.1)

10.5(1.11900.10)

10.5(1.11900.13)

10.5(1.98000.106)

10.5(1.98000.138)

10.5(1.98000.6)

10.5(2.10000.5)

11.0(0.98100.18)

9.1(2.13079.1)