background

A new business online, online error reported, open Cat to check, very frustrated, there is no valuable information, so I want to check, there is no specific information too painful

The JVM stack loss is caused by an optimization of the JVM: XX: – OmitStackTraceInFastThrow think carefully, and the CAT exception reporting, or in the operation, can get a complete stack information, so Pass out the answer

Set out to

Originally called Children, the following source code will be associated with this, then briefly looked at the source code, wrote a demo, run

The cat.logEvent () method came to mind when it occurred to me that a Transaction should be designed as a chain of transactions

Add events and continue debugging

Look at the result

What time is it self consistent

  • Why have I never called, there is some stack information (such as RPC research)?

Company internal components may already be integrated, so look at the source code to find it

  • Why do you sometimes log in here?

Error automatically raises cat.logerror () if the project’s logs are integrated with CatAppender, so this Transaction is also present

 <appender name="catAppender" class="com.dianping.cat.log4j.CatAppender"></appender>
Copy the code

Additional words

Have a look at CAT source code, feeling or pretty good to understand.

MessageManager, MessageProducer, MessageManager, MessageProducer, MessageManager, MessagProducer, messagProducer, MessageManager, MessagProducer, MessagProducer, MessagProducer, MessageManager, MessagProducer, MessagProducer, MessagProducer, MessagProducer, MessagProducer, MessageManager, MessagProducer, MessagProducer, MessagProducer, MessagProducer