Hopefully, when I get a place to test my new releases against your new releases, it won't take a manual to do a build! :-)
Ralph
> -----Original Message-----
> From: ivan.masar@... [mailto:ivan.masar@...] On Behalf Of
> helix84
> Sent: Friday, July 23, 2010 4:50 PM
> To: Mark Diggory
> Cc: Domingo Iglesias; dspace-tech@...; LeVan,Ralph
> Subject: Re: [Dspace-tech] [dspace-tech] DRIVER & OAI Extended Addon
>
> Hello Mark,
>
> I'm only a user of DSpace and I don't know the details of how Maven
> works. I can only say it would be great if we can build all add-ons
> from one repository. I understand Ant and Maven are tools created to
> enable this but it needs some integration work first. I'm sure you can
> figure this out together with Ralph. If you require some user
> feedback, I'll be glad to help.
>
> I'll try to help out with the manual, too - there were many issues I
> ran into and I compiled a list of problems and solutions which should
> be helpful to other users. As soon as I get a working SRW instance I
> can do a short installation manual. Hopefully when SRW will be built
> from the DSpace source eventually, it can become a part of the DSpace
> manual.
>
> Regards,
> ~~helix84

Found the solution. The problem was with the Debian system.
Check this link for solution
https://bugs.launchpad.net/debian/+source/sun-java5/+bug/162232
On Fri, Jul 23, 2010 at 2:48 PM, Koushik Banerjee <
koushik.banerjee@...> wrote:
> Hello,
> I am running DSpace 1.4.1 on
> OS: Debian Linux (lenny)
> Web Server: Apache Tomcat
> DBMS: postgresql
>
> When I click on the "Titles" link at the left navigational bar to browse by
> titles, I get a page which has the header, left navigational bar and a
> crumbtrail with link to [HOME]> but nothing else. No error jsp, no footer.
> The html code just ends abruptly. The browsing works when I click the
> "titles" button from inside a community, except for one particular
> community. When I click "titles" from that community, the output is similar
> except it shows crumbtrail for the community below [HOME]->. I hacked
> the org.dspace.app.webui.servlet.BrowseServlet.java to catch any exception
> and print the stack trace. This is what I get -
> null=============================================
> org.apache.jasper.JasperException at
> org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:460)at
> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:355) at
> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:329) at
> org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265) at
> javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269) at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at
> org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:679) at
> org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:461) at
> org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:399) at
> org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301)at org.dspace.app.webui.util.JSPManager.showJSP(JSPManager.java:91) at
> org.dspace.app.webui.servlet.BrowseServlet.doDSGet(BrowseServlet.java:501) at
> org.dspace.app.webui.servlet.DSpaceServlet.processRequest(DSpaceServlet.java:151) at
> org.dspace.app.webui.servlet.DSpaceServlet.doGet(DSpaceServlet.java:99) at
> javax.servlet.http.HttpServlet.service(HttpServlet.java:689) at
> javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269) at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:172)at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117) at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108) at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:174)at
> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:874) at
> org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665) at
> org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528) at
> org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81) at
> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689) at
> java.lang.Thread.run(Thread.java:595)
>
> Anyone has any idea what might be wrong. I was looking at
> other JasperException reported, but they seem to have originated from
> slightly different sources.
>
> Thanks for your help.
>

Hello Mark,
I'm only a user of DSpace and I don't know the details of how Maven
works. I can only say it would be great if we can build all add-ons
from one repository. I understand Ant and Maven are tools created to
enable this but it needs some integration work first. I'm sure you can
figure this out together with Ralph. If you require some user
feedback, I'll be glad to help.
I'll try to help out with the manual, too - there were many issues I
ran into and I compiled a list of problems and solutions which should
be helpful to other users. As soon as I get a working SRW instance I
can do a short installation manual. Hopefully when SRW will be built
from the DSpace source eventually, it can become a part of the DSpace
manual.
Regards,
~~helix84

