Thanks Alon, turns out the file I needed was the wrapper.log file, which had ended up in ./bin/wrapper.log instead of ./log/wrapper.log. This file contained the exception I was looking for.
Martin On Tuesday, 4 September 2012 at 17:34, Alon Gamliel wrote: > Use bin/run.bat, it should give you more information and hopefully the > exception trace > > > Date: Tue, 4 Sep 2012 17:03:50 +0100 > > Subject: Diagnosing startup rollback problems > > From: [email protected] (mailto:[email protected]) > > To: [email protected] (mailto:[email protected]) > > > > Hi all, > > > > I've developed my (two, small) custom elements for James, and have > > tested them thoroughly locally, and am going about deploying James on > > a server so we can test it remotely. > > > > However, when I do ./bin/james start, the process begins, runs for a > > bit, and then exits. Dialling up the log level and examining the > > output, I can see that the startup process is reaching a certain point > > and then rolling back, destroying everything and quitting. > > > > What I can't tell is what point in the startup stage it's at, or why > > it starts rolling back. > > > > The only "decision point" I can see is: > > > > DEBUG 15:58:35,268 | > > org.springframework.beans.factory.support.DefaultListableBeanFactory | > > Finished creating instance of bean > > 'org.apache.james.smtpserver.jmx.HookResultJMXMonitor' > > INFO 15:58:35,420 | > > org.springframework.beans.factory.support.DefaultListableBeanFactory | > > Destroying singletons in > > org.springframework.beans.factory.support.DefaultListableBeanFactory@2c1533c8: > > defining beans [org.sprin.... > > > > Which doesn't give me much to go on. > > > > Any help as to where I can look to work out what's causing the > > rollback would be very welcome. > > > > Many thanks, > > > > Martin > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > (mailto:[email protected]) > > For additional commands, e-mail: [email protected] > > (mailto:[email protected]) > > > > > >
