Henry Atsu Agbodza wrote:
Hi folks,
I am from Ghana and i have a problem of which i need some help. I´ve
installed DSpace on Fedora on a test machine. Everything works fine. I can
access port 80 of the DSPACE computer on other clients on the LAN but i
can´t access port 8080 let alone the
Hi.
Here @Exeter we are primarily using a Creative Commons license with an
embedded link.
However, when viewed in every other browser than IE this just displays the
html. I've boiled this down to the bitstream format, and its possible mainly
to add it to the known formats per item, but is
Hello Jason,
the liftdate is computed based on the embargo terms and the setter used.
At the moment there is one default embargo setter:
org.dspace.embargo.DefaultEmbargoSetter
which assumes the basic use case of the term being a date.
Which setter plugin to use is configured in the
All,
As you may or may not have been aware, in the past, we had an
(unadvertised) DSpace Demonstration Repository available for live demos,
testing, or just a place to play with the software before installing it.
We've now updated this DSpace Demonstration Repository to run DSpace
1.6.0, and
Henry,
It is also possible to run Tomcat on port 80, rather than port 8080.
To run Tomcat on port 80 in Linux, you'd have to do the following:
(1) Change its port from 8080 to 80 in [tomcat]/conf/server.xml
(2) Compile the 'jsvc' tool that comes with Tomcat, and start Tomcat
using 'jsvc'. You
Hi Kevin,
See:
- http://jira.dspace.org/jira/browse/DS-295
This has been fixed in DSpace 1.6.0. You may be able to use some of the
information from the JIRA issue to fix your current version if upgrading isn't
an option right now.
Thanks,
Stuart Lewis
IT Innovations Analyst and Developer
I'm having a puzzling problem. I am updating my system from DSpace 1.52 to 1.6.
I'm running RHEL Server release 5.3 (Tikanga).
My Java version is 1.5.0_20
My Tomcat version is 5.5.26 and I'm using mod_proxy_ajp to redirect to port 80.
I have upgraded correctly on my live server and everything
Jason,
Check your hosts file comparing with your virtual machine.
I had same problem that you my handle server is not worked, the hostname had
resolving a internal IP and we need to resolve a external IP (internet IP).
[ ]'s
Antoanne Pontes
On Thu, Apr 1, 2010 at 4:48 PM, Jason Fowler
I think I have my problem solved. It all had to do with the way I had
dspace.BaseUrl configured. I removed the xmlui from the end, and everything
went back to working like normal.
The startup is still painfully slow, though. Would anyone have any idea why?
-- Jason Fowler, CA, MSLS
Hi Jason,
How slow is slow? (Is it the handle server that is slow to startup, or tomcat?)
DSpace 1.6 will take slightly longer than earlier versions to start up as it
now has to start a new webapp (solr) and 'warm up' the solr indexes. Somewhere
between 20 seconds and a minute should be
As a tangent, You can run the webapps like solr on separate tomcat
instances if this becomes a concern. They seldom need to be restarted
as often as DSpace does. In fact, there are very good scalability
strategies that are oriented around replicating solr instances across
a cluster of tomcat
Stuart,
I have confirmed from watching catalina.out that it consistently takes nearly10
minutes to start. Here's the section of the file where the hangup occurs.
Apr 1, 2010 9:23:28 PM org.apache.coyote.http11.Http11BaseProtocol init
INFO: Initializing Coyote HTTP/1.1 on http-8080
Apr 1, 2010
It looks like the delay is before the solr servlet init log entry is
being called, IE before solr is loaded, disable the solr
webapplication from loading and test if the delay is still there
Likewise, what is the storage mount situation you are using here? If
file access is slow across this
Mark,
I'm not sure exactly how to disable the solr webapplication. Any suggestions?
The file access is pretty quick. We've never had any trouble before. We have an
app server for running the webapps and a storage server for everything else.
--Jason Fowler, CA, MSLS
Hi Jason,
You can disable the solr webapp by removing the whole solr directory from
[tomcat]/webapps.
Your storage server may be slowing down the loading of the solr index, but 10
minutes sounds quite severe. You could test it by moving the indexes to the
local disk. They shouldn't get too
Hello Mohit
In Tomcat Try this one : Give Full path(not relative) in appBase
Host name=xmlui appBase=/dspace/webapps/xmlui
unpackWARs=true autoDeploy=true
xmlValidation=false xmlNamespaceAware=false
For JSPUI :
Host name=jspui appBase=/dspace/webapps/jspui
16 matches
Mail list logo
