Administrator
|
Hi,
Just to let you know that the trunk demo crashed because it lacked memory after 12h- ------------------------------------------------------------------------------------------------------------------------------------------------------ # There is insufficient memory for the Java Runtime Environment to continue. # Native memory allocation (mmap) failed to map 20971520 bytes for committing reserved memory. # An error report file with more information is saved as: # /home/ofbizDemo/trunk/hs_err_pid31729.log Java HotSpot(TM) 64-Bit Server VM warning: INFO: os::commit_memory(0x00000000e146f000, 20971520, 0) failed; error='Cannot allocate memory' (errno=12) :ofbiz FAILED FAILURE: Build failed with an exception. * What went wrong: Execution failed for task ':ofbiz '. > Process 'command '/usr/lib/jvm/java-8-oracle/bin/java'' finished with non-zero exit value 1 Total time: 11 hrs 51 mins 32.598 secs ------------------------------------------------------------------------------------------------------------------------------------------------------ This did not happen before and could be due to now running stable (R16.11) and old (R13.07) which maybe need more memory than previously stable (R13.07) and old (R12.04) . We have only 4GB to run the 3 demos, if this happens again I'll ask infra to slightly increase the available memory The trunk demo is restarting... Jacques |
Administrator
|
Le 13/12/2016 à 17:34, Jacques Le Roux a écrit :
> Hi, > > Just to let you know that the trunk demo crashed because it lacked memory after 12h- > ------------------------------------------------------------------------------------------------------------------------------------------------------ > > # There is insufficient memory for the Java Runtime Environment to continue. > # Native memory allocation (mmap) failed to map 20971520 bytes for committing reserved memory. > # An error report file with more information is saved as: > # /home/ofbizDemo/trunk/hs_err_pid31729.log > Java HotSpot(TM) 64-Bit Server VM warning: INFO: os::commit_memory(0x00000000e146f000, 20971520, 0) failed; error='Cannot allocate memory' (errno=12) > :ofbiz FAILED > > FAILURE: Build failed with an exception. > > * What went wrong: > Execution failed for task ':ofbiz '. > > Process 'command '/usr/lib/jvm/java-8-oracle/bin/java'' finished with non-zero exit value 1 > > Total time: 11 hrs 51 mins 32.598 secs > ------------------------------------------------------------------------------------------------------------------------------------------------------ > > This did not happen before and could be due to now running stable (R16.11) and old (R13.07) which maybe need more memory than previously stable > (R13.07) and old (R12.04) . > We have only 4GB to run the 3 demos, if this happens again I'll ask infra to slightly increase the available memory Another possibility is to not use Gradle to deploy but plain Java Jacques > > The trunk demo is restarting... > > Jacques > > |
Is that a leak, or just not enough to begin with?
On 12/13/2016 01:49 PM, Jacques Le Roux wrote: > Le 13/12/2016 à 17:34, Jacques Le Roux a écrit : >> Hi, >> >> Just to let you know that the trunk demo crashed because it lacked >> memory after 12h- >> ------------------------------------------------------------------------------------------------------------------------------------------------------ >> >> >> # There is insufficient memory for the Java Runtime Environment to >> continue. >> # Native memory allocation (mmap) failed to map 20971520 bytes for >> committing reserved memory. >> # An error report file with more information is saved as: >> # /home/ofbizDemo/trunk/hs_err_pid31729.log >> Java HotSpot(TM) 64-Bit Server VM warning: INFO: >> os::commit_memory(0x00000000e146f000, 20971520, 0) failed; >> error='Cannot allocate memory' (errno=12) >> :ofbiz FAILED >> >> FAILURE: Build failed with an exception. >> >> * What went wrong: >> Execution failed for task ':ofbiz '. >> > Process 'command '/usr/lib/jvm/java-8-oracle/bin/java'' finished >> with non-zero exit value 1 >> >> Total time: 11 hrs 51 mins 32.598 secs >> ------------------------------------------------------------------------------------------------------------------------------------------------------ >> >> >> This did not happen before and could be due to now running stable >> (R16.11) and old (R13.07) which maybe need more memory than >> previously stable (R13.07) and old (R12.04) . >> We have only 4GB to run the 3 demos, if this happens again I'll ask >> infra to slightly increase the available memory > > Another possibility is to not use Gradle to deploy but plain Java > > Jacques > >> >> The trunk demo is restarting... >> >> Jacques >> >> > |
In reply to this post by Jacques Le Roux
Hi Jacques,
First, I don't think this discussion belongs in the user ML. Also guessing what might be the cause does not help. It could be a memory leak, a bug, a server setup error, or a hundred other things. Either way, this should be discussed in the dev ML, not here. On Tue, Dec 13, 2016 at 9:49 PM, Jacques Le Roux < [hidden email]> wrote: > Le 13/12/2016 à 17:34, Jacques Le Roux a écrit : > >> Hi, >> >> Just to let you know that the trunk demo crashed because it lacked memory >> after 12h- >> ------------------------------------------------------------ >> ------------------------------------------------------------ >> ------------------------------ >> >> # There is insufficient memory for the Java Runtime Environment to >> continue. >> # Native memory allocation (mmap) failed to map 20971520 bytes for >> committing reserved memory. >> # An error report file with more information is saved as: >> # /home/ofbizDemo/trunk/hs_err_pid31729.log >> Java HotSpot(TM) 64-Bit Server VM warning: INFO: >> os::commit_memory(0x00000000e146f000, 20971520, 0) failed; error='Cannot >> allocate memory' (errno=12) >> :ofbiz FAILED >> >> FAILURE: Build failed with an exception. >> >> * What went wrong: >> Execution failed for task ':ofbiz '. >> > Process 'command '/usr/lib/jvm/java-8-oracle/bin/java'' finished with >> non-zero exit value 1 >> >> Total time: 11 hrs 51 mins 32.598 secs >> ------------------------------------------------------------ >> ------------------------------------------------------------ >> ------------------------------ >> >> This did not happen before and could be due to now running stable >> (R16.11) and old (R13.07) which maybe need more memory than previously >> stable (R13.07) and old (R12.04) . >> We have only 4GB to run the 3 demos, if this happens again I'll ask infra >> to slightly increase the available memory >> > > Another possibility is to not use Gradle to deploy but plain Java > > Jacques > > > >> The trunk demo is restarting... >> >> Jacques >> >> >> > |
In reply to this post by Jacques Le Roux
As I have pointed out elsewhere: Gradle is a *build* solution. It is not
the tool to run in production environments. Best regards, Pierre Smits ORRTIZ.COM <http://www.orrtiz.com> OFBiz based solutions & services OFBiz Extensions Marketplace http://oem.ofbizci.net/oci-2/ On Tue, Dec 13, 2016 at 7:49 PM, Jacques Le Roux < [hidden email]> wrote: > Le 13/12/2016 à 17:34, Jacques Le Roux a écrit : > >> Hi, >> >> Just to let you know that the trunk demo crashed because it lacked memory >> after 12h- >> ------------------------------------------------------------ >> ------------------------------------------------------------ >> ------------------------------ >> >> # There is insufficient memory for the Java Runtime Environment to >> continue. >> # Native memory allocation (mmap) failed to map 20971520 bytes for >> committing reserved memory. >> # An error report file with more information is saved as: >> # /home/ofbizDemo/trunk/hs_err_pid31729.log >> Java HotSpot(TM) 64-Bit Server VM warning: INFO: >> os::commit_memory(0x00000000e146f000, 20971520, 0) failed; error='Cannot >> allocate memory' (errno=12) >> :ofbiz FAILED >> >> FAILURE: Build failed with an exception. >> >> * What went wrong: >> Execution failed for task ':ofbiz '. >> > Process 'command '/usr/lib/jvm/java-8-oracle/bin/java'' finished with >> non-zero exit value 1 >> >> Total time: 11 hrs 51 mins 32.598 secs >> ------------------------------------------------------------ >> ------------------------------------------------------------ >> ------------------------------ >> >> This did not happen before and could be due to now running stable >> (R16.11) and old (R13.07) which maybe need more memory than previously >> stable (R13.07) and old (R12.04) . >> We have only 4GB to run the 3 demos, if this happens again I'll ask infra >> to slightly increase the available memory >> > > Another possibility is to not use Gradle to deploy but plain Java > > Jacques > > > >> The trunk demo is restarting... >> >> Jacques >> >> >> > |
Administrator
|
In reply to this post by Craig Parker
Just not enough to continue after ~12h for a reason impossible to determine. I guess just not enough memory to run the 3 instances with the 2 Gradle
wrappers at this point. Jacques Le 13/12/2016 à 19:55, Craig Parker a écrit : > Is that a leak, or just not enough to begin with? > > > On 12/13/2016 01:49 PM, Jacques Le Roux wrote: >> Le 13/12/2016 à 17:34, Jacques Le Roux a écrit : >>> Hi, >>> >>> Just to let you know that the trunk demo crashed because it lacked memory after 12h- >>> ------------------------------------------------------------------------------------------------------------------------------------------------------ >>> >>> >>> # There is insufficient memory for the Java Runtime Environment to continue. >>> # Native memory allocation (mmap) failed to map 20971520 bytes for committing reserved memory. >>> # An error report file with more information is saved as: >>> # /home/ofbizDemo/trunk/hs_err_pid31729.log >>> Java HotSpot(TM) 64-Bit Server VM warning: INFO: os::commit_memory(0x00000000e146f000, 20971520, 0) failed; error='Cannot allocate memory' (errno=12) >>> :ofbiz FAILED >>> >>> FAILURE: Build failed with an exception. >>> >>> * What went wrong: >>> Execution failed for task ':ofbiz '. >>> > Process 'command '/usr/lib/jvm/java-8-oracle/bin/java'' finished with non-zero exit value 1 >>> >>> Total time: 11 hrs 51 mins 32.598 secs >>> ------------------------------------------------------------------------------------------------------------------------------------------------------ >>> >>> >>> This did not happen before and could be due to now running stable (R16.11) and old (R13.07) which maybe need more memory than previously stable >>> (R13.07) and old (R12.04) . >>> We have only 4GB to run the 3 demos, if this happens again I'll ask infra to slightly increase the available memory >> >> Another possibility is to not use Gradle to deploy but plain Java >> >> Jacques >> >>> >>> The trunk demo is restarting... >>> >>> Jacques >>> >>> >> > > |
Administrator
|
In reply to this post by taher
Hi Taher,
I don't see the need to discuss about this, I have expressed facts, that's all Jacques Le 13/12/2016 à 20:36, Taher Alkhateeb a écrit : > Hi Jacques, > > First, I don't think this discussion belongs in the user ML. Also guessing > what might be the cause does not help. It could be a memory leak, a bug, a > server setup error, or a hundred other things. Either way, this should be > discussed in the dev ML, not here. > > On Tue, Dec 13, 2016 at 9:49 PM, Jacques Le Roux < > [hidden email]> wrote: > >> Le 13/12/2016 à 17:34, Jacques Le Roux a écrit : >> >>> Hi, >>> >>> Just to let you know that the trunk demo crashed because it lacked memory >>> after 12h- >>> ------------------------------------------------------------ >>> ------------------------------------------------------------ >>> ------------------------------ >>> >>> # There is insufficient memory for the Java Runtime Environment to >>> continue. >>> # Native memory allocation (mmap) failed to map 20971520 bytes for >>> committing reserved memory. >>> # An error report file with more information is saved as: >>> # /home/ofbizDemo/trunk/hs_err_pid31729.log >>> Java HotSpot(TM) 64-Bit Server VM warning: INFO: >>> os::commit_memory(0x00000000e146f000, 20971520, 0) failed; error='Cannot >>> allocate memory' (errno=12) >>> :ofbiz FAILED >>> >>> FAILURE: Build failed with an exception. >>> >>> * What went wrong: >>> Execution failed for task ':ofbiz '. >>>> Process 'command '/usr/lib/jvm/java-8-oracle/bin/java'' finished with >>> non-zero exit value 1 >>> >>> Total time: 11 hrs 51 mins 32.598 secs >>> ------------------------------------------------------------ >>> ------------------------------------------------------------ >>> ------------------------------ >>> >>> This did not happen before and could be due to now running stable >>> (R16.11) and old (R13.07) which maybe need more memory than previously >>> stable (R13.07) and old (R12.04) . >>> We have only 4GB to run the 3 demos, if this happens again I'll ask infra >>> to slightly increase the available memory >>> >> Another possibility is to not use Gradle to deploy but plain Java >> >> Jacques >> >> >> >>> The trunk demo is restarting... >>> >>> Jacques >>> >>> >>> |
On Tue, Dec 13, 2016 at 9:43 PM, Jacques Le Roux <
[hidden email]> wrote: > Hi Taher, > > I don't see the need to discuss about this, I have expressed facts, that's > all > > Jacques but we need more facts to identify the core cause of the crash and fix it :-) I think that Craig asked the right question: if there was enough memory to start the instances and run them for 12 hours then the memory, under the same load, should be enough to run them forever. If on the other hand the memory usage slowly goes up then there is a memory leak or something else that needs to be fixed. Better move this conversation to the dev list where we can do a thorough analysis together. Jacopo |
In reply to this post by Pierre Smits
I'm a day late and a dollar short on this one maybe... Pierre, can you
explain this comment to a bit of a Java noob? I'm wondering about two terms you mention, but also if I'm doing something wrong by using gradle to get a working instance of OFBiz running for me to play with. ------------------------------------------------------------------------------- As I have pointed out elsewhere: Gradle is a *build* solution. It is not the tool to run in production environments. ------------------------------------------------------------------------------- I guess I don't know the difference between build solution and production environment. This may very well be beyond the scope of this mailing list. If it is, no problem, just point me in the direction of some education. I really want to get going on OFBiz and help with docs on the way. I'm really hoping that my experience will help some small business owner who would otherwise throw up his hands at what he's currently got to go on for docs. If gradle and ant are just "build solutions," then I guess I'm not sure how you'd fire this software up without either of them in a production environment. Jacques later commented: ------------------------------------------------------------------------------ Another possibility is to not use Gradle to deploy but plain Java Jacques ------------------------------------------------------------------------------ How? Is that outlined somewhere in a doc I've missed? Does using ant vs. gradle create the same thing (like a crew of Norwegians vs. a crew of Egyptians building a house from the same blueprint -- house ends up looking the same but the two work crews look, act, and sound radically different) or am I totally missing the mark? Any helpful, wise-cracking, get off this mailing list, or "derogatory noob" types of comments are most welcome. I work at a proprietary ERP company, and plan on picking one of the friendlier devs brains over the next couple of days. It will help at my job too, so it's technically ok... :) |
Administrator
|
Hi Craig,
This is explained here https://cwiki.apache.org/confluence/display/OFBIZ/Apache+OFBiz+Technical+Production+Setup+Guide#ApacheOFBizTechnicalProductionSetupGuide-RunningOFBiz Jacques Le 15/12/2016 à 03:53, Craig Parker a écrit : > I'm a day late and a dollar short on this one maybe... Pierre, can you explain this comment to a bit of a Java noob? I'm wondering about two terms > you mention, but also if I'm doing something wrong by using gradle to get a working instance of OFBiz running for me to play with. > > ------------------------------------------------------------------------------- > As I have pointed out elsewhere: Gradle is a *build* solution. It is not > the tool to run in production environments. > ------------------------------------------------------------------------------- > > I guess I don't know the difference between build solution and production environment. This may very well be beyond the scope of this mailing list. > If it is, no problem, just point me in the direction of some education. I really want to get going on OFBiz and help with docs on the way. I'm > really hoping that my experience will help some small business owner who would otherwise throw up his hands at what he's currently got to go on for > docs. > > If gradle and ant are just "build solutions," then I guess I'm not sure how you'd fire this software up without either of them in a production > environment. > > Jacques later commented: > > ------------------------------------------------------------------------------ > Another possibility is to not use Gradle to deploy but plain Java > > Jacques > ------------------------------------------------------------------------------ > > How? Is that outlined somewhere in a doc I've missed? > > Does using ant vs. gradle create the same thing (like a crew of Norwegians vs. a crew of Egyptians building a house from the same blueprint -- house > ends up looking the same but the two work crews look, act, and sound radically different) or am I totally missing the mark? > > Any helpful, wise-cracking, get off this mailing list, or "derogatory noob" types of comments are most welcome. I work at a proprietary ERP company, > and plan on picking one of the friendlier devs brains over the next couple of days. It will help at my job too, so it's technically ok... :) > > |
In reply to this post by Craig Parker
Hi Craig,
If you want to 'play', or experiment with OFBiz I would say: anything goes.... I like your analogy of the different crews building the house. Ant vs Gradle is like that. You could say that both achieve the same result, yet the one builds on the experience of the other. But it is one thing to build the house. It is another thing to live in the house. The same applies to playing vs working with OFBiz. When playing with you'll bound to accept more exceptions than when working with. Because different requirements exist or can be thought of. These requirements might be unknown when starting to play with, and may become clear when playing with. And when acknowledged will tighten the leeway for a production setup. Best regards, Pierre Smits ORRTIZ.COM <http://www.orrtiz.com> OFBiz based solutions & services OFBiz Extensions Marketplace http://oem.ofbizci.net/oci-2/ On Thu, Dec 15, 2016 at 3:53 AM, Craig Parker <[hidden email]> wrote: > I'm a day late and a dollar short on this one maybe... Pierre, can you > explain this comment to a bit of a Java noob? I'm wondering about two terms > you mention, but also if I'm doing something wrong by using gradle to get a > working instance of OFBiz running for me to play with. > > ------------------------------------------------------------ > ------------------- > As I have pointed out elsewhere: Gradle is a *build* solution. It is not > the tool to run in production environments. > ------------------------------------------------------------ > ------------------- > > I guess I don't know the difference between build solution and production > environment. This may very well be beyond the scope of this mailing list. > If it is, no problem, just point me in the direction of some education. I > really want to get going on OFBiz and help with docs on the way. I'm really > hoping that my experience will help some small business owner who would > otherwise throw up his hands at what he's currently got to go on for docs. > > If gradle and ant are just "build solutions," then I guess I'm not sure > how you'd fire this software up without either of them in a production > environment. > > Jacques later commented: > > ------------------------------------------------------------ > ------------------ > Another possibility is to not use Gradle to deploy but plain Java > > Jacques > ------------------------------------------------------------ > ------------------ > > How? Is that outlined somewhere in a doc I've missed? > > Does using ant vs. gradle create the same thing (like a crew of Norwegians > vs. a crew of Egyptians building a house from the same blueprint -- house > ends up looking the same but the two work crews look, act, and sound > radically different) or am I totally missing the mark? > > Any helpful, wise-cracking, get off this mailing list, or "derogatory > noob" types of comments are most welcome. I work at a proprietary ERP > company, and plan on picking one of the friendlier devs brains over the > next couple of days. It will help at my job too, so it's technically ok... > :) > > |
Free forum by Nabble | Edit this page |