Jump to: navigation, search

Difference between revisions of "EclipseLink/Debugging"

m (Debugging EclipseLink on a Remote Application Server)
m (WebLogic)
 
Line 19: Line 19:
 
*Debugging on WebLogic Server requires disabling the default 30 second transaction timeout
 
*Debugging on WebLogic Server requires disabling the default 30 second transaction timeout
 
**- launch admin console at '''http://127.0.0.1:7001/console'''
 
**- launch admin console at '''http://127.0.0.1:7001/console'''
**- change '''Domain Configuration | Services | JTA | Timeout Seconds: (from 30 to 2147483647 max)'''
+
*- 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=
 
=Performance Discussion=

Latest revision as of 10:41, 23 September 2010

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
  • - 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