Hello Andrey
As Kern said in that bugreport, "Every job that starts opens a new connection (sometimes during the job additional connections will be opened)."
But is not persistent.
If you are running a command "list files jobid=XXX" of a job with some million of files and you have connection problems, maybe bconsole can be close, but is very rare.
Probably you can have a network issue and not bacula issue
If you have some problem about connection lost with client or storage, is interesting activate the option "Heartbeat Interval" in some Resources:
Heartbeat Interval = 300 seconds # Is a good configuration
Include the option above in the following files/resources:
bacula-dir.conf - Director, Storage, Client
bacula-fd.conf - FileDaemon (client side)