Hello,
I am running DSpace 1.4.1 on
OS: Debian Linux (lenny)
Web Server: Apache Tomcat
DBMS: postgresql
When I click on the "Titles" link at the left navigational bar to browse by
titles, I get a page which has the header, left navigational bar and a
crumbtrail with link to [HOME]> but nothing else. No error jsp, no footer.
The html code just ends abruptly. The browsing works when I click the
"titles" button from inside a community, except for one particular
community. When I click "titles" from that community, the output is similar
except it shows crumbtrail for the community below [HOME]->. I hacked
the org.dspace.app.webui.servlet.BrowseServlet.java to catch any exception
and print the stack trace. This is what I get -
null=============================================
org.apache.jasper.JasperException at
org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:460)at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:355)at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:329)at
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265)at
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)at
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:679)at
org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:461)at
org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:399)at
org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301)at
org.dspace.app.webui.util.JSPManager.showJSP(JSPManager.java:91)at
org.dspace.app.webui.servlet.BrowseServlet.doDSGet(BrowseServlet.java:501)at
org.dspace.app.webui.servlet.DSpaceServlet.processRequest(DSpaceServlet.java:151)at
org.dspace.app.webui.servlet.DSpaceServlet.doGet(DSpaceServlet.java:99)at
javax.servlet.http.HttpServlet.service(HttpServlet.java:689)at
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:172)at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:174)at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:874)at
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665)at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528)at
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81)at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689)at
java.lang.Thread.run(Thread.java:595)
Anyone has any idea what might be wrong. I was looking at
other JasperException reported, but they seem to have originated from
slightly different sources.
Thanks for your help.

