Re: [dspace-tech] Re: Internal Error in jspui when searching or entering on a collection item
Hi Freddy! Well, it has been a long time since I faced this problem. I don't remember in details, but basically what I did was export all collections separately and perform a clean install, importing each collection separetely. Every time I imported a collection I verified whether it makes dspace crash or not. I don't know exactly if it was a problem with a given collection or if was a problem during the installation. Before reinstalling, please make a backup. The first time I exported the entire collection and reinstalled, dspace gave me an error during importing process. I could recover some collections, but others were lost. Best regards, *Walter* Em seg, 24 de set de 2018 às 01:14, Freddy Guerrero escreveu: > Now I have the same error in dspace version 6.3, I wanted to ask if you > could solve it? > > Freddy > > > > El jueves, 26 de octubre de 2017, 18:05:53 (UTC-5), Walter Nakamura > escribió: >> >> Hi! I'm having trouble when accessing a item on a collection or searching >> in jspui interface. The problem does not occur in xmlui. >> >> Any ideas? >> >> Here is the log file: >> >> 2017-10-26 18:53:03,485 INFO >> org.dspace.app.webui.discovery.DiscoverySearchRequestProcessor @ >> anonymous:session_id=D2FA8115706527A25FD50A90876A2F09:ip_addr=192.168.1.1: >> search:scope=null,query="null",results=(0,0,1) >> 2017-10-26 18:53:03,557 WARN org.dspace.app.webui.servlet.DSpaceServlet >> @ >> anonymous:session_id=D2FA8115706527A25FD50A90876A2F09:ip_addr=192.168.1.1:general_jspui_error:javax.servlet.ServletException\colon; >> org.apache.jasper.JasperException\colon; The absolute uri\colon; >> [http\colon;//java.sun.com/jsp/jstl/core] cannot be resolved in either >> web.xml or the jar files deployed with this application >> javax.servlet.ServletException: org.apache.jasper.JasperException: The >> absolute uri: [http://java.sun.com/jsp/jstl/core] cannot be resolved in >> either web.xml or the jar files deployed with this application >> at >> org.dspace.app.webui.util.JSPManager.showJSP(JSPManager.java:71) >> at >> org.dspace.app.webui.discovery.DiscoverySearchRequestProcessor.doSimpleSearch(DiscoverySearchRequestProcessor.java:447) >> at >> org.dspace.app.webui.servlet.SimpleSearchServlet.doDSGet(SimpleSearchServlet.java:63) >> at >> org.dspace.app.webui.servlet.DSpaceServlet.processRequest(DSpaceServlet.java:126) >> at >> org.dspace.app.webui.servlet.DSpaceServlet.doGet(DSpaceServlet.java:73) >> at javax.servlet.http.HttpServlet.service(HttpServlet.java:635) >> at javax.servlet.http.HttpServlet.service(HttpServlet.java:742) >> at >> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231) >> at >> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) >> at >> org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) >> at >> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) >> at >> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) >> at >> org.dspace.utils.servlet.DSpaceWebappServletFilter.doFilter(DSpaceWebappServletFilter.java:78) >> at >> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) >> at >> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) >> at >> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:198) >> at >> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96) >> at >> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:478) >> at >> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:140) >> at >> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:80) >> at >> org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:650) >> at >> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:87) >> at >> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:342) >> at >> org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:799) >> at >> org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66) >> at >> org.apache.coyote
Re: [dspace-tech] Problem with semicolons in bitstreams' name
I mean "indeed" instead of "in fact". Sorry! :) Em terça-feira, 18 de setembro de 2018 13:45:29 UTC-4, Walter Nakamura escreveu: > > Hi, Tim! In fact, we're using JSPUI. > > Thank you very much for the quick reply. I'll be waiting for the updates > regarding this issue. > > - Walter > > Em terça-feira, 18 de setembro de 2018 10:32:46 UTC-4, Tim Donohue > escreveu: >> >> Hi Walter, >> >> I just tried uploading a PDF with a semicolon in its name to our demo >> server (currently running DSpace 6.3). >> >> It works fine from the XMLUI: http://demo.dspace.org/xmlui/handle/10673/5 >> However, it looks like the JSPUI has difficulty with the semicolon: >> http://demo.dspace.org/jspui/handle/10673/5 (It throws an invalid >> identifier error.) >> >> So, this looks to be a bug in the JSPUI. I'm not aware of a fix at this >> time, but I logged the bug at: https://jira.duraspace.org/browse/DS-4011 >> >> - Tim >> >> On Mon, Sep 17, 2018 at 8:22 PM Walter Nakamura >> wrote: >> >>> Hi, guys! >>> >>> We're having a problem with dspace and semicolons in filenames. When we >>> upload a file without a semicolon in its name, the file opens as usual. >>> However, when it has a semicolon, dspace gives an error saying that the >>> identifier is invalid. If I edit the filename in dspace after its upload, >>> the bitstream works again. Is it normal? Is there any way to workaround >>> this problem? >>> >>> Thank you! >>> >>> -- >>> All messages to this mailing list should adhere to the DuraSpace Code of >>> Conduct: https://duraspace.org/about/policies/code-of-conduct/ >>> --- >>> 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...@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. >>> >> -- >> Tim Donohue >> Technical Lead for DSpace & DSpaceDirect >> DuraSpace.org | DSpace.org | DSpaceDirect.org >> > -- All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/ --- 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+unsubscr...@googlegroups.com. To post to this group, send email to dspace-tech@googlegroups.com. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
Re: [dspace-tech] Problem with semicolons in bitstreams' name
Hi, Tim! In fact, we're using JSPUI. Thank you very much for the quick reply. I'll be waiting for the updates regarding this issue. - Walter Em terça-feira, 18 de setembro de 2018 10:32:46 UTC-4, Tim Donohue escreveu: > > Hi Walter, > > I just tried uploading a PDF with a semicolon in its name to our demo > server (currently running DSpace 6.3). > > It works fine from the XMLUI: http://demo.dspace.org/xmlui/handle/10673/5 > However, it looks like the JSPUI has difficulty with the semicolon: > http://demo.dspace.org/jspui/handle/10673/5 (It throws an invalid > identifier error.) > > So, this looks to be a bug in the JSPUI. I'm not aware of a fix at this > time, but I logged the bug at: https://jira.duraspace.org/browse/DS-4011 > > - Tim > > On Mon, Sep 17, 2018 at 8:22 PM Walter Nakamura > wrote: > >> Hi, guys! >> >> We're having a problem with dspace and semicolons in filenames. When we >> upload a file without a semicolon in its name, the file opens as usual. >> However, when it has a semicolon, dspace gives an error saying that the >> identifier is invalid. If I edit the filename in dspace after its upload, >> the bitstream works again. Is it normal? Is there any way to workaround >> this problem? >> >> Thank you! >> >> -- >> All messages to this mailing list should adhere to the DuraSpace Code of >> Conduct: https://duraspace.org/about/policies/code-of-conduct/ >> --- >> 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...@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. >> > -- > Tim Donohue > Technical Lead for DSpace & DSpaceDirect > DuraSpace.org | DSpace.org | DSpaceDirect.org > -- All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/ --- 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+unsubscr...@googlegroups.com. To post to this group, send email to dspace-tech@googlegroups.com. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
[dspace-tech] Problem with semicolons in bitstreams' name
Hi, guys! We're having a problem with dspace and semicolons in filenames. When we upload a file without a semicolon in its name, the file opens as usual. However, when it has a semicolon, dspace gives an error saying that the identifier is invalid. If I edit the filename in dspace after its upload, the bitstream works again. Is it normal? Is there any way to workaround this problem? Thank you! -- All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/ --- 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+unsubscr...@googlegroups.com. To post to this group, send email to dspace-tech@googlegroups.com. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
[dspace-tech] Internal Error in jspui when searching or entering on a collection item
Hi! I'm having trouble when accessing a item on a collection or searching in jspui interface. The problem does not occur in xmlui. Any ideas? Here is the log file: 2017-10-26 18:53:03,485 INFO org.dspace.app.webui.discovery.DiscoverySearchRequestProcessor @ anonymous:session_id=D2FA8115706527A25FD50A90876A2F09:ip_addr=192.168.1.1:search:scope=null,query="null",results=(0,0,1) 2017-10-26 18:53:03,557 WARN org.dspace.app.webui.servlet.DSpaceServlet @ anonymous:session_id=D2FA8115706527A25FD50A90876A2F09:ip_addr=192.168.1.1:general_jspui_error:javax.servlet.ServletException\colon; org.apache.jasper.JasperException\colon; The absolute uri\colon; [http\colon;//java.sun.com/jsp/jstl/core] cannot be resolved in either web.xml or the jar files deployed with this application javax.servlet.ServletException: org.apache.jasper.JasperException: The absolute uri: [http://java.sun.com/jsp/jstl/core] cannot be resolved in either web.xml or the jar files deployed with this application at org.dspace.app.webui.util.JSPManager.showJSP(JSPManager.java:71) at org.dspace.app.webui.discovery.DiscoverySearchRequestProcessor.doSimpleSearch(DiscoverySearchRequestProcessor.java:447) at org.dspace.app.webui.servlet.SimpleSearchServlet.doDSGet(SimpleSearchServlet.java:63) at org.dspace.app.webui.servlet.DSpaceServlet.processRequest(DSpaceServlet.java:126) at org.dspace.app.webui.servlet.DSpaceServlet.doGet(DSpaceServlet.java:73) at javax.servlet.http.HttpServlet.service(HttpServlet.java:635) at javax.servlet.http.HttpServlet.service(HttpServlet.java:742) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at org.dspace.utils.servlet.DSpaceWebappServletFilter.doFilter(DSpaceWebappServletFilter.java:78) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:198) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:478) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:140) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:80) at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:650) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:87) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:342) at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:799) at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66) at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:868) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1457) at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) at java.lang.Thread.run(Thread.java:748) Caused by: org.apache.jasper.JasperException: The absolute uri: [http://java.sun.com/jsp/jstl/core] cannot be resolved in either web.xml or the jar files deployed with this application at org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:55) at org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:293) at org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:80) at org.apache.jasper.compiler.TagLibraryInfoImpl.generateTldResourcePath(TagLibraryInfoImpl.java:251) at org.apache.jasper.compiler.TagLibraryInfoImpl.(TagLibraryInfoImpl.java:122) at org.apache.jasper.compiler.Parser.parseTaglibDirective(Parser.java:434) at org.apache.jasper.compiler.Parser.parseDirective(Parser.java:492) at org.apache.jasper.compiler.Parser.parseElements(Parser.java:1448) at org.apache.jasper.compiler.Parser.parse(Parser.java:145) at
