Hello,
Am 29.10.2007 um 17:49 schrieb [EMAIL PROTECTED]:
> The product installed fine. Got the Oracle schema built. When I
> perform the documented test (telnet localhost 8080) or attempt to
> access the application otherwise it fails. I am attaching the
> relavent content from various conf files and scripts at the very
> bottom.
Ok, thats a lot of stuff, great - hopefully it is also
the *right* stuff ...
> When I perform the action below I get no response from the server
> or logging at all.
> dspacedev1 Z telnet localhost 8080
> Trying 127.0.0.1...
> Connected to localhost.
> Escape character is '^]'.
> GET /dspace HTTP/1.1
I usually go the simple way and use a browser but here
we go: If I try to connect to my webserver on the cmd line,
I have to enter three lines, the GET request, a host: line
and an empty line. But, your second example looks as if it
works for you with only the GET request and an empty line.
I suggest, you try to reach the tomcat homepage first before
you try your app: GET / HTTP/1.1 Enter, Enter. Does it run?
Second, what does your webapps dir look like? Do the wars
get unpacked? If not, check your server.xml and show us a
bit more of this. Hint: Autodeployment. I would not be sur-
prised if the usual defaults were tweaked under Solaris.
Maybe you dont want to autodeploy in production but you
can change this later.
> Begin server.xml
> <snip>
> <!-- Define a non-SSL HTTP/1.1 Connector on port 8080 -->
> <Connector port="8080" maxHttpHeaderSize="8192"
> maxThreads="150" minSpareThreads="25"
> maxSpareThreads="75"
> enableLookups="false" redirectPort="8443"
> acceptCount="100"
> connectionTimeout="20000" disableUploadTimeout="true"
> URIEncoding="UTF-8"/>
> <snip>
If you get to the dspace homepage but see a system error, then
you are at the point where you have to decide whether to deal
with your database connection first or to go and check the in-
tegration with apache:
> Start http.conf
> <snip>
> LoadModule jk_module modules/mod_jk.so
> JkWorkersFile "/etc/NLM/apache2/workers.properties"
> JkShmFile "/var/tmp/jk-runtime-status
> <snip>
> #
> RewriteEngine On
> RewriteCond %{REQUEST_METHOD} ^(TRACE|TRACK) RewriteRule .* - [F]
> JkLogFile "/www/logs/raw/mod_jk.log"
> JkLogLevel debug
> JkMount /dspace ajp13_dspace
> JkMount /dspace/ ajp13_dspace
I did not use mod_jk yet, but I wonder why you have to have both,
/dspace and /dspace/. Anyway, I would start with just a single /
to be able to reach the tomcat homepage and the tomcat manager,
then changing this in a second step.
In all, my setup is fairly different with Mac OS X, Java 1.5,
ant 1.6.5, tomcat standalone and so on. All my ideas are based
on reading your information thoroughly and thinking about the
point where I would loose oversight if I were working on this
for hours. So, if it all sounds stupid, it is just meant like
this, because most blocking errors are really stupid - but they
happen to everybody from time to time. Let us know how it went
on.
Bye, Christian
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
