[Building Sakai] Upgrade to James 2.3.1 (or latest)?

[Thomas Amsler]

I took a first stab at this a couple of months back. I got a working
pom.xml, whose dependencies changed significantly. If I remember
correctly, it start up but complains about some misconfigured section
in config.xml. I did this against 2.5.x. If someone is interested to
continue this work, I could provide the 2.5.x patch for the pom.xml
changes.
Best,
-- Thomas




On Tue, Mar 24, 2009 at 8:18 AM, Knoop, Peter <knoop at umich.edu> wrote:
> Is there anyone interested in looking further into upgrading James for trunk?  Is this something someone would like to take on for Sakai 2.7, and possibly for merging back to the 2.5.x and 2.6.x maintenance branches?
>
> -peter
> Sakai Project Coordinator
>
>
>> -----Original Message-----
>> From: sakai-dev-bounces at collab.sakaiproject.org [mailto:sakai-dev-
>> bounces at collab.sakaiproject.org] On Behalf Of Thomas Amsler
>> Sent: Tuesday, March 24, 2009 11:07 AM
>> To: Daniel Merino
>> Cc: sakai-dev
>> Subject: Re: [Building Sakai] James configuration
>>
>> We have the exact same problem and spent some time figuring out the
>> source of this issue.
>>
>> We simulated various load and usage scenarios but were never able to
>> reproduce this issue. By reading up on the Apache James email
>> archives, it's highly recommended to upgrade to the latest version
>> which is v2.3.1 and Sakai is using v2.1.3.
>>
>> Our current solution is that one node is handling all the mail. That
>> node doesn't allow any user connections so that we can restart that
>> sakai instance as soon as our monitoring script detects the "Maximum
>> number of open connections ..." problem.
>>
>> We have some of this documented here:
>> https://confluence.ucdavis.edu/confluence/x/KYC3
>>
>> Best,
>> -- Thomas
>>
>>
>>
>>
>> On Tue, Mar 24, 2009 at 4:42 AM, Daniel Merino
>> <daniel.merino at unavarra.es> wrote:
>> > Hi all.
>> >
>> > We have problems with James. Sometimes the mailarchive stops working
>> and it
>> > gives us the next error in the logs:
>> >
>> > 24/03/09 12:34:55 WARN  connections: Maximum number of open
>> connections
>> > exceeded - refusing connection.  Current number of connections is 30
>> >
>> > In the file
>> > /home/sinfo/sakai_2-5-3/mailarchive/mailarchive-
>> james/james/src/webapp/apps/james/SAR-INF/config.xml
>> > we have 30 connections allowed.
>> >
>> > <connections>
>> >       <idle-timeout>300000</idle-timeout>
>> >       <max-connections>30</max-connections>
>> >    </connections>
>> >
>> > We don't know if maybe this is a low value for the number of
>> connections or
>> > if James doesn't free properly these connections.
>> >
>> > Could somebody tell me how can we configurate correctly this
>> parameter?
>> > Thanks in advance.
>> > --
>> > Daniel Merino
>> > daniel.merino at unavarra.es
>> > Gestor de teleformación - Centro Superior de Innovación Educativa.
>> > Tfno: 948-168489 - Universidad Pública de Navarra.
>> > --
>> > Cualquier idiota puede decir la verdad, pero para mentir hace falta
>> tener
>> > imaginación. (Perich)
>> >
>> > _______________________________________________
>> > sakai-dev mailing list
>> > sakai-dev at collab.sakaiproject.org
>> > http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>> >
>> > TO UNSUBSCRIBE: send email to sakai-dev-
>> unsubscribe at collab.sakaiproject.org
>> > with a subject of "unsubscribe"
>> >
>> _______________________________________________
>> sakai-dev mailing list
>> sakai-dev at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>
>> TO UNSUBSCRIBE: send email to sakai-dev-
>> unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
>