Re: sqlResources.xml

2019-03-26 Thread cryptearth
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 when dovecot starts its "transfered" or "redirected" to it 
(however this might work in linux).


Nice to hear you got that fixed. And also for me a good info to look out 
for when upgrading to current version after system update.


Matt

Am 26.03.2019 um 20:06 schrieb Marans.Jeffrey:

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
pop3110/tcp pop-3   # POP version 3
pop3110/udp pop-3
pop3s   995/tcp # POP-3 over SSL
pop3s   995/udp # POP-3 over SSL

I believe that's why both udp and tcp were occupied, but I didn't see that 
until I used the command   lsof -i -P -n | grep ':110'
Turning off portreserver, a program I've never seen before, fixed the issue.

Hope that's a reasonable explanation.
Again, thanks for help, it's much appreciated.

Jeffrey Marans.

-Original Message-
From: cryptearth [mailto:cryptea...@cryptearth.de]
Sent: Tuesday, March 26, 2019 2:31 PM
To: server-user@james.apache.org
Subject: Re: sqlResources.xml

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 *:110 - but I don't know if this works).

Matt

Am 26.03.2019 um 19:13 schrieb Marans.Jeffrey:

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 [mailto:cryptea...@cryptearth.de]
Sent: Tuesday, March 26, 2019 1:16 PM
To: server-user@james.apache.org
Subject: Re: sqlResources.xml

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 contains one pop3 server entry and should only try to start pop3 once on tcp/110. If nothing 
else runs on TCP/110 the next issue I could come up with is that some other config contains a 
server part wich is started before pop3 and already uses 110. Check your other configs wich other 
service mind bind to TCP/110.

One more "stupid" question: You do start james as root?

Matt

Am 26.03.2019 um 15:59 schrieb Marans.Jeffrey:

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 bind code the same in 3.2 and 3.3?

I've attached the wrapper log.

-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 
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 13:59 schrieb Marans.Jeffrey:

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  08:51:03,450 | 
org.apache.james.protocols.lib.netty.AbstractConfigurableAsyncServer | POP3 
Service bound to: nsep1u9254:110
INFO   | jvm 1| 2019/03/26 08:51:03 | INFO  08:51:03,450 | 
org.apache.james.protocols.lib.netty.AbstractConfigurableAsyncServer | POP3 
Service is running on: nsep1u9254
INFO   | jvm 1| 2019/03/26 08:51:03 | INFO  08:51:03,450 | 
org.apache.james.protocols.lib.netty.AbstractConfigurableAsyncServer | POP3 
Service handler hello name is: nsep1u9254
INFO   | jvm 1| 2019/03/26 08:51:03 | INFO  08:51:03,451 | 
org.apache.james.protocols.lib.netty.AbstractConfigurableAsyn

RE: sqlResources.xml

2019-03-26 Thread Marans . Jeffrey
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 
pop3110/tcp pop-3   # POP version 3
pop3110/udp pop-3
pop3s   995/tcp # POP-3 over SSL
pop3s   995/udp # POP-3 over SSL

I believe that's why both udp and tcp were occupied, but I didn't see that 
until I used the command   lsof -i -P -n | grep ':110'
Turning off portreserver, a program I've never seen before, fixed the issue.

Hope that's a reasonable explanation.
Again, thanks for help, it's much appreciated.

Jeffrey Marans.

-Original Message-
From: cryptearth [mailto:cryptea...@cryptearth.de] 
Sent: Tuesday, March 26, 2019 2:31 PM
To: server-user@james.apache.org
Subject: Re: sqlResources.xml

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 *:110 - but I don't know if this works).

Matt

Am 26.03.2019 um 19:13 schrieb Marans.Jeffrey:
> 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 [mailto:cryptea...@cryptearth.de]
> Sent: Tuesday, March 26, 2019 1:16 PM
> To: server-user@james.apache.org
> Subject: Re: sqlResources.xml
>
> 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 contains one pop3 
> server entry and should only try to start pop3 once on tcp/110. If nothing 
> else runs on TCP/110 the next issue I could come up with is that some other 
> config contains a server part wich is started before pop3 and already uses 
> 110. Check your other configs wich other service mind bind to TCP/110.
>
> One more "stupid" question: You do start james as root?
>
> Matt
>
> Am 26.03.2019 um 15:59 schrieb Marans.Jeffrey:
>> 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 bind code the same in 3.2 and 3.3?
>>
>> I've attached the wrapper log.
>>
>> -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 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 13:59 schrieb Marans.Jeffrey:
>>> 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  08:51:03,450 | 
>>> org.apache.james.protocols.lib.netty.AbstractConfigurableAsyncServer | POP3 
>>> Service bound to: nsep1u9254:110
>>> INFO   | jvm 1| 2019/03/26 08:51:03 | INFO  08:51:03,450 | 
>>> org.apache.james.protocols.lib.netty.AbstractConfigurableAsyncServer | POP3 
>>> Service is running on: nsep1u9254
>>> INFO   | jvm 1| 2019/03/26 08:51:03 | INFO  08:51:03,450 | 
>>> org.apache.james.protocols.lib.netty.AbstractConfigurableAsyncServer | POP3 
>>> Service handler hello name is: nsep1u9254
>>> INFO   | jvm 1| 2019/03/26 08:51:03 | INFO  08:51:03,451 | 
>>> org.apache.james.protocols.lib.netty.AbstractConfigurableAsyncServer | POP3 
&

Re: sqlResources.xml

2019-03-26 Thread 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 *:110 - but I don't know if this 
works).


Matt

Am 26.03.2019 um 19:13 schrieb Marans.Jeffrey:

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 [mailto:cryptea...@cryptearth.de]
Sent: Tuesday, March 26, 2019 1:16 PM
To: server-user@james.apache.org
Subject: Re: sqlResources.xml

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 contains one pop3 server entry and should only try to start pop3 once on tcp/110. If nothing 
else runs on TCP/110 the next issue I could come up with is that some other config contains a 
server part wich is started before pop3 and already uses 110. Check your other configs wich other 
service mind bind to TCP/110.

One more "stupid" question: You do start james as root?

Matt

Am 26.03.2019 um 15:59 schrieb Marans.Jeffrey:

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 bind code the same in 3.2 and 3.3?

I've attached the wrapper log.

-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 
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 13:59 schrieb Marans.Jeffrey:

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  08:51:03,450 | 
org.apache.james.protocols.lib.netty.AbstractConfigurableAsyncServer | POP3 
Service bound to: nsep1u9254:110
INFO   | jvm 1| 2019/03/26 08:51:03 | INFO  08:51:03,450 | 
org.apache.james.protocols.lib.netty.AbstractConfigurableAsyncServer | POP3 
Service is running on: nsep1u9254
INFO   | jvm 1| 2019/03/26 08:51:03 | INFO  08:51:03,450 | 
org.apache.james.protocols.lib.netty.AbstractConfigurableAsyncServer | POP3 
Service handler hello name is: nsep1u9254
INFO   | jvm 1| 2019/03/26 08:51:03 | INFO  08:51:03,451 | 
org.apache.james.protocols.lib.netty.AbstractConfigurableAsyncServer | POP3 
Service handler connection timeout is: 1200
INFO   | jvm 1| 2019/03/26 08:51:03 | INFO  08:51:03,451 | 
org.apache.james.protocols.lib.netty.AbstractConfigurableAsyncServer | POP3 
Service connection backlog is: 200
INFO   | jvm 1| 2019/03/26 08:51:03 | WARN  08:51:03,548 | 
org.apache.james.container.spring.context.JamesServerApplicationContext | 
Exception encountered during context initialization - cancelling refresh 
attempt: 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: 
nsep1u9254/10.33.117.54:110

