That makes sense. We have restrictions on our server forbidding it to
access arbitrary remote URLs. When I substituted the external dtd
reference with your internal version, the WMS link worked fine.
Thanks a lot!
Egil
On 04/17/2013 04:40 PM, Marcos Hermida wrote:
Ok Egil,
It looks like it has problems to validate the wmsConfig.xml, that uses
an external dtd (
http://www.unidata.ucar.edu/schemas/thredds/dtd/ncwms/wmsConfig.dtd)
I'm attaching a wmsConfig.xml that has an internal dtd. Could you try to
use this one? (By default wmsConfig.xml lives in the
$TOMCAT_HOME/content/thredds directory)
Cheers!
On 04/17/2013 07:44 AM, Egil Støren wrote:
Hi Marcos,
I get the following error in the serverStartup.log:
2013-04-17T13:15:18.894+0000 [ 5548522][ ] ERROR
org.springframework.web.servlet.DispatcherServlet: Context
initialization failed
org.springframework.beans.factory.BeanCreationException: Error
creating bean with name 'wmsController' defined in ServletContext
resource [/WEB-INF/wms-servlet.xml]: Invocation of init method failed;
nested exception is java.net.ConnectException: Connection timed out
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1455)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:519)
A long list of similar lines follow.
I also find similar "Connection timed out" errors in the tomcat7 logs,
and it takes a very long time before the error shows up in the browser
after clicking on the WMS link.
I think maybe this error is caused by the cleaning actions I did
(removing the work/Catalina/localhost/thredds directory) in order to
get rid of the problem.
Previously I also got an 500 error, but without finding any unusual
log messages, and the time it took to receive the response was very
short.
Hope this gives some clues.
Egil
On 04/17/2013 02:58 PM, Marcos Hermida wrote:
Hi Egil,
I think we need some more information to figure out what's going on.
Could you check if something shows up in the thredds or tomcat logs?
Cheers!
On 04/17/2013 06:14 AM, Egil Støren wrote:
Hi all,
I have recently upgraded to TDS version 4.3.16, and everything seem to
work as expected, except when I click on a WMS getCapabilities link,
which gives me an 500 Internal server error.
I have searched for postings describing similar errors, and I found
this:
https://www.unidata.ucar.edu/mailing_lists/archives/thredds/2013/msg00037.html
advising to update the wmsConfig.xml document according to the
description in
http://www.unidata.ucar.edu/projects/THREDDS/tech/tds4.3/UpgradingTo4.3.html.
This I did, but the error still persists.
I also removed the CATALINA_BASE/work/Catalina/localhost/thredds
directory and the webapps/thredds directory before I restarted tomcat
(according to advise in another posting), but to no avail.
I am using tomcat7, java7 and are running tomcat behind an apache
proxy.
Any help appreciated.
Best regards,
Egil Støren
met.no
_______________________________________________
thredds mailing list
thredds@xxxxxxxxxxxxxxxx
For list information or to unsubscribe, visit:
http://www.unidata.ucar.edu/mailing_lists/
