DX NetOps

  • 1.  Issue with Report Manager

    Posted May 10, 2018 02:30 AM

    Hi ,

     

    I have installed Spectrum 10.2 with Jasper report 6.3 initially everything is working fine.But when I have restarted spectrum and tried to access Report Manager I am seeing the error.

    And the Spectrum tomcat log shows the root cause as: May 07, 2018 2:57:14 PM org.apache.catalina.core.StandardWrapperValve invoke SEVERE: Servlet.service() for servlet [jsp] in context with path [/spectrum] threw exception [com.aprisma.spectrum.app.repmgr.container.BeanNotReadyException: srmRegistry] with root cause com.aprisma.spectrum.app.repmgr.container.BeanNotReadyException: srmRegistry at com.aprisma.spectrum.app.repmgr.container.SRMApplicationContext.getBeanWithRetry(Unknown Source) at org.apache.jsp.repmgr.admin.navigation_jsp._jspService(navigation_jsp.java:167) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) at javax.servlet.http.HttpServlet.service(HttpServlet.java:731) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:439) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:395) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:339) at javax.servlet.http.HttpServlet.service(HttpServlet.java:731) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:218) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:614) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:169) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:956) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:442) at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1083) at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:640) at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:318) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) at java.lang.Thread.run(Thread.java:745)

     

    May 08, 2018 16:52:57.376 (PoolThread-2: Availability Handler Queue => ServiceAvailabilityTask: for domain cvserver1 (0x800000)) (SLM_STAT_EVENT) - slm to begin processing historical outages for domain=0x800000
    java.sql.SQLException: No Parameters set. The command addBatch() must have been set
    at org.mariadb.jdbc.internal.util.ExceptionMapper.getSqlException(ExceptionMapper.java:149)
    at org.mariadb.jdbc.MariaDbServerPreparedStatement.executeBatch(MariaDbServerPreparedStatement.java:209)
    at com.aprisma.util.mysql.Database.writeBatch(Database.java:822)
    at com.aprisma.spectrum.app.slm.web.stat.SLMDbReadWrite.addLossOfManagementOutage(SLMDbReadWrite.java:5367)
    at com.aprisma.spectrum.app.slm.web.stat.SLMServiceAvailabilityHandler.createDomainOutage(SLMServiceAvailabilityHandler.java:549)
    at com.aprisma.spectrum.app.slm.web.stat.SLMServiceAvailabilityHandler.handleDomainEvent(SLMServiceAvailabilityHandler.java:1587)
    at com.aprisma.spectrum.app.slm.web.stat.SLMServiceAvailabilityHandler.handleEvent(SLMServiceAvailabilityHandler.java:621)
    at com.aprisma.spectrum.app.event.web.model.AbstractAvailabilityHandler.handleRecordEvent(AbstractAvailabilityHandler.java:528)
    at com.aprisma.spectrum.app.event.web.model.AbstractAvailabilityHandler.historicalEventUpdate(AbstractAvailabilityHandler.java:760)
    at com.aprisma.spectrum.app.event.web.model.BackEndEventDataModel$HistoricalUpdateJob.fireUpdate(BackEndEventDataModel.java:2419)
    at com.aprisma.spectrum.app.event.web.model.BackEndEventDataModel$HistoricalUpdateJob.getEvents(BackEndEventDataModel.java:2568)
    at com.aprisma.spectrum.app.event.web.model.BackEndEventDataModel$HistoricalUpdateJob.performTask(BackEndEventDataModel.java:2340)
    at com.aprisma.util.thread.CachedThread.run(CachedThread.java:116)

     

    Can someone please help me to solve the issue.



  • 2.  Re: Issue with Report Manager

    Broadcom Employee


  • 3.  Re: Issue with Report Manager

    Broadcom Employee
    Posted May 10, 2018 07:41 AM

    Hi Sheetal,

     

    The first error is benign. It shows up when you click on the "Report Manager" in the OneClick Administration page while the SRM is starting up.

    The second error is regarding Service Manager, not SRM.

     

    I would suggest to open a case at CA Support and attach the output of getSpectrumInfo.sh script.

     

    1. Open a bash shell (bash -login)

     

    2. Run:
    bin/support/getSpectrumInfo.sh lite

     

    3. Gather the $SPECROOT/logs-<hostname>-yyyymmdd-hhmm.tar.gz file

     

    Note: You must run the getSpectrumInfo.sh script from the $SPECROOT directory. It does not run from the $SPECROOT/bin directory.

     

    Thanks,

    Silvio