[
https://jira.duraspace.org/browse/DS-1324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26858#comment-26858
]
Nestor Oviedo commented on DS-1324:
-----------------------------------
Hi Robin.
I think in a "normal usage", assuming the browse links are ok, this error
shouldn't appear. We've seen a lot of these errors when some bots crawled our
site.
The problem is a bad handling of parameters in class
org.dspace.browse.BrowseEngine, which assumes the index is of type "metadata"
just because the authority (or value) parameter is present, instead of checking
for the type parameter.
I couldn't tell if this replicates a problem that happens somewhere else. I saw
it here only.
This might be a minor bug, first because it requires a "bad" URL to reproduce
it, and also because discovery is about to replace these browse classes.
Cheers
> BrowseEngine tries to use a non existent bi_*_dmap and bi_*_dis
> ---------------------------------------------------------------
>
> Key: DS-1324
> URL: https://jira.duraspace.org/browse/DS-1324
> Project: DSpace
> Issue Type: Bug
> Components: DSpace API
> Affects Versions: 1.8.2, 3.0
> Reporter: Nestor Oviedo
> Labels: Browse, PSQLException, bi_1_dmap
> Fix For: 3.0
>
>
> When you make a request for "/browse?type={some_index}", where {some_index}
> is configured as of type "item", e.g.:
> "webui.browse.index.1 = dateissued:item:dateissued",
> and you also specifify the "value" (or "authority") parameter, the following
> exception is raised:
> "org.dspace.app.xmlui.utils.UIException: Unable to process browse".
> with the following Root exception:
> "org.postgresql.util.PSQLException: ERROR: current transaction is aborted,
> commands ignored until end of transaction block"
> You can reproduce this error in the demo site:
> http://demo.dspace.org/xmlui/browse?type=dateissued&value=some
> We have found that the problem seems to be in the method
> "org.dspace.browse.BrowseEngine.browseByItem()". It test if there is some
> filter value and then adds the "bi_x_dmap" and "bi_x_dis" as the filter
> mapping tables, without considering this browse index doesn't creates those
> tables.
> The Postgre log shows the following lines:
> ERROR: relation "bi_1_dmap" does not exist at character 95
> STATEMENT: SELECT COUNT(*) AS num FROM bi_item, (SELECT
> communities2item.item_id FROM communities2item, bi_1_dmap, bi_1_dis WHERE
> bi_1_dmap.distinct_id=bi_1_dis.id AND bi_1_dis.authority=$1 AND
> bi_1_dmap.item_id=communities2item.item_id AND
> communities2item.community_id=$2 ) mappings WHERE
> bi_item.item_id=mappings.item_id
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
