Hi everyone,
I would like to bring to your attention some peculiar am experiencing with
Mifos on the cloud.
Zone Name Arch Instance Type AMI-ID
Asia Pacific (Singapore) Mifos 2.6.0 i386 ebs ami-7f4e0c2d
I managed to successfully launch the community AMI above: (
http://www.confluxtechnologies.com/1/post/2012/12/mifosamazonec2-ami-locator.html)
To initiate Mifos, I usually run the following jetty command available: *java
-Xms768M -Xmx768M -XX:MaxPermSize=256m -jar start.jar. *
these instructions are available at
http://www.confluxtechnologies.com/1/post/2013/01/setup-mifos-on-amazon-ec2.html
>From my observation the Mifos becomes accessible for while then gets
un-accessible. I have to run the above command again to make the mifos
application accessible.
What could be the reason for this??
How Can it be resolved???
Your swift reply will be highly appreciated.
------------------------------------------------------------------------------
WatchGuard Dimension instantly turns raw network data into actionable
security intelligence. It gives you real-time visual feedback on key
security issues and trends. Skip the complicated setup - simply import
a virtual appliance and go from zero to informed in seconds.
http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.clktrk
_______________________________________________
Mifos-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-users
