JavaBaseDebugPort - Analytics Database - Teradata Vantage

Database Utilities
Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
VMware
Product
Analytics Database
Teradata Vantage
Release Number
17.20
Published
June 2022
ft:locale
en-US
ft:lastEdition
2024-05-02
dita:mapPath
ymn1628096214445.ditamap
dita:ditavalPath
qkf1628213546010.ditaval
dita:id
vkz1472241255652
lifecycle
latest
Product Category
Teradata Vantage™

Specifies the base number used to determine the debug port for Java external routines (Java external stored procedures and Java user-defined functions). This field is only used when debugging Java external routines.

Default

0 (The JVM debug port is disabled.)

Usage Notes

The actual port number to use for attaching a debugger to a Java external routine is the value of JavaBaseDebugPort plus an offset.

For Java user-defined functions running on a hybrid server, the offset is always 2000, so the debug port for these routines is always the value of JavaBaseDebugPort plus 2000.

For Java external routines running on secure servers, the offset depends on which instance of the server is executing the routine (there can be up to 10 secure servers per vproc), and on the type and ID of the vproc that is executing the routine. There are a total of 1000 offsets per node available for PE processes, and 1000 available for AMP processes. Therefore, only the following vprocs have debug ports available for Java external routines on each node:
  • The first hundred AMPs that have the lowest vproc ID numbers
  • The top hundred PEs that have the highest vproc ID numbers

The following table demonstrates how representative offsets are determined on a node with continuous vproc assignment.

Vproc IDs for PEs that have debug ports will be lower for systems upgraded from pre-14.0 releases.
Vproc Type Vproc ID Secure Server Instance Offset
PE 30719

(16383 on upgraded systems)

 1 through 10 0 through 9
PE 30718

(16382 on upgraded systems)

 1 through 10 10 through 19
PE 30717

(16381 on upgraded systems)

 1 through 10 20 through 29
  continuing on through:    
PE (16284 on upgraded systems) 1 through 10 990 through 999
PE 30619 or lower

(16283 on upgraded systems)

 None available None available
AMP 0 1 through 10 1000 through 1009
AMP 1 1 through 10 1010 through 1019
AMP 2 1 through 10 1020 through 1029
  continuing on through:    
AMP 99 1 through 10 1990 through 1999
AMP 100 or higher None available None available

Example: Java debug ports

Assume the value of JavaBaseDebugPort is 8000.
  • To debug any external routine running on a hybrid server, connect the debugger to port 10,000 (8000 plus the offset of 2000).
  • To debug an external routine running on the second secure server on PE 30719, connect the debugger to port 8001 (8000 plus the offset of 1).
  • To debug an external routine running on the fifth secure server on PE 30717, connect the debugger to port 8024 (8000 plus the offset of 24).
  • To debug an external routine running on the first secure server on AMP 0, connect the debugger to port 9000 (8000 plus the offset of 1000).

Related Information

For more information on Java external stored procedures and Java user-defined functions, see Teradata Vantage™ - SQL External Routine Programming, B035-1147.