Re: [Dspace-tech] Dspace Setup

2011-12-13 Thread helix84 
On Tue, Dec 13, 2011 at 14:23, Henry Atsu Agbodza
henry_agbo...@libr.ug.edu.gh wrote:
 Thanks so much.
 I was also thinking about another scenario where i can make the full text
 bitstream available but make sure people can not download it. That is they
 can view and read the entire text but can't download it.
 Can it also be done. If yes how can it be done.
 Once again Thank you.

What is the difference? When they're reading it they have already downloaded it.

Please, keep dspace-tech in CC when replying.

Regards,
~~helix84

--
Systems Optimization Self Assessment
Improve efficiency and utilization of IT resources. Drive out cost and 
improve service delivery. Take 5 minutes to use this Systems Optimization 
Self Assessment. http://www.accelacomm.com/jaw/sdnl/114/51450054/
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech

[Dspace-tech] Dspace Setup

2011-12-12 Thread Henry Atsu Agbodza 
Dear all, is it possible that i can limit access to a full text repository
by making sure people can only access some files by inputing a username
and a password.
Please if yes can you direct me as to how it can be done?
Thank you




--
Learn Windows Azure Live!  Tuesday, Dec 13, 2011
Microsoft is holding a special Learn Windows Azure training event for 
developers. It will provide a great way to learn Windows Azure and what it 
provides. You can attend the event by watching it streamed LIVE online.  
Learn more at http://p.sf.net/sfu/ms-windowsazure
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech

Re: [Dspace-tech] Dspace Setup

2011-12-12 Thread helix84 
On Mon, Dec 12, 2011 at 17:12, Henry Atsu Agbodza
henry_agbo...@libr.ug.edu.gh wrote:
 Dear all, is it possible that i can limit access to a full text repository
 by making sure people can only access some files by inputing a username
 and a password.
 Please if yes can you direct me as to how it can be done?
 Thank you

Hello Henry,

it is possible, just follow these steps (these are for XMLUI):

1) log in as administrator
2) put your users who should be have access into a group
3a) first try this with an individual item: open the item you want to
protect, choose Edit this item, Authorizations and for each file edit
it's access rights
3b) when you verify it works on an individual item, you can change
authorizations of whole collections using the Access control -
Authorizations - Click here to go to the item wildcard policy admin
tool
4) remove bitstream read access from the Anonymous group (which
represents all users including those who are not logged in)
5) add bitstream read access to your new group
6) that covered existing items; to ensure all newly submitted items
will have this policy, edit the collections which contains them and
set the same access rights; again, you can use the wildcard policy
admin tool

Before you do these changes, make sure to back up your database. It's
very likely you won't be able to get it to work on the first attempt,
so make sure you can revert the repository to a working state. You can
also back up your assetstore, but if you will be changing only access
rights and not adding/removing bitstreams, you don't need to touch the
assetstore (all access rights are stored in the database).

Regards,
~~helix84

--
Learn Windows Azure Live!  Tuesday, Dec 13, 2011
Microsoft is holding a special Learn Windows Azure training event for 
developers. It will provide a great way to learn Windows Azure and what it 
provides. You can attend the event by watching it streamed LIVE online.  
Learn more at http://p.sf.net/sfu/ms-windowsazure
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech

Re: [Dspace-tech] DSpace Setup

2010-10-01 Thread Pottinger, Hardy J. 
Doh! I just noticed I forgot to include the total number of unique titles in 
our repository: ~7,600.

And thanks to Keith Gilbertson for the replies. I've dug through catalina.out 
for the past few days, and the only errors we're seeing is typical broken pipe 
warnings, from users moving on before a thread finishes. Hmm... maybe it's safe 
to scale back the nightly tomcat reboot to a weekly reboot?

