The only error message I see is in domainlist.log. INFO 21:16:25,225 | james.domainlist | Set autodetect to: true INFO 21:16:25,226 | james.domainlist | Set autodetectIP to: true INFO 21:16:25,232 | james.domainlist | Bean org.apache.james.domainlist.xml.XMLDomainList started. INFO 21:16:25,389 | james.domainlist | Local host is: 192.168.1.3 ERROR 21:16:25,515 | james.domainlist | Cannot get IP address(es) for localhost INFO 21:20:13,701 | james.domainlist | Set autodetect to: true INFO 21:20:13,702 | james.domainlist | Set autodetectIP to: true INFO 21:20:13,709 | james.domainlist | Bean org.apache.james.domainlist.xml.XMLDomainList started. INFO 21:20:13,788 | james.domainlist | Local host is: 192.168.1.3 ERROR 21:20:13,809 | james.domainlist | Cannot get IP address(es) for localhost
Could this be the problem? On Tue, Mar 15, 2011 at 9:17 AM, Something Something < [email protected]> wrote: > Getting message... "The connection to 6243 did not succeed". > > After I start James I see this when I run jps > > 6304 WrapperSimpleApp > > Within less than 30 seconds this process dies! Hmm... I will look at > logs.. but any ideas? Thanks again for your help. > > > > On Tue, Mar 15, 2011 at 7:14 AM, Eric Charles <[email protected]> wrote: > >> Hi, >> No telnet in 3.0-2 if I remember well. >> james-cli is still a work in-progress and is not operational in 3.0-M2. >> >> To manage via JMX, launch jconsole command is your shell box, connect to >> the james process, and go to the MBeans tab. >> You should have methods available to create domains, users,... >> >> Tks, >> - Eric >> >> >> On 15/03/2011 14:50, Something Something wrote: >> >> No stacktrace in james-server.log. Where else should I look? >> >> I am using james-server-container-spring-3.0-M2. No, telnet for this, >> right? >> >> I read in one of the previous emails from Norman... " All the management >> stuff need to get done via JMX or james-cli" >> >> What's james-cli? I promise I will research, but any notes/tips about >> starting JMX or james-cli quickly? Thanks for help. >> >> >> On Tue, Mar 15, 2011 at 12:51 AM, Eric Charles <[email protected]> wrote: >> >>> Hi, >>> Which version are you using? >>> If you use the snapshot, telnet is no more available and you can manage >>> james via JMX. >>> Eric >>> >>> >>> On 15/03/2011 07:19, Norman Maurer wrote: >>> >>>> When you say James dies what does this mean ? Any stacktrace ? >>>> >>>> I use osx as development platform without a problem... >>>> >>>> Bye, >>>> Norman >>>> >>>> >>>> 2011/3/15 Something Something<[email protected]> >>>> >>>> Has anyone tried starting James on Mac for development purposes? Is >>>>> Mac a >>>>> supported platform? >>>>> >>>>> It's not working for me. I am using James 3.0.M2 >>>>> >>>>> When I do: >>>>> >>>>> ./james start >>>>> >>>>> It seems to start. I see no errors in the log. But when I do: >>>>> >>>>> telnet localhost 4555 >>>>> >>>>> I get this: >>>>> >>>>> Trying ::1... >>>>> telnet: connect to address ::1: Connection refused >>>>> Trying fe80::1... >>>>> telnet: connect to address fe80::1: Connection refused >>>>> Trying 127.0.0.1... >>>>> telnet: connect to address 127.0.0.1: Connection refused >>>>> telnet: Unable to connect to remote host >>>>> >>>>> & James dies. >>>>> >>>>> Any ideas? >>>>> >>>>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >>> >> >> >
