Browse Prior Art Database

Determining appropriate trace string from exception stack to catch trace of second failure

IP.com Disclosure Number: IPCOM000233181D
Publication Date: 2013-Nov-28
Document File: 2 page(s) / 45K

Publishing Venue

The IP.com Prior Art Database

Abstract

This article describes utilising data in method stacks and surrounding information in first failure event reports to automatically generate appropriate trace strings and potentially configure other data gathering mechanisms to ensure appropriate diagnostic data is collected on subsequent equivalent failures.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 51% of the total text.

Page 01 of 2

Determining appropriate trace string from exception stack to catch trace of second failure

It is often the case that following a first failure event additional trace / debug information would be requested by support teams to diagnose and resolve the issue experienced. This typically requires logging a problem with the support team,

waiting for an appropriate representative to review the data before requesting a

recreate of the problem and additional data. This process takes time, and issues could be temporal - it may not be easy to recreate a problem (especially in a production environment).

    The present disclosure proposes dynamic analysis of the first failure event and exception stack to determine appropriate trace / debug options to capture the relevant data required by support engineers to fully diagnose the problem.

The disclosed technique would identify and extract method stacks / package names through known pattern matching and context search technologies. Once these have been identified additional analysis would be performed to extract all fully qualified class names / package structures into a list. An example would be:

[16/03/13 12:15:04:425 GMT] FFDC Exception:java.lang.NullPointerException SourceId:com.xxx.ws.management.connector.soap.SOAPUtils.extractSoapCall ProbeId:157

java.lang.NullPointerException
at org.apache.soap.transport.TransportMessage.read(TransportMessage.java:206)
at org.apache.soap.server.ServerUtils.readEnvelopeFromInputStream(ServerUtils.java:111)
at com.xxx.ws.management.connector.soap.SOAPUtils.extractSoapCall(SOAPUtils.java:97)
at com.xxx.ws.management.connector.soap.SOAPConnector.service(SOAPConnector.java:166)
at com.xxx.ws.management.connector.soap.SOAPConnection.handleRequest(SOAPConnection.java:65)
at com.xxx.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:733)
at com.xxx.ws.http.HttpConnection.run(HttpConnection.java:522)
at com.xxx.ws.util.ThreadPool$Worker.run(ThreadPool.java:1815)
==> Performing default dump from com.xxx.ws.management.dm.ConnectorDM :Sat Mar 16 12:15:04 GMT 2013 IntrospectDepth set from:3 to: 5
Dump of callerThis:null
IntrospectDepth reset to:3
+Data for directive [defaultconnector] obtained.:
==> Dump complete for com.xxx.ws.management.dm.ConnectorDM :Sat Mar 16 12:15:04 GMT 2013

Is analysed and the fo...