The effect of setting 'auto-commit=true' (or similar) in jdbc drivers or the like

Hi,

   Studying a raw trace file produced by setting event 10046 on shows a number of lines such as:

XCTEND rlbk=0, rd_only=0, tim=13558440385826

This, presumably, indicates the end of a transaction - i.e. a 'commit'. Now, studying a 10046-trace with WebLogic at the 'client' end, commit activity, as reflected in the trace file by lines such as that above, appears to be reasonable (i.e. not after every single SQL update/insert/delete statement, but at what appears to be transaction boundaries). However, with other 'clients', such as jdbc thin driver (with auto-commit set to 'true'), there appear to be very few of these  'XCTEND' lines in the trace. My question therefore is - if auto-commit is set to true in these drivers, does this force