--Hardy 

 -Original Message-
 From: Pottinger, Hardy J. [mailto:pottinge...@umsystem.edu]
 Sent: Thursday, September 30, 2010 5:36 PM
 To: dspace-tech@lists.sourceforge.net
 Subject: Re: [Dspace-tech] DSpace Setup
 
 1. Contact Info: Hardy Pottinger, University of Missouri (MOspace)
 (message sent from my main e-mail address, use that).
 
 2.a. DSpace 1.6.2 (XMLUI) with local mods for user interface, and
 Shibboleth special groups handling
 1 assetstore at 1TB, 35GB used (big plans! really!)
 Number of items:
 
 2.b. Oracle Database 10g Enterprise Edition Release 10.2.0.4.0, running
 on another server (unknown spec)
 
 db.maxconnections = 50 (anything less than 50 is unstable)
 db.maxwait = 5000
 db.maxidle = 0 (idle connections are nailed by the firewall on the
 Oracle server, sysadmins will not change)
 
 2.c. All RHEL-provided, Tomcat 5.5.23, running behind Apache 2.2.3 via
 mod_proxy
 
 2.d. DSpace and Tomcat are on one server, Oracle db is on a shared
 server.
 
Server: Dell PowerEdge 2950
Memory size: 8110 MB
CPUs: 4 x Intel Xeon 5160 @ 3.00 GHz
OS: Red Hat Enterprise Linux Server release 5.5 (kernel 2.6.18-
 194.3.1.el5PAE)
 
 2.e. JAVA_OPTS=-Xmx512M -Xms256M (this will likely change soon, need
 to bump up PermGen)
 
 3. Back when we were running on DSpace 1.5.1, after a period of about
 24-36 hours of uptime, Tomcat became unavailable. Apache reported 503:
 service unavailable. Looking at a dump after killing all Java processes,
 it appeared that all database connections were unavailable. Changing the
 db.maxconnections and db.maxidle settings (see above) was helpful, but
 we are proactively rebooting tomcat and apache every night, to clean
 out the cobwebs. Have not disabled the nightly reboot since the upgrade
 to 1.6.2, so do not have current data/log files. I'm willing to try
 other config settings. I'm pretty sure I saw an interesting looking
 patch that drops database connections (mainly for streaming situations)
 that I can't seem to find right now, but might help this particular
 stability issue.
 
 4. Volunteer to help? Of course! I am a fledgling Java developer,
 reasonably competent application manager, and working with XSLT only
 makes me want to cry a little bit, nowadays. :-) We have a development
 server with a snapshot of our live repository, and are willing to do
 load testing, run a profiler, whatever it takes to help. We're certainly
 not experts in any the various tech running under the hood of DSpace,
 but keeping our repository running smoothly is our main job, and we aim
 to please. You may use my address as the main contact, but we have two
 more developers here who are willing to pitch in.
 
 --Hardy
 
  -Original Message-
  From: George Stanley Kozak [mailto:g...@cornell.edu]
  Sent: Wednesday, September 29, 2010 11:28 AM
  To: dspace-tech@lists.sourceforge.net
  Subject: [Dspace-tech] DSpace Setup
 
  Hi...
  Based on Tim Donohue's suggestion to share configuration and setup
  information, here is Cornell University's Dspace configuration:
 
  1.  Server: Sun sun4v T5140
Memory size: 65312 Megabytes (4 CPUs)
 
  2.  Running DSpace 1.6.2 (JSPUI) with local mods for User Interface,
  Embargo, and Refworks.
db.maxconnections = 50
db.maxwait = 5000
db.maxidle = 5
2 assetstores at 300GB each (using currently 323 GB)
Number of items: 14,960
Number of Communities/Collections: 789
 
  3.  Java 1.5.0_24
 
  4.  Apache 2.29 running mod_jk to tomcat
 
  5.  Tomcat 5.5.26
  JAVA_OPTS=-server -Xms1024m -Xmx2048m -Xmn64m
 -Dfile.encoding=UTF-8
 -XX:+UseParallelGC -verbose:gc
 -Xloggc:/dspace/dspace/log/gc.log
 -XX:+HeapDumpOnOutOfMemoryError
 -XX:PermSize=1024m -XX:MaxPermSize=1024m
 -XX:-UseGCOverheadLimit
 
  6.  PostGreSQL 8.3
  max_connections = 300
  shared_buffers = 32MB
  max_fsm_pages = 204800
 
  Though we experienced some performance problems in the past, that
 seemed
  to disappear after we went to DSpace 1.5.2.
 
  George Kozak
  Digital Library Specialist
  Cornell University Library Information Technologies (CUL-IT)
  501 Olin Library
  Cornell University
  Ithaca, NY 14853
  607-255-8924
 
  --
 --
  --
  Start uncovering the many advantages of virtual appliances
  and start using them to simplify application deployment and
  accelerate your shift to cloud computing

