Skip to end of metadata
Go to start of metadata

Stack trace

The stack trace of the exception is stored in the developer trace file in path /usr/sap/<SID>/<inst_nr>/j2ee/cluster/serverX/log/defaulttrace).

From the stack trace the exception ID, user ID, timestamp, source file name with line number, related software component can be found:

stack trace example
#2.0#2016 05 14 06:17:49:477#+0200
#Error
#com.sap.mdm.internal.net.SimpleConnectionImpl##com.sap.mdm.tech.mdm4j
#C0000A42090A001F006771AF00001678##
#com.sap.mdm.internal.net.SimpleConnectionImpl.SimpleConnectionImpl
#J2EE_GUEST#0##3079AF11DEBC11E582F50000005E0A6A##3079af11debc11e582f50000005e0a6a#0#
Thread[Finalizer,8,system]#Plain## 
Connection refused: connect [EXCEPTION] java.net.ConnectException: Connection refused: connect
  at java.net.PlainSocketImpl.socketConnect(Native Method)
  at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:351)
  at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:213)
  at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:200)
  at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
  at java.net.Socket.connect(Socket.java:531)
  at com.sap.mdm.internal.net.DataSocket.<init>(DataSocket.java:56)
  at com.sap.mdm.internal.net.ConnectionImpl.initConnection(ConnectionImpl.java:566)
  at com.sap.mdm.internal.net.SimpleConnectionImpl.<init>(SimpleConnectionImpl.java:94)
  at com.sap.mdm.internal.net.SimpleConnectionImpl.<init>(SimpleConnectionImpl.java:73)
  at com.sap.mdm.net.SimpleConnectionFactory.createConnection(SimpleConnectionFactory.java:260)
  at com.sap.mdm.net.SimpleConnectionFactory.getInstance(SimpleConnectionFactory.java:151)
  at com.sap.mdm.internal.notification.NotificationRegistrar.getConnection(NotificationRegistrar.java:201)
  at com.sap.mdm.internal.notification.NotificationRegistrar.unregisterServerAndRepositories(NotificationRegistrar.java:1730)
  at com.sap.mdm.internal.notification.NotificationDispatcher.terminate(NotificationDispatcher.java:534)
  at com.sap.mdm.internal.notification.NotificationDispatcher.finalize(NotificationDispatcher.java:572)
  at java.lang.ref.Finalizer.invokeFinalizeMethod(Native Method)
  at java.lang.ref.Finalizer.runFinalizer(Finalizer.java:83)
  at java.lang.ref.Finalizer.access$100(Finalizer.java:14)
  at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:160)

 

Most frequent runtime exceptions:

 BufferOverflowException

It is thrown when an application tries to put more item in a buffer as the buffer size.
Usually it happens due to a program error.

 

 ArrayIndexOutOfBoundsException

It is thrown when an application tries to access an item in an array which is out of the array boundaries.
Usually it happens due to a program error.

 

 StringIndexOutOfBoundsException

It is  thrown when an application tries to access a character in a string array which is out of the sting size.
Usually it happens due to a program error.

 

 MissingResourceException

It is thrown when an application tries to access a resource which does not exist.
Usually it happens due to a program error.

 

 NoSuchElementException

It is thrown when an application tries to access an item in a list which does not exist.
Usually it happens due to a program error.

 

 NegativeArraySizeException

It is thrown when an application tries to create an array with negative size.
Usually it is happens due to a program error. 

 

 NoSuchMethodException

It is thrown when a method cannot with a specific signature cannot be found.
It can happen due to inconsitent support package stack.

 

 NullPointerException

It is thrown when an application tries to access an object with a null object:

  • calling a method of a null object
  • accessing a field of a null object
  • checking the length of a null object 

Usually it happens due to a program error.

 

 

 

  • No labels