Ivan and Domingo,
Why not manage this in the dspace svn modules directory
(http://scm.dspace.org/svn/repo/modules/) and we setup a process to
get the Maven repository publishing necessary for your's and others
modules? Once we get the artifacts deployed there, you can drop having
have the user having to compile them on installation.
Its another excellent use-case for dspace modularity and we are about
to entertain a discussion on the topic in an upcoming special topics
meeting in the near future? this makes two, we have the dspace-srw
work we see Ralph LeVan and other approaching and this use-case where
we have a need to release separate versions of oai-extended to support
various versions of DSpace.
This is where we need feedback from the community, where are the
pain-points in the current approach to modularity, how do we continue
to step away from the idea of patching DSpace to include addons? These
are questions you can provide requirements/feedback on to assist us in
improving the mechanism.
For instance, adding in configuration requires merging into the
dspace/config directory those files required to customize the oai
options. Can this be alleviated by having some installer
functionality in the Service-Manager that creates the files in config
if they are absent?
Separate files for that configuration rather than merging into the
dspace.cfg is a great start, if the addon can operate on defaults
without the files present, your alleviating another installation step
and leaving such additions for customizing default behavior after
installation.
We welcome your feedback and interaction.
Cheers,
Mark
On Fri, Jul 23, 2010 at 1:02 AM, helix84 <helix84@...> wrote:
> On Fri, Jul 23, 2010 at 09:48, Domingo Iglesias <diglesias@...> wrote:
>> I think the problem is not related with the access to the repository
>> from the dspace server since I cannot access the following urls with
>> my browser:
>> http://repo1.maven.org/maven2/org/dspace/dspace-oaiextended-webapp/1.5.2/dspace-oaiextended-webapp-1.5.2.pom
>> http://repo1.maven.org/maven2/org/dspace/dspace-oaiextended-api/1.5.2/dspace-oaiextended-api-1.5.2.pom
>> http://repo1.maven.org/maven2/org/dspace/dspace-oaiextended-webapp/1.5.2/dspace-oaiextended-webapp-1.5.2.war
>> http://repo1.maven.org/maven2/org/dspace/dspace-oaiextended-api/1.5.2/dspace-oaiextended-api-1.5.2.jar
>>
>> it reports http error 404, file not found, but I can access the file
>> that appears in the thread
>> (http://repo1.maven.org/maven2/org/apache/maven/doxia/doxia/1.0-alpha-11/doxia-1.0-alpha-11.pom)
>
> Ah, you're right. It's not a problem on your side, the files are
> missing in the maven repository.
>
> Which version of dspace are you building? The regular release
> (dspace-1.5.2-release.zip) or the source release
> (dspace-1.5.2-src-release.zip)? In the former case it may help if you
> use the source release instead and build the modules yourself (the
> procedure is the same, only building takes a minute longer). I'm not
> sure it will help but it might.
>
> Regards,
> ~~helix84
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> _______________________________________________
> DSpace-tech mailing list
> DSpace-tech@...
> https://lists.sourceforge.net/lists/listinfo/dspace-tech
>
--
Mark R. Diggory
Head of U.S. Operations - @mire
http://www.atmire.com - Institutional Repository Solutions
http://www.togather.eu - Before getting together, get Tog@...

If we can get a reference to the oclc release svn or jar/war we can
begin to publish it into our maven repository and I can drop retaining
the code locally in the dspace repo... We could then use our maven
overlay process to build in any necessary dspace customizations on our
end and we would manage the deployment to maven central repo for you.
This would likewise, work well for the Discovery customizations we
have talked about doing.
Cheers,
Mark
On Thu, Jul 22, 2010 at 10:51 AM, LeVan,Ralph <levan@...> wrote:
> My preference is to work on the oclcsrw version and find a mechanism to synchronize that with a DSpace copy.
>
> Ralph
>
>> -----Original Message-----
>> From: ivan.masar@... [mailto:ivan.masar@...] On Behalf Of
>> helix84
>> Sent: Thursday, July 22, 2010 11:23 AM
>> To: LeVan,Ralph
>> Cc: dspace-tech
>> Subject: Re: [Dspace-tech] SRW/U server problems
>>
>> On Thu, Jul 22, 2010 at 17:14, LeVan,Ralph <levan@...> wrote:
>> > Please include me in that conversation.
>> >
>> > I'd really like to get you guys running on my latest code. I've made
>> > significant enhancements to support Linked Data and think you'd like to
>> > have them.
>> >
>> > But, I have a problem. I don't run a DSpace instance myself and
>> > installing one just for testing purposes had gotten way too complicated.
>> > Is there someone out there that runs a test DSpace that would be willing
>> > to give me a logon to their server so I could test new SRW releases?
>>
>> Yes, I could do that. I'll look into it tomorrow. Installing DSpace is
>> not a problem for me, installing SRW is, so you would have to play
>> with that.
>>
>> Which SRW server are you developing? The OCLC one? Or the dspace-srw
>> module?
>>
>> Regards,
>> ~~helix84
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> _______________________________________________
> DSpace-tech mailing list
> DSpace-tech@...
> https://lists.sourceforge.net/lists/listinfo/dspace-tech
>
--
Mark R. Diggory
Head of U.S. Operations - @mire
http://www.atmire.com - Institutional Repository Solutions
http://www.togather.eu - Before getting together, get Tog@...

Not that I'm aware of since there's no entry in dspace.cfg for it. Perhaps someone can dig around in the code to see if it was an oversight.
--
sands fish
Software Engineer
MIT Libraries
Technology Research & Development
sands@...<mailto:sands@...>
E25-131
On Jul 23, 2010, at 11:47 AM, helix84 wrote:
On Fri, Jul 23, 2010 at 17:27, Sands Alden Fish <sands@...<mailto:sands@...>> wrote:
What I was suggesting is removing the HTML code that displays that link. Is that not sufficient? Do you need to disable the /register URL if none of your users know it's available?
Well, I might resort to that, but I thought there must be a way to
turn it off...
Regards,
~~helix84

On Fri, Jul 23, 2010 at 17:27, Sands Alden Fish <sands@...> wrote:
> What I was suggesting is removing the HTML code that displays that link. Is that not sufficient? Do you need to disable the /register URL if none of your users know it's available?
Well, I might resort to that, but I thought there must be a way to
turn it off...
Regards,
~~helix84

What I was suggesting is removing the HTML code that displays that link. Is that not sufficient? Do you need to disable the /register URL if none of your users know it's available?
-sf
On Jul 23, 2010, at 11:21 AM, helix84 wrote:
> On Fri, Jul 23, 2010 at 17:07, Sands Alden Fish <sands@...> wrote:
>> Is it not enough to remove the link?
>
> I'm not sure what you mean by "it". In my configuration as I described
> above, the Register link is still shown and /register url can be used.
>
> Regards,
> ~~helix84

On Fri, Jul 23, 2010 at 17:07, Sands Alden Fish <sands@...> wrote:
> Is it not enough to remove the link?
I'm not sure what you mean by "it". In my configuration as I described
above, the Register link is still shown and /register url can be used.
Regards,
~~helix84

Is it not enough to remove the link?
--
sands fish
Software Engineer
MIT Libraries
Technology Research & Development
sands@...<mailto:sands@...>
E25-131
On Jul 23, 2010, at 3:36 AM, helix84 wrote:
Hello,
I want to have all my users in LDAP autoregister in DSpace, but only
users I add manually (administrators) login via password.
The problem is that I haven't found a way to turn off autoregistration
for the password method, i.e. there's a "Register" link in XMLUI and
users can enter their email and register. I checked, there's no
authentication.password.autoregister = false
How do I disable registration?

Hi Bram,
it seems related to our memory problems. Restarting Tomcat solved the problem and RSS are shown as they should. We have increased memory allocation to Tomcat from 1GB to 2GB, in the hope we can prevent running out of memory.
It remains strange though, because the site would display normally. Only the RSS feeds were giving errors.
Regards,
Francis Brouns
________________________________
Van: bluyten@... [mailto:bluyten@...] Namens Bram Luyten
Verzonden: vrijdag 23 juli 2010 13:57
Aan: Brouns, Francis
CC: dspace-tech@...
Onderwerp: Re: [Dspace-tech] Authorisation error on rss feeds
Hi Francis,
does the problem go away when you change:
#harvest.includerestricted.oai = false
into
harvest.includerestricted.oai = true ?
I'm not sure, but the ListIdentifiers call might also be used for the RSS, so it's related to http://jira.dspace.org/jira/browse/DS-212
In any case, that specific error is fixed in DSpace 1.6 with the attached patch.
regards,
Bram Luyten
@mire - http://www.atmire.com
Technologielaan 9 - 3001 Heverlee - Belgium
533 2nd Street - Encinitas, CA 92024 - USA
http://www.togather.eu - Before getting together, get Tog@...
On Fri, Jul 23, 2010 at 11:47 AM, Brouns, Francis <Francis.Brouns@...<mailto:Francis.Brouns@...>> wrote:
Hi,
Last week we upgraded our DSpace 1.4.2 server to DSpace 1.5.2. The tests at the testserver went all fine. Now on the production server we are running into problems we did not encounter at the testserver. For example with the RSS feeds.
The configuration in dspace.cfg is:
harvest.includerestricted.rss = false
#harvest.includerestricted.oai = false
harvest.includerestricted.subscription = false
On the test server this is working fine. On the new production server, we get internal server errors on the RSS feeds. An example error message is given below.
On the mailing list there are comparable messages, but they refer to the OAI-PMH harvest. In our case, the harvest is not causing any problems.
Any tips on how to trace the source of this problem are welcome.
-- URL Was: http://dspace.ou.nl/feed/rss_2.0/site
-- Method: GET
-- Parameters were:
Exception:
java.lang.NullPointerException
at org.dspace.authorize.AuthorizeManager.getAuthorizedGroups(AuthorizeManager.java:718)
at org.dspace.search.Harvest.harvest(Harvest.java:273)
at org.dspace.app.webui.servlet.FeedServlet.itemsChanged(FeedServlet.java:281)
at org.dspace.app.webui.servlet.FeedServlet.doDSGet(FeedServlet.java:230)
at org.dspace.app.webui.servlet.DSpaceServlet.processRequest(DSpaceServlet.java:151)
at org.dspace.app.webui.servlet.DSpaceServlet.doGet(DSpaceServlet.java:99)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:845)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:595)
Kind regards,
Francis Brouns
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first<http://sprint.com/first&gt; -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
DSpace-tech mailing list
DSpace-tech@...<mailto:DSpace-tech@...>
https://lists.sourceforge.net/lists/listinfo/dspace-tech