Re: [Dspace-tech] DSpace Setup

2010-10-01 Thread Hilton Gibson 

 Hi All

What are your URL's  or website address's ?

On 01/10/2010 18:59, Pottinger, Hardy J. wrote:

Doh! I just noticed I forgot to include the total number of unique titles in 
our repository: ~7,600.

And thanks to Keith Gilbertson for the replies. I've dug through catalina.out 
for the past few days, and the only errors we're seeing is typical broken pipe 
warnings, from users moving on before a thread finishes. Hmm... maybe it's safe 
to scale back the nightly tomcat reboot to a weekly reboot?

--Hardy


-Original Message-
From: Pottinger, Hardy J. [mailto:pottinge...@umsystem.edu]
Sent: Thursday, September 30, 2010 5:36 PM
To: dspace-tech@lists.sourceforge.net
Subject: Re: [Dspace-tech] DSpace Setup

1. Contact Info: Hardy Pottinger, University of Missouri (MOspace)
(message sent from my main e-mail address, use that).

2.a. DSpace 1.6.2 (XMLUI) with local mods for user interface, and
Shibboleth special groups handling
 1 assetstore at 1TB, 35GB used (big plans! really!)
 Number of items:

2.b. Oracle Database 10g Enterprise Edition Release 10.2.0.4.0, running
on another server (unknown spec)

 db.maxconnections = 50 (anything less than 50 is unstable)
 db.maxwait = 5000
 db.maxidle = 0 (idle connections are nailed by the firewall on the
Oracle server, sysadmins will not change)

2.c. All RHEL-provided, Tomcat 5.5.23, running behind Apache 2.2.3 via
mod_proxy

2.d. DSpace and Tomcat are on one server, Oracle db is on a shared
server.

Server: Dell PowerEdge 2950
Memory size: 8110 MB
CPUs: 4 x Intel Xeon 5160 @ 3.00 GHz
OS: Red Hat Enterprise Linux Server release 5.5 (kernel 2.6.18-
194.3.1.el5PAE)

2.e. JAVA_OPTS=-Xmx512M -Xms256M (this will likely change soon, need
to bump up PermGen)

3. Back when we were running on DSpace 1.5.1, after a period of about
24-36 hours of uptime, Tomcat became unavailable. Apache reported 503:
service unavailable. Looking at a dump after killing all Java processes,
it appeared that all database connections were unavailable. Changing the
db.maxconnections and db.maxidle settings (see above) was helpful, but
we are proactively rebooting tomcat and apache every night, to clean
out the cobwebs. Have not disabled the nightly reboot since the upgrade
to 1.6.2, so do not have current data/log files. I'm willing to try
other config settings. I'm pretty sure I saw an interesting looking
patch that drops database connections (mainly for streaming situations)
that I can't seem to find right now, but might help this particular
stability issue.

4. Volunteer to help? Of course! I am a fledgling Java developer,
reasonably competent application manager, and working with XSLT only
makes me want to cry a little bit, nowadays. :-) We have a development
server with a snapshot of our live repository, and are willing to do
load testing, run a profiler, whatever it takes to help. We're certainly
not experts in any the various tech running under the hood of DSpace,
but keeping our repository running smoothly is our main job, and we aim
to please. You may use my address as the main contact, but we have two
more developers here who are willing to pitch in.

--Hardy


-Original Message-
From: George Stanley Kozak [mailto:g...@cornell.edu]
Sent: Wednesday, September 29, 2010 11:28 AM
To: dspace-tech@lists.sourceforge.net
Subject: [Dspace-tech] DSpace Setup

