Layer7 API Management

 View Only
  • 1.  WHile we try to start the gateway node, the node is not getting started and we see the error in the ssg logs.

    Posted May 16, 2016 05:06 AM

    We get the below exception:

     

    2016-05-16T04:55:55.027-0400 WARNING 1 STDERR: Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'rbacServices' defined in class path resource [com/l7tech/server/resources/ssgApplicationContext.xml]: Cannot create inner bean 'com.l7tech.server.security.rbac.RbacServicesImpl#4d2c70d2' of type [com.l7tech.server.security.rbac.RbacServicesImpl] while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'com.l7tech.server.security.rbac.RbacServicesImpl#4d2c70d2' defined in class path resource [com/l7tech/server/resources/ssgApplicationContext.xml]: Cannot resolve reference to bean 'roleManager' while setting bean property 'roleManager'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'roleManager' defined in class path resource [com/l7tech/server/resources/ssgApplicationContext.xml]: Cannot resolve reference to bean 'sessionFactory' while setting bean property 'sessionFactory'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'sessionFactory' defined in class path resource [com/l7tech/server/resources/dataAccessContext.xml]: Invocation of init method failed; nested exception is java.lang.NullPointerException

    2016-05-16T04:29:47.207-0400 INFO    1 com.l7tech.server.boot.GatewayBoot: Starting Layer 7 SecureSpan Suite 8.1.0 build 4608, built 20131212194351 by root at build64.l7tech.com

    2016-05-16T04:29:47.575-0400 INFO    1 com.l7tech.server.boot.GatewayBoot: Database type: mysql

    2016-05-16T04:30:17.577-0400 SEVERE  12 com.l7tech.server.boot.GatewayBoot: WARNING: No database connections open after 30 seconds; possible DB connection failure?

    2016-05-16T04:34:51.575-0400 WARNING 1 org.springframework.jdbc.datasource.LazyConnectionDataSourceProxy: Could not retrieve default auto-commit and transaction isolation settings

    java.sql.SQLException: Connections could not be acquired from the underlying database!

            at com.mchange.v2.sql.SqlUtils.toSQLException(SqlUtils.java:106)



  • 2.  Re: WHile we try to start the gateway node, the node is not getting started and we see the error in the ssg logs.

    Broadcom Employee
    Posted May 17, 2016 12:29 AM

    SEVERE  12 com.l7tech.server.boot.GatewayBoot: WARNING: No database connections open after 30 seconds; possible DB connection failure?

     

    Can you check if the database for gateway is running? Is it mysql database on the same server?

     

    It would be better to open a support ticket to investigate further.



  • 3.  Re: WHile we try to start the gateway node, the node is not getting started and we see the error in the ssg logs.

    Posted May 17, 2016 05:40 AM

    It's an active - active setup the above error occurred during a restart of the appliance, after establishing sql replication from secondary to primary.

     

    This was resolved through support ticket.



  • 4.  Re: WHile we try to start the gateway node, the node is not getting started and we see the error in the ssg logs.
    Best Answer

    Posted May 25, 2016 02:34 AM

    I have see this error before " No database connections open after 30 seconds; possible DB connection failure". Usually this happens when grants go missing. Its better to check grants when we see this error in logs



  • 5.  Re: WHile we try to start the gateway node, the node is not getting started and we see the error in the ssg logs.

    Posted Sep 21, 2016 04:52 PM

    hi,

    I have the same problem. How it was resolved? I need help... Also, how to check grants? Thank you!



  • 6.  Re: WHile we try to start the gateway node, the node is not getting started and we see the error in the ssg logs.

    Broadcom Employee
    Posted Sep 21, 2016 05:40 PM

    Aleksandra,

     

    There are several reasons that can cause this error:

    1) DNS issues with connecting to or resolving the hostname connecting as they relate to grants

    2) Grants not properly setup. Run the command to see if all the hosts are setup and that a % wildcard exist along with the password hash aligning: mysql -e "select host,user,password from mysql.user"

    3) Firewall blocking access from the processing node to the database

     

    Sincerely,

     

    Stephen Hughes

    Director, CA Support



  • 7.  Re: WHile we try to start the gateway node, the node is not getting started and we see the error in the ssg logs.

    Posted Sep 30, 2016 10:24 AM

    Thanks Stephen!

     

    Based on the feedback from the colleague who continued to work on this problem, the cause of the problem was 100% full of mysql DB. He made backup of gateway, purged the audits and restored gateway. And the problem was gone!

     

    (in the meanwhile, before you gave the answer, the appliance was restarted (the day before there were some network outages and issues with servers; exceptions in logs indicated problems with mysql, but not this particular error; after restart of appliance, this specific error appeared).

     

    Regards,

    Aleksandra.