Dear Robin, Hilton,
Thanks for your quick replies. I will also allocate the memory directly to tomcat, instead of setting java_opts as environment variable.
Thanks, Francis
-----Oorspronkelijk bericht-----
Van: TAYLOR Robin [mailto:Robin.Taylor@...]
Verzonden: vrijdag 23 juli 2010 13:01
Aan: Brouns, Francis; 'dspace-tech@...'
Onderwerp: RE: Dspace out of memory errors
Hi Francis,
It's the memory allocated to Tomcat rather than the total available to the server that is the problem. The memory required by DSpace has increased over the years but there are no known memory leaks in 1.5 (there were in earlier versions). Since you have nothing else running on the machine allocate another gigabyte to Tomcat and see if that helps . We have up to 3G allocated to various installations although most are running more than one Dspace.
Cheers, Robin.
Robin Taylor
Main Library
University of Edinburgh
Tel. 0131 6513808
> -----Original Message-----
> From: Brouns, Francis [mailto:Francis.Brouns@...]
> Sent: 23 July 2010 10:48
> To: 'dspace-tech@...'
> Subject: [Dspace-tech] Dspace out of memory errors
>
> Hi,
>
> Last week we completed the upgrade of our DSpace 1.4.2
> instance to DSpace 1.5.2, but now are encountering lots of
> memory problems, which we did not encounter on our test server.
>
> DSpace is installed on a SLES11 server, the Oracle database
> is located at a different machine. We are running Tomcat6
> (installed via Yast) and Sun Java 1.5 (installed via RPM). We
> run the daily-digest, filter-media and the stats cronjob.
> Apart from DSpace no other applications are running on this
> server. We now assigned 6GB RAM to the server, and increased
> java_opts to Xmx1024. In addition, Tomcat is restarted every
> night. At first this seemed to help, but we are still running
> into memory errors.
>
> On our previous production server we also encountered these
> kind of problems, but could solve them by adding additional
> RAM to the server, increasing heapsize in java_opts and
> restarting tomcat every night. This time this does not
> prevent the errors.
>
> Any tips on where I should look at to figure out what is
> causing this, are welcome.
>
> Exception:
> javax.servlet.ServletException: java.lang.OutOfMemoryError:
> Java heap space
> at
> org.apache.jasper.runtime.PageContextImpl.doHandlePageExceptio
> n(PageContextImpl.java:852)
> at
> org.apache.jasper.runtime.PageContextImpl.handlePageException(
> PageContextImpl.java:781)
> at org.apache.jsp.index_jsp._jspService(index_jsp.java:137)
> at
> org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
> at
> org.apache.jasper.servlet.JspServletWrapper.service(JspServlet
> Wrapper.java:374)
> at
> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet
> .java:342)
> at
> org.apache.jasper.servlet.JspServlet.service(JspServlet.java:267)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilt
> er(ApplicationFilterChain.java:290)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(Appli
> cationFilterChain.java:206)
> at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardW
> rapperValve.java:233)
> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardC
> ontextValve.java:191)
> at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHost
> Valve.java:128)
> at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReport
> Valve.java:102)
> at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEn
> gineValve.java:109)
> at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdap
> ter.java:286)
> at
> org.apache.coyote.http11.Http11Processor.process(Http11Process
> or.java:845)
> at
> org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandle
> r.process(Http11Protocol.java:583)
> at
> org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.
> java:447)
> at java.lang.Thread.run(Thread.java:595)
> Caused by: java.lang.OutOfMemoryError: Java heap space
>
> Kind regards,
> Francis Brouns
>
>
> --------------------------------------------------------------
> ----------------
> This SF.net email is sponsored by Sprint What will you do
> first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> _______________________________________________
> DSpace-tech mailing list
> DSpace-tech@...
> https://lists.sourceforge.net/lists/listinfo/dspace-tech
>
--
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.

