[Dspace-devel] [DuraSpace JIRA] (DS-1925) JSP UI failed to display page due to exception in registering usage event
Title: Message Title Monika Mevenkamp commented on an issue Re: JSP UI failed to display page due to exception in registering usage event here is the exception stack trace 2014-05-08 09:47:32,802 ERROR org.dspace.statistics.SolrLogger @ Failed DNS Lookup for IP:0:0:0:0:0:0:0:1%0 2014-05-08 09:47:32,802 DEBUG org.dspace.statistics.SolrLogger @ Invalid IP address java.net.UnknownHostException: Invalid IP address at org.xbill.DNS.ReverseMap.fromAddress(ReverseMap.java:109) at org.xbill.DNS.ReverseMap.fromAddress(ReverseMap.java:122) at org.dspace.statistics.util.DnsLookup.reverseDns(DnsLookup.java:30) at org.dspace.statistics.SolrLogger.post(SolrLogger.java:212) at org.dspace.statistics.SolrLoggerUsageEventListener.receiveEvent(SolrLoggerUsageEventListener.java:37) at org.dspace.services.events.SystemEventService.fireLocalEvent(SystemEventService.java:144) at org.dspace.services.events.SystemEventService.fireEvent(SystemEventService.java:86) at org.dspace.app.webui.servlet.HandleServlet.displayItem(HandleServlet.java:404) at org.dspace.app.webui.servlet.HandleServlet.doDSGet(HandleServlet.java:186) at org.dspace.app.webui.servlet.DSpaceServlet.processRequest(DSpaceServlet.java:126) at org.dspace.app.webui.servlet.DSpaceServlet.doGet(DSpaceServlet.java:71) at javax.servlet.http.HttpServlet.service(HttpServlet.java:621) at javax.servlet.http.HttpServlet.service(HttpServlet.java:728) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.dspace.utils.servlet.DSpaceWebappServletFilter.doFilter(DSpaceWebappServletFilter.java:78) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:502) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:100) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:953) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408) at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1041) at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:603) at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) at java.lang.Thread.run(Thread.java:695) Add Comment
[Dspace-devel] [DuraSpace JIRA] (DS-1986) REST API holds on to context for too long, should use DB pool
Title: Message Title Graham Triggs updated an issue DSpace / DS-1986 REST API holds on to context for too long, should use DB pool Change By: Graham Triggs Priority: Minor Critical Add Comment This message was sent by Atlassian JIRA (v6.1.7#6163-sha1:94d557d) -- Is your legacy SCM system holding you back? Join Perforce May 7 to find out: #149; 3 signs your SCM is hindering your productivity #149; Requirements for releasing software faster #149; Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1986) REST API holds on to context for too long, should use DB pool
Title: Message Title Graham Triggs commented on an issue Re: REST API holds on to context for too long, should use DB pool The context is being stored in a private STATIC member variable in the ItemsResource class (and probably the others too - I haven't checked). This means that it will create it once, and never let it go. Even removing the STATIC probably won't help - it's being wired through Spring, which typically only creates a single instance of the object when processing the configuration. Which puts it in the same class as webapp servlets - also, only a single instance is ever constructed for those too. These objects/methods really should be re-entrant. So no member variables - apart from static instances to loggers and other things that you deliberately know need to persist over multiple calls. Everything should be passed as parameters. This is particularly true for contexts / transactions that demarcate units of work. Apart from rare circumstances, these should always be passed in to method calls. Add Comment DSpace / DS-1986 REST API holds on to context for too long, should use DB pool REST API (Jersey), grabs a context, and never frees/returns/releases it. I don't know exactly what is going on, but it causes the REST API to not be able to reflect real-time updates to content. To repeat. Load a DSpace-REST result for some endpoint. Edit the title/name of the first object returned in that result. Reload the REST endpoint. For me, the... This message was sent by Atlassian JIRA (v6.1.7#6163-sha1:94d557d)
Re: [Dspace-devel] [DuraSpace JIRA] (DS-1925) JSP UI failed to display page due to exception in registering usage event
Hm, looks like an access from the local machine to me. And then of course DNS lookup would not work. Anja -- Anja Le Blanc Jorum Team Mimas On 08/05/2014 14:56, Monika Mevenkamp (DuraSpace JIRA) wrote: Monika Mevenkamp https://jira.duraspace.org/secure/ViewProfile.jspa?name=monikam *commented* on an issue Re: JSP UI failed to display page due to exception in registering usage event https://jira.duraspace.org/browse/DS-1925 here is the exception stack trace 2014-05-08 09:47:32,802 ERROR org.dspace.statistics.SolrLogger @ Failed DNS Lookup for IP:0:0:0:0:0:0:0:1%0 2014-05-08 09:47:32,802 DEBUG org.dspace.statistics.SolrLogger @ Invalid IP address java.net.UnknownHostException: Invalid IP address at org.xbill.DNS.ReverseMap.fromAddress(ReverseMap.java:109) at org.xbill.DNS.ReverseMap.fromAddress(ReverseMap.java:122) at org.dspace.statistics.util.DnsLookup.reverseDns(DnsLookup.java:30) at org.dspace.statistics.SolrLogger.post(SolrLogger.java:212) at org.dspace.statistics.SolrLoggerUsageEventListener.receiveEvent(SolrLoggerUsageEventListener.java:37) at org.dspace.services.events.SystemEventService.fireLocalEvent(SystemEventService.java:144) at org.dspace.services.events.SystemEventService.fireEvent(SystemEventService.java:86) at org.dspace.app.webui.servlet.HandleServlet.displayItem(HandleServlet.java:404) at org.dspace.app.webui.servlet.HandleServlet.doDSGet(HandleServlet.java:186) at org.dspace.app.webui.servlet.DSpaceServlet.processRequest(DSpaceServlet.java:126) at org.dspace.app.webui.servlet.DSpaceServlet.doGet(DSpaceServlet.java:71) at javax.servlet.http.HttpServlet.service(HttpServlet.java:621) at javax.servlet.http.HttpServlet.service(HttpServlet.java:728) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.dspace.utils.servlet.DSpaceWebappServletFilter.doFilter(DSpaceWebappServletFilter.java:78) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:502) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:100) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:953) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408) at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1041) at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:603) at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) at java.lang.Thread.run(Thread.java:695) Add Comment https://jira.duraspace.org/browse/DS-1925#add-comment Add Comment https://jira.duraspace.org/browse/DS-1925#add-comment DSpace https://jira.duraspace.org/browse/DS / Improvement https://jira.duraspace.org/browse/DS-1925 DS-1925 https://jira.duraspace.org/browse/DS-1925 JSP UI failed to display page due to exception in registering usage event https://jira.duraspace.org/browse/DS-1925 running on my laptop DSPACE failed to display an item page I tracked it down to an exception in HandleServet.java: displayItem new DSpace().getEventService().fireEvent( new UsageEvent( UsageEvent.Action.VIEW, request, context, ... This message was sent by Atlassian JIRA (v6.1.7#6163-sha1:94d557d) Atlassian logo -- Is your legacy SCM system holding you back? Join Perforce May 7 to find out: #149; 3 signs your SCM is hindering your productivity #149; Requirements for releasing software faster #149; Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel -- Is your legacy SCM system holding you back? Join Perforce May 7 to find out: #149; 3 signs
[Dspace-devel] [DuraSpace JIRA] (DS-1986) REST API holds on to context for too long, should use DB pool
Title: Message Title Peter Dietz commented on an issue Re: REST API holds on to context for too long, should use DB pool So I have solved this by removing the static portion, however I can't commit it because it causes severe performance issues, ie 90% error on jmeter due to db pool/connection mismanagement. I'll sadly stick with stale data for the time being, until I can address db pool performance. Add Comment DSpace / DS-1986 REST API holds on to context for too long, should use DB pool REST API (Jersey), grabs a context, and never frees/returns/releases it. I don't know exactly what is going on, but it causes the REST API to not be able to reflect real-time updates to content. To repeat. Load a DSpace-REST result for some endpoint. Edit the title/name of the first object returned in that result. Reload the REST endpoint. For me, the... This message was sent by Atlassian JIRA (v6.1.7#6163-sha1:94d557d) -- Is your legacy SCM system holding you back? Join Perforce May 7 to find out: #149; 3 signs your SCM is hindering your productivity #149; Requirements for releasing software faster
