DX Application Performance Management

Expand all | Collapse all

RAWSQL PROPERTY IS NOT WORKING (Agent v9.1.0.2)

Jump to Best Answer
  • 1.  RAWSQL PROPERTY IS NOT WORKING (Agent v9.1.0.2)

    Posted 06-15-2012 06:33 PM
    Hi Everyone:

    A java agent is configured in a weblogic server 10.3 and it is necessary to get SQL parameters, so I found a property in a pdf file that describe how to do it.

    It consist of uncommenting introscope.agent.sqlagent.sql.rawsql and set into "true" value.

    But at this moment I can not see parameters in a trasanction trace as the attached image shows.


    6/13/12 12:34:08 PM CDT [INFO] [IntroscopeAgent.ProbeInformation] Instrumentation of code in managed application has created a non supported ordering of tracer. This could lead to application performance degradation and missing reported data. Please verify the autoprobe log and consult documentation. 
    Probed declared class name: oracle.jdbc.driver.OraclePreparedStatement
    Probed method: executeQuery()Ljava/sql/ResultSet;
    Probed runtime class name: oracle.jdbc.driver.T4CPreparedStatement
    
    6/13/12 12:34:08 PM CDT [INFO] [IntroscopeAgent.Agent] Configuration property (introscope.agent.errorsnapshots.throttle) set to "10"
    6/13/12 12:34:08 PM CDT [INFO] [IntroscopeAgent.Agent] Configuration property (introscope.agent.errorsnapshots.throttle) set to "10"
    6/13/12 12:35:17 PM CDT [VERBOSE] [IntroscopeAgent.Agent] Skipping invalid class name:com.syc.fortimax.service.model.package-info
    6/13/12 12:35:22 PM CDT [VERBOSE] [IntroscopeAgent.Agent] Skipping invalid class name:com.syc.fortimax.service.model.package-info
    6/13/12 12:37:37 PM CDT [INFO] [IntroscopeAgent.Agent] Cross-JVM tracing has been disabled
    6/13/12 12:37:37 PM CDT [INFO] [IntroscopeAgent.Agent] Activating JMX Data Collection
    6/13/12 12:37:42 PM CDT [INFO] [IntroscopeAgent.Agent] Using the following JMX Primary Keys: 
    6/13/12 12:37:42 PM CDT [INFO] [IntroscopeAgent.Agent] Using the following JMX Filter Keys: ThreadPoolRuntime:ExecuteThreadIdleCount,ThreadPoolRuntime:ExecuteThreadTotalCount,ThreadPoolRuntime:HoggingThreadCount,ThreadPoolRuntime:PendingUserRequestCount,ThreadPoolRuntime:QueueLength,ThreadPoolRuntime:StandbyThreadCount,ThreadPoolRuntime:Throughput,JDBCDataSourceRuntime|*:ActiveConnectionsCurrentCount,JDBCDataSourceRuntime|*:ActiveConnectionsHighCount,JDBCDataSourceRuntime|*:ConnectionDelayTime,JDBCDataSourceRuntime|*:ConnectionsTotalCount,JDBCDataSourceRuntime|*:CurrCapacity,JDBCDataSourceRuntime|*:CurrCapacityHighCount,JDBCDataSourceRuntime|*:FailedReserveRequestCount,JDBCDataSourceRuntime|*:FailuresToReconnectCount,JDBCDataSourceRuntime|*:HighestNumAvailable,JDBCDataSourceRuntime|*:HighestNumUnavailable,JDBCDataSourceRuntime|*:LeakedConnectionCount,JDBCDataSourceRuntime|*:NumAvailable,JDBCDataSourceRuntime|*:NumUnavailable,JDBCDataSourceRuntime|*:WaitingForConnectionCurrentCount,JDBCDataSourceRuntime|*:WaitingForConnectionFailureTotal,JDBCDataSourceRuntime|*:WaitingForConnectionHighCount,JDBCDataSourceRuntime|*:WaitingForConnectionSuccessTotal,JDBCDataSourceRuntime|*:WaitingForConnectionTotal,JDBCDataSourceRuntime|*:WaitSecondsHighCount,JMSDestinationRuntime|*:BytesCurrentCount,JMSDestinationRuntime|*:BytesHighCount,JMSDestinationRuntime|*:BytesPendingCount,JMSDestinationRuntime|*:BytesReceivedCount,JMSDestinationRuntime|*:ConsumersCurrentCount,JMSDestinationRuntime|*:ConsumersHighCount,JMSDestinationRuntime|*:ConsumersTotalCount,JMSDestinationRuntime|*:MessagesCurrentCount,JMSDestinationRuntime|*:MessagesDeletedCurrentCount,JMSDestinationRuntime|*:MessagesHighCount,JMSDestinationRuntime|*:MessagesPendingCount,JMSDestinationRuntime|*:MessagesReceivedCount,WorkManagerRuntime|*:CompletedRequests,WorkManagerRuntime|*:PendingRequests,WorkManagerRuntime|*:StuckThreadCount,ExecuteQueueRuntime|*:ExecuteThreadCurrentIdleCount,ExecuteQueueRuntime|*:ExecuteThreadTotalCount,ExecuteQueueRuntime|*:PendingRequestCurrentCount,ExecuteQueueRuntime|*:ServicedRequestTotalCount,WebAppComponentRuntime|*:OpenSessionsCurrentCount,WebAppComponentRuntime|*:OpenSessionsHighCount,WebAppComponentRuntime|*:SessionsOpenedTotalCount,WebAppComponentRuntime|*:SessionTimeoutSecs
    6/13/12 12:37:42 PM CDT [INFO] [IntroscopeAgent.Agent] Lookup and use the platform MBeanServer instead of creating a new one
    
    
    
    
     (com.wily.use.platform.mbeanserver) set to default value of "false"
    6/13/12 12:37:42 PM CDT [INFO] [IntroscopeAgent.JMXService] JMX data collection activated
    6/13/12 12:41:29 PM CDT [INFO] [IntroscopeAgent.Agent] Automatically renaming the Agent to "evolv_bco_dev_domain//evolv_bco_dev_server".
    6/13/12 12:41:29 PM CDT [INFO] [IntroscopeAgent.Agent] The Introscope AutoProbe log file has been automatically renamed from /bea/Introscope9.1.0.2/wily/logs/AutoProbe.WebLogicAgent.log to /bea/Introscope9.1.0.2/wily/logs/AutoProbe.evolv_bco_dev_domain__evolv_bco_dev_server.log.
    6/13/12 12:41:29 PM CDT [INFO] [IntroscopeAgent.Agent] The Introscope Agent log file has been automatically renamed from /bea/Introscope9.1.0.2/wily/logs/IntroscopeAgent.WebLogicAgent.log to /bea/Introscope9.1.0.2/wily/logs/IntroscopeAgent.evolv_bco_dev_domain__evolv_bco_dev_server.log.
    6/13/12 12:41:29 PM CDT [INFO] [IntroscopeAgent.Agent] The Introscope Agent is sending a name change request (from "WebLogicAgent" to "evolv_bco_dev_domain//evolv_bco_dev_server") to the Introscope Enterprise Manager.
    6/13/12 12:41:29 PM CDT [INFO] [IntroscopeAgent.IsengardServerConnectionManager] The name of the Introscope Agent has been changed to "evolv_bco_dev_domain//evolv_bco_dev_server".
    6/13/12 12:41:29 PM CDT [VERBOSE] [IntroscopeAgent.Agent] Registering RemoteConfigurationService for new agent name : wlsdev|WebLogic|evolv_bco_dev_domain//evolv_bco_dev_server
    6/13/12 12:41:29 PM CDT [VERBOSE] [IntroscopeAgent.Thread dump] The ThreadDump Extension is attempting to register its service with the EM
    6/13/12 12:41:29 PM CDT [VERBOSE] [IntroscopeAgent.Agent] Registering class com.wily.introscope.agent.bizrecording.BizRecordingServiceBean for new agent name : wlsdev|WebLogic|evolv_bco_dev_domain//evolv_bco_dev_server
    6/13/12 12:43:57 PM CDT [INFO] [IntroscopeAgent.Agent] Waiting for the agent server connection to set the sampling per interval and samples per intervals
    6/13/12 12:43:57 PM CDT [INFO] [IntroscopeAgent.Agent] Waiting for the agent server connection to set the sampling per interval and samples per intervals
    6/13/12 12:43:58 PM CDT [INFO] [IntroscopeAgent.Agent] Waiting for the agent server connection to set the sampling per interval and samples per intervals
    6/13/12 12:43:58 PM CDT [INFO] [IntroscopeAgent.Agent] Waiting for the agent server connection to set the sampling per interval and samples per intervals
    6/13/12 12:43:58 PM CDT [INFO] [IntroscopeAgent.Agent] Waiting for the agent server connection to set the sampling per interval and samples per intervals
    6/13/12 12:43:58 PM CDT [INFO] [IntroscopeAgent.Agent] Waiting for the agent server connection to set the sampling per interval and samples per intervals
    6/13/12 12:43:59 PM CDT [INFO] [IntroscopeAgent.Agent] Waiting for the agent server connection to set the sampling per interval and samples per intervals
    6/13/12 12:43:59 PM CDT [INFO] [IntroscopeAgent.Agent] Waiting for the agent server connection to set the sampling per interval and samples per intervals
    6/13/12 12:43:59 PM CDT [INFO] [IntroscopeAgent.Agent] Waiting for the agent server connection to set the sampling per interval and samples per intervals
    6/13/12 12:44:00 PM CDT [INFO] [IntroscopeAgent.Agent] Waiting for the agent server connection to set the sampling per interval and samples per intervals
    6/13/12 12:44:00 PM CDT [WARN] [IntroscopeAgent.Agent] The agent server connection did not set the sampling per interval and samples per intervals!
    6/13/12 12:44:37 PM CDT [INFO] [IntroscopeAgent.ProbeInformation] Instrumentation of code in managed application has created a non supported ordering of tracer. This could lead to application performance degradation and missing reported data. Please verify the autoprobe log and consult documentation. 
    Probed declared class name: oracle.jdbc.driver.OraclePreparedStatement
    Probed method: executeBatch()[I
    Probed runtime class name: oracle.jdbc.driver.T4CPreparedStatement
    Best Regards

    Rodrigo


  • 2.  RE: RAWSQL PROPERTY IS NOT WORKING (Agent v9.1.0.2)

    Posted 06-15-2012 06:44 PM
    Actually, it looks like it may be working - note that the (UP_VALOR,?) component gets represented as (UP_VALOR, 5) in the actual transaction Trace View. My guess is that, since it's a PreparedStatement object, that actually is the raw SQL - the JDBC layer is what's adding the ? parameter placeholders, not Introscope. If you have any Statement objects being traced, you would likely see completely un-normalized SQL statements in your transaction traces. As for the component name, I'm not sure why it's still getting normalized, unless that's intended behavior or a Normalizer is still enabled in the agent properties.

    Does anyone know if this is, in fact, what's happening here?


  • 3.  RE: RAWSQL PROPERTY IS NOT WORKING (Agent v9.1.0.2)

    Posted 11-06-2012 05:05 AM
    Hi Rodrigo,

    Were you able to find a solution to see bind variables of SQL statements. I have been working on this for quite some time and that,s how I came across this post.
    My java agent version 9.1.1.1 and I have a similar requirement - to see the parameters being passed to sql statements.


    Would you be able to give suggestions /comments on how you resolved the issue.Please reply.

    Thanks
    Geethu


  • 4.  Re: RAWSQL PROPERTY IS NOT WORKING (Agent v9.1.0.2)
    Best Answer

    Posted 04-21-2015 09:01 PM

    Closing discussion.

     

    We have a FieldPack available to address this issue for Java agents.



  • 5.  Re: RAWSQL PROPERTY IS NOT WORKING (Agent v9.1.0.2)

    Posted 02-28-2016 09:26 PM

    Hi Haruhiko,

    I have the same problem but with a .Net agent..

    Can you tell me where find the FieldPack for this?



  • 6.  Re: RAWSQL PROPERTY IS NOT WORKING (Agent v9.1.0.2)

    Posted 02-29-2016 09:58 AM

    We do not, as of yet. I'm trying to find the time to port this over to .NET, but I can't guarantee a delivery time.



  • 7.  Re: RAWSQL PROPERTY IS NOT WORKING (Agent v9.1.0.2)

    Posted 06-15-2016 05:29 PM

    Hi Haruhiko,

     

    Could you please share the link of this fieldpack?

     

    Regards!



  • 8.  Re: RAWSQL PROPERTY IS NOT WORKING (Agent v9.1.0.2)

    Posted 06-20-2016 02:58 PM

    Please contact your CA Presales or Services rep.