From: Dannes W. <da...@ex...> - 2011-09-07 07:15:08
|
Hi, I found out that when existdb runs isolated, behind a corporate firewall, one or two threads keep hanging on an HTTP connection; when try to shut down the db I see the following trace (exist.log): 2011-09-07 09:06:16,244 [jetty shutdown schedule] INFO (JettyStart.java [lifeCycleStopped]:406) - Jetty server stopped 2011-09-07 09:06:28,613 [eXistThread-994] WARN (URLSource.java [getInputStream]:140) - Unable to connect to URL: Connection timed out 2011-09-07 09:06:28,614 [eXistThread-994] ERROR (FunDoc.java [eval]:122) - Connection timed out ( http://atomic.exist-db.org/atom/summary/wiki/blogs/eXist/) 2011-09-07 09:06:28,615 [eXistThread-994] ERROR (XQueryServlet.java [process]:573) - java.lang.NullPointerException at org.exist.http.servlets.XQueryServlet.process(XQueryServlet.java:515) at org.exist.http.servlets.XQueryServlet.doGet(XQueryServlet.java:217) .... in std out: 07 Sep 2011 09:06:16,244 [jetty shutdown schedule] INFO (JettyStart.java [lifeCycleStopped]:406) - Jetty server stopped 07 Sep 2011 09:06:28,619 [eXistThread-994] WARN (Slf4jLog.java [warn]:50) - /exist/feed.xql java.lang.NullPointerException at org.exist.storage.BrokerPool.release(BrokerPool.java:1477) at org.exist.http.servlets.XQueryServlet.process(XQueryServlet.java:582) ... while in the html admin interface I see IDTypeSourceStartedStatus 2340291File /usr/local/asm/opt/eXist-1.5/webapp/feed.xql2011-09-07T09:02:43.987+02:00 terminating Probably we need to set an HTTP timeout or so....? any idea? cheers Dannes -- eXist-db Native XML Database - http://exist-db.org Join us on linked-in: http://www.linkedin.com/groups?gid=35624 |