Hey Jeffrey, hey Garry,
as I look through the source from 3.4 it seems this is already fixed, at
least it was in master-branch as of Feb 28th 08:05 UTC (a quick check:
3.2.x doesn't contain the fix, but the 3.3.x does).
Once I encountered a similar issue as I once didn't set database type
Thanks guys.
You're right, 3.3 does have the fix, and it creates the tables, but throws this
exception:
WrapperSimpleApp: Encountered an error running main:
org.springframework.beans.factory.BeanCreationException: Error creating bean
with name 'pop3server': Invocation of init method failed;
Could james be trying to start the pop server more than once?
INFO | jvm 1| 2019/03/26 08:51:03 | INFO 08:51:03,433 |
org.apache.james.protocols.lib.netty.AbstractConfigurableAsyncServer | LMTP
Service disabled by configuration
INFO | jvm 1| 2019/03/26 08:51:03 | INFO
Well, first: the stack is incomplete - there should be an IOException as
lowest exception.
second: this stack doesn't fit to the config you send earlier.
So somethings blocking TCP/110.
Just do a complete system reboot (if possible) cause it seems somethings
"hung up".
Matt
Am 26.03.2019 um
Thanks, I'll try the reboot.
-Original Message-
From: cryptearth [mailto:cryptea...@cryptearth.de]
Sent: Tuesday, March 26, 2019 9:03 AM
To: server-user@james.apache.org
Subject: Re: sqlResources.xml
Well, first: the stack is incomplete - there should be an IOException as lowest
The error is
WrapperSimpleApp: Encountered an error running main:
org.springframework.beans.factory.BeanCreationException: Error creating bean
with name 'pop3server': Invocation of init method failed; nested exception is
org.jboss.netty.channel.ChannelException: Failed to bind to: /0.0.0.0:110
Well, I don't use pop3 - but looks like an config issue. Please post
your conf/pop3server.xml
Matt
Am 26.03.2019 um 11:57 schrieb Marans.Jeffrey:
Thanks guys.
You're right, 3.3 does have the fix, and it creates the tables, but throws this
exception:
WrapperSimpleApp: Encountered an error
Well, the issue is, that you have anything else already running on
TCP/110 - like another POP3 server. Check your system what other POP3
server is running ...
Matt
Am 26.03.2019 um 13:38 schrieb Marans.Jeffrey:
The error is
WrapperSimpleApp: Encountered an error running main:
Thanks, I check port 110 and found nothing there.
I also telneted to localhost 110 and got a connection refused, which means
nothing's listening.
-Original Message-
From: cryptearth [mailto:cryptea...@cryptearth.de]
Sent: Tuesday, March 26, 2019 8:53 AM
To: server-user@james.apache.org
The system on which I'm developing was running dovecot. Even though I turned
off and chkconfig'd off dovecot, the portreserve file contained the entries
imap, imaps, pop3, pop3s.
Those entries didn't specify TCP or UDP, so the portreserve program read
/etc/services which contains
pop3
The reason james would not run on port 110 is that the portreserve program is
on UDP 110.
I don't know why I didn't see that earlier, but Matt and Gary, thanks for your
time, patience, and in-depth knowledge.
Regards,
Jeffrey Marans
-Original Message-
From: cryptearth
Well, if something runs on UDP/110 - you should still be able to bind to
TCP/110 - as TCP and UDP are independent, unless the "portreserve" you
speak about also binds/blocks TCP/110.
Unless you have a multi-homed system or any other specific reason,
0.0.0.0:110 should be used (maybe also
Well, wikipedia lists the UDP ports as "protocol assigned, but not
used". Maybe you would had found it when you just had used "lsof -i" -
without grep. I guess this "port reserve stuff" is something starting
way early in the system startup to block other programms to use needed
ports - and
Well,
the "error" you got is "cannot bind - address already in use" - this
usually means, that there is already something bound to the port you try
to use. Altough the config somehow doesn't match to the latest log
(config says 0.0.0.0:110 but log shows hostname), the one you shown only
I've rebooted the system twice and am still getting the same exception.
Nothing's listening on 110 as evidenced by
"telnet nsep1u9254 110
Trying 10.33.117.54...
telnet: connect to address 10.33.117.54: Connection refused"
This also returns nothing: lsof -i -P -n | grep LISTEN
Is the popserver
I am starting james as root, and I've tried using 0.0.0.0:110, the
IPaddress:110, the servername:110, and the fqdn:110.
All 3 give essentially the same "cannot bind" result.
The only file in conf that refers to port 110 is pop3server.xml and it only has
one uncommented bind line.
Out of
16 matches
Mail list logo