Hi Francis,
It's the memory allocated to Tomcat rather than the total available to the server that is the problem. The memory required by DSpace has increased over the years but there are no known memory leaks in 1.5 (there were in earlier versions). Since you have nothing else running on the machine allocate another gigabyte to Tomcat and see if that helps . We have up to 3G allocated to various installations although most are running more than one Dspace.
Cheers, Robin.
Robin Taylor
Main Library
University of Edinburgh
Tel. 0131 6513808
> -----Original Message-----
> From: Brouns, Francis [mailto:Francis.Brouns@...]
> Sent: 23 July 2010 10:48
> To: 'dspace-tech@...'
> Subject: [Dspace-tech] Dspace out of memory errors
>
> Hi,
>
> Last week we completed the upgrade of our DSpace 1.4.2
> instance to DSpace 1.5.2, but now are encountering lots of
> memory problems, which we did not encounter on our test server.
>
> DSpace is installed on a SLES11 server, the Oracle database
> is located at a different machine. We are running Tomcat6
> (installed via Yast) and Sun Java 1.5 (installed via RPM). We
> run the daily-digest, filter-media and the stats cronjob.
> Apart from DSpace no other applications are running on this
> server. We now assigned 6GB RAM to the server, and increased
> java_opts to Xmx1024. In addition, Tomcat is restarted every
> night. At first this seemed to help, but we are still running
> into memory errors.
>
> On our previous production server we also encountered these
> kind of problems, but could solve them by adding additional
> RAM to the server, increasing heapsize in java_opts and
> restarting tomcat every night. This time this does not
> prevent the errors.
>
> Any tips on where I should look at to figure out what is
> causing this, are welcome.
>
> Exception:
> javax.servlet.ServletException: java.lang.OutOfMemoryError:
> Java heap space
> at
> org.apache.jasper.runtime.PageContextImpl.doHandlePageExceptio
> n(PageContextImpl.java:852)
> at
> org.apache.jasper.runtime.PageContextImpl.handlePageException(
> PageContextImpl.java:781)
> at org.apache.jsp.index_jsp._jspService(index_jsp.java:137)
> at
> org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
> at
> org.apache.jasper.servlet.JspServletWrapper.service(JspServlet
> Wrapper.java:374)
> at
> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet
> .java:342)
> at
> org.apache.jasper.servlet.JspServlet.service(JspServlet.java:267)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilt
> er(ApplicationFilterChain.java:290)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(Appli
> cationFilterChain.java:206)
> at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardW
> rapperValve.java:233)
> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardC
> ontextValve.java:191)
> at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHost
> Valve.java:128)
> at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReport
> Valve.java:102)
> at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEn
> gineValve.java:109)
> at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdap
> ter.java:286)
> at
> org.apache.coyote.http11.Http11Processor.process(Http11Process
> or.java:845)
> at
> org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandle
> r.process(Http11Protocol.java:583)
> at
> org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.
> java:447)
> at java.lang.Thread.run(Thread.java:595)
> Caused by: java.lang.OutOfMemoryError: Java heap space
>
> Kind regards,
> Francis Brouns
>
>
> --------------------------------------------------------------
> ----------------
> This SF.net email is sponsored by Sprint What will you do
> first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> _______________________________________________
> DSpace-tech mailing list
> DSpace-tech@...
> https://lists.sourceforge.net/lists/listinfo/dspace-tech
>
--
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.