-Original Message-
From: cryptearth [mailto:cryptea...@cryptearth.de]
Sent: Tuesday, March 26, 2019 8:24 AM
To: server-user@james.apache.org
Subject: Re: sqlResources.xml

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 running main: 
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'pop3server': Invocation of init method failed; nested exception is 
java.lang.ArrayIndexOutOfBoundsException: 1
INFO   | jvm 1| 2019/03/25 15:01:27 | 
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'pop3server': Invocation of init method failed; nested exception is 
java.lang.ArrayIndexOutOfBoundsExce

RE: sqlResources.xml

2019-03-26 Thread Marans . Jeffrey
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 [mailto:cryptea...@cryptearth.de] 
Sent: Tuesday, March 26, 2019 1:16 PM
To: server-user@james.apache.org
Subject: Re: sqlResources.xml

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 contains one pop3 
server entry and should only try to start pop3 once on tcp/110. If nothing else 
runs on TCP/110 the next issue I could come up with is that some other config 
contains a server part wich is started before pop3 and already uses 110. Check 
your other configs wich other service mind bind to TCP/110.

One more "stupid" question: You do start james as root?

Matt

Am 26.03.2019 um 15:59 schrieb Marans.Jeffrey:
> 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 bind code the same in 3.2 and 3.3?
>
> I've attached the wrapper log.
>
> -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 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 13:59 schrieb Marans.Jeffrey:
>> 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  08:51:03,450 | 
>> org.apache.james.protocols.lib.netty.AbstractConfigurableAsyncServer | POP3 
>> Service bound to: nsep1u9254:110
>> INFO   | jvm 1| 2019/03/26 08:51:03 | INFO  08:51:03,450 | 
>> org.apache.james.protocols.lib.netty.AbstractConfigurableAsyncServer | POP3 
>> Service is running on: nsep1u9254
>> INFO   | jvm 1| 2019/03/26 08:51:03 | INFO  08:51:03,450 | 
>> org.apache.james.protocols.lib.netty.AbstractConfigurableAsyncServer | POP3 
>> Service handler hello name is: nsep1u9254
>> INFO   | jvm 1| 2019/03/26 08:51:03 | INFO  08:51:03,451 | 
>> org.apache.james.protocols.lib.netty.AbstractConfigurableAsyncServer | POP3 
>> Service handler connection timeout is: 1200
>> INFO   | jvm 1| 2019/03/26 08:51:03 | INFO  08:51:03,451 | 
>> org.apache.james.protocols.lib.netty.AbstractConfigurableAsyncServer | POP3 
>> Service connection backlog is: 200
>> INFO   | jvm 1| 2019/03/26 08:51:03 | WARN  08:51:03,548 | 
>> org.apache.james.container.spring.context.JamesServerApplicationContext | 
>> Exception encountered during context initialization - cancelling refresh 
>> attempt: 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: nsep1u9254/10.33.117.54:110
>>
>> -Original Message-
>> From: cryptearth [mailto:cryptea...@cryptearth.de]
>> Sent: Tuesday, March 26, 2019 8:24 AM
>> To: server-user@james.apache.org
>> Subject: Re: sqlResources.xml
>>
>> 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 running main: 
>>> org.springframework.beans.factory.BeanCreationException: Error creating 
>>> bean with name 'pop3server': Invocation of init method failed; nested 
>>> exception is java.lang.ArrayIndexOutOfBoundsException: 1
>>> INFO   | jvm 1| 2019/03/25 15:01:27 | 
&g

RE: sqlResources.xml

2019-03-26 Thread Marans . Jeffrey
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 curiosity I tried bringing up james using port 222 and it seemed to run 
ok.
But I need it to use 110.


Jeff.

-Original Message-
From: cryptearth [mailto:cryptea...@cryptearth.de] 
Sent: Tuesday, March 26, 2019 1:16 PM
To: server-user@james.apache.org
Subject: Re: sqlResources.xml

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 contains one pop3 
server entry and should only try to start pop3 once on tcp/110. If nothing else 
runs on TCP/110 the next issue I could come up with is that some other config 
contains a server part wich is started before pop3 and already uses 110. Check 
your other configs wich other service mind bind to TCP/110.

One more "stupid" question: You do start james as root?

Matt

Am 26.03.2019 um 15:59 schrieb Marans.Jeffrey:
> 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 bind code the same in 3.2 and 3.3?
>
> I've attached the wrapper log.
>
> -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 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 13:59 schrieb Marans.Jeffrey:
>> 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  08:51:03,450 | 
>> org.apache.james.protocols.lib.netty.AbstractConfigurableAsyncServer | POP3 
>> Service bound to: nsep1u9254:110
>> INFO   | jvm 1| 2019/03/26 08:51:03 | INFO  08:51:03,450 | 
>> org.apache.james.protocols.lib.netty.AbstractConfigurableAsyncServer | POP3 
>> Service is running on: nsep1u9254
>> INFO   | jvm 1| 2019/03/26 08:51:03 | INFO  08:51:03,450 | 
>> org.apache.james.protocols.lib.netty.AbstractConfigurableAsyncServer | POP3 
>> Service handler hello name is: nsep1u9254
>> INFO   | jvm 1| 2019/03/26 08:51:03 | INFO  08:51:03,451 | 
>> org.apache.james.protocols.lib.netty.AbstractConfigurableAsyncServer | POP3 
>> Service handler connection timeout is: 1200
>> INFO   | jvm 1| 2019/03/26 08:51:03 | INFO  08:51:03,451 | 
>> org.apache.james.protocols.lib.netty.AbstractConfigurableAsyncServer | POP3 
>> Service connection backlog is: 200
>> INFO   | jvm 1| 2019/03/26 08:51:03 | WARN  08:51:03,548 | 
>> org.apache.james.container.spring.context.JamesServerApplicationContext | 
>> Exception encountered during context initialization - cancelling refresh 
>> attempt: 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: nsep1u9254/10.33.117.54:110
>>
>> -Original Message-
>> From: cryptearth [mailto:cryptea...@cryptearth.de]
>> Sent: Tuesday, March 26, 2019 8:24 AM
>> To: server-user@james.apache.org
>> Subject: Re: sqlResources.xml
>>
>> 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 running main: 
>>> org.springframework.beans.factory.BeanCreationException: Error creating 
>>> bean with name 'p

Re: sqlResources.xml

2019-03-26 Thread cryptearth

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 
contains one pop3 server entry and should only try to start pop3 once on 
tcp/110. If nothing else runs on TCP/110 the next issue I could come up 
with is that some other config contains a server part wich is started 
before pop3 and already uses 110. Check your other configs wich other 
service mind bind to TCP/110.


One more "stupid" question: You do start james as root?

Matt

Am 26.03.2019 um 15:59 schrieb Marans.Jeffrey:

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 bind code the same in 3.2 and 3.3?

I've attached the wrapper log.

