topic Re: Max connections for dbaxlweb at jdbcurl exceed in Management

Max connections for dbaxlweb at jdbcurl exceed

winston — Thu, 19 Jun 2014 18:42:19 GMT

Max connections for dbaxlweb at jdbcurl exceed. Connection not allowed

Has anyone received this error when attempting to access call manager via axl?

Re: Max connections for dbaxlweb at jdbcurl exceed

Geevarghese Cheria — Mon, 23 Jun 2014 12:17:59 GMT

Hi Winston,

There is a BUG ID CSCuj25350 which is related to this issue and the work around is Rebooting CUCM or restarting CUCM Services.

This could happen because of some application that is constantly querying which could result in

1) not re-using a pre-existing connection

2) attempting to open too many connections to perform their task(s)

3) not playing nicely with all other AXL-based applications

Thanks and Regards,

Geevarghese

Re: Max connections for dbaxlweb at jdbcurl exceed

winston — Mon, 23 Jun 2014 15:08:33 GMT

Is there documentation on how to re-use connections or how to make sure connections are closed?

Re: Max connections for dbaxlweb at jdbcurl exceed

dkartio20 — Fri, 06 Mar 2015 15:06:14 GMT

Geevarghese -

Could you explain/show an example how to reuse/"play nice" an AXL call. From what Cisco documentation and example code (aka AXLToolkit plugin download) shows, there is no closing of a SOAP message, which is what the AXL call is.

Re: Max connections for dbaxlweb at jdbcurl exceed

npetrele — Fri, 06 Mar 2015 15:50:44 GMT

Your first AXL SOAP call returns a session ID in the header. You can re-use that session ID for subsequent calls, which bypasses the need to authenticate and connect again. But you can't work around this particular bug by managing your SOAP connections that way.