Service Virtualization

Expand all | Collapse all

Error in Registry.log

Jump to Best Answer
  • 1.  Error in Registry.log

    Posted 06-20-2019 05:11 PM
    Hi all,

    Has anyone seen this error before in the registry log?  it's writing 1 every second.  It's only happening on one of our many Registry machines.

    storage is fine on c and d drive

    Thanks!
    Gary Jones

    2019-06-20 20:48:53,519Z (15:48) [Event Sink Thread Pool Thread 1] ERROR com.itko.lisa.dradis.comm.DradisRestStrategy - Failed sending component 'null', saving to dradis cache.
    2019-06-20 20:48:53,519Z (15:48) [Event Sink Thread Pool Thread 1] ERROR com.itko.lisa.dradis.comm.DradisRestStrategy - Exception: 507 Insufficient Storage
    2019-06-20 20:48:53,519Z (15:48) [Event Sink Thread Pool Thread 1] ERROR com.itko.lisa.coordinator.TestRegistryImpl - Failed sending component 'null', saving to dradis cache.
    2019-06-20 20:48:54,098Z (15:48) [qtp1438972363-4706] ERROR com.itko.lisa.dradis.comm.DradisRestStrategy - Failed sending component 'null', saving to dradis cache.
    2019-06-20 20:48:54,098Z (15:48) [qtp1438972363-4706] ERROR com.itko.lisa.dradis.comm.DradisRestStrategy - Exception: 507 Insufficient Storage
    2019-06-20 20:48:54,098Z (15:48) [qtp1438972363-4706] ERROR com.itko.lisa.coordinator.TestRegistryImpl - Failed sending component 'null', saving to dradis cache.
    2019-06-20 20:48:54,644Z (15:48) [Event Sink Thread Pool Thread 1] ERROR com.itko.lisa.dradis.comm.DradisRestStrategy - Failed sending component 'null', saving to dradis cache.
    2019-06-20 20:48:54,644Z (15:48) [Event Sink Thread Pool Thread 1] ERROR com.itko.lisa.dradis.comm.DradisRestStrategy - Exception: 507 Insufficient Storage



    ------------------------------
    Applications Systems Engineer
    Wells Fargo
    ------------------------------


  • 2.  RE: Error in Registry.log

    Posted 06-20-2019 05:48 PM
    Hi Gary - looks like disk space issues on the Registry box likely where you have the database. Pls check for disk space. The other issue could be the disk space for the dradis database but check the registry database space first. 



  • 3.  RE: Error in Registry.log
    Best Answer

    Posted 06-20-2019 10:06 PM
    Hi Gary,
          Could you please tell us the version of Devtest you are using? We noticed that, queue used by dradis (Enterprise Dashboard) was filled and not cleared in back end. Due to this error registry was not responded until restart of the service. This issue was addressed from Devtest 10.1.
          In latest version (after version 10.3) also, we have seen these error messages in registry logs, but registry and ED components are working fine. We are working on this defect (DE415891) internally to show these messages as a WARN or DEBUG in future releases.
          If storage and disk space are fine in Devtest environment and still getting these errors, you can ignore these ERROR messages if registry and ED are responding fine. If any issues in Devtest components, please raise a support case by attaching registry and enterprisedashboard logs to support case.

    Thanks & Regards,
    Srikanth Gajawada



  • 4.  RE: Error in Registry.log

    Posted 06-21-2019 12:08 PM
    Hi Srikanth,

    Thanks for the reply.  We are on 10.4.  ​Thank you!

    Gary

    ------------------------------
    Applications Systems Engineer
    Wells Fargo
    ------------------------------



  • 5.  RE: Error in Registry.log

    Posted 01-13-2020 03:13 AM
    Hi Srikanth,

    I am getting these errors in Devtest 10.5 version as well after an upgrade though components are loading just fine. But because of these errors Registry logs are piling up and somehow response time from Registry goes high costing timeout for some actions like user login/loading portal etc. May I know if this issue is fixed or is it still under development.

    ------------------------------
    Robin Gupta
    Consultant
    HCL Enterprise Studio
    ------------------------------



  • 6.  RE: Error in Registry.log

    Posted 01-13-2020 01:32 PM
    Hi Robin,

    We were provided a patch from Broadcom for this error.  It was 10.4, but it might work in 10.5 or they may have a patch for 10.5 as well.

     

    patch_DE422315_10.4.0_GA.jar



    ------------------------------
    Applications Systems Engineer
    Wells Fargo
    ------------------------------