-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 
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 13:59 schrieb Marans.Jeffrey:

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  08:51:03,450 | 
org.apache.james.protocols.lib.netty.AbstractConfigurableAsyncServer | POP3 
Service bound to: nsep1u9254:110
INFO   | jvm 1| 2019/03/26 08:51:03 | INFO  08:51:03,450 | 
org.apache.james.protocols.lib.netty.AbstractConfigurableAsyncServer | POP3 
Service is running on: nsep1u9254
INFO   | jvm 1| 2019/03/26 08:51:03 | INFO  08:51:03,450 | 
org.apache.james.protocols.lib.netty.AbstractConfigurableAsyncServer | POP3 
Service handler hello name is: nsep1u9254
INFO   | jvm 1| 2019/03/26 08:51:03 | INFO  08:51:03,451 | 
org.apache.james.protocols.lib.netty.AbstractConfigurableAsyncServer | POP3 
Service handler connection timeout is: 1200
INFO   | jvm 1| 2019/03/26 08:51:03 | INFO  08:51:03,451 | 
org.apache.james.protocols.lib.netty.AbstractConfigurableAsyncServer | POP3 
Service connection backlog is: 200
INFO   | jvm 1| 2019/03/26 08:51:03 | WARN  08:51:03,548 | 
org.apache.james.container.spring.context.JamesServerApplicationContext | 
Exception encountered during context initialization - cancelling refresh 
attempt: 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: 
nsep1u9254/10.33.117.54:110

-Original Message-
From: cryptearth [mailto:cryptea...@cryptearth.de]
Sent: Tuesday, March 26, 2019 8:24 AM
To: server-user@james.apache.org
Subject: Re: sqlResources.xml

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 running main: 
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'pop3server': Invocation of init method failed; nested exception is 
java.lang.ArrayIndexOutOfBoundsException: 1
INFO   | jvm 1| 2019/03/25 15:01:27 | 
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'pop3server': Invocation of init method failed; nested exception is 
java.lang.ArrayIndexOutOfBoundsException: 1

Jeff.

-Original Message-
From: cryptearth [mailto:cryptea...@cryptearth.de]
Sent: Tuesday, March 26, 2019 2:13 AM
To: server-user@james.apache.org
Subject: Re: sqlResources.xml

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 correctly 
in james-database.properties file.

So, possible fix: update to 3.3.x branch.


greetings,

Matt

Am 25.03.2019 um 21:09 schrieb Garry Hurley:

Yeah, I had put up a bug report on that issue. I had to fix that in the source 
code. The problem is the MailboxAnnotation class uses the column name ‘KEY’ 
which is a res

RE: sqlResources.xml

2019-03-26 Thread Marans . Jeffrey
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 bind code the same in 3.2 and 3.3?

I've attached the wrapper log.

-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 
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 13:59 schrieb Marans.Jeffrey:
> 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  08:51:03,450 | 
> org.apache.james.protocols.lib.netty.AbstractConfigurableAsyncServer | POP3 
> Service bound to: nsep1u9254:110
> INFO   | jvm 1| 2019/03/26 08:51:03 | INFO  08:51:03,450 | 
> org.apache.james.protocols.lib.netty.AbstractConfigurableAsyncServer | POP3 
> Service is running on: nsep1u9254
> INFO   | jvm 1| 2019/03/26 08:51:03 | INFO  08:51:03,450 | 
> org.apache.james.protocols.lib.netty.AbstractConfigurableAsyncServer | POP3 
> Service handler hello name is: nsep1u9254
> INFO   | jvm 1| 2019/03/26 08:51:03 | INFO  08:51:03,451 | 
> org.apache.james.protocols.lib.netty.AbstractConfigurableAsyncServer | POP3 
> Service handler connection timeout is: 1200
> INFO   | jvm 1| 2019/03/26 08:51:03 | INFO  08:51:03,451 | 
> org.apache.james.protocols.lib.netty.AbstractConfigurableAsyncServer | POP3 
> Service connection backlog is: 200
> INFO   | jvm 1| 2019/03/26 08:51:03 | WARN  08:51:03,548 | 
> org.apache.james.container.spring.context.JamesServerApplicationContext | 
> Exception encountered during context initialization - cancelling refresh 
> attempt: 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: nsep1u9254/10.33.117.54:110
>
> -Original Message-
> From: cryptearth [mailto:cryptea...@cryptearth.de]
> Sent: Tuesday, March 26, 2019 8:24 AM
> To: server-user@james.apache.org
> Subject: Re: sqlResources.xml
>
> 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 running main: 
>> org.springframework.beans.factory.BeanCreationException: Error creating bean 
>> with name 'pop3server': Invocation of init method failed; nested exception 
>> is java.lang.ArrayIndexOutOfBoundsException: 1
>> INFO   | jvm 1| 2019/03/25 15:01:27 | 
>> org.springframework.beans.factory.BeanCreationException: Error creating bean 
>> with name 'pop3server': Invocation of init method failed; nested exception 
>> is java.lang.ArrayIndexOutOfBoundsException: 1
>>
>> Jeff.
>>
>> -Original Message-
>> From: cryptearth [mailto:cryptea...@cryptearth.de]
>> Sent: Tuesday, March 26, 2019 2:13 AM
>> To: server-user@james.apache.org
>> Subject: Re: sqlResources.xml
>>
>> 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 
>> correctly in james-database.properties file.
>>
>> So, possible fix: update to 3.3.x branch.
>>
>>
>> greetings,
>>
>> Matt
>>
>> Am 25.03.2019 um 21:09 schrieb Garry Hurley:
>>> Yeah, I had put up a bug report on that issue. I had to fix that in the 
>>> source code. The problem is the MailboxAnnotation class uses the column 
>>> name ‘KEY’ which is a reserved word in SQL, so most real SQL databases balk 
>>> at it. I thought that had been fixed before the 3.3 tag was finalized. All 
>>> we need to do is change the column name to ‘AN

RE: sqlResources.xml

2019-03-26 Thread Marans . Jeffrey
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 
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 13:59 schrieb Marans.Jeffrey:
> 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  08:51:03,450 | 
> org.apache.james.protocols.lib.netty.AbstractConfigurableAsyncServer | POP3 
> Service bound to: nsep1u9254:110
> INFO   | jvm 1| 2019/03/26 08:51:03 | INFO  08:51:03,450 | 
> org.apache.james.protocols.lib.netty.AbstractConfigurableAsyncServer | POP3 
> Service is running on: nsep1u9254
> INFO   | jvm 1| 2019/03/26 08:51:03 | INFO  08:51:03,450 | 
> org.apache.james.protocols.lib.netty.AbstractConfigurableAsyncServer | POP3 
> Service handler hello name is: nsep1u9254
> INFO   | jvm 1| 2019/03/26 08:51:03 | INFO  08:51:03,451 | 
> org.apache.james.protocols.lib.netty.AbstractConfigurableAsyncServer | POP3 
> Service handler connection timeout is: 1200
> INFO   | jvm 1| 2019/03/26 08:51:03 | INFO  08:51:03,451 | 
> org.apache.james.protocols.lib.netty.AbstractConfigurableAsyncServer | POP3 
> Service connection backlog is: 200
> INFO   | jvm 1| 2019/03/26 08:51:03 | WARN  08:51:03,548 | 
> org.apache.james.container.spring.context.JamesServerApplicationContext | 
> Exception encountered during context initialization - cancelling refresh 
> attempt: 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: nsep1u9254/10.33.117.54:110
>
> -Original Message-
> From: cryptearth [mailto:cryptea...@cryptearth.de]
> Sent: Tuesday, March 26, 2019 8:24 AM
> To: server-user@james.apache.org
> Subject: Re: sqlResources.xml
>
> 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 running main: 
>> org.springframework.beans.factory.BeanCreationException: Error creating bean 
>> with name 'pop3server': Invocation of init method failed; nested exception 
>> is java.lang.ArrayIndexOutOfBoundsException: 1
>> INFO   | jvm 1| 2019/03/25 15:01:27 | 
>> org.springframework.beans.factory.BeanCreationException: Error creating bean 
>> with name 'pop3server': Invocation of init method failed; nested exception 
>> is java.lang.ArrayIndexOutOfBoundsException: 1
>>
>> Jeff.
>>
>> -Original Message-
>> From: cryptearth [mailto:cryptea...@cryptearth.de]
>> Sent: Tuesday, March 26, 2019 2:13 AM
>> To: server-user@james.apache.org
>> Subject: Re: sqlResources.xml
>>
>> 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 
>> correctly in james-database.properties file.
>>
>> So, possible fix: update to 3.3.x branch.
>>
>>
>> greetings,
>>
>> Matt
>>
>> Am 25.03.2019 um 21:09 schrieb Garry Hurley:
>>> Yeah, I had put up a bug report on that issue. I had to fix that in the 
>>> source code. The problem is the MailboxAnnotation class uses the column 
>>> name ‘KEY’ which is a reserved word in SQL, so most real SQL databases balk 
>>> at it. I thought that had been fixed before the 3.3 tag was finalized. All 
>>> we need to do is change the column name to ‘ANNOTATION_KEY’. That has to be 
>>> done in source code though, not in the sqlResources file. Welcome to JPA.
>>>
>>> Sent from my iPhone
>>>
>>>> On Mar 25, 2019, at 12:49 PM, Marans.Jeffrey  
>>>> wrote:
>>>>
>>>> When I start james 3.0.2 the log contains C

