Notice: this Wiki will be going read only early in 2024 and edits will no longer be 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 on a Remote Application Server) |
m (→WebLogic) |
||
(3 intermediate revisions by the same user not shown) | |||
Line 14: | Line 14: | ||
==Debugging EclipseLink on a Remote Application Server== | ==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]] | [[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 2^30 (the normal 2147483647 max will throw a -1 int exception currently))''' | ||
+ | |||
+ | =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:41, 23 September 2010
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
WebSphere
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 2^30 (the normal 2147483647 max will throw a -1 int exception currently))
Performance Discussion
- Rehash HashMap implementations periodically so that put/get calls achieve O(1) constant-time performance.
References
Page started on build 20090204