Thanks Bernd.
I re-started James, and got below memory info:
[lihaiming@iZ28m97ac83Z bin]$ free -mh
total used free shared buff/cache available
Mem: 991M 741M 106M 50M 143M 90M
Swap: 0B 0B 0B
Certainly no problem to run james-cli.
The I wondering who ate the memory from 106M ???
Btw: I have changed the startup parameter as
root 946 909 9 19:04 pts/4 00:00:19
/etc/alternatives/jre_1.8.0/bin/java -XX:+HeapDumpOnOutOfMemoryError -Xms128m
-Xmx256m …
发送自 Windows 10 版邮件应用
发件人: Bernd Waibel<mailto:[email protected]>
发送时间: 2016年9月23日 17:50
收件人: James Users List<mailto:[email protected]>
主题: AW: james-cli failure [unsigned]
Hi,
you have a total of 991 Mb with 790 Mb used.
So you have 69 Mb free, but James want to commit 89 Mb.
And you do not have a swap space.
It seems that your machine do not have enough memory, or other processes do use
the memory.
Best regards
Bernd Waibel
-----Ursprüngliche Nachricht-----
Von: li hai ming [mailto:[email protected]]
Gesendet: Freitag, 23. September 2016 10:20
An: 'James Users List' <[email protected]>
Betreff: RE: james-cli failure [unsigned]
Thanks.
When James is started, there is no problem to execute james-cli.
But after a while, below memory error occurs.
Someone is eating the memory?
Btw: i have java8 and use ./james/bin/run.sh&. (./james/james start does NOT
work on my server).
Pls also see below <<<.
[@iZ28m97ac83Z bin]$ free -mh
total used free shared buff/cache
available
Mem: 991M 790M 69M 50M 131M
48M
Swap: 0B 0B 0B
-----Original Message-----
From: Bernd Waibel [mailto:[email protected]]
Sent: Friday, September 23, 2016 15:24
To: James Users List <[email protected]>
Subject: AW: james-cli failure [unsigned]
Hi
no, never had seen this before.
I could only remember: we had a user who wanted to send a very large video
file via mail.
The video was too much for any mail server to be handled.
Most mail servers do have a limit of about 20 MB per mail.
Did James try to handle a large mail (89 MB) in this case of situation?
<<< no. we just started James and are doing some experimental by sending
small emails.
I think I could not help, but maybe recommend:
What surprised me is that 89 Megabyte should be committed.
How much memory do you have? (free -mh).
It could just be a memory problem (not having enough OS memory free).
You could read that:
http://stackoverflow.com/questions/27262629/jvm-cant-map-reserved-memory-whe
n-running-in-docker-container
Best regards
Bernd Waibel
-----Ursprüngliche Nachricht-----
Von: li hai ming [mailto:[email protected]]
Gesendet: Freitag, 23. September 2016 05:58
An: 'server-user' <[email protected]>
Betreff: RE: james-cli failure
Does anyone meet the same problem? any clue on the root cause and the
solution?
From: haiming li [mailto:[email protected]]
Sent: Thursday, September 22, 2016 12:25
To: 'server-user' <[email protected]>
Subject: james-cli failure
We have v3-beta4 up and running since yesterday. This morning I got below
error when trying to run james-cli.
[...]$ ./james-cli.sh -h localhost -p 9999 listdomains OpenJDK 64-Bit Server
VM warning: INFO: os::commit_memory(0x00000000eaaa0000, 89522176, 0) failed;
error='Cannot allocate memory' (errno=12) # # There is insufficient memory
for the Java Runtime Environment to continue.
# Native memory allocation (mmap) failed to map 89522176 bytes for
committing reserved memory.
# An error report file with more information is saved as:
# .../apache-james-3.0-beta4/bin/hs_err_pid21130.log
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