I had the same problem.
Now I use the following on an Ubuntu machine.
>>>>
# Arguments to pass to the Java virtual machine (JVM).
JAVA_OPTS="-Djava.awt.headless=true -Xms512m -Xmx1024m
-XX:MaxPermSize=512m -XX:+CMSClassUnloadingEnabled
-XX:+CMSPermGenSweepingEnabled"
>>>>
On 23/07/2010 11:47, Brouns, Francis wrote:
> Hi,
>
> Last week we completed the upgrade of our DSpace 1.4.2 instance to DSpace 1.5.2, but now are encountering lots of memory problems, which we did not encounter on our test server.
>
> DSpace is installed on a SLES11 server, the Oracle database is located at a different machine. We are running Tomcat6 (installed via Yast) and Sun Java 1.5 (installed via RPM). We run the daily-digest, filter-media and the stats cronjob. Apart from DSpace no other applications are running on this server. We now assigned 6GB RAM to the server, and increased java_opts to Xmx1024. In addition, Tomcat is restarted every night. At first this seemed to help, but we are still running into memory errors.
>
> On our previous production server we also encountered these kind of problems, but could solve them by adding additional RAM to the server, increasing heapsize in java_opts and restarting tomcat every night. This time this does not prevent the errors.
>
> Any tips on where I should look at to figure out what is causing this, are welcome.
>
> Exception:
> javax.servlet.ServletException: java.lang.OutOfMemoryError: Java heap space
> at org.apache.jasper.runtime.PageContextImpl.doHandlePageException(PageContextImpl.java:852)
> at org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:781)
> at org.apache.jsp.index_jsp._jspService(index_jsp.java:137)
> at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
> at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:374)
> at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:342)
> at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:267)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:845)
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
> at java.lang.Thread.run(Thread.java:595)
> Caused by: java.lang.OutOfMemoryError: Java heap space
>
> Kind regards,
> Francis Brouns
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> _______________________________________________
> DSpace-tech mailing list
> DSpace-tech@...
> https://lists.sourceforge.net/lists/listinfo/dspace-tech
>
--
Hilton Gibson
Systems Administrator
JS Gericke Library Room 1025D
Stellenbosch University
Private Bag X5036
Stellenbosch
7599
South Africa
Tel: +27 21 808 4100 | Cell: +27 84 646 4758

