|
|
(One intermediate revision by one other user not shown) |
Line 1: |
Line 1: |
− | =Debugging EclipseLink API=
| + | This page is obsolete now. |
− | 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.
| + | |
− | | + | |
− | <pre>
| + | |
− | javac.debug=true
| + | |
− | javac.debuglevel=lines,vars,source
| + | |
− | </pre>
| + | |
− | | + | |
− | | + | |
− | ==Debugging EclipseLink on a Remote Application Server==
| + | |
− | ===WebSphere===
| + | |
− | [[EclipseLink/Examples/JPA/WebSphere7_Web_Tutorial#Remote_Debugging_EclipseLink_in_WebSphere_7.0_from_Eclipse_3.4| Remote Debugging EclipseLink on IBM WebSphere Application Server 7]]
| + | |
− | ===WebLogic===
| + | |
− | *Debugging on WebLogic Server requires disabling the default 30 second transaction timeout
| + | |
− | **- launch admin console at '''http://127.0.0.1:7001/console'''
| + | |
− | **- change '''Domain Configuration | Services | JTA | Timeout Seconds: (from 30 to 2147483647 max)'''
| + | |
− | | + | |
− | =Performance Discussion=
| + | |
− | *Rehash HashMap implementations periodically so that put/get calls achieve O(1) constant-time performance.
| + | |
− | | + | |
− | =References=
| + | |
− | | + | |
− | Page started on build 20090204
| + | |
Latest revision as of 13:37, 18 April 2015
This page is obsolete now.