Re: sqlResources.xml

2019-03-26 Thread cryptearth
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 13:59 schrieb Marans.Jeffrey:

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  08:51:03,450 | 
org.apache.james.protocols.lib.netty.AbstractConfigurableAsyncServer | POP3 
Service bound to: nsep1u9254:110
INFO   | jvm 1| 2019/03/26 08:51:03 | INFO  08:51:03,450 | 
org.apache.james.protocols.lib.netty.AbstractConfigurableAsyncServer | POP3 
Service is running on: nsep1u9254
INFO   | jvm 1| 2019/03/26 08:51:03 | INFO  08:51:03,450 | 
org.apache.james.protocols.lib.netty.AbstractConfigurableAsyncServer | POP3 
Service handler hello name is: nsep1u9254
INFO   | jvm 1| 2019/03/26 08:51:03 | INFO  08:51:03,451 | 
org.apache.james.protocols.lib.netty.AbstractConfigurableAsyncServer | POP3 
Service handler connection timeout is: 1200
INFO   | jvm 1| 2019/03/26 08:51:03 | INFO  08:51:03,451 | 
org.apache.james.protocols.lib.netty.AbstractConfigurableAsyncServer | POP3 
Service connection backlog is: 200
INFO   | jvm 1| 2019/03/26 08:51:03 | WARN  08:51:03,548 | 
org.apache.james.container.spring.context.JamesServerApplicationContext | 
Exception encountered during context initialization - cancelling refresh 
attempt: 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: 
nsep1u9254/10.33.117.54:110

-Original Message-
From: cryptearth [mailto:cryptea...@cryptearth.de]
Sent: Tuesday, March 26, 2019 8:24 AM
To: server-user@james.apache.org
Subject: Re: sqlResources.xml

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 running main: 
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'pop3server': Invocation of init method failed; nested exception is 
java.lang.ArrayIndexOutOfBoundsException: 1
INFO   | jvm 1| 2019/03/25 15:01:27 | 
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'pop3server': Invocation of init method failed; nested exception is 
java.lang.ArrayIndexOutOfBoundsException: 1

Jeff.

-Original Message-
From: cryptearth [mailto:cryptea...@cryptearth.de]
Sent: Tuesday, March 26, 2019 2:13 AM
To: server-user@james.apache.org
Subject: Re: sqlResources.xml

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 correctly 
in james-database.properties file.

So, possible fix: update to 3.3.x branch.


greetings,

Matt

Am 25.03.2019 um 21:09 schrieb Garry Hurley:

Yeah, I had put up a bug report on that issue. I had to fix that in the source 
code. The problem is the MailboxAnnotation class uses the column name ‘KEY’ 
which is a reserved word in SQL, so most real SQL databases balk at it. I 
thought that had been fixed before the 3.3 tag was finalized. All we need to do 
is change the column name to ‘ANNOTATION_KEY’. That has to be done in source 
code though, not in the sqlResources file. Welcome to JPA.

Sent from my iPhone


On Mar 25, 2019, at 12:49 PM, Marans.Jeffrey  wrote:

When I start james 3.0.2 the log contains Connected to Microsoft SQL Server 
version 12.12 using JDBC driver Microsoft JDBC Driver 7.2 for SQL Server 
version 7.2.1.0, and 3 tables were  created.

But this warning turns fatal
WARN  12:21:51,120 |
org.apache.james.container.spring.context.JamesServerApplicationCont
e xt | Exception encountered during context initialization -
cancelling refresh attempt:
org.springframework.beans.factory.UnsatisfiedDependencyException:
Error creating bean with name 'authenticator' defined in class path
resource
[META-INF/org/apache/james/spring-mailbox-authenticator.xml]:
Unsatisfied dependency expressed through constructor argument with
index 0 of type [org.apache.james.user.api.UsersRepository]: : Error
creating bean with name 'usersrepository': Injection of autowired
dependencies failed; nested exception is
org.springframework.beans.factory.BeanCreationException: Could not
autowire method: p

RE: sqlResources.xml

2019-03-26 Thread Marans . Jeffrey
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  08:51:03,450 | 
org.apache.james.protocols.lib.netty.AbstractConfigurableAsyncServer | POP3 
Service bound to: nsep1u9254:110
INFO   | jvm 1| 2019/03/26 08:51:03 | INFO  08:51:03,450 | 
org.apache.james.protocols.lib.netty.AbstractConfigurableAsyncServer | POP3 
Service is running on: nsep1u9254
INFO   | jvm 1| 2019/03/26 08:51:03 | INFO  08:51:03,450 | 
org.apache.james.protocols.lib.netty.AbstractConfigurableAsyncServer | POP3 
Service handler hello name is: nsep1u9254
INFO   | jvm 1| 2019/03/26 08:51:03 | INFO  08:51:03,451 | 
org.apache.james.protocols.lib.netty.AbstractConfigurableAsyncServer | POP3 
Service handler connection timeout is: 1200
INFO   | jvm 1| 2019/03/26 08:51:03 | INFO  08:51:03,451 | 
org.apache.james.protocols.lib.netty.AbstractConfigurableAsyncServer | POP3 
Service connection backlog is: 200
INFO   | jvm 1| 2019/03/26 08:51:03 | WARN  08:51:03,548 | 
org.apache.james.container.spring.context.JamesServerApplicationContext | 
Exception encountered during context initialization - cancelling refresh 
attempt: 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: 
nsep1u9254/10.33.117.54:110