Hi...
Based on Tim Donohue's suggestion to share configuration and setup
information, here is Cornell University's Dspace configuration:

1.  Server: Sun sun4v T5140
   Memory size: 65312 Megabytes (4 CPUs)

2.  Running DSpace 1.6.2 (JSPUI) with local mods for User Interface,
Embargo, and Refworks.
   db.maxconnections = 50
   db.maxwait = 5000
   db.maxidle = 5
   2 assetstores at 300GB each (using currently 323 GB)
   Number of items: 14,960
   Number of Communities/Collections: 789

3.  Java 1.5.0_24

4.  Apache 2.29 running mod_jk to tomcat

5.  Tomcat 5.5.26
JAVA_OPTS=-server -Xms1024m -Xmx2048m -Xmn64m
   -Dfile.encoding=UTF-8
   -XX:+UseParallelGC -verbose:gc
   -Xloggc:/dspace/dspace/log/gc.log
   -XX:+HeapDumpOnOutOfMemoryError
   -XX:PermSize=1024m -XX:MaxPermSize=1024m
   -XX:-UseGCOverheadLimit

6.  PostGreSQL 8.3
max_connections = 300
shared_buffers = 32MB
max_fsm_pages = 204800

Though we experienced some performance problems in the past, that

seemed

to disappear after we went to DSpace 1.5.2.

George Kozak
Digital Library Specialist
Cornell University Library Information Technologies (CUL-IT)
501 Olin Library
Cornell University
Ithaca, NY 14853
607-255-8924

--

--

--
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your

Re: [Dspace-tech] DSpace Setup

2010-10-01 Thread Tim Donohue 
Hilton and all,

Quick FYI -- we actually have a list of all known DSpace installs 
worldwide off the DSpace webiste (under the Who's Using DSpace link).

http://www.dspace.org/index.php?option=com_formdashboardItemid=151lang=en

So, if you are ever curious to see someone's install, it's highly likely 
you can find a link there. This list is also searchable, and you can 
filter by database type, DSpace version, OS, etc.

- Tim

On 10/1/2010 12:18 PM, Hilton Gibson wrote:
   Hi All

 What are your URL's or website address's ?

 On 01/10/2010 18:59, Pottinger, Hardy J. wrote:
 Doh! I just noticed I forgot to include the total number of unique titles in 
 our repository: ~7,600.

 And thanks to Keith Gilbertson for the replies. I've dug through 
 catalina.out for the past few days, and the only errors we're seeing is 
 typical broken pipe warnings, from users moving on before a thread finishes. 
 Hmm... maybe it's safe to scale back the nightly tomcat reboot to a weekly 
 reboot?

 --Hardy

 -Original Message-
 From: Pottinger, Hardy J. [mailto:pottinge...@umsystem.edu]
 Sent: Thursday, September 30, 2010 5:36 PM
 To:dspace-tech@lists.sourceforge.net
 Subject: Re: [Dspace-tech] DSpace Setup

 1. Contact Info: Hardy Pottinger, University of Missouri (MOspace)
 (message sent from my main e-mail address, use that).

 2.a. DSpace 1.6.2 (XMLUI) with local mods for user interface, and
 Shibboleth special groups handling
  1 assetstore at 1TB, 35GB used (big plans! really!)
  Number of items:

 2.b. Oracle Database 10g Enterprise Edition Release 10.2.0.4.0, running
 on another server (unknown spec)

  db.maxconnections = 50 (anything less than 50 is unstable)
  db.maxwait = 5000
  db.maxidle = 0 (idle connections are nailed by the firewall on the
 Oracle server, sysadmins will not change)

 2.c. All RHEL-provided, Tomcat 5.5.23, running behind Apache 2.2.3 via
 mod_proxy

 2.d. DSpace and Tomcat are on one server, Oracle db is on a shared
 server.

 Server: Dell PowerEdge 2950
 Memory size: 8110 MB
 CPUs: 4 x Intel Xeon 5160 @ 3.00 GHz
 OS: Red Hat Enterprise Linux Server release 5.5 (kernel 2.6.18-
 194.3.1.el5PAE)

 2.e. JAVA_OPTS=-Xmx512M -Xms256M (this will likely change soon, need
 to bump up PermGen)

 3. Back when we were running on DSpace 1.5.1, after a period of about
 24-36 hours of uptime, Tomcat became unavailable. Apache reported 503:
 service unavailable. Looking at a dump after killing all Java processes,
 it appeared that all database connections were unavailable. Changing the
 db.maxconnections and db.maxidle settings (see above) was helpful, but
 we are proactively rebooting tomcat and apache every night, to clean
 out the cobwebs. Have not disabled the nightly reboot since the upgrade
 to 1.6.2, so do not have current data/log files. I'm willing to try
 other config settings. I'm pretty sure I saw an interesting looking
 patch that drops database connections (mainly for streaming situations)
 that I can't seem to find right now, but might help this particular
 stability issue.

 4. Volunteer to help? Of course! I am a fledgling Java developer,
 reasonably competent application manager, and working with XSLT only
 makes me want to cry a little bit, nowadays. :-) We have a development
 server with a snapshot of our live repository, and are willing to do
 load testing, run a profiler, whatever it takes to help. We're certainly
 not experts in any the various tech running under the hood of DSpace,
 but keeping our repository running smoothly is our main job, and we aim
 to please. You may use my address as the main contact, but we have two
 more developers here who are willing to pitch in.

 --Hardy

 -Original Message-
 From: George Stanley Kozak [mailto:g...@cornell.edu]
 Sent: Wednesday, September 29, 2010 11:28 AM
 To:dspace-tech@lists.sourceforge.net
 Subject: [Dspace-tech] DSpace Setup

 Hi...
 Based on Tim Donohue's suggestion to share configuration and setup
 information, here is Cornell University's Dspace configuration:

 1. Server: Sun sun4v T5140