Hi,
Last week we completed the upgrade of our DSpace 1.4.2 instance to DSpace 1.5.2, but now are encountering lots of memory problems, which we did not encounter on our test server.
DSpace is installed on a SLES11 server, the Oracle database is located at a different machine. We are running Tomcat6 (installed via Yast) and Sun Java 1.5 (installed via RPM). We run the daily-digest, filter-media and the stats cronjob. Apart from DSpace no other applications are running on this server. We now assigned 6GB RAM to the server, and increased java_opts to Xmx1024. In addition, Tomcat is restarted every night. At first this seemed to help, but we are still running into memory errors.
On our previous production server we also encountered these kind of problems, but could solve them by adding additional RAM to the server, increasing heapsize in java_opts and restarting tomcat every night. This time this does not prevent the errors.
Any tips on where I should look at to figure out what is causing this, are welcome.
Exception:
javax.servlet.ServletException: java.lang.OutOfMemoryError: Java heap space
at org.apache.jasper.runtime.PageContextImpl.doHandlePageException(PageContextImpl.java:852)
at org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:781)
at org.apache.jsp.index_jsp._jspService(index_jsp.java:137)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:374)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:342)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:267)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:845)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.OutOfMemoryError: Java heap space
Kind regards,
Francis Brouns

Hi,
Last week we upgraded our DSpace 1.4.2 server to DSpace 1.5.2. The tests at the testserver went all fine. Now on the production server we are running into problems we did not encounter at the testserver. For example with the RSS feeds.
The configuration in dspace.cfg is:
harvest.includerestricted.rss = false
#harvest.includerestricted.oai = false
harvest.includerestricted.subscription = false
On the test server this is working fine. On the new production server, we get internal server errors on the RSS feeds. An example error message is given below.
On the mailing list there are comparable messages, but they refer to the OAI-PMH harvest. In our case, the harvest is not causing any problems.
Any tips on how to trace the source of this problem are welcome.
-- URL Was: http://dspace.ou.nl/feed/rss_2.0/site
-- Method: GET
-- Parameters were:
Exception:
java.lang.NullPointerException
at org.dspace.authorize.AuthorizeManager.getAuthorizedGroups(AuthorizeManager.java:718)
at org.dspace.search.Harvest.harvest(Harvest.java:273)
at org.dspace.app.webui.servlet.FeedServlet.itemsChanged(FeedServlet.java:281)
at org.dspace.app.webui.servlet.FeedServlet.doDSGet(FeedServlet.java:230)
at org.dspace.app.webui.servlet.DSpaceServlet.processRequest(DSpaceServlet.java:151)
at org.dspace.app.webui.servlet.DSpaceServlet.doGet(DSpaceServlet.java:99)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:845)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:595)
Kind regards,
Francis Brouns