-Original Message-
From: cryptearth [mailto:cryptea...@cryptearth.de] 
Sent: Tuesday, March 26, 2019 8:24 AM
To: server-user@james.apache.org
Subject: Re: sqlResources.xml

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 running main: 
> org.springframework.beans.factory.BeanCreationException: Error creating bean 
> with name 'pop3server': Invocation of init method failed; nested exception is 
> java.lang.ArrayIndexOutOfBoundsException: 1
> INFO   | jvm 1| 2019/03/25 15:01:27 | 
> org.springframework.beans.factory.BeanCreationException: Error creating bean 
> with name 'pop3server': Invocation of init method failed; nested exception is 
> java.lang.ArrayIndexOutOfBoundsException: 1
>
> Jeff.
>
> -Original Message-
> From: cryptearth [mailto:cryptea...@cryptearth.de]
> Sent: Tuesday, March 26, 2019 2:13 AM
> To: server-user@james.apache.org
> Subject: Re: sqlResources.xml
>
> 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 
> correctly in james-database.properties file.
>
> So, possible fix: update to 3.3.x branch.
>
>
> greetings,
>
> Matt
>
> Am 25.03.2019 um 21:09 schrieb Garry Hurley:
>> Yeah, I had put up a bug report on that issue. I had to fix that in the 
>> source code. The problem is the MailboxAnnotation class uses the column name 
>> ‘KEY’ which is a reserved word in SQL, so most real SQL databases balk at 
>> it. I thought that had been fixed before the 3.3 tag was finalized. All we 
>> need to do is change the column name to ‘ANNOTATION_KEY’. That has to be 
>> done in source code though, not in the sqlResources file. Welcome to JPA.
>>
>> Sent from my iPhone
>>
>>> On Mar 25, 2019, at 12:49 PM, Marans.Jeffrey  
>>> wrote:
>>>
>>> When I start james 3.0.2 the log contains Connected to Microsoft SQL Server 
>>> version 12.12 using JDBC driver Microsoft JDBC Driver 7.2 for SQL Server 
>>> version 7.2.1.0, and 3 tables were  created.
>>>
>>> But this warning turns fatal
>>> WARN  12:21:51,120 |
>>> org.apache.james.container.spring.context.JamesServerApplicationCont
>>> e xt | Exception encountered during context initialization - 
>>> cancelling refresh attempt:
>>> org.springframework.beans.factory.UnsatisfiedDependencyException:
>>> Error creating bean with name 'authenticator' defined in class path 
>>> resource
>>> [META-INF/org/apache/james/spring-mailbox-authenticator.xml]:
>>> Unsatisfied dependency expressed through constructor argument with 
>>> index 0 of type [org.apache.james.user.api.UsersRepository]: : Error 
>>> creating bean wit

RE: sqlResources.xml

2019-03-26 Thread Marans . Jeffrey
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
Subject: Re: sqlResources.xml

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: 
> 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
> INFO   | jvm 1| 2019/03/26 08:35:36 | 
> 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
>
> Caused by: java.net.BindException: Address already in use
>
>
> -Original Message-
> From: cryptearth [mailto:cryptea...@cryptearth.de]
> Sent: Tuesday, March 26, 2019 8:24 AM
> To: server-user@james.apache.org
> Subject: Re: sqlResources.xml
>
> 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 running main: 
>> org.springframework.beans.factory.BeanCreationException: Error creating bean 
>> with name 'pop3server': Invocation of init method failed; nested exception 
>> is java.lang.ArrayIndexOutOfBoundsException: 1
>> INFO   | jvm 1| 2019/03/25 15:01:27 | 
>> org.springframework.beans.factory.BeanCreationException: Error creating bean 
>> with name 'pop3server': Invocation of init method failed; nested exception 
>> is java.lang.ArrayIndexOutOfBoundsException: 1
>>
>> Jeff.
>>
>> -Original Message-
>> From: cryptearth [mailto:cryptea...@cryptearth.de]
>> Sent: Tuesday, March 26, 2019 2:13 AM
>> To: server-user@james.apache.org
>> Subject: Re: sqlResources.xml
>>
>> 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 
>> correctly in james-database.properties file.
>>
>> So, possible fix: update to 3.3.x branch.
>>
>>
>> greetings,
>>
>> Matt
>>
>> Am 25.03.2019 um 21:09 schrieb Garry Hurley:
>>> Yeah, I had put up a bug report on that issue. I had to fix that in the 
>>> source code. The problem is the MailboxAnnotation class uses the column 
>>> name ‘KEY’ which is a reserved word in SQL, so most real SQL databases balk 
>>> at it. I thought that had been fixed before the 3.3 tag was finalized. All 
>>> we need to do is change the column name to ‘ANNOTATION_KEY’. That has to be 
>>> done in source code though, not in the sqlResources file. Welcome to JPA.
>>>
>>> Sent from my iPhone
>>>
>>>> On Mar 25, 2019, at 12:49 PM, Marans.Jeffrey  
>>>> wrote:
>>>>
>>>> When I start james 3.0.2 the log contains Connected to Microsoft SQL 
>>>> Server version 12.12 using JDBC driver Microsoft JDBC Driver 7.2 for SQL 
>>>> Server version 7.2.1.0, and 3 tables were  created.
>>>>
>>>> But this warning turns fatal
>>>> WARN  12:21:51,120 |
>>>> org.apache.james.container.spring.context.JamesServerApplicationCon
>>>> t e xt | Exception encountered during context initialization - 
>>>> cancelling refresh attempt:
>>>> org.springframework.beans.factory.UnsatisfiedDependencyException:
>>>> Error creating bean with name 'authenticator' defined in class path 
>>>> resource
>>>> [META-INF/org/apache/james/spring-mailbox-authenticator.xml]:
>>>> Unsatisfied dependency expressed through constructor argument with 
>>>> index 0 of type [org.apache.james.user.api.UsersRepository]: : 
>>>> Error creating bean with name 'usersrepository': Injection

Re: sqlResources.xml

2019-03-26 Thread cryptearth
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: 
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
INFO   | jvm 1| 2019/03/26 08:35:36 | 
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

Caused by: java.net.BindException: Address already in use


-Original Message-
From: cryptearth [mailto:cryptea...@cryptearth.de]
Sent: Tuesday, March 26, 2019 8:24 AM
To: server-user@james.apache.org
Subject: Re: sqlResources.xml

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 running main: 
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'pop3server': Invocation of init method failed; nested exception is 
java.lang.ArrayIndexOutOfBoundsException: 1
INFO   | jvm 1| 2019/03/25 15:01:27 | 
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'pop3server': Invocation of init method failed; nested exception is 
java.lang.ArrayIndexOutOfBoundsException: 1

Jeff.

-Original Message-
From: cryptearth [mailto:cryptea...@cryptearth.de]
Sent: Tuesday, March 26, 2019 2:13 AM
To: server-user@james.apache.org
Subject: Re: sqlResources.xml

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 correctly 
in james-database.properties file.

So, possible fix: update to 3.3.x branch.


greetings,

Matt

Am 25.03.2019 um 21:09 schrieb Garry Hurley:

Yeah, I had put up a bug report on that issue. I had to fix that in the source 
code. The problem is the MailboxAnnotation class uses the column name ‘KEY’ 
which is a reserved word in SQL, so most real SQL databases balk at it. I 
thought that had been fixed before the 3.3 tag was finalized. All we need to do 
is change the column name to ‘ANNOTATION_KEY’. That has to be done in source 
code though, not in the sqlResources file. Welcome to JPA.

Sent from my iPhone


On Mar 25, 2019, at 12:49 PM, Marans.Jeffrey  wrote:

When I start james 3.0.2 the log contains Connected to Microsoft SQL Server 
version 12.12 using JDBC driver Microsoft JDBC Driver 7.2 for SQL Server 
version 7.2.1.0, and 3 tables were  created.