Memory size: 65312 Megabytes (4 CPUs)

 2. Running DSpace 1.6.2 (JSPUI) with local mods for User Interface,
 Embargo, and Refworks.
db.maxconnections = 50
db.maxwait = 5000
db.maxidle = 5
2 assetstores at 300GB each (using currently 323 GB)
Number of items: 14,960
Number of Communities/Collections: 789

 3. Java 1.5.0_24

 4. Apache 2.29 running mod_jk to tomcat

 5. Tomcat 5.5.26
JAVA_OPTS=-server -Xms1024m -Xmx2048m -Xmn64m
   -Dfile.encoding=UTF-8
   -XX:+UseParallelGC -verbose:gc
   -Xloggc:/dspace/dspace/log/gc.log
   -XX:+HeapDumpOnOutOfMemoryError
   -XX:PermSize=1024m -XX:MaxPermSize=1024m
   -XX:-UseGCOverheadLimit

 6. PostGreSQL 8.3
max_connections = 300
shared_buffers = 32MB
max_fsm_pages = 204800

 Though we experienced

Re: [Dspace-tech] DSpace Setup

2010-10-01 Thread Pottinger, Hardy J. 
Doh! Again. The URL to our repository is: https://mospace.umsystem.edu/xmlui/.

--Hardy 

 -Original Message-
 From: Hilton Gibson [mailto:hilton.gib...@gmail.com]
 Sent: Friday, October 01, 2010 12:19 PM
 To: dspace-tech@lists.sourceforge.net
 Subject: Re: [Dspace-tech] DSpace Setup
 
 Hi All
 
 What are your URL's  or website address's ?
 
 On 01/10/2010 18:59, Pottinger, Hardy J. wrote:
 
   Doh! I just noticed I forgot to include the total number of unique
 titles in our repository: ~7,600.
 
   And thanks to Keith Gilbertson for the replies. I've dug through
 catalina.out for the past few days, and the only errors we're seeing is
 typical broken pipe warnings, from users moving on before a thread
 finishes. Hmm... maybe it's safe to scale back the nightly tomcat reboot
 to a weekly reboot?
 
   --Hardy
 
 
   -Original Message-
   From: Pottinger, Hardy J. [mailto:pottinge...@umsystem.edu]
   Sent: Thursday, September 30, 2010 5:36 PM
   To: dspace-tech@lists.sourceforge.net
   Subject: Re: [Dspace-tech] DSpace Setup
 
   1. Contact Info: Hardy Pottinger, University of Missouri
 (MOspace)
   (message sent from my main e-mail address, use that).
 
   2.a. DSpace 1.6.2 (XMLUI) with local mods for user interface,
 and
   Shibboleth special groups handling
   1 assetstore at 1TB, 35GB used (big plans! really!)
   Number of items:
 
   2.b. Oracle Database 10g Enterprise Edition Release
 10.2.0.4.0, running
   on another server (unknown spec)
 
   db.maxconnections = 50 (anything less than 50 is
 unstable)
   db.maxwait = 5000
   db.maxidle = 0 (idle connections are nailed by the
 firewall on the
   Oracle server, sysadmins will not change)
 
   2.c. All RHEL-provided, Tomcat 5.5.23, running behind Apache
 2.2.3 via
   mod_proxy
 
   2.d. DSpace and Tomcat are on one server, Oracle db is on a
 shared
   server.
 
  Server: Dell PowerEdge 2950
  Memory size: 8110 MB
  CPUs: 4 x Intel Xeon 5160 @ 3.00 GHz
  OS: Red Hat Enterprise Linux Server release 5.5 (kernel
 2.6.18-
   194.3.1.el5PAE)
 
   2.e. JAVA_OPTS=-Xmx512M -Xms256M (this will likely change
 soon, need
   to bump up PermGen)
 
   3. Back when we were running on DSpace 1.5.1, after a period
 of about
   24-36 hours of uptime, Tomcat became unavailable. Apache
 reported 503:
   service unavailable. Looking at a dump after killing all Java
 processes,
   it appeared that all database connections were unavailable.
 Changing the
   db.maxconnections and db.maxidle settings (see above) was
 helpful, but
   we are proactively rebooting tomcat and apache every night,
 to clean
   out the cobwebs. Have not disabled the nightly reboot since
 the upgrade
   to 1.6.2, so do not have current data/log files. I'm willing
 to try
   other config settings. I'm pretty sure I saw an interesting
 looking
   patch that drops database connections (mainly for streaming
 situations)
   that I can't seem to find right now, but might help this
 particular
   stability issue.
 
   4. Volunteer to help? Of course! I am a fledgling Java
 developer,
   reasonably competent application manager, and working with
 XSLT only
   makes me want to cry a little bit, nowadays. :-) We have a
 development
   server with a snapshot of our live repository, and are
 willing to do
   load testing, run a profiler, whatever it takes to help.
 We're certainly
   not experts in any the various tech running under the hood of
 DSpace,
   but keeping our repository running smoothly is our main job,
 and we aim
   to please. You may use my address as the main contact, but we
 have two
   more developers here who are willing to pitch in.
 
   --Hardy
 
 
   -Original Message-
   From: George Stanley Kozak [mailto:g...@cornell.edu]
   Sent: Wednesday, September 29, 2010 11:28 AM
   To: dspace-tech@lists.sourceforge.net
   Subject: [Dspace-tech] DSpace Setup
 
   Hi...
   Based on Tim Donohue's suggestion to share configuration
 and setup
   information, here is Cornell University's Dspace
 configuration:
 
   1.  Server: Sun sun4v T5140
 Memory size: 65312 Megabytes (4 CPUs)
 
   2

