Guest

Preview Tool

Cisco Bug: CSCup43923 - AXL connection "dbaxlweb" not closing

Last Modified

Sep 16, 2020

Products (1)

  • Cisco Unified Communications Manager (CallManager)

Known Affected Releases

10.5(1.10000.7) 9.1(2.10000.28)

Description (partial)

Symptom:
error message coming in response
Max connections for dbaxlweb at jdbcurl exceed. Connection not allowed

Conditions:
execute large number of axl requests

Related Community Discussions

Subsequent requests: Jdbcurl error Max connections
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 ...
Latest activity: Apr 15, 2015
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.