But this warning turns fatal
WARN  12:21:51,120 |
org.apache.james.container.spring.context.JamesServerApplicationCont
e xt | Exception encountered during context initialization -
cancelling refresh attempt:
org.springframework.beans.factory.UnsatisfiedDependencyException:
Error creating bean with name 'authenticator' defined in class path
resource
[META-INF/org/apache/james/spring-mailbox-authenticator.xml]:
Unsatisfied dependency expressed through constructor argument with
index 0 of type [org.apache.james.user.api.UsersRepository]: : Error
creating bean with name 'usersrepository': Injection of autowired
dependencies failed; nested exception is
org.springframework.beans.factory.BeanCreationException: Could not
autowire method: public void
org.apache.james.user.lib.AbstractUsersRepository.setDomainList(org.
a pache.james.domainlist.api.DomainList); nested exception is
org.springframework.beans.factory.BeanCreationException: Error
creating bean with name 'domainlist': Initialization of bean failed;
nested exception is org.springframework.beans.FatalBeanException:
Unable to execute lifecycle method on beandomainlist; nested
exception is 
org.apache.openjpa.persistence.PersistenceException: Incorrect
syntax near the keyword 'KEY'. {stmnt 1664030951 CREATE TABLE
JAMES_MAILBOX_ANNOTATION (KEY VARCHAR(200) NOT NULL, MAILBOX_ID
BIGINT NOT NULL, VALUE VARCHAR(255), PRIMARY KEY (KEY, MAILBOX_ID))}
[code=156, state=S0001]; nested exception is
org.springframework.beans.factory.BeanCreationException: Error
creating bean with name 'usersrepository': Injection of autowired
dependencies failed; nested exception is
org.springframework.beans.factory.BeanCreationException: Could not
autowire method: public void
org.apache.james.user.lib.AbstractUsersRepository.setDomainList(org.
a pache.james.domainlist.api.DomainList); nested exception

RE: sqlResources.xml

2019-03-26 Thread Marans . Jeffrey
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
INFO   | jvm 1| 2019/03/26 08:35:36 | 
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

Caused by: java.net.BindException: Address already in use