Hi Ralph
Did you get access to a DSpace instance? If not, I can probably spin up
one of my Amazon instances for you to test on over the weekend.
Let me know.
Cheers
Hayden
On 23/07/10 01:51, LeVan,Ralph wrote:
> My preference is to work on the oclcsrw version and find a mechanism to synchronize that with a DSpace copy.
>
> Ralph
>
>
>> -----Original Message-----
>> From: ivan.masar@... [mailto:ivan.masar@...] On Behalf Of
>> helix84
>> Sent: Thursday, July 22, 2010 11:23 AM
>> To: LeVan,Ralph
>> Cc: dspace-tech
>> Subject: Re: [Dspace-tech] SRW/U server problems
>>
>> On Thu, Jul 22, 2010 at 17:14, LeVan,Ralph<levan@...> wrote:
>>
>>> Please include me in that conversation.
>>>
>>> I'd really like to get you guys running on my latest code. I've made
>>> significant enhancements to support Linked Data and think you'd like to
>>> have them.
>>>
>>> But, I have a problem. I don't run a DSpace instance myself and
>>> installing one just for testing purposes had gotten way too complicated.
>>> Is there someone out there that runs a test DSpace that would be willing
>>> to give me a logon to their server so I could test new SRW releases?
>>>
>> Yes, I could do that. I'll look into it tomorrow. Installing DSpace is
>> not a problem for me, installing SRW is, so you would have to play
>> with that.
>>
>> Which SRW server are you developing? The OCLC one? Or the dspace-srw
>> module?
>>
>> Regards,
>> ~~helix84
>>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> _______________________________________________
> DSpace-tech mailing list
> DSpace-tech@...
> https://lists.sourceforge.net/lists/listinfo/dspace-tech
>
--
Hayden Young
Managing Director
Wijiti Pty Ltd
p. +61 (0) 8 6102 1198
m. +61 (0) 405 520 778
e. haydenyoung@...
w. http://www.wijiti.com
vcard. http://www.wijiti.com/vcard/haydenyoung.vcf
NOTICE
This e-mail and any attachments are intended for the addressee(s) only and may be confidential. They may contain legally privileged or copyright material. You should not read, copy, use or disclose them without authorization. If you are not the intended recipient please contact the sender as soon as possible by return e-mail and then please delete both messages. This notice should not be removed.

Hello,
I want to have all my users in LDAP autoregister in DSpace, but only
users I add manually (administrators) login via password.
The problem is that I haven't found a way to turn off autoregistration
for the password method, i.e. there's a "Register" link in XMLUI and
users can enter their email and register. I checked, there's no
authentication.password.autoregister = false
How do I disable registration?
Regards,
~~helix84