Re: [djatoka-devel] djatoka linux install - http 500 error
Status: Beta
Brought to you by:
rchute
Menu
▾
▴
Re: [djatoka-devel] djatoka linux install - http 500 error
|
From: Eric J. <cir...@ho...> - 2010-04-15 18:23:24
|
Thanks for the response Ryan.
I didn't start the server from usr/local/adore-djatoka-1.1/bin/tomcat.sh as there are other things running on that tomcat, but you can see the startup parameters and java opts from my last posts.
But, I changed the {catalina_home}/webapps/adore-djatoka/WEB-INF/classes/log4j.properties to:
# REPORTING LEVELS: OFF, DEBUG, INFO, WARN, ERROR and FATAL
log.dir=.
datestamp=yyyy-MM-dd/HH:mm:ss.SSS/zzz
roll.pattern.hourly=.yyyy-MM-dd.HH
roll.pattern.daily=.yyyy-MM-dd
# djatoka.log -- Default catch-all.
log4j.rootLogger=DEBUG, defaultLog
log4j.appender.defaultLog=org.apache.log4j.DailyRollingFileAppender
log4j.appender.defaultLog.DatePattern=${roll.pattern.daily}
#log4j.appender.defaultLog.File=${log.dir}/djatoka.log
log4j.appender.defaultLog.File=/data/app/fedora-tomcat-5.5.26/logs/djatoka.log
log4j.appender.defaultLog.layout=org.apache.log4j.PatternLayout
log4j.appender.defaultLog.layout.ConversionPattern=%d{${datestamp}} [%t] %-5p %m%n
So that the rootlogger=DEBUG instead of INFO, and the defaultLog.File=/data/app/fedora-tomcat-5.5.26/logs/djatoka.log, just so I can be sure exactly he path where the djatoka log is being written to.
I then, go to the tomcat/manager and reload adore-djatoka, and try accessing the resolver in the browser, getting that broken image using the default parameters. But still no sign of a djatoka.log being written to /data/app/fedora-tomcat-5.5.26/logs/djatoka.log.
Thanks again,
Eric
From: rc...@gm...
To: cir...@ho...
Subject: Re: [djatoka-devel] djatoka linux install - http 500 error
Date: Thu, 15 Apr 2010 06:53:08 -1000
CC: dja...@li...
Hi Eric,
We'll need to figure out the location of and the contents of the djatoka.log file file for more info. Provided the server is started from /usr/local/adore-djatoka-1.1/bin using ./tomcat.sh start the djatoka.log should appear in the same directory. If not present, I'd verify that no messages are going to catalina.out. If you are able to find a stack trace go ahead and post it, otherwise I'll be back in the office on Monday and will better be able to assist.
Cheers,
Ryan
Sent from my iPhone
On Apr 14, 2010, at 11:34 AM, Eric James <cir...@ho...> wrote:
Hi,
I've followed the install instructions and can get to a page:
http://<server>:8080/adore-djatoka/
Which has a form where you can enter parameters, I keep the default, and then click on the "Update Image". The result is a broken image link, and the display of the generated url at the bottom of the screen:
http://localhost:8080/adore-djatoka/resolver?url_ver=Z39.88-2004
&rft_id=http://memory.loc.gov/gmd/gmd433/g4330/g4330/np000066.jp2
&svc_id=info:lanl-repo/svc/getRegion
&svc_val_fmt=info:ofi/fmt:kev:mtx:jpeg2000
&svc.format=image/jpeg
&svc.level=3
&svc.rotate=0
&svc.region=0,0,500,500
If I try the above url directly, replacing the "localhost" with the actual server, the result is a 500 error.
I checked the log4j properties, they are set, but it doesn't seem like the djatoka.log is being generated:
log.dir=.
datestamp=yyyy-MM-dd/HH:mm:ss.SSS/zzz
roll.pattern.hourly=.yyyy-MM-dd.HH
roll.pattern.daily=.yyyy-MM-dd
# djatoka.log -- Default catch-all.
log4j.rootLogger=DEBUG, defaultLog
log4j.appender.defaultLog=org.apache.log4j.DailyRollingFileAppender
log4j.appender.defaultLog.DatePattern=${roll.pattern.daily}
log4j.appender.defaultLog.File=${log.dir}/djatoka.log
log4j.appender.defaultLog.layout=org.apache.log4j.PatternLayout
log4j.appender.defaultLog.layout.ConversionPattern=%d{${datestamp}} [%t] %-5p %m%n
I looked at the tomcat startup parameters and they are as follows:
/data/app/java/jdk1.5.0_05/bin/java
-Xms128m
-Xmx512m
-Djava.awt.headless=true
-Dkakadu.home=/usr/local/adore-djatoka-1.1/bin/Linux-x86-32
-Djava.library.path=/usr/local/adore-djatoka-1.1/lib/Linux-x86-32
-Djavax.net.ssl.trustStore=/data/app/fedora-2.2.4/server/truststore
-Djavax.net.ssl.trustStorePassword=<pw>
-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
-Djava.util.logging.config.file=/data/app/fedora-tomcat-5.5.26/conf/logging.properties
-Djava.endorsed.dirs=/data/app/fedora-tomcat-5.5.26/common/endorsed
-classpath :/data/app/fedora-tomcat-5.5.26/bin/bootstrap.jar:/data/app/fedora-tomcat-5.5.26/bin/commons-logging-api.jar
-Dcatalina.base=/data/app/fedora-tomcat-5.5.26
-Dcatalina.home=/data/app/fedora-tomcat-5.5.26
-Djava.io.tmpdir=/data/app/fedora-tomcat-5.5.26/temp
org.apache.catalina.startup.Bootstrap start
I looked at the JAVA_OPTS
JAVA_OPTS=
-Xms128m
-Xmx512m
-Djava.awt.headless=true
-Dkakadu.home=/usr/local/adore-djatoka-1.1/bin/Linux-x86-32
-Djava.library.path=/usr/local/adore-djatoka-1.1/lib/Linux-x86-32
-Djavax.net.ssl.trustStore=/data/app/fedora-2.2.4/server/truststore
-Djavax.net.ssl.trustStorePassword=tomcat
If I click on the "Open Image in new window" button, nothing happens, but there is a "invalid argument" javascript error on the following line in djatoka.js:
jp2k = window.open(openUrl, 'djatoka OpenURL', 'left=20,top=20,width=500,height=500,toolbar=1,resizable=1,location=1,scrollbars=1');
I'm running out of diagnostic options here, any help would be appreciated.
Thanks,
Eric
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
djatoka-devel mailing list
dja...@li...
https://lists.sourceforge.net/lists/listinfo/djatoka-devel
|