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?
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-when-running-in-docker-container Best regards Bernd Waibel -----Ursprüngliche Nachricht----- Von: li hai ming [mailto:haiming...@outlook.com] Gesendet: Freitag, 23. September 2016 05:58 An: 'server-user' <server-user@james.apache.org> Betreff: RE: james-cli failure Does anyone meet the same problem? any clue on the root cause and the solution? From: haiming li [mailto:haiming...@outlook.com] Sent: Thursday, September 22, 2016 12:25 To: 'server-user' <server-user@james.apache.org> 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: server-user-unsubscr...@james.apache.org For additional commands, e-mail: server-user-h...@james.apache.org