[WG: Production / Deploying Sakai] The Switch to Java 1.6

Knoop, Peter knoop at umich.edu
Wed Mar 18 11:15:26 PDT 2009

Probably should've remembered to post this to the production list as well, if I want to hear about folks' production experiences :)


From: Knoop, Peter
Sent: Wednesday, March 18, 2009 12:32 PM
To: sakai-dev at collab.sakaiproject.org
Cc: Seth Theriault; Jones, Matthew
Subject: The Switch to Java 1.6

Thanks for bringing this up, Seth.  There are a number of things we'll have to sort out here for Sakai 2.5 and 2.6 maintenance releases, Sakai 2.7.0 and trunk, and Sakai 3.  I've created SAK-15874 to help track progress:


Both Sakai 2.5.x and Sakai 2.6.0 have only been QA'ed with 1.5 to-date.  At some point will need to transition to QA-ing on 1.6.  In the meantime, if anyone is building and running Sakai 2.5.x or Sakai 2.6.x with 1.6 in production, could you please comment on SAK-15874 about your experience?   It would be good to know that there are some early adopters in production having success before we take the plunge as a whole.

Maybe we could also get a quick show of hands via this email thread on:

*         Are you building your Sakai 2.5 or 2.6 instance using Java 1.6?

*         When did you start building with and which version of Java 1.6, or when do you plan to change to 1.6?

*         Are you running your Sakai 2.5 or 2.6 instance using Java 1.6?

*         When did you start running with and which version of Java 1.6, or when do you plan to change to 1.6?

We'll also need to move trunk/Sakai 2.7 to Java 1.6 at some point as well.  Any thoughts folks have on when it would be best to do this?  Perhaps sooner is better than later?

What do folks working on Sakai 3.0/Kernel 2 think?  Are the plans for the mid-year early adopters release to run on Java 1.5 or 1.6?



From: sakai-dev-bounces at collab.sakaiproject.org [mailto:sakai-dev-bounces at collab.sakaiproject.org] On Behalf Of Matthew Jones
Sent: Monday, March 16, 2009 7:36 PM
To: Seth Theriault
Cc: sakai-dev at collab.sakaiproject.org
Subject: Re: [Building Sakai] JDK 1.5 "end-of-service-life" date is October 30, 2009

Well, sakai 2.5.3 compiles all fine for me under java 1.6, and I've been running a sakai 1.5 compiled code our development server under a 1.6 JVM for the past 6 months with nothing out of the ordinary occurring. The benchmarks have 1.6 running a certain percentage faster on certain application (I think for me sakai was starting up a few seconds faster) and the big one was that it doesn't have the debugging where it can crash the server (under 1.5) which makes it much better for development. I haven't actively ran a 1.6 compiled sakai under a 1.6 jvm lately though.

I have been using that tomcat workaround mentioned in Steven's post through for the java_opt

This conversion to 1.6 was tracked here without too much activity: http://jira.sakaiproject.org/jira/browse/SAK-10716

I'll try to roll it out tomorrow and see how it looks, but it would probably be worth having a QA server eventually running 1.6/1.6 to see how it goes as the posts suggest.

I can volunteer one of the 2.5.x QA's if Pete wants.

On Mon, Mar 16, 2009 at 4:23 PM, Seth Theriault <slt at columbia.edu<mailto:slt at columbia.edu>> wrote:

I am not sure what the plans to move Sakai to Java 6 are, but
this statement is probably worth noting:

"J2SE 5.0 is in its Java Technology End of Life (EOL) transition
period. The EOL transition period began April 8th, 2008 and will
complete October 30th, 2009, when J2SE 5.0 will have reached its
End of Service Life (EOSL)."


More info at:



sakai-dev mailing list
sakai-dev at collab.sakaiproject.org<mailto:sakai-dev at collab.sakaiproject.org>

TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org<mailto:sakai-dev-unsubscribe at collab.sakaiproject.org> with a subject of "unsubscribe"

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/production/attachments/20090318/96b04766/attachment-0001.html 

More information about the production mailing list