DX Application Performance Management

  • 1.  error in log

    Posted Feb 15, 2019 10:15 AM

    Hi,

     

    I've installed an was agent and looking in logs I see those msgs:

     

    Autoprobe.log

     

    Processing class oracle/jdbc/driver/OracleStatementWrapper
    < n/a > Skipping class for Tracer group SQLAgentStatements
    < n/a > Skipping class for Tracer group SQLAgentStatements
    < n/a > Skipping class for Tracer group SQLAgentStatements
    < n/a > Skipping class for Tracer group SQLAgentStatements

    ...

    < n/a > Skipping class for Tracer group SQLAgentStatementsWithParams
    < n/a > Skipping class for Tracer group SQLAgentStatementsWithParams
    < n/a > Skipping class for Tracer group SQLAgentStatementsWithParams

    ...

    close:0 inserted method tracer object allocation: com/wily/introscope/agent/sqlagent/hc2/StatementCloseCleanupTracer
    Processing class oracle/jdbc/driver/OracleClosedStatement
    setArray:0 inserted method tracer object allocation: com/wily/introscope/agent/sqlparamagent/PrepStmtSetTracer
    setArray:0 inserted method tracer object allocation: com/wily/introscope/agent/sqlparamagent/PrepStmtSetTracer
    setBigDecimal:0 inserted method tracer object allocation: com/wily/introscope/agent/sqlparamagent/PrepStmtSetTracer

     

    IntroscopeAgent.log (there are 4 logs files full of this error)

     

    2/15/19 11:51:41 AM ART [ERROR] [IntroscopeAgent.Agent] Exception finishing method tracer com.wily.introscope.agent.sqlagent.ResultSetToSQLMappingTracer actual trace for oracle.jdbc.driver.OraclePreparedStatement.executeQuery
    2/15/19 11:51:41 AM ART [ERROR] [IntroscopeAgent.Agent] Exception finishing method tracer com.wily.introscope.agent.sqlagent.ResultSetToSQLMappingTracer actual trace for oracle.jdbc.driver.OraclePreparedStatement.executeQuery
    2/15/19 11:51:41 AM ART [ERROR] [IntroscopeAgent.Agent] Exception finishing method tracer com.wily.introscope.agent.sqlagent.ResultSetToSQLMappingTracer actual trace for oracle.jdbc.driver.OraclePreparedStatement.executeQuery

    ....

     

    do you have some clue of possible reason for this?



  • 2.  Re: error in log
    Best Answer

    Broadcom Employee
    Posted Feb 15, 2019 03:42 PM

    I see that 01302077 was already created. Please report back the resolution to help others.