-Original Message-
From: cryptearth [mailto:cryptea...@cryptearth.de] 
Sent: Tuesday, March 26, 2019 8:24 AM
To: server-user@james.apache.org
Subject: Re: sqlResources.xml

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 running main: 
> org.springframework.beans.factory.BeanCreationException: Error creating bean 
> with name 'pop3server': Invocation of init method failed; nested exception is 
> java.lang.ArrayIndexOutOfBoundsException: 1
> INFO   | jvm 1| 2019/03/25 15:01:27 | 
> org.springframework.beans.factory.BeanCreationException: Error creating bean 
> with name 'pop3server': Invocation of init method failed; nested exception is 
> java.lang.ArrayIndexOutOfBoundsException: 1
>
> Jeff.
>
> -Original Message-
> From: cryptearth [mailto:cryptea...@cryptearth.de]
> Sent: Tuesday, March 26, 2019 2:13 AM
> To: server-user@james.apache.org
> Subject: Re: sqlResources.xml
>
> 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 
> correctly in james-database.properties file.
>
> So, possible fix: update to 3.3.x branch.
>
>
> greetings,
>
> Matt
>
> Am 25.03.2019 um 21:09 schrieb Garry Hurley:
>> Yeah, I had put up a bug report on that issue. I had to fix that in the 
>> source code. The problem is the MailboxAnnotation class uses the column name 
>> ‘KEY’ which is a reserved word in SQL, so most real SQL databases balk at 
>> it. I thought that had been fixed before the 3.3 tag was finalized. All we 
>> need to do is change the column name to ‘ANNOTATION_KEY’. That has to be 
>> done in source code though, not in the sqlResources file. Welcome to JPA.
>>
>> Sent from my iPhone
>>
>>> On Mar 25, 2019, at 12:49 PM, Marans.Jeffrey  
>>> wrote:
>>>
>>> When I start james 3.0.2 the log contains Connected to Microsoft SQL Server 
>>> version 12.12 using JDBC driver Microsoft JDBC Driver 7.2 for SQL Server 
>>> version 7.2.1.0, and 3 tables were  created.
>>>
>>> But this warning turns fatal
>>> WARN  12:21:51,120 |
>>> org.apache.james.container.spring.context.JamesServerApplicationCont
>>> e xt | Exception encountered during context initialization - 
>>> cancelling refresh attempt:
>>> org.springframework.beans.factory.UnsatisfiedDependencyException:
>>> Error creating bean with name 'authenticator' defined in class path 
>>> resource
>>> [META-INF/org/apache/james/spring-mailbox-authenticator.xml]:
>>> Unsatisfied dependency expressed through constructor argument with 
>>> index 0 of type [org.apache.james.user.api.UsersRepository]: : Error 
>>> creating bean with name 'usersrepository': Injection of autowired 
>>> dependencies failed; nested exception is
>>> org.springframework.beans.factory.BeanCreationException: Could not 
>>> autowire method: public void 
>>> org.apache.james.user.lib.AbstractUsersRepository.setDomainList(org.
>>> a pache.james.domainlist.api.DomainList); nested exception is
>>> org.springframework.beans.factory.BeanCreationException: Error 
>>> creating bean with name 'domainlist': Initialization of bean failed; 
>>> nested exception is org.springframework.beans.FatalBeanException:
>>> Unable to execute lifecycle method on beandomainlist; nested 
>>> exception is 
>>> org.apache.openjpa.persistence.PersistenceException: Incorrect 
>>> syntax near the keyword 'KEY'. {stmnt 1664030951 CREATE TABLE 
>>> JAMES_MAILBOX_ANNOTATION (KEY VARCHAR(200) NOT NULL, MAILBOX_ID 
>>> BIGINT NOT NULL, V

Re: sqlResources.xml

2019-03-26 Thread cryptearth
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 running main: 
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'pop3server': Invocation of init method failed; nested exception is 
java.lang.ArrayIndexOutOfBoundsException: 1
INFO   | jvm 1| 2019/03/25 15:01:27 | 
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'pop3server': Invocation of init method failed; nested exception is 
java.lang.ArrayIndexOutOfBoundsException: 1

Jeff.

-Original Message-
From: cryptearth [mailto:cryptea...@cryptearth.de]
Sent: Tuesday, March 26, 2019 2:13 AM
To: server-user@james.apache.org
Subject: Re: sqlResources.xml

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 correctly 
in james-database.properties file.

So, possible fix: update to 3.3.x branch.


greetings,

Matt

Am 25.03.2019 um 21:09 schrieb Garry Hurley:

Yeah, I had put up a bug report on that issue. I had to fix that in the source 
code. The problem is the MailboxAnnotation class uses the column name ‘KEY’ 
which is a reserved word in SQL, so most real SQL databases balk at it. I 
thought that had been fixed before the 3.3 tag was finalized. All we need to do 
is change the column name to ‘ANNOTATION_KEY’. That has to be done in source 
code though, not in the sqlResources file. Welcome to JPA.

Sent from my iPhone


On Mar 25, 2019, at 12:49 PM, Marans.Jeffrey  wrote:

When I start james 3.0.2 the log contains Connected to Microsoft SQL Server 
version 12.12 using JDBC driver Microsoft JDBC Driver 7.2 for SQL Server 
version 7.2.1.0, and 3 tables were  created.

But this warning turns fatal
WARN  12:21:51,120 |
org.apache.james.container.spring.context.JamesServerApplicationConte
xt | Exception encountered during context initialization - cancelling
refresh attempt:
org.springframework.beans.factory.UnsatisfiedDependencyException:
Error creating bean with name 'authenticator' defined in class path
resource
[META-INF/org/apache/james/spring-mailbox-authenticator.xml]:
Unsatisfied dependency expressed through constructor argument with
index 0 of type [org.apache.james.user.api.UsersRepository]: : Error
creating bean with name 'usersrepository': Injection of autowired
dependencies failed; nested exception is
org.springframework.beans.factory.BeanCreationException: Could not
autowire method: public void
org.apache.james.user.lib.AbstractUsersRepository.setDomainList(org.a
pache.james.domainlist.api.DomainList); nested exception is
org.springframework.beans.factory.BeanCreationException: Error
creating bean with name 'domainlist': Initialization of bean failed;
nested exception is org.springframework.beans.FatalBeanException:
Unable to execute lifecycle method on beandomainlist; nested
exception is 
org.apache.openjpa.persistence.PersistenceException: Incorrect syntax
near the keyword 'KEY'. {stmnt 1664030951 CREATE TABLE
JAMES_MAILBOX_ANNOTATION (KEY VARCHAR(200) NOT NULL, MAILBOX_ID
BIGINT NOT NULL, VALUE VARCHAR(255), PRIMARY KEY (KEY, MAILBOX_ID))}
[code=156, state=S0001]; nested exception is
org.springframework.beans.factory.BeanCreationException: Error
creating bean with name 'usersrepository': Injection of autowired
dependencies failed; nested exception is
org.springframework.beans.factory.BeanCreationException: Could not
autowire method: public void
org.apache.james.user.lib.AbstractUsersRepository.setDomainList(org.a
pache.james.domainlist.api.DomainList); nested exception is
org.springframework.beans.factory.BeanCreationException: Error
creating bean with name 'domainlist': Initialization of bean failed;
nested exception is org.springframework.beans.FatalBeanException:
Unable to execute lifecycle method on beandomainlist; nested
exception is 
org.apache.openjpa.persistence.PersistenceException: Incorrect syntax
near the keyword 'KEY'. {stmnt 1664030951 CREATE TABLE
JAMES_MAILBOX_ANNOTATION (KEY VARCHAR(200) NOT NULL, MAILBOX_ID
BIGINT NOT NULL, VALUE VARCHAR(255), PRIMARY KEY (KEY, MAILBOX_ID))}
[code=156, state=S0001]

I can't find anything on the web regarding how to modify sqlResources.xml to 
work with MS SQL Server.


Jeffrey Marans

Enterprise Architect Biometrics, Domestic Network Immigration,
Refugees and Citizenship Canada / Government of Canada
jeffrey.mar...@cic.gc.ca<mailto:jeffrey.mar...@cic.gc.ca> / Tel:
613-437-9890

Architecte de biométrie (Consultant), Solutions et gestion de
l'information Immigration, Réfugiés et Citoyenneté Canada /
Gouvernement du Canada
jeffr

RE: sqlResources.xml

2019-03-26 Thread 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 running main: 
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'pop3server': Invocation of init method failed; nested exception is 
java.lang.ArrayIndexOutOfBoundsException: 1
INFO   | jvm 1| 2019/03/25 15:01:27 | 
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'pop3server': Invocation of init method failed; nested exception is 
java.lang.ArrayIndexOutOfBoundsException: 1

Jeff.

-Original Message-
From: cryptearth [mailto:cryptea...@cryptearth.de] 
Sent: Tuesday, March 26, 2019 2:13 AM
To: server-user@james.apache.org
Subject: Re: sqlResources.xml

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 correctly 
in james-database.properties file.

So, possible fix: update to 3.3.x branch.


greetings,

Matt

Am 25.03.2019 um 21:09 schrieb Garry Hurley:
> Yeah, I had put up a bug report on that issue. I had to fix that in the 
> source code. The problem is the MailboxAnnotation class uses the column name 
> ‘KEY’ which is a reserved word in SQL, so most real SQL databases balk at it. 
> I thought that had been fixed before the 3.3 tag was finalized. All we need 
> to do is change the column name to ‘ANNOTATION_KEY’. That has to be done in 
> source code though, not in the sqlResources file. Welcome to JPA.
>
> Sent from my iPhone
>
>> On Mar 25, 2019, at 12:49 PM, Marans.Jeffrey  
>> wrote:
>>
>> When I start james 3.0.2 the log contains Connected to Microsoft SQL Server 
>> version 12.12 using JDBC driver Microsoft JDBC Driver 7.2 for SQL Server 
>> version 7.2.1.0, and 3 tables were  created.
>>
>> But this warning turns fatal
>> WARN  12:21:51,120 | 
>> org.apache.james.container.spring.context.JamesServerApplicationConte
>> xt | Exception encountered during context initialization - cancelling 
>> refresh attempt: 
>> org.springframework.beans.factory.UnsatisfiedDependencyException: 
>> Error creating bean with name 'authenticator' defined in class path 
>> resource 
>> [META-INF/org/apache/james/spring-mailbox-authenticator.xml]: 
>> Unsatisfied dependency expressed through constructor argument with 
>> index 0 of type [org.apache.james.user.api.UsersRepository]: : Error 
>> creating bean with name 'usersrepository': Injection of autowired 
>> dependencies failed; nested exception is 
>> org.springframework.beans.factory.BeanCreationException: Could not 
>> autowire method: public void 
>> org.apache.james.user.lib.AbstractUsersRepository.setDomainList(org.a
>> pache.james.domainlist.api.DomainList); nested exception is 
>> org.springframework.beans.factory.BeanCreationException: Error 
>> creating bean with name 'domainlist': Initialization of bean failed; 
>> nested exception is org.springframework.beans.FatalBeanException: 
>> Unable to execute lifecycle method on beandomainlist; nested 
>> exception is  
>> org.apache.openjpa.persistence.PersistenceException: Incorrect syntax 
>> near the keyword 'KEY'. {stmnt 1664030951 CREATE TABLE 
>> JAMES_MAILBOX_ANNOTATION (KEY VARCHAR(200) NOT NULL, MAILBOX_ID 
>> BIGINT NOT NULL, VALUE VARCHAR(255), PRIMARY KEY (KEY, MAILBOX_ID))} 
>> [code=156, state=S0001]; nested exception is 
>> org.springframework.beans.factory.BeanCreationException: Error 
>> creating bean with name 'usersrepository': Injection of autowired 
>> dependencies failed; nested exception is 
>> org.springframework.beans.factory.BeanCreationException: Could not 
>> autowire method: public void 
>> org.apache.james.user.lib.AbstractUsersRepository.setDomainList(org.a
>> pache.james.domainlist.api.DomainList); nested exception is 
>> org.springframework.beans.factory.BeanCreationException: Error 
>> creating bean with name 'domainlist': Initialization of bean failed; 
>> nested exception is org.springframework.beans.FatalBeanException: 
>> Unable to execute lifecycle method on beandomainlist; nested 
>> exception is  
>> org.apache.openjpa.persistence.PersistenceException: Incorrect syntax 
>> near the keyword 'KEY'. {stmnt 1664030951 CREATE TABLE 
>> JAMES_MAILBOX_ANNOTATION (KEY VARCHAR(200) NOT NULL, MAILBOX_ID 
>> BIGINT NOT NULL, VALUE VARCHAR(255), PRIMARY KEY (KEY, MAILBOX_ID))} 
>> [code=156, state=S0001]
>>
>> I can't find anything on the web regarding how to modify sqlResour

Re: sqlResources.xml

2019-03-26 Thread cryptearth

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 
correctly in james-database.properties file.


So, possible fix: update to 3.3.x branch.


greetings,

Matt

Am 25.03.2019 um 21:09 schrieb Garry Hurley:

Yeah, I had put up a bug report on that issue. I had to fix that in the source 
code. The problem is the MailboxAnnotation class uses the column name ‘KEY’ 
which is a reserved word in SQL, so most real SQL databases balk at it. I 
thought that had been fixed before the 3.3 tag was finalized. All we need to do 
is change the column name to ‘ANNOTATION_KEY’. That has to be done in source 
code though, not in the sqlResources file. Welcome to JPA.

Sent from my iPhone


On Mar 25, 2019, at 12:49 PM, Marans.Jeffrey  wrote:

When I start james 3.0.2 the log contains Connected to Microsoft SQL Server 
version 12.12 using JDBC driver Microsoft JDBC Driver 7.2 for SQL Server 
version 7.2.1.0, and 3 tables were  created.

But this warning turns fatal
WARN  12:21:51,120 | 
org.apache.james.container.spring.context.JamesServerApplicationContext | Exception 
encountered during context initialization - cancelling refresh attempt: 
org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with 
name 'authenticator' defined in class path resource 
[META-INF/org/apache/james/spring-mailbox-authenticator.xml]: Unsatisfied dependency 
expressed through constructor argument with index 0 of type 
[org.apache.james.user.api.UsersRepository]: : Error creating bean with name 
'usersrepository': Injection of autowired dependencies failed; nested exception is 
org.springframework.beans.factory.BeanCreationException: Could not autowire method: public 
void 
org.apache.james.user.lib.AbstractUsersRepository.setDomainList(org.apache.james.domainlist.api.DomainList);
 nested exception is org.springframework.beans.factory.BeanCreationException: Error 
creating bean with name 'domainlist': Initialization of bean failed; nested exception is 
org.springframework.beans.FatalBeanException: Unable to execute lifecycle method on 
beandomainlist; nested exception is  org.apache.openjpa.persistence.PersistenceException: Incorrect syntax near the 
keyword 'KEY'. {stmnt 1664030951 CREATE TABLE JAMES_MAILBOX_ANNOTATION (KEY VARCHAR(200) 
NOT NULL, MAILBOX_ID BIGINT NOT NULL, VALUE VARCHAR(255), PRIMARY KEY (KEY, MAILBOX_ID))} 
[code=156, state=S0001]; nested exception is 
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 
'usersrepository': Injection of autowired dependencies failed; nested exception is 
org.springframework.beans.factory.BeanCreationException: Could not autowire method: public 
void 
org.apache.james.user.lib.AbstractUsersRepository.setDomainList(org.apache.james.domainlist.api.DomainList);
 nested exception is org.springframework.beans.factory.BeanCreationException: Error 
creating bean with name 'domainlist': Initialization of bean failed; nested exception is 
org.springframework.beans.FatalBeanException: Unable to execute lifecycle method on 
beandomainlist; nested exception is  org.apache.openjpa.persistence.PersistenceException: Incorrect syntax near the 
keyword 'KEY'. {stmnt 1664030951 CREATE TABLE JAMES_MAILBOX_ANNOTATION (KEY VARCHAR(200) 
NOT NULL, MAILBOX_ID BIGINT NOT NULL, VALUE VARCHAR(255), PRIMARY KEY (KEY, MAILBOX_ID))} 
[code=156, state=S0001]

I can't find anything on the web regarding how to modify sqlResources.xml to 
work with MS SQL Server.


Jeffrey Marans

Enterprise Architect Biometrics, Domestic Network
Immigration, Refugees and Citizenship Canada / Government of Canada
jeffrey.mar...@cic.gc.ca / Tel: 613-437-9890

Architecte de biométrie (Consultant), Solutions et gestion de l'information
Immigration, Réfugiés et Citoyenneté Canada / Gouvernement du Canada
jeffrey.mar...@cic.gc.ca / Tél.: 613-437-9890


-
To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org
For additional commands, e-mail: server-user-h...@james.apache.org





-
To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org
For additional commands, e-mail: server-user-h...@james.apache.org



Re: sqlResources.xml

2019-03-25 Thread Garry Hurley
Yeah, I had put up a bug report on that issue. I had to fix that in the source 
code. The problem is the MailboxAnnotation class uses the column name ‘KEY’ 
which is a reserved word in SQL, so most real SQL databases balk at it. I 
thought that had been fixed before the 3.3 tag was finalized. All we need to do 
is change the column name to ‘ANNOTATION_KEY’. That has to be done in source 
code though, not in the sqlResources file. Welcome to JPA. 

Sent from my iPhone

> On Mar 25, 2019, at 12:49 PM, Marans.Jeffrey  wrote:
> 
> When I start james 3.0.2 the log contains Connected to Microsoft SQL Server 
> version 12.12 using JDBC driver Microsoft JDBC Driver 7.2 for SQL Server 
> version 7.2.1.0, and 3 tables were  created.
> 
> But this warning turns fatal
> WARN  12:21:51,120 | 
> org.apache.james.container.spring.context.JamesServerApplicationContext | 
> Exception encountered during context initialization - cancelling refresh 
> attempt: org.springframework.beans.factory.UnsatisfiedDependencyException: 
> Error creating bean with name 'authenticator' defined in class path resource 
> [META-INF/org/apache/james/spring-mailbox-authenticator.xml]: Unsatisfied 
> dependency expressed through constructor argument with index 0 of type 
> [org.apache.james.user.api.UsersRepository]: : Error creating bean with name 
> 'usersrepository': Injection of autowired dependencies failed; nested 
> exception is org.springframework.beans.factory.BeanCreationException: Could 
> not autowire method: public void 
> org.apache.james.user.lib.AbstractUsersRepository.setDomainList(org.apache.james.domainlist.api.DomainList);
>  nested exception is org.springframework.beans.factory.BeanCreationException: 
> Error creating bean with name 'domainlist': Initialization of bean failed; 
> nested exception is org.springframework.beans.FatalBeanException: Unable to 
> execute lifecycle method on beandomainlist; nested exception is 
>  
> org.apache.openjpa.persistence.PersistenceException: Incorrect syntax near 
> the keyword 'KEY'. {stmnt 1664030951 CREATE TABLE JAMES_MAILBOX_ANNOTATION 
> (KEY VARCHAR(200) NOT NULL, MAILBOX_ID BIGINT NOT NULL, VALUE VARCHAR(255), 
> PRIMARY KEY (KEY, MAILBOX_ID))} [code=156, state=S0001]; nested exception is 
> org.springframework.beans.factory.BeanCreationException: Error creating bean 
> with name 'usersrepository': Injection of autowired dependencies failed; 
> nested exception is org.springframework.beans.factory.BeanCreationException: 
> Could not autowire method: public void 
> org.apache.james.user.lib.AbstractUsersRepository.setDomainList(org.apache.james.domainlist.api.DomainList);
>  nested exception is org.springframework.beans.factory.BeanCreationException: 
> Error creating bean with name 'domainlist': Initialization of bean failed; 
> nested exception is org.springframework.beans.FatalBeanException: Unable to 
> execute lifecycle method on beandomainlist; nested exception is 
>  
> org.apache.openjpa.persistence.PersistenceException: Incorrect syntax near 
> the keyword 'KEY'. {stmnt 1664030951 CREATE TABLE JAMES_MAILBOX_ANNOTATION 
> (KEY VARCHAR(200) NOT NULL, MAILBOX_ID BIGINT NOT NULL, VALUE VARCHAR(255), 
> PRIMARY KEY (KEY, MAILBOX_ID))} [code=156, state=S0001]
> 
> I can't find anything on the web regarding how to modify sqlResources.xml to 
> work with MS SQL Server.
> 
> 
> Jeffrey Marans
> 
> Enterprise Architect Biometrics, Domestic Network
> Immigration, Refugees and Citizenship Canada / Government of Canada
> jeffrey.mar...@cic.gc.ca / Tel: 613-437-9890
> 
> Architecte de biométrie (Consultant), Solutions et gestion de l'information
> Immigration, Réfugiés et Citoyenneté Canada / Gouvernement du Canada
> jeffrey.mar...@cic.gc.ca / Tél.: 613-437-9890
> 

-
To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org
For additional commands, e-mail: server-user-h...@james.apache.org