Q:

Is it appropriate to use exception names in bug report title?

Bug report title is very important to distinguish one bug from another without opening its description (steps, attachments). If we will not name them in appropriate way it would be:

lots of duplicates
many questions from project manager (What is it about? Is it really severe?..)

If testers have access to the console log, is it appropriate to use exception names in defect title?
E.g.: When 'Print contract' button is pressed, message "Provider org.apache.xalan.processor.TransformerFactoryImpl not found" is displayed in console-log.
Or: "java.lang.OutOfMemoryError: Java heap space." after 4 hours of work
Reason to use is that two different parts of software could arise a bug which originates from one place. TransformerFactoryImpl not found could crash stuff in different parts of software so why do we need to create dozens of bugs?

A:

We should not use exception names as Bug Titles:

Bug Title - Its expected to tell the story about bug in a single straight & clean sentence
We should always title a bug according to its behavior. 
According to me, good practice to title bug will be - simple english sentence which speaks about behavior of application 
This can be easily recollected and recognize by everyone as you mentioned like Tester, Developers, Manager & leads

