The line numbers in StackTrace indicate the start of the method

We are developing a web application with Rational Application Developer 7.5 (based on Eclipse 3.4) for WebSphere Application Server 6.1. When checking stacktraces on a staging server, the line numbers always point to the start of the methods, not the actual line. In a local development environment (each developer has their own local launch of Websphere 6.1) everything seems perfect.

In Eclipse preferences under Java> Compiler> Classfile Generation section everything is checked.

Deployment is done by creating an EAR file using the RAD earExport

Ant target (rather than the main task ear

). It is then repackaged to remove unneeded files. No explicit compilation is triggered - classes from the workspace are used.

How can it happen that this information is lost? Is this part of some Hotspot optimization? If so, can you turn it off?

And how can I get the correct line numbers back?

+1


a source to share


1 answer


What is your staging platform? I have a client whose staging / prod environment is iSeries, and only after they upgraded the iSeries OS to one of the newer levels that they finally started lining up the debug line numbers.



+3


a source







All Articles