Difference between revisions of "Debugging Tips"

From truxwiki.com
Jump to navigation Jump to search
(Created page with "Truxton is made of separate processes communicating with each other over a message bus. This makes debugging easy and hard. =Getting The Process ID= Truxton ETL processes are...")
 
 
Line 7: Line 7:
 
So when they die and display a dialog box error message, it is very annoying.
 
So when they die and display a dialog box error message, it is very annoying.
 
If you are attempting to debug an error on a production server, it gets even more annoying.
 
If you are attempting to debug an error on a production server, it gets even more annoying.
While the dialog box tells you the name of the process, it does NOT tell you the process id.
+
While the dialog box tells you the name of the process, it does NOT tell you ''which'' process.
 
To find the process id you can use the <code>tasklist</code> tool.
 
To find the process id you can use the <code>tasklist</code> tool.
 
<source lang="bat">
 
<source lang="bat">
 
tasklist /FI "IMAGENAME eq MyETL.exe" /V
 
tasklist /FI "IMAGENAME eq MyETL.exe" /V
 
</source>
 
</source>

Latest revision as of 04:27, 2 November 2020

Truxton is made of separate processes communicating with each other over a message bus. This makes debugging easy and hard.

Getting The Process ID

Truxton ETL processes are windowless. They are not GUIs. So when they die and display a dialog box error message, it is very annoying. If you are attempting to debug an error on a production server, it gets even more annoying. While the dialog box tells you the name of the process, it does NOT tell you which process. To find the process id you can use the tasklist tool.

tasklist /FI "IMAGENAME eq MyETL.exe" /V