My Oracle Support Banner

Line Numbering Missing in Top Frame of Java Thread's Stack Trace (Doc ID 1544189.1)

Last updated on NOVEMBER 05, 2016

Applies to:

Java SE JDK and JRE - Version 6 to 7 [Release 6 to 7]
Oracle JRockit - Version R27.5 to R28.2.0 [Release JRockit]
Information in this document applies to any platform.


Line numbering is missing from the top frame in a Java thread's stack trace.

Here is what it may look like:

(1) Example taken from stack trace received with Java SE Hotspot VM:
    'Java SE 6 Update 37' was used.
2013-01-29 14:15:30,481 WARN -
Caused by: Throwable = java.lang.NullPointerException
  in weblogic.jdbc.jta.DataSource.getConnection(                      <== Note the missing line number
  in weblogic.jdbc.jta.DataSource.connect(
  in weblogic.jdbc.common.internal.RmiDataSource.getConnection(

(2) Example taken from stack trace received with Jrockit VM:
 Thread-120 "[STUCK] ExecuteThread: '21' for queue: 'weblogic.kernel.Default (self-tuning)'" <alive, in native, suspended, priority=1, DAEMON> {
   com.erp.fis.arm.action.ArmJcdeAction.unspecified(           <==  Note that the line number is replaced by question marks

 If line numbering was suppressed by compiling the Java source with the compilation option '-g:none', it would simply print '(Unknown Source)'.
 -g:none     Do not generate any debugging information.
 Of course, this requires that you are either running a special build of Java SE or have compiled your own for use.



To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.