It uses the same method as described here for "Single-process deployable war² but configured within the product: https://manifoldcf.apache.org/release/release-1.10/en_US/how-to-build-and-de ploy.html#Single-process+deployable+war
However, I think I¹m going to pursue using the standalone version for now and see if experience the same issues or not. Thanks for your help. Regards, Phil Riethmuller Technical Consultant Funnelback | 437 Kent Street, Sydney, NSW 2000 T +61 2 9045 2882 | funnelback.com <http://www.funnelback.com/> AUSTRALIA | UNITED KINGDOM | NEW ZEALAND | POLAND | UNITED STATES Connect with us: LinkedIn <http://www.linkedin.com/company/funnelback> - Twitter From: Karl Wright <[email protected]> Reply-To: <[email protected]> Date: Wednesday, 20 January 2016 10:43 am To: "[email protected]" <[email protected]> Subject: Re: How to resolve a 503 error in the manifoldCF admin UI So, how did you deploy an additional webapp under the single-process example? This is not something I would imagine it would be straightforward to do. If you need to run more than one webapp under your web server, you would need to deploy the combined war under a standalone instance of jetty or tomcat. Karl On Tue, Jan 19, 2016 at 6:35 PM, Phil Riethmuller <[email protected]> wrote: > Hi Karl - > > It¹s currently a single-process setup, running under Jetty. Currently, it > also has Funnelback (search) running under the same Jetty instance but > ultimately they will be running under their own jetty instances. > > The Funnelback admin and search page both show OK. > > It was running using the default HSQLDB database, but I¹ve tried to switch > over to postgres. > > Thanks > Phil > > > > From: Karl Wright <[email protected]> > Reply-To: <[email protected]> > Date: Wednesday, 20 January 2016 10:20 am > To: "[email protected]" <[email protected]> > Subject: Re: How to resolve a 503 error in the manifoldCF admin UI > > Hi Phil, > > A 503 error is not returned by the MCF web application; it comes from the web > server that the application runs in. > > Can you describe your setup? Is this the single-process example running under > Jetty? or is this a Tomcat or Resin deployment? > > Karl > > > On Tue, Jan 19, 2016 at 4:59 PM, Phil Riethmuller > <[email protected]> wrote: >> Hi All - >> >> Does anyone know how to go about resolving a 503 error in the manifoldCF >> admin ui? >> >> I¹ve tried to configure it with Postgres, but get a 503 service unavailable >> when I try to access the admin interface. >> >> The log file specified in the logging.ini file does not have any errors in >> it, and I¹ve set the following to debug mode in the properties.xml file: >> >> <property name="org.apache.manifoldcf.db" value="DEBUG"/> >> >> <property name="org.apache.manifoldcf.root" value="DEBUG"/> >> >> <property name="org.apache.manifoldcf.misc" value="DEBUG"/> >> >> <property name="org.apache.manifoldcf.lock" value="DEBUG"/> >> >> <property name="org.apache.manifoldcf.cache" value="DEBUG"/> >> >> <property name="org.apache.manifoldcf.keystore" value="DEBUG"/> >> >> <property name="org.apache.manifoldcf.perf" value="DEBUG"/> >> >> <property name="org.apache.manifoldcf.injest" value="DEBUG"/> >> >> <property name="org.apache.manifoldcf.api" value="DEBUG"/> >> >> <property name="org.apache.manifoldcf.threads" value="DEBUG"/> >> >> <property name="org.apache.manifoldcf.hopcount" value="DEBUG"/> >> >> <property name="org.apache.manifoldcf.scheduling" value="DEBUG"/> >> >> <property name="org.apache.manifoldcf.authorityconnectors" value="DEBUG"/> >> >> <property name="org.apache.manifoldcf.agents" value="DEBUG"/> >> >> >> Thanks >> Phil >> >
