Problem with display of Community List in DSpace 6.0

[George Kozak]

Hi...

I have just migrated from DSpace 5.5 to DSpace 6.0 (in test).  Everything works fine, but when I go to display the community list (<my dspace url>/community-list), I get an error:

java.lang.NullPointerException

I am using XMLUI interface with a modified MIrage2 theme.  I went to using a vanilla install to see if it was one of my modifications, but the vanilla Mirage2 theme produces the same error.

There is no error in the DSpace log file, but I see this:

2017-02-17 09:07:15,914 INFO  org.dspace.app.xmlui.aspect.discovery.SidebarFacetsTransformer @ facets for scope, null: 5

However, in the vanilla Mirage2, the default Communities display on the home page works.  So, I know that the information exists.

Any ideas as to what might be happening?  
--

***************************
George Kozak
Digital Library Specialist
Cornell University Library - IT
218 Olin Library
Cornell University
Ithaca, NY 14853
607-255-8924

gs...@cornell.edu

[Terry Brady]

Can you get a stack trace for the Null Pointer Exception?

Can you find anything useful in the tomcat log?

--
You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dspace-tech+unsubscribe@googlegroups.com.
To post to this group, send email to dspac...@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

--

Terry Brady

Applications Programmer Analyst

Georgetown University Library Information Technology

http://georgetown-university-libraries.github.io/

425-298-5498 (Seattle, WA)

[George Kozak]

Hi, Terry:

Nothing is showing up in the Tomcat log, and the underlining stack trace displayed just shows: "java.lang.NullPointerException"

and nothing else.

I did find the following error in the cocoon log:

2017-02-17 09:07:22,465 ERROR cocoon.handled  - Could not read resource cocoon://DRI/8/community-list

 at <map:serialize type="xml"> - resource://aspects/Discovery/sitemap.xmap:223:40        

 at <map:transform type="Navigation"> - resource://aspects/Discovery/sitemap.xmap:79:47

 at <map:generate> - resource://aspects/Discovery/sitemap.xmap:67:28        

 at <map:serialize type="xml"> - resource://aspects/Administrative/sitemap.xmap:1077:31

 at <map:transform type="Navigation"> - resource://aspects/Administrative/sitemap.xmap:299:38        

 at <map:transform type="SystemwideAlerts"> - resource://aspects/Administrative/sitemap.xmap:298:44

 at <map:generate> - resource://aspects/Administrative/sitemap.xmap:296:19

 (continues)

This has me stumped.

George Kozak

Cornell University

 

[George Kozak]

Terry:

I recompiled DSpace 6.0 and now I am seeing a stack trace when I go to see the community-list.  

Here is an excerpt of the trace:

Java stacktrace: java.lang.NullPointerException 

at org.dspace.content.DSpaceObjectServiceImpl.match(DSpaceObjectServiceImpl.java:427) 

at org.dspace.content.DSpaceObjectServiceImpl.getMetadata(DSpaceObjectServiceImpl.java:131) 

at org.dspace.content.DSpaceObjectServiceImpl.getMetadataFirstValue(DSpaceObjectServiceImpl.java:380) 

at org.dspace.content.CollectionServiceImpl.getMetadata(CollectionServiceImpl.java:395) 

at org.dspace.content.CollectionServiceImpl.getMetadata(CollectionServiceImpl.java:43) 

at org.dspace.app.xmlui.utils.DSpaceValidity.add(DSpaceValidity.java:271) 

at org.dspace.app.xmlui.aspect.artifactbrowser.CommunityBrowser.getValidity(CommunityBrowser.java:160) 

at sun.reflect.GeneratedMethodAccessor77.invoke(Unknown Source) 

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 

at java.lang.reflect.Method.invoke(Method.java:606) 

at org.apache.cocoon.core.container.spring.avalon.PoolableProxyHandler.invoke(PoolableProxyHandler.java:71) 

at com.sun.proxy.$Proxy287.getValidity(Unknown Source) 

at org.apache.cocoon.components.pipeline.impl.AbstractCachingProcessingPipeline.getValidityForInternalPipeline(AbstractCachingProcessingPipeline.java:987) 

...

George Kozak

Cornell University

[Dale Poulter]

I am encountering the same issue.  Did you determine the cause?

To unsubscribe from this group and stop receiving emails from it, send an email to dspac...@googlegroups.com.

[Nicholas Woodward]

I don't know the source of the bug, but when we upgraded from 5.x to 6.x we ran into a similar problem with that stack trace. The issue had to do with Collections that had a null field in the metadatavalue database table for their title. The lack of a title metadata field appeared to be left over from a previous migration. 

The SQL statement below resolved the problem for us by setting the null metadata_field_id to 64, which is the metadata_field_id for the title field in the metadatafieldregistry table. I would first check to see if you have any null metadata_field_id's with a resource_type_id of 3 (for collections) in your metadatavalue table. And also find the correct metadata_field_id for the title field in the metadatafieldregistry table, since it may be different in your database. And finally, be sure to test this query or any other like it on a staging instance of your database before you run it on production.

update metadatavalue set metadata_field_id = 64 where metadata_value_id in(SELECT metadata_value_id FROM metadatavalue JOIN handle as h ON h.resource_id = metadatavalue.dspace_object_id WHERE metadata_field_id is null AND resource_type_id=3);