Re: [Dspace-tech] DSpace Setup

2010-09-30 Thread Pottinger, Hardy J. 
1. Contact Info: Hardy Pottinger, University of Missouri (MOspace) (message 
sent from my main e-mail address, use that).

2.a. DSpace 1.6.2 (XMLUI) with local mods for user interface, and Shibboleth 
special groups handling
1 assetstore at 1TB, 35GB used (big plans! really!)
Number of items: 

2.b. Oracle Database 10g Enterprise Edition Release 10.2.0.4.0, running on 
another server (unknown spec)

db.maxconnections = 50 (anything less than 50 is unstable)
db.maxwait = 5000
db.maxidle = 0 (idle connections are nailed by the firewall on the Oracle 
server, sysadmins will not change)

2.c. All RHEL-provided, Tomcat 5.5.23, running behind Apache 2.2.3 via mod_proxy

2.d. DSpace and Tomcat are on one server, Oracle db is on a shared server. 

   Server: Dell PowerEdge 2950
   Memory size: 8110 MB
   CPUs: 4 x Intel Xeon 5160 @ 3.00 GHz
   OS: Red Hat Enterprise Linux Server release 5.5 (kernel 
2.6.18-194.3.1.el5PAE)

2.e. JAVA_OPTS=-Xmx512M -Xms256M (this will likely change soon, need to bump 
up PermGen)

