I'm still experiencing this issue on release 5.6.5.

@drizzuto says "Note that this doesn't stop the underlying cause, but simply stops the log spam about it.", what are the side effects of this error? Do users still get mention notifications?

The reason I ask is that some users have reported intermittent issues receiving notifications and the only error I can find that looks remotely related is this one, as it's occurring on NotificationSender thread in my case.

We are running 5.7.3 and still get the error. Any chance of a resolution?

This is still an issue in 5.7.1 - this was noted in our current logs:

"2015-04-07 08:08:50,536 WARN [NotificationSender:thread-2] [atlassian.confluence.core.DefaultDataSourceFactory] getAvatar Error getting profile picture for user=[wroth], profilePicture=[com.atlassian.confluence.user.actions.ProfilePictureInfo@519a0980[downloadPath=/download/attachments/819260/user-avatar?version=2&modificationDate=1427319701273&api=v2,fileName=user-avatar,uploaded=true]] : The [DefaultAttachmentManager] is missing a reference to a [ContentEntityObjectDao] due to being improperly initialized via a legacy constructor.
"

I am wondering when this can be addressed; squelching warnings from the logs is an exceedingly painful work-around.

Hello, we used Confluence v5.4.1 and had this problem. We were asked to update the platform to v5.5.
We have updated the platform to v 5.5.6, but the error remains.
Help us , what do we do?

"2015-03-10 12:36:16,840 WARN [AtlassianEvent::CustomizableThreadFactory-3] [atlassian.confluence.core.DefaultDataSourceFactory] getAvatar Error getting profile picture for user=[sandrova], profilePicture=[com.atlassian.confluence.user.actions.ProfilePictureInfo@24accc7d[downloadPath=/download/attachments/193594576/sandrova.png?version=1&modificationDate=1380870449000&api=v2,fileName=sandrova.png,uploaded=true]] : The [DefaultAttachmentManager] is missing a reference to a [ContentEntityObjectDao] due to being improperly initialized via a legacy constructor.
– referer: https://bass.netcracker.com/display/COG/BR-SOW-SOPS-014 | url: /rest/statistics/1.0/service/saveViewStatistics/269825442/COG/scherbakov | userName: scherbakov
java.lang.RuntimeException: The [DefaultAttachmentManager] is missing a reference to a [ContentEntityObjectDao] due to being improperly initialized via a legacy constructor."

ralf.scheller@mueller.de, if you wish to simply suppress the log messages you can do the following:

1) Go to confluence admin
2) Go to "logging and profiling" on the left hand pane
3) Add a new entry for "com.atlassian.confluence.core.DefaultDataSourceFactory" at level ERROR or FATAL.

This will suppress all warning logging from that class.

Note that this doesn't stop the underlying cause, but simply stops the log spam about it.

We still use database storage in 5.6.3 - switching to anaother way is no option for us in the Moment.
There should be a option to suppress these errors in the logfile! It is almost impossible to find other errors in the logfile.
The amount of entries in the logfile also seems to cause a performance problem.

warning still occurs in 5.6.3

twjnorth, Confluence 5.6 supports clustering in it's Data Center edition. It requires a shared network drive of some flavour for attachment storage rather than making us of the database.

Paul, when you say database storage is deprecated, is this also for clustered confluence which states it has to use database storage ? - or does 5.5 also deprecate support for clustered confluence ? If the latter, what options are there for highly scalable confluence as this was the direction i was working towards and testing confluence for and if that support is not available, i will need to reconsider confluence all together ?