Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "EclipseLink/Debugging"
m (→Debugging EclipseLink API) |
m (→Performance Discussion) |
||
| Line 18: | Line 18: | ||
=Performance Discussion= | =Performance Discussion= | ||
| + | *Rehash HashMap implementations periodically so that put/get calls achieve O(1) constant-time performance. | ||
=References= | =References= | ||
Page started on build 20090204 | Page started on build 20090204 | ||
Revision as of 11:53, 19 June 2009
Contents
Debugging EclipseLink API
This document details configuration steps and procedures that will aide the developer that is debugging EclipseLink running in an application server or a standalone application.
Preparing eclipselink.jar for Debugging
The eclipselink.jar is build by default with javac.debug=true, however you may want to increase the debug level.
- Add the following javac.debug properties if you are debugging in Eclipse using code built either by Eclipse or Ant.
javac.debug=true javac.debuglevel=lines,vars,source
Debugging EclipseLink on a Remote Application Server
Remote Debugging EclipseLink on IBM WebSphere Application Server 7
Performance Discussion
- Rehash HashMap implementations periodically so that put/get calls achieve O(1) constant-time performance.
References
Page started on build 20090204