3. Back when we were running on DSpace 1.5.1, after a period of about 24-36 
hours of uptime, Tomcat became unavailable. Apache reported 503: service 
unavailable. Looking at a dump after killing all Java processes, it appeared 
that all database connections were unavailable. Changing the db.maxconnections 
and db.maxidle settings (see above) was helpful, but we are proactively 
rebooting tomcat and apache every night, to clean out the cobwebs. Have not 
disabled the nightly reboot since the upgrade to 1.6.2, so do not have current 
data/log files. I'm willing to try other config settings. I'm pretty sure I saw 
an interesting looking patch that drops database connections (mainly for 
streaming situations) that I can't seem to find right now, but might help this 
particular stability issue.

4. Volunteer to help? Of course! I am a fledgling Java developer, reasonably 
competent application manager, and working with XSLT only makes me want to cry 
a little bit, nowadays. :-) We have a development server with a snapshot of our 
live repository, and are willing to do load testing, run a profiler, whatever 
it takes to help. We're certainly not experts in any the various tech running 
under the hood of DSpace, but keeping our repository running smoothly is our 
main job, and we aim to please. You may use my address as the main contact, but 
we have two more developers here who are willing to pitch in.

--Hardy 

 -Original Message-
 From: George Stanley Kozak [mailto:g...@cornell.edu]
 Sent: Wednesday, September 29, 2010 11:28 AM
 To: dspace-tech@lists.sourceforge.net
 Subject: [Dspace-tech] DSpace Setup
 
 Hi...
 Based on Tim Donohue's suggestion to share configuration and setup
 information, here is Cornell University's Dspace configuration:
 
 1.Server: Sun sun4v T5140
   Memory size: 65312 Megabytes (4 CPUs)
 
 2.Running DSpace 1.6.2 (JSPUI) with local mods for User Interface,
 Embargo, and Refworks.
   db.maxconnections = 50
   db.maxwait = 5000
   db.maxidle = 5
   2 assetstores at 300GB each (using currently 323 GB)
   Number of items: 14,960
   Number of Communities/Collections: 789
 
 3.Java 1.5.0_24
 
 4.Apache 2.29 running mod_jk to tomcat
 
 5.Tomcat 5.5.26
   JAVA_OPTS=-server -Xms1024m -Xmx2048m -Xmn64m
  -Dfile.encoding=UTF-8
  -XX:+UseParallelGC -verbose:gc
  -Xloggc:/dspace/dspace/log/gc.log
  -XX:+HeapDumpOnOutOfMemoryError
  -XX:PermSize=1024m -XX:MaxPermSize=1024m
  -XX:-UseGCOverheadLimit
 
 6.PostGreSQL 8.3
   max_connections = 300
   shared_buffers = 32MB
   max_fsm_pages = 204800
 
 Though we experienced some performance problems in the past, that seemed
 to disappear after we went to DSpace 1.5.2.
 
 George Kozak
 Digital Library Specialist
 Cornell University Library Information Technologies (CUL-IT)
 501 Olin Library
 Cornell University
 Ithaca, NY 14853
 607-255-8924
 
 
 --
 Start uncovering the many advantages of virtual appliances
 and start using them to simplify application deployment and
 accelerate your shift to cloud computing.
 http://p.sf.net/sfu/novell-sfdev2dev
 ___
 DSpace-tech mailing list
 DSpace-tech@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/dspace-tech

--
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech

Re: [Dspace-tech] DSpace Setup

