Make the Debug participant extend the doPrepare(...) method to get profile dump the debug participant's timing info about jpos-ee HOT 4 CLOSED

The Debug participant functionality have been incorporated into the TransactionManager itself. The main reason for doing that was to emit in the same LogEvent profiling information. We don't have Debug and Trace events separated anymore, they get automatically emitted by the TM at the end of every transaction (provided the debug is on, which is usually the case).

Regarding the commit ID, it's right there: banknet-txnmgr-9:idle:1 - the 1 there is the commit ID.

from jpos-ee.

This may not be an issue.

I had the debug flag set to true and the debug participant added, this ended up creating 2 context loggings for one transaction.

I kept the flag and removed the participant and one entry got logged and the profiler entry for debug got logged too.

However I did notice that the commit entry in the log did not have a commit id.

<log realm="org.jpos.transaction.TransactionManager" at="2022-07-07T20:01:32.337" lifespan="2852ms">
  <commit>
    banknet-txnmgr-9:idle:1
    <context>
      NANOSTART: 114558888454917
      REQUEST: 
       <isomsg direction="incoming">
         <!-- org.jpos.iso.packager.GenericPackager[cfg/banknet_ebcidic_pci.xml] -->
         <field id="bitmap" value="{2, 3, 4, 6, 7, 10, 11, 12, 13, 14, 15, 16, 18, 22, 28, 32, 33, 35, 37, 41, 42, 43, 48, 49, 51, 61, 63}" type="bitmap"/>

Is this expected?

from jpos-ee.

Maybe we can document the following.

If you use the debug flag don't use the debug participant, otherwise you end up with 2 context log entries in the log.

from jpos-ee.

Done in jPOS-EE (bc9ceff).

jPOS-EE.pdf has been updated, the new notice looks like this:

from jpos-ee.