Layer7 API Management

 View Only
  • 1.  CA API Gateway- JDBC Connection issue

    Posted Jun 30, 2020 08:27 AM
    UKB R67 siteminder changes UKB R67 siteminder changes 
    Hi There,

    We are getting the below error when trying to test the connection. 


    Have tried adding following properties too.. but no luck.

    c3p0.EnableCancelTimeout

    true

    c3p0.idleConnectionTestPeriod

    600

    c3p0.maxConnectionAge

    0

    c3p0.maxIdleTime

    0

    c3p0.preferredTestQuery

    "select 1 from dual"


    Also, unlocked the DB account many times.. but still it's getting locked again and again..

    Found below logs:
    2020-06-30T12:00:47.612+0100 WARNING 55 com.l7tech.server.jdbc.JdbcConnectionPoolManager: Ignoring unknown C3P0 property 'c3p0.EnableCancelTimeout' for JDBC connection 'AA'.
    2020-06-30T12:00:47.614+0100 WARNING 55 com.l7tech.server.jdbc.JdbcConnectionPoolManager: Password-only context variable expression referred to a nonexistent secure password alias; assuming literal password. Exception caught!
    2020-06-30T12:00:47.615+0100 WARNING 55 com.l7tech.server.jdbc.JdbcConnectionManagerImpl: Clearing all cached JdbcConnection entities
    2020-06-30T12:00:56.465+0100 WARNING 50 com.l7tech.server.jdbc.JdbcConnectionPoolManager: Ignoring unknown C3P0 property 'c3p0.EnableCancelTimeout' for JDBC connection 'AA'.
    2020-06-30T12:00:56.467+0100 WARNING 50 com.l7tech.server.jdbc.JdbcConnectionPoolManager: Password-only context variable expression referred to a nonexistent secure password alias; assuming literal password. Exception caught!

    But we are using the context variable expression which is exactly configured for password.

    Happy to share any more logs or config.

    Please Help!!!



  • 2.  RE: CA API Gateway- JDBC Connection issue
    Best Answer

    Broadcom Employee
    Posted Jun 30, 2020 02:54 PM
    Edited by Christopher Hackett Jul 02, 2020 04:03 PM
    It would help if we could see the contents of the password field. I assume you have set it to ${secpass.something.plaintext}, where "something" is the name of a password in your stored passwords that has the "Permit use via context variable reference" checkbox ticked. In the following screenshots, I set a stored password called "testpwd" to 7layer, which is the password for my ssg db, then referenced it in the jdbc connection by password reference. The test button worked fine.



    As for the locking out, that is probably due to a configuration at the DB that locks out a user with too many failed attempts to connect. If you are not sending the right password (or the literal context variable string '${secpass.something.plaintext}', which is my suspicion), then your tests will lock you out.

    ------------------------------
    Jay MacDonald - Adoption Architect - Broadcom API Management (Layer 7)
    ------------------------------