2010-09-30 Thread Keith Gilbertson 

On Sep 30, 2010, at 6:36 PM, Pottinger, Hardy J. wrote:

 
 
 3. Back when we were running on DSpace 1.5.1, after a period of about 24-36 
 hours of uptime, Tomcat became unavailable. Apache reported 503: service 
 unavailable. Looking at a dump after killing all Java processes, it appeared 
 that all database connections were unavailable. Changing the 
 db.maxconnections and db.maxidle settings (see above) was helpful, but we are 
 proactively rebooting tomcat and apache every night, to clean out the 
 cobwebs. Have not disabled the nightly reboot since the upgrade to 1.6.2, so 
 do not have current data/log files. I'm willing to try other config settings. 
 I'm pretty sure I saw an interesting looking patch that drops database 
 connections (mainly for streaming situations) that I can't seem to find right 
 now, but might help this particular stability issue.


There's a patch here for xmlui:
http://jira.dspace.org/jira/browse/DS-677

I'm don't know if this addresses the problem that you used to have in 1.5, 
though.  I think I've seen something like what you're talking about with a 
scheduling conflict between vacuuming or other maintenance of the database and 
the media filter processes running.  It's been a long time though and I'm very 
fuzzy on this.

In 1.6, the solr statistics code seems to make heavy use of database 
connections to figure out which item, collections, and communities a bitstream 
belongs.  I haven't spent enough time poking around though to see if the 
database usage might be reduced, or the connections held open less often. 

 On a side note, I noticed that in the slides for the recent presentation from 
@mire about the statistics system, there are a few suggestions for optimizing 
solr sites with heavy usage.  I missed the seminar, though, so I'm not sure of 
the details.

--keith


--
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech

Re: [Dspace-tech] DSpace Setup

2010-09-30 Thread Keith Gilbertson 

On Sep 30, 2010, at 7:14 PM, Keith Gilbertson wrote:
   I think I've seen something like what you're talking about with a 
 scheduling conflict between vacuuming or other maintenance of the database 
 and the media filter processes running.  It's been a long time though and I'm 
 very fuzzy on this.

Now that I'm thinking about it, it may have been an item import or some other 
long running batch process.

   I haven't spent enough time poking around though to see if the database 
 usage might be reduced, or the connections held open less often. 


Instead of connections held open less often, I think I meant something more 
along the lines of reduce the amount of time it takes to return a database 
connection back to the database pool and/or reduce the number of concurrent 
connections needed.

 


--
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech

[Dspace-tech] DSpace Setup

2010-09-29 Thread George Stanley Kozak 
Hi...
Based on Tim Donohue's suggestion to share configuration and setup information, 
here is Cornell University's Dspace configuration:

1.  Server: Sun sun4v T5140
  Memory size: 65312 Megabytes (4 CPUs) 

2.  Running DSpace 1.6.2 (JSPUI) with local mods for User Interface, 
Embargo, and Refworks. 
  db.maxconnections = 50
  db.maxwait = 5000
  db.maxidle = 5
  2 assetstores at 300GB each (using currently 323 GB)
  Number of items: 14,960
  Number of Communities/Collections: 789 

3.  Java 1.5.0_24

4.  Apache 2.29 running mod_jk to tomcat

5.  Tomcat 5.5.26
JAVA_OPTS=-server -Xms1024m -Xmx2048m -Xmn64m
   -Dfile.encoding=UTF-8 
   -XX:+UseParallelGC -verbose:gc
   -Xloggc:/dspace/dspace/log/gc.log
   -XX:+HeapDumpOnOutOfMemoryError
   -XX:PermSize=1024m -XX:MaxPermSize=1024m
   -XX:-UseGCOverheadLimit

6.  PostGreSQL 8.3
max_connections = 300
shared_buffers = 32MB
max_fsm_pages = 204800

Though we experienced some performance problems in the past, that seemed to 
disappear after we went to DSpace 1.5.2.

George Kozak
Digital Library Specialist
Cornell University Library Information Technologies (CUL-IT)
501 Olin Library
Cornell University
Ithaca, NY 14853
607-255-8924

--
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech