[sakai2-tcc] 2.6.3 and Java 6

[Berg, Alan]

Cool Matthew beat me by a second:

Hi,

I have been running 2.6.x on Java 1.6 without issue since the start of testing. With the recommended Java_OPTS from 2.7 everything is going fine.

I do note the over obvious:

J2SE 5.0 reached its End of Service Life (EOSL) on November 3, 2009, which is the date of the final publicly available update of version 5.0 (J2SE 5.0 Update 22).

Therefore how long will organizations run 2.6.3 or above following our recommendations with a JVM that is way past end of life.



The top level pom.xml  amd also master/pom.xmldoes have a reporting stanza with a trivial link to 1.5 in the JavaDoc

<plugin>
<!-- javadocs -->
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-javadoc-plugin</artifactId>
−
<configuration>
<debug>true</debug>
−
<links>
<link>http://java.sun.com/j2se/1.5.0/docs/api/</link>
</links>
<breakiterator>true</breakiterator>
<verbose>false</verbose>
<aggregate>true</aggregate>
−
<!--
 allows javadocs builds to succeed
          <maxmemory>512m</maxmemory>
          <additionalJOption>-J-Xms168m -J-Xmx512m -J-XX:PermSize=128m -J-XX:NewSize=64m</additionalJOption>
          <version>2.3</version>
-->
</configuration>
</plugin>

 Further, I am actively looking for a QA lead for performance, to deal with these types of issues.  I have already contact with 2 well known figures on this subject.

Alan B

Alan Berg
QA Director - The Sakai Foundation

Senior Developer / Quality Assurance
Group Education and Research Services
Central Computer Services
University of Amsterdam

http://home.uva.nl/a.m.berg
________________________________
From: sakai2-tcc-bounces at collab.sakaiproject.org [sakai2-tcc-bounces at collab.sakaiproject.org] on behalf of Matthew Jones [jonespm at umich.edu]
Sent: 21 July 2010 17:23
To: csev
Cc: sakai2-tcc at collab.sakaiproject.org
Subject: Re: [sakai2-tcc] 2.6.3 and Java 6

I partially agree, but Java 5 has been end of life for over 8 months (as of today) and isn't *easily* available the latest OSX release. So these would be the biggest reasons, security fixes and easier availability, to recommend using a new version even on a minor, even if though need to use options.

However it should remain compilable with Java 5, at least until 2.8. (No new language features allowed)

I'd be interested in how many QA's and production instances are on Java 6. Currently University of Michigan is still running Sakai 2.6 on Java 5 because of some unresolved load test issues with Java 6. We hope to revisit these soon and ideally will be on Java 6 in the next few months.

On Wed, Jul 21, 2010 at 11:10 AM, csev <csev at umich.edu<mailto:csev at umich.edu>> wrote:
It would seem strange to change the JVM version in a minor release unless there is some strong issue.

If 2.6.0 recommended Java 1.5 - then absent some overriding concern, 2.6.3 should recommend 1.5 as well.

/Chuck

On Jul 21, 2010, at 7:32 AM, Anthony Whyte wrote:

> Shall we recommend deployers run 2.6.3 in a Java 6 SE JVM?  If so, I'll update the demo start up script in 2.6.x as well as the release notes.
>
> Cheers,
>
> Anth
>
>
> _______________________________________________
> sakai2-tcc mailing list
> sakai2-tcc at collab.sakaiproject.org<mailto:sakai2-tcc at collab.sakaiproject.org>
> http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc

_______________________________________________
sakai2-tcc mailing list
sakai2-tcc at collab.sakaiproject.org<mailto:sakai2-tcc at collab.sakaiproject.org>
http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai2-tcc/attachments/20100721/c40e69ee/attachment.html