Yes, much better :) [INFO] Apache James :: Server ............................ SUCCESS [36.652s] [INFO] Apache James :: Server :: Data :: API ............ SUCCESS [58.100s] [INFO] Apache James :: Server :: Lifecycle API ........... SUCCESS [9.845s] [INFO] Apache James :: Server :: Filesystem API .......... SUCCESS [28.043s] [INFO] Apache James :: Server :: Mailetcontainer API ..... SUCCESS [11.013s] [INFO] Apache James :: Server :: Common Utilities ........ SUCCESS [30.426s] [INFO] Apache James :: Server :: Protocols Library ....... SUCCESS [27.006s] [INFO] Apache James :: Server :: Core .................... SUCCESS [22.882s] [INFO] Apache James :: Server :: Container Spring ........ SUCCESS [1:03.995s] [INFO] Apache James :: Server :: Client .................. SUCCESS [31.717s] [INFO] Apache James :: Server :: DNS Service :: API ...... SUCCESS [11.958s] [INFO] Apache James :: Server :: DNS Service :: Library .. SUCCESS [12.659s] [INFO] Apache James :: Server :: Mail Queue :: API ....... SUCCESS [11.804s] [INFO] Apache James :: Server :: Mailetcontainer Camel ... SUCCESS [35.056s] [INFO] Apache James :: Server :: Mailbox Adapter ......... SUCCESS [21.262s] [INFO] Apache James :: Server :: DNS Service :: Implementation SUCCESS [11.802s] [INFO] Apache James :: Server :: Data :: Library ......... SUCCESS [21.232s] [INFO] Apache James :: Server :: Data :: LDAP Implementation SUCCESS [10.695s] [INFO] Apache James :: Server :: SMTP .................... SUCCESS [54.297s] [INFO] Apache James :: Server :: IMAP .................... SUCCESS [19.716s] [INFO] Apache James :: Server :: LMTP .................... SUCCESS [25.032s] [INFO] Apache James :: Server :: POP3 .................... SUCCESS [24.491s] [INFO] Apache James :: Server :: FetchMail ............... SUCCESS [15.891s] [INFO] Apache James :: Server :: Mail Queue :: File ...... SUCCESS [15.189s] [INFO] Apache James :: Server :: Mail Queue :: JMS ....... SUCCESS [26.472s] [INFO] Apache James :: Server :: Mail Queue :: ActiveMQ .. SUCCESS [25.252s] [INFO] Apache James :: Server :: Mailets ................. SUCCESS [54.790s] [INFO] Apache James :: Server :: Data :: File Persistence SUCCESS [26.919s] [INFO] Apache James :: Server :: Data :: JPA Persistence . SUCCESS [34.841s] [INFO] Apache James :: Server :: Data :: JDBC Persistence SUCCESS [20.827s] [INFO] Apache James :: Server :: Data :: HBase Persistence SUCCESS [1:21.442s] [INFO] Apache James :: Server :: Data :: JCR Persistence . SUCCESS [19.723s] [INFO] Apache James :: Server :: App ..................... SUCCESS [6:38.745s] [INFO] Apache James :: Karaf :: Features ................. SUCCESS [3.256s] [INFO] Apache James :: Karaf :: James Server ............. SUCCESS [2:39.625s] [INFO] Apache James :: Karaf :: Integration tests ........ SUCCESS [1:05.665s] [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 26:01.933s [INFO] Finished at: Mon Feb 02 11:46:00 CST 2015 [INFO] Final Memory: 72M/172M [INFO] ------------------------------------------------------------------------
There's a new Raspberry Pi with 1GB RAM and a faster CPU (for the same price), so I've got a better chance with that update... I'll continue deployment on this device until the v2 rPi shows up stateside (only available for purchase in the UK at the moment). -Chris -----Original Message----- From: Robert Munn [mailto:[email protected]] Sent: Monday, February 02, 2015 11:04 AM To: James Users List Subject: Re: Minimum Platform Requirements? There is a typo, try this: http://svn.apache.org/repos/asf/james/server/trunk/ On Feb 1, 2015, at 5:01 PM, Chris Means <[email protected]> wrote: > Robert, > > What's the correct/current URL to use for James? > > This is what is in your video (if I'm reading it right): > > http://svn.apache.org/respos/asf/james/server/trunk/ > > But, the page doesn't exist. > > -Chris > > -----Original Message----- > From: Chris Means [mailto:[email protected]] > Sent: Saturday, January 31, 2015 8:52 PM > To: 'James Users List' > Subject: RE: Minimum Platform Requirements? > > Great. Thanks! > > -----Original Message----- > From: Robert Munn [mailto:[email protected]] > Sent: Saturday, January 31, 2015 8:49 PM > To: James Users List > Subject: Re: Minimum Platform Requirements? > > Probably then your best course is to set up a test and see if James > can run with -Xmx=64m or -Xmx=128m, which is maybe the max you are > going to be able to dedicate to the application unless you have > stripped the OS install down to the bones. If you decide to give it a > try, please post your findings back to the list for others' benefit. > If you want to run James, I suggest building it from source. There is a post on my blog here: > > http://blog.bonnydoonmedia.com/post.cfm/video-building-apache-james-wi > th-ecl > ipse > > That links to the Youtube video instructions, and Bernd Waibel has > provided some written instructions for the build process, also linked > from my blog, > here: > > http://blog.bonnydoonmedia.com/post.cfm/walkthrough-tutorials-compilin > g-apac > he-james-v3-with-eclipse > > > > On Jan 31, 2015, at 6:25 PM, Chris Means <[email protected]> wrote: > >> Thanks Robert. >> >> I'm on an rPi kick at the moment, and want the flexibility to >> re-task/mix tasks for the devices, so keeping them all the same >> (core) will make it easier for me at the moment. >> >> I'm still learning my way around Linux, so keeping to Raspbian will >> also help. >> >> -Chris >> >> -----Original Message----- >> From: Robert Munn [mailto:[email protected]] >> Sent: Saturday, January 31, 2015 6:45 PM >> To: James Users List >> Subject: Re: Minimum Platform Requirements? >> >> I don't know about James v2 versus v 3, but in my experience 512 MB >> RAM would be a pretty minimal environment for any Java server app. >> >> If what you want is a small, low-power appliance-type device, have >> you considered an Atom-based SFF PC? You can pick up a used Asus >> eeeBox with HDD, 2GB RAM, and Windows 7 for not much more than a >> Raspberry Pi. I've been using one of them as an entertainment PC for >> a few years, they are small, quiet and consume very little power. >> Asus, Zotac, and many other brands offer these machines, and they are >> in good supply new or used. If you keep it on Windows, you can >> upgrade to 4GB > RAM for ~ $15. >> >> Robert >> >> >> >> On Jan 31, 2015, at 10:21 AM, Chris Means <[email protected]> wrote: >> >>> Hi, >>> >>> >>> >>> I'm a James User/Developer from many, many moons ago. >>> >>> >>> >>> I've been running James v2.2 w/MySQL on an old WinNT device that I'm >>> planning on decommissioning. My hope is that I can migrate to a >>> Raspberry Pi B+.I've not found much on this sort of deployment on >>> the > web. >>> >>> >>> >>> I only have a few users (5 - 10), so there's not a lot of traffic >>> (mostly Junk email). >>> >>> >>> >>> Is the rPi a reasonable platform? It only has 512MB RAM, which I >>> assume will be the primary constraint.though I also believe that >>> using MySQL will off-load some of the memory issues for James. >>> >>> >>> >>> Any thoughts? >>> >>> >>> >>> Should I aim for trying James v3, or go to what's stable in v2? >>> >>> >>> >>> Any migration issues for MySQL I should be aware of? >>> >>> >>> >>> Thanks. >>> >>> >>> >>> -Chris >>> >> >> >> --------------------------------------------------------------------- >> 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] > > > > > --------------------------------------------------------------------- > 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
