Service Virtualization

  • 1.  Not able to open VSI or VSM in Registry

    Posted Aug 08, 2017 07:15 AM

    Hello All,

     

    One more issue we are facing while opening VSI or VSM in particular registry and getting below error stack;

     

    In logs also below I am seeing data base errors:

     

    2017-08-08 11:12:55,041Z (12:12) [qtp150892791-107] INFO  com.itko.lisa.serverconsole.server.network.vse.GetVirtualServicesHandler - Virtual Service Environment is not null. List of all services = [com.itko.lisa.vse.VirtualServiceStatus@68134cd0, com.itko.lisa.vse.VirtualServiceStatus@4b182111, com.itko.lisa.vse.VirtualServiceStatus@1d23099b, com.itko.lisa.vse.VirtualServiceStatus@674bae0e, com.itko.lisa.vse.VirtualServiceStatus@19904e1d, com.itko.lisa.vse.VirtualServiceStatus@50f85f07, com.itko.lisa.vse.VirtualServiceStatus@6226ee18, com.itko.lisa.vse.VirtualServiceStatus@69d99bff, com.itko.lisa.vse.VirtualServiceStatus@4d90b8a3, com.itko.lisa.vse.VirtualServiceStatus@5849fd1d, com.itko.lisa.vse.VirtualServiceStatus@6188a833, com.itko.lisa.vse.VirtualServiceStatus@52dade4b, com.itko.lisa.vse.VirtualServiceStatus@1f38386c, com.itko.lisa.vse.VirtualServiceStatus@24004a77, com.itko.lisa.vse.VirtualServiceStatus@f18dd18, com.itko.lisa.vse.VirtualServiceStatus@295b5a66, com.itko.lisa.vse.VirtualServiceStatus@2c8bf3c0, com.itko.lisa.vse.VirtualServiceStatus@182fd919, com.itko.lisa.vse.VirtualServiceStatus@6d5604b6, com.itko.lisa.vse.VirtualServiceStatus@2a4f80ce, com.itko.lisa.vse.VirtualServiceStatus@49916a15, com.itko.lisa.vse.VirtualServiceStatus@69cbae6e, com.itko.lisa.vse.VirtualServiceStatus@3b28ee05, com.itko.lisa.vse.VirtualServiceStatus@7c22a89a, com.itko.lisa.vse.VirtualServiceStatus@476b5621, com.itko.lisa.vse.VirtualServiceStatus@57e3b528, com.itko.lisa.vse.VirtualServiceStatus@268a822c, com.itko.lisa.vse.VirtualServiceStatus@4f682a78, com.itko.lisa.vse.VirtualServiceStatus@3fbc5502, com.itko.lisa.vse.VirtualServiceStatus@657116fe, com.itko.lisa.vse.VirtualServiceStatus@639cb1b9, com.itko.lisa.vse.VirtualServiceStatus@44581bc6, com.itko.lisa.vse.VirtualServiceStatus@74878737, com.itko.lisa.vse.VirtualServiceStatus@6dbe67a5, com.itko.lisa.vse.VirtualServiceStatus@6f86b9ec, com.itko.lisa.vse.VirtualServiceStatus@76186e27, com.itko.lisa.vse.VirtualServiceStatus@3de7ff03, com.itko.lisa.vse.VirtualServiceStatus@4a173db5, com.itko.lisa.vse.VirtualServiceStatus@3bd45c13, com.itko.lisa.vse.VirtualServiceStatus@72e90214, com.itko.lisa.vse.VirtualServiceStatus@1f87a9fc, com.itko.lisa.vse.VirtualServiceStatus@3a8ef90, com.itko.lisa.vse.VirtualServiceStatus@4807d8d0, com.itko.lisa.vse.VirtualServiceStatus@7b2b64a1, com.itko.lisa.vse.VirtualServiceStatus@5ddbc533, com.itko.lisa.vse.VirtualServiceStatus@76fc769, com.itko.lisa.vse.VirtualServiceStatus@3b8cc24f, com.itko.lisa.vse.VirtualServiceStatus@1628ef14, com.itko.lisa.vse.VirtualServiceStatus@59681569]
    2017-08-08 11:13:07,462Z (12:13) [pool-15-thread-1] ERROR com.itko.lisa.report.services.QueryService - Error cleaning summaries
    java.sql.SQLException: Connections could not be acquired from the underlying database!
        at com.mchange.v2.sql.SqlUtils.toSQLException(SqlUtils.java:118)
        at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool.checkoutPooledConnection(C3P0PooledConnectionPool.java:689)
        at com.mchange.v2.c3p0.impl.AbstractPoolBackedDataSource.getConnection(AbstractPoolBackedDataSource.java:140)
        at com.itko.lisa.utils.db.LisaWrappedDataSource.getConnection(LisaWrappedDataSource.java:32)
        at com.itko.lisa.report.dbutil.ConnectionHelper.getConnection(ConnectionHelper.java:53)
        at com.itko.lisa.report.dbutil.ConnectionHelper.getConnection(ConnectionHelper.java:34)
        at com.itko.lisa.report.services.QueryService.removeBadSummaries(QueryService.java:6933)
        at com.itko.lisa.report.utils.CalcPerfSummary.run(CalcPerfSummary.java:35)
        at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)

     

     

    Please advise in this as well.

     

    Cheers..



  • 2.  Re: Not able to open VSI or VSM in Registry

    Broadcom Employee
    Posted Aug 08, 2017 09:20 AM

    Make sure the database this Registry is connecting to is accessible.  Maybe the password has expired. 



  • 3.  Re: Not able to open VSI or VSM in Registry

    Posted Aug 08, 2017 09:32 AM

    Thanks Marcy. I was also suspecting the same. If suppose passowrd is changed and with help of different ,it is reset then where we ahve to make change or update in Lisa side?

     

    Please advise.

     

    Cheers..

    Shivam Garg



  • 4.  Re: Not able to open VSI or VSM in Registry

    Broadcom Employee
    Posted Aug 08, 2017 10:41 AM

    I am assuming you are connecting to an external database.

    The Registry external database configuration is done in the site.properties.

    What version of DevTest are you on?



  • 5.  Re: Not able to open VSI or VSM in Registry

    Posted Aug 08, 2017 10:22 PM

    We are using some SQL data base connecting to registry. In Lloyds bank as of now we are using 7.5.2. Upgradation to new version is in discussion between LBG management and Ray Linford (Account Manager assigned to Bank).

     

    For your information, we have raised one incident to check weather something wrong at data base side or not. 

     

    If you want I can raise CA Case ?

     

    Thanks for looking into it.

     

    Cheers..

    Shivam Garg



  • 6.  Re: Not able to open VSI or VSM in Registry
    Best Answer

    Posted Aug 09, 2017 07:18 AM

    Hello Marcy,

     

    Issue is resolved now. There was only I MB space left at SQL server which was causing this. With help of SQL support team, space is freed to 10 GB and post that I tried , it was working fine.

     

    Cheers..

    Shivam Garg



  • 7.  Re: Not able to open VSI or VSM in Registry

    Broadcom Employee
    Posted Aug 09, 2017 08:35 AM

    Very glad to hear this is working for you.