Scribd
Upload
52 views

Debugging Sessions in Application Server

To debug a T24 application running in an application server, you must first configure the application server to allow debugging. This involves specifying a debugging port when starting the server. In Eclipse, you then set up a JBC Remote debug configuration targeting that port. This allows debugging the application as if it were running locally, setting breakpoints and examining variables. Once debugging is complete, the application server continues running normally while Eclipse disconnects.

Uploaded by

M'hamed Zhioua
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
52 views

Debugging Sessions in Application Server

To debug a T24 application running in an application server, you must first configure the application server to allow debugging. This involves specifying a debugging port when starting the server. In Eclipse, you then set up a JBC Remote debug configuration targeting that port. This allows debugging the application as if it were running locally, setting breakpoints and examining variables. Once debugging is complete, the application server continues running normally while Eclipse disconnects.

Uploaded by

M'hamed Zhioua
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

Debugging sessions in Application Server 25/06/2020 14)16

You are here: Enterprise Frameworks > Platform Framework > TAFJ > TAFJ-JBC-Remote-Debugger > Debugging sessions in
Application Server

Debugging sessions in Application Server


Foremost, this document will concentrate on jBoss app server. Anything described for jBoss should work the same in any other app server. However, at the
time of this documentation is inscribed, it has tested on JBoss EAP 7.0.0.GA.

In order to debug your T24 running in an application server, first you need to let your app server know that you want to be able to debug it. For that, you have
to specify a debugging port using the option “jbc.debug” like this:

-Djbc.debug=<a_free_tcp_port>

As an example, locate your starting script and edit this line:

./standalone.sh --server-config=standalone-utp.xml -Djbc.debug=10314 . . .

Then start your server as usually.

In Eclipse, use the run menu and choose “debug configuration”

The window will ask which type of debug configuration wish to create. Choose JBC Remote and click New Launch Configuration

Below is the reference screenshot of configuration page for JBC Remote,

file:///Users/aajouad/Documents/T24%20Documentation/Help%20R1…_Remote_Debugger/Debugging%20sessions%20in%20Application.htm Page 1 sur 3


Debugging sessions in Application Server 25/06/2020 14)16

Container project: Choose the project in which you have the sources corresponding to what is deployed in the app server. BY selecting “Browse” only the
projects having the TAFJ Nature will be listed.

Host: Provide the host name or IP on which your app server is running

Port: Provide the TCP port specified in -Djbc.remote on your app server.

Connection Timeout (secs): You could launch the Debug target before your app server. In that case, Eclipse will wait until the app server is available. This
field indicates how many seconds Eclipse should wait.

Redirect Output: Normally, when running in an app server, CRT and PRINT are de-activated. However when debugging, this could be good to see those
outputs in your Eclipse IDE. This checkbox should always be ticked.

Set eclipse in listen mode: This option is for debugging the API and will be described in the next chapter.

Once you specified all those fields give a name to the configuration, click apply and debug.

Below is the reference screenshot of console:

Below is the reference screenshot of debug view:

At this point, you can debug whatever runs (JBC) on your app server.

You can view the new Session, once created:

file:///Users/aajouad/Documents/T24%20Documentation/Help%20R1…_Remote_Debugger/Debugging%20sessions%20in%20Application.htm Page 2 sur 3


Debugging sessions in Application Server 25/06/2020 14)16

You can do suspend, resume, set break points, etc. as a “normal” session.

As soon as you can stop your debug target, this will not stop the app server, instead, this will disconnect from it and let it run as normal.

Published on: 26/04/2018

file:///Users/aajouad/Documents/T24%20Documentation/Help%20R1…_Remote_Debugger/Debugging%20sessions%20in%20Application.htm Page 3 sur 3

You might also like