[
https://jira.duraspace.org/browse/DS-421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25875#comment-25875
]
Peter Dietz commented on DS-421:
--------------------------------
While looking through SolrLogger, I've noticed that the code to support
stuffing metadata into Solr stats is still possible.
https://github.com/DSpace/DSpace/blob/deb732e3cb2f36325cfda8aa28989695bfbd4cab/dspace-stats/src/main/java/org/dspace/statistics/SolrLogger.java#L137
Even though its been removed from dspace.cfg.
I would recommend removing all traces of metadataStorageInfo, IDEA says this
would affect a number of files.
> Setting solr.metadata.item.X property to an unqualified field generates
> exception in SolrLogger.post on item view and prevents Solr from logging the
> event
> ----------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DS-421
> URL: https://jira.duraspace.org/browse/DS-421
> Project: DSpace
> Issue Type: Bug
> Components: DSpace API
> Affects Versions: 1.6.0
> Reporter: Scott Hanrath
> Assignee: Mark Diggory
> Fix For: 1.6.0
>
>
> Setting a solr.metadata.item.X property to an unqualified field (e.g.,
> dc.title rather then dc.title.alternative) generates an exception in
> SolrLogger.post on item view. The ArrayIndexOutOfBoundsException appear to
> prevent Solr from logging the event.
> The stacktrace from the logs is:
> java.lang.ArrayIndexOutOfBoundsException: 2
> at org.dspace.statistics.SolrLogger.post(SolrLogger.java:216)
> at
> org.dspace.statistics.SolrLoggerUsageEventListener.receiveEvent(SolrLoggerUsageEventListener.java:48)
> at
> org.dspace.services.events.SystemEventService.fireLocalEvent(SystemEventService.java:154)
> at
> org.dspace.services.events.SystemEventService.fireEvent(SystemEventService.java:97)
> at
> org.dspace.app.xmlui.cocoon.UsageLoggerAction.logDspaceObject(UsageLoggerAction.java:61)
> [...]
> This is similar to DS-419 in that a metadata field like 'schema.element' is
> being split into an array and the methods is then trying to access
> non-existent 3rd element of the array (i.e., array[2], representing the
> qualifier) without checking the array length first.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.duraspace.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
