From ohart@example.net Sat May 01 11:23:16 2010 Return-Path: <ohart@example.net> Delivered-To: ohart@example.net Received: (qmail 4114 invoked from network); 1 May 2010 11:23:16 -0000 Received: from unknown (HELO mail.apache.org) (83.161.120.155) by 83.161.120.155 with SMTP; 1 May 2010 11:23:16 -0000 Received: (qmail 87496 invoked by uid 500); 1 May 2010 11:23:16 -0000 Delivered-To: ohart@example.net Received: (qmail 87482 invoked by uid 500); 1 May 2010 11:23:15 -0000 Mailing-List: contact ohart@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:ohart@example.net> List-Unsubscribe: <mailto:ohart@example.net> List-Post: <mailto:ohart@example.net> List-Id: <dev.uima.apache.org> Reply-To: ohart@example.net Delivered-To: mailing list ohart@example.net Received: (qmail 87474 invoked by uid 99); 1 May 2010 11:23:15 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 01 May 2010 11:23:15 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO thor.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 01 May 2010 11:23:14 +0000 Received: from thor (localhost [83.161.120.155]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o41BMrwj027065 for <ohart@example.net>; Sat, 1 May 2010 11:22:53 GMT Message-ID: <19675049.49651272712973387.JavaMail.jira@thor> Date: Sat, 1 May 2010 07:22:53 -0400 (EDT) From: "Marshall Schor (JIRA)" <ohart@example.net> To: ohart@example.net Subject: [jira] Created: (UIMA-1775) TLP Graduation incubator tidying up MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 TLP Graduation incubator tidying up ----------------------------------- Key: UIMA-1775 URL: https://issues.apache.org/jira/browse/UIMA-1775 Project: UIMA Issue Type: Improvement Reporter: Marshall Schor Assignee: Marshall Schor Priority: Minor * Remove from incubator reporting schedule - already done (by Jukka Zitting 4/2010) * Update Projects in Incubation table - move to graduated * Remove entry from right side panel on incubator website * Tidy the project status page * After release as non-incubator, removing current incubator releases (will still be available in archive) and updating uima download page to reflect this. * Verifying that confluence commit msgs are going to the right mailing list (ohart@example.net) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. From ohart@example.net Sun May 02 20:10:17 2010 Return-Path: <ohart@example.net> Delivered-To: ohart@example.net Received: (qmail 83751 invoked from network); 2 May 2010 20:10:17 -0000 Received: from unknown (HELO mail.apache.org) (83.161.120.155) by 83.161.120.155 with SMTP; 2 May 2010 20:10:17 -0000 Received: (qmail 72941 invoked by uid 500); 2 May 2010 20:10:17 -0000 Delivered-To: ohart@example.net Received: (qmail 72895 invoked by uid 500); 2 May 2010 20:10:16 -0000 Mailing-List: contact ohart@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:ohart@example.net> List-Unsubscribe: <mailto:ohart@example.net> List-Post: <mailto:ohart@example.net> List-Id: <dev.uima.apache.org> Reply-To: ohart@example.net Delivered-To: mailing list ohart@example.net Received: (qmail 72887 invoked by uid 99); 2 May 2010 20:10:16 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 02 May 2010 20:10:16 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO thor.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 02 May 2010 20:10:15 +0000 Received: from thor (localhost [83.161.120.155]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o42K9twW021746 for <ohart@example.net>; Sun, 2 May 2010 20:09:55 GMT Message-ID: <21962549.7841272830995203.JavaMail.jira@thor> Date: Sun, 2 May 2010 16:09:55 -0400 (EDT) From: "Marshall Schor (JIRA)" <ohart@example.net> To: ohart@example.net Subject: [jira] Created: (UIMA-1776) broken / bad links for docbook-generated sandbox docs, and PearPackagingMavenPlugin on website MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 broken / bad links for docbook-generated sandbox docs, and PearPackagingMavenPlugin on website ---------------------------------------------------------------------------------------------- Key: UIMA-1776 URL: https://issues.apache.org/jira/browse/UIMA-1776 Project: UIMA Issue Type: Improvement Components: Website Affects Versions: 2.3 Reporter: Marshall Schor The links need to be updated for 2.3.0. The PearPackagingMavenPlugin doc was moved into the main tools doc, but the link on the website points to the 2.2.2 version of the tools doc, which doesn't have the content. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. From ohart@example.net Sun May 02 20:12:32 2010 Return-Path: <ohart@example.net> Delivered-To: ohart@example.net Received: (qmail 83923 invoked from network); 2 May 2010 20:12:32 -0000 Received: from unknown (HELO mail.apache.org) (83.161.120.155) by 83.161.120.155 with SMTP; 2 May 2010 20:12:32 -0000 Received: (qmail 75189 invoked by uid 500); 2 May 2010 20:12:32 -0000 Delivered-To: ohart@example.net Received: (qmail 75173 invoked by uid 500); 2 May 2010 20:12:32 -0000 Mailing-List: contact ohart@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:ohart@example.net> List-Unsubscribe: <mailto:ohart@example.net> List-Post: <mailto:ohart@example.net> List-Id: <dev.uima.apache.org> Reply-To: ohart@example.net Delivered-To: mailing list ohart@example.net Received: (qmail 75165 invoked by uid 99); 2 May 2010 20:12:32 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 02 May 2010 20:12:32 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO thor.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 02 May 2010 20:12:30 +0000 Received: from thor (localhost [83.161.120.155]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o42KC8R9021752 for <ohart@example.net>; Sun, 2 May 2010 20:12:08 GMT Message-ID: <1848865.7861272831128175.JavaMail.jira@thor> Date: Sun, 2 May 2010 16:12:08 -0400 (EDT) From: "Marshall Schor (JIRA)" <ohart@example.net> To: ohart@example.net Subject: [jira] Created: (UIMA-1777) generate conventional documentation for PearPackagingMavenPlugin MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org generate conventional documentation for PearPackagingMavenPlugin ---------------------------------------------------------------- Key: UIMA-1777 URL: https://issues.apache.org/jira/browse/UIMA-1777 Project: UIMA Issue Type: Improvement Components: Sandbox-PearPackagingMavenPlugin Reporter: Marshall Schor Priority: Minor The community of users of Maven plugins are used to seeing a standard organization of documentation for the plugin. Update this documentation to follow that convention. Also see about getting this plugin added to the maven plugin lists in the maven project -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. From ohart@example.net Mon May 03 03:01:14 2010 Return-Path: <ohart@example.net> Delivered-To: ohart@example.net Received: (qmail 46853 invoked from network); 3 May 2010 03:01:13 -0000 Received: from unknown (HELO mail.apache.org) (83.161.120.155) by 83.161.120.155 with SMTP; 3 May 2010 03:01:13 -0000 Received: (qmail 23989 invoked by uid 500); 3 May 2010 03:01:13 -0000 Delivered-To: ohart@example.net Received: (qmail 23942 invoked by uid 500); 3 May 2010 03:01:13 -0000 Mailing-List: contact ohart@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:ohart@example.net> List-Unsubscribe: <mailto:ohart@example.net> List-Post: <mailto:ohart@example.net> List-Id: <dev.uima.apache.org> Reply-To: ohart@example.net Delivered-To: mailing list ohart@example.net Received: (qmail 23934 invoked by uid 99); 3 May 2010 03:01:12 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 May 2010 03:01:12 +0000 X-ASF-Spam-Status: No, hits=-0.5 required=10.0 tests=AWL,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of ohart@example.net designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO gateway15.websitewelcome.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with SMTP; Mon, 03 May 2010 03:01:04 +0000 Received: (qmail 22366 invoked from network); 3 May 2010 03:03:52 -0000 Received: from gator74.hostgator.com (83.161.120.155) by gateway15.websitewelcome.com with SMTP; 3 May 2010 03:03:52 -0000 Received: from ool-44c6c63b.dyn.optonline.net ([83.161.120.155]:56237 helo=[83.161.120.155]) by gator74.hostgator.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <ohart@example.net>) id 1O8ltd-0004LB-Ii for ohart@example.net; Sun, 02 May 2010 22:00:37 -0500 Message-ID: <ohart@example.net> Date: Sun, 02 May 2010 23:00:46 -0400 From: Marshall Schor <ohart@example.net> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:83.161.120.155) Gecko/20100317 Thunderbird/3.0.4 MIME-Version: 1.0 To: ohart@example.net Subject: Re: Apache site updates for UIMA References: <ohart@example.net> In-Reply-To: <ohart@example.net> X-Enigmail-Version: 1.0.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - gator74.hostgator.com X-AntiAbuse: Original Domain - uima.apache.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - schor.com UIMA now shows as one of the top level Apache projects on the apache pages. The DOAP file info was resubmitted after 3 minor problems were discovered, and the fixed version was successful in creating the UIMA entry at http://projects.apache.org If you see any problems with the DOAP entry, please feel free to improve it - it's in SVN here: http://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/doap/uima.rdf -Marshall Schor On 4/30/2010 6:14 PM, Marshall Schor wrote: > I've submitted a patch to infrastructure to update the top level Apache > sites so they show Apache UIMA as a top level project. > > I've also made and submitted a DOAP file for UIMA so our project will > show up on projects.apache.org. > > -Marshall > > > From ohart@example.net Mon May 03 08:17:18 2010 Return-Path: <ohart@example.net> Delivered-To: ohart@example.net Received: (qmail 94637 invoked from network); 3 May 2010 08:17:18 -0000 Received: from unknown (HELO mail.apache.org) (83.161.120.155) by 83.161.120.155 with SMTP; 3 May 2010 08:17:18 -0000 Received: (qmail 66594 invoked by uid 500); 3 May 2010 08:17:18 -0000 Delivered-To: ohart@example.net Received: (qmail 66544 invoked by uid 500); 3 May 2010 08:17:18 -0000 Mailing-List: contact ohart@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:ohart@example.net> List-Unsubscribe: <mailto:ohart@example.net> List-Post: <mailto:ohart@example.net> List-Id: <dev.uima.apache.org> Reply-To: ohart@example.net Delivered-To: mailing list ohart@example.net Received: (qmail 66536 invoked by uid 99); 3 May 2010 08:17:17 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 May 2010 08:17:17 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO thor.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 May 2010 08:17:16 +0000 Received: from thor (localhost [83.161.120.155]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o438GtHE024698 for <ohart@example.net>; Mon, 3 May 2010 08:16:55 GMT Message-ID: <10382514.10831272874615818.JavaMail.jira@thor> Date: Mon, 3 May 2010 04:16:55 -0400 (EDT) From: =?utf-8?Q?J=C3=B6rn_Kottmann_=28JIRA=29?= <ohart@example.net> To: ohart@example.net Subject: [jira] Commented: (UIMA-1726) Long GC causes UIMA AS service to loose broker connection and marks the client as dead MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/UIMA-1726?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D12863= 262#action_12863262 ]=20 J=C3=B6rn Kottmann commented on UIMA-1726: ------------------------------------- The warning is now longer logged in our test system after the update to rev= ision 937028. > Long GC causes UIMA AS service to loose broker connection and marks the c= lient as dead > -------------------------------------------------------------------------= ------------- > > Key: UIMA-1726 > URL: https://issues.apache.org/jira/browse/UIMA-1726 > Project: UIMA > Issue Type: Bug > Components: Async Scaleout > Reporter: Jerry Cwiklik > Assignee: Jerry Cwiklik > Fix For: 2.3AS > > > When the JVMs GC takes a long time, the UIMA AS fails to validate the bro= ker connection and proceeds to close it as if the broker died. It seems tha= t the long GC freezes the jvm and prevents the low level socket pinging to = work correctly. This pinging is a mechanism by which the low level AMQ code= relies upon to detect a broker failure. In this case, the broker is actual= ly fine. The side effect of the above is that the UIMA AS service falsely a= dds the client to the DoNotProcess list. This is an optimization that was r= ecently added that prevents wasting processing cycles while handling CASes = that are known to have come from clients that had gone away. Each CAS origi= n is checked against that list and if there is a match the CAS is thrown aw= ay. It seems that we need a better mechanism to detect broker failure. =20 --=20 This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. From ohart@example.net Mon May 03 08:23:22 2010 Return-Path: <ohart@example.net> Delivered-To: ohart@example.net Received: (qmail 95736 invoked from network); 3 May 2010 08:23:22 -0000 Received: from unknown (HELO mail.apache.org) (83.161.120.155) by 83.161.120.155 with SMTP; 3 May 2010 08:23:22 -0000 Received: (qmail 69835 invoked by uid 500); 3 May 2010 08:23:22 -0000 Delivered-To: ohart@example.net Received: (qmail 69719 invoked by uid 500); 3 May 2010 08:23:22 -0000 Mailing-List: contact ohart@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:ohart@example.net> List-Unsubscribe: <mailto:ohart@example.net> List-Post: <mailto:ohart@example.net> List-Id: <dev.uima.apache.org> Reply-To: ohart@example.net Delivered-To: mailing list ohart@example.net Received: (qmail 69707 invoked by uid 99); 3 May 2010 08:23:21 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 May 2010 08:23:21 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO thor.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 May 2010 08:23:19 +0000 Received: from thor (localhost [83.161.120.155]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o438MviD024737 for <ohart@example.net>; Mon, 3 May 2010 08:22:57 GMT Message-ID: <30488662.10911272874977812.JavaMail.jira@thor> Date: Mon, 3 May 2010 04:22:57 -0400 (EDT) From: =?utf-8?Q?J=C3=B6rn_Kottmann_=28JIRA=29?= <ohart@example.net> To: ohart@example.net Subject: [jira] Commented: (UIMA-1658) UIMA AS worker does not respond to client initialize after failover MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/UIMA-1658?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D12863= 264#action_12863264 ]=20 J=C3=B6rn Kottmann commented on UIMA-1658: ------------------------------------- It seems that the same happens when the network connection to the broker is= lost for a short period of time e.g. through network maintenance. In this = case the services should just try to reconnect until the broker can be reac= hed again. > UIMA AS worker does not respond to client initialize after failover > ------------------------------------------------------------------- > > Key: UIMA-1658 > URL: https://issues.apache.org/jira/browse/UIMA-1658 > Project: UIMA > Issue Type: Bug > Components: Async Scaleout > Affects Versions: 2.3AS > Environment: Ubuntu 8.10 Server, Java 1.6 and ActiveMQ 5.3.0 > Reporter: J=C3=B6rn Kottmann > > A Pure Master Slave Broker is used to increase availability of the broker= .=20 > More information about it can be found in the activemq documentation: > http://activemq.apache.org/pure-master-slave.html=20 > In a test we simulated Master failure through killing the process with ki= ll -9. > Here is the log output from the worker node: > INFO FailoverTransport - Successfully connected to tcp://XX= X1:61616 > Here I stopped the master broker process with kill -9=20 > WARN FailoverTransport - Transport failed to tcp://XXX1:616= 16 , attempting to automatically reconnect due to: java.io.EOFException > WARN FailoverTransport - Transport failed to tcp://XXX1:616= 16 , attempting to automatically reconnect due to: java.io.EOFException > WARN FailoverTransport - Transport failed to tcp://XXX1:616= 16 , attempting to automatically reconnect due to: java.io.EOFException > INFO FailoverTransport - Successfully reconnected to tcp://= XXX2:61616 > INFO FailoverTransport - Successfully reconnected to tcp://= XXX2:61616 > INFO FailoverTransport - Successfully reconnected to tcp://= XXX2:61616=20 > Afterwards the client was restarted but got a time out error during initi= alize. > During initializes it sends a message to the worker nodes input queue, bu= t this > message if never retrieved. > I used the activemq web interface to get some information about the messa= ge: > Command 2001 > MessageFrom ID:XXXX-51032-1257865414664-0:1:1 > ServerURI failover:(tcp://XXX1:61616,tcp://XXX2:61616)?randomize=3Dfa= lse > MessageType 3000=20 --=20 This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. From ohart@example.net Mon May 03 08:23:23 2010 Return-Path: <ohart@example.net> Delivered-To: ohart@example.net Received: (qmail 95753 invoked from network); 3 May 2010 08:23:22 -0000 Received: from unknown (HELO mail.apache.org) (83.161.120.155) by 83.161.120.155 with SMTP; 3 May 2010 08:23:22 -0000 Received: (qmail 69905 invoked by uid 500); 3 May 2010 08:23:22 -0000 Delivered-To: ohart@example.net Received: (qmail 69763 invoked by uid 500); 3 May 2010 08:23:22 -0000 Mailing-List: contact ohart@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:ohart@example.net> List-Unsubscribe: <mailto:ohart@example.net> List-Post: <mailto:ohart@example.net> List-Id: <dev.uima.apache.org> Reply-To: ohart@example.net Delivered-To: mailing list ohart@example.net Received: (qmail 69718 invoked by uid 99); 3 May 2010 08:23:22 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 May 2010 08:23:22 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO thor.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 May 2010 08:23:19 +0000 Received: from thor (localhost [83.161.120.155]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o438Mw7d024743 for <ohart@example.net>; Mon, 3 May 2010 08:22:58 GMT Message-ID: <4958849.10931272874978476.JavaMail.jira@thor> Date: Mon, 3 May 2010 04:22:58 -0400 (EDT) From: =?utf-8?Q?J=C3=B6rn_Kottmann_=28JIRA=29?= <ohart@example.net> To: ohart@example.net Subject: [jira] Issue Comment Edited: (UIMA-1726) Long GC causes UIMA AS service to loose broker connection and marks the client as dead MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/UIMA-1726?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D12863= 262#action_12863262 ]=20 J=C3=B6rn Kottmann edited comment on UIMA-1726 at 5/3/10 4:22 AM: ------------------------------------------------------------- The warning is no longer logged in our test system after the update to revi= sion 937028. was (Author: joern): The warning is now longer logged in our test system after the update to= revision 937028. =20 > Long GC causes UIMA AS service to loose broker connection and marks the c= lient as dead > -------------------------------------------------------------------------= ------------- > > Key: UIMA-1726 > URL: https://issues.apache.org/jira/browse/UIMA-1726 > Project: UIMA > Issue Type: Bug > Components: Async Scaleout > Reporter: Jerry Cwiklik > Assignee: Jerry Cwiklik > Fix For: 2.3AS > > > When the JVMs GC takes a long time, the UIMA AS fails to validate the bro= ker connection and proceeds to close it as if the broker died. It seems tha= t the long GC freezes the jvm and prevents the low level socket pinging to = work correctly. This pinging is a mechanism by which the low level AMQ code= relies upon to detect a broker failure. In this case, the broker is actual= ly fine. The side effect of the above is that the UIMA AS service falsely a= dds the client to the DoNotProcess list. This is an optimization that was r= ecently added that prevents wasting processing cycles while handling CASes = that are known to have come from clients that had gone away. Each CAS origi= n is checked against that list and if there is a match the CAS is thrown aw= ay. It seems that we need a better mechanism to detect broker failure. =20 --=20 This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. From ohart@example.net Mon May 03 09:58:20 2010 Return-Path: <ohart@example.net> Delivered-To: ohart@example.net Received: (qmail 8580 invoked from network); 3 May 2010 09:58:20 -0000 Received: from unknown (HELO mail.apache.org) (83.161.120.155) by 83.161.120.155 with SMTP; 3 May 2010 09:58:20 -0000 Received: (qmail 45776 invoked by uid 500); 3 May 2010 09:58:20 -0000 Delivered-To: ohart@example.net Received: (qmail 45674 invoked by uid 500); 3 May 2010 09:58:20 -0000 Mailing-List: contact ohart@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:ohart@example.net> List-Unsubscribe: <mailto:ohart@example.net> List-Post: <mailto:ohart@example.net> List-Id: <dev.uima.apache.org> Reply-To: ohart@example.net Delivered-To: mailing list ohart@example.net Received: (qmail 45666 invoked by uid 99); 3 May 2010 09:58:19 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 May 2010 09:58:19 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO thor.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 May 2010 09:58:17 +0000 Received: from thor (localhost [83.161.120.155]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o439vth0025419 for <ohart@example.net>; Mon, 3 May 2010 09:57:55 GMT Message-ID: <30511100.11831272880675700.JavaMail.jira@thor> Date: Mon, 3 May 2010 05:57:55 -0400 (EDT) From: =?utf-8?Q?J=C3=B6rn_Kottmann_=28JIRA=29?= <ohart@example.net> To: ohart@example.net Subject: [jira] Commented: (UIMA-1766) Fix Memory Leak in UIMA AS Service MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/UIMA-1766?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D12863= 290#action_12863290 ]=20 J=C3=B6rn Kottmann commented on UIMA-1766: ------------------------------------- The problem described in the last comment is actually linked to UIMA-1726 a= nd not to this issue. > Fix Memory Leak in UIMA AS Service > ---------------------------------- > > Key: UIMA-1766 > URL: https://issues.apache.org/jira/browse/UIMA-1766 > Project: UIMA > Issue Type: Bug > Components: Async Scaleout > Affects Versions: 2.3AS > Reporter: Jerry Cwiklik > Assignee: Jerry Cwiklik > > When running an Aggregate with a colocated Cas Multiplier per CAS statist= ics are not being removed from a Map maintained by the Cas Multiplier servi= ce. As more CASes are sent to the CM, instances of ServicePerformance objec= t are added to the Map and never removed leading to a memory leak and event= ual OOM error.=20 --=20 This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. From ohart@example.net Mon May 03 10:04:17 2010 Return-Path: <ohart@example.net> Delivered-To: ohart@example.net Received: (qmail 9666 invoked from network); 3 May 2010 10:04:17 -0000 Received: from unknown (HELO mail.apache.org) (83.161.120.155) by 83.161.120.155 with SMTP; 3 May 2010 10:04:17 -0000 Received: (qmail 51149 invoked by uid 500); 3 May 2010 10:04:17 -0000 Delivered-To: ohart@example.net Received: (qmail 51048 invoked by uid 500); 3 May 2010 10:04:17 -0000 Mailing-List: contact ohart@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:ohart@example.net> List-Unsubscribe: <mailto:ohart@example.net> List-Post: <mailto:ohart@example.net> List-Id: <dev.uima.apache.org> Reply-To: ohart@example.net Delivered-To: mailing list ohart@example.net Received: (qmail 50870 invoked by uid 99); 3 May 2010 10:04:17 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 May 2010 10:04:17 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO thor.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 May 2010 10:04:16 +0000 Received: from thor (localhost [83.161.120.155]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o43A3tJV025483 for <ohart@example.net>; Mon, 3 May 2010 10:03:55 GMT Message-ID: <1601350.11931272881035762.JavaMail.jira@thor> Date: Mon, 3 May 2010 06:03:55 -0400 (EDT) From: =?utf-8?Q?J=C3=B6rn_Kottmann_=28JIRA=29?= <ohart@example.net> To: ohart@example.net Subject: [jira] Commented: (UIMA-1766) Fix Memory Leak in UIMA AS Service MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/UIMA-1766?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D12863= 293#action_12863293 ]=20 J=C3=B6rn Kottmann commented on UIMA-1766: ------------------------------------- It seems that now all memory leaks are fixed, the memory consumption did no= t increase after processing 350K CASes in our test system with the latest r= evision.=20 > Fix Memory Leak in UIMA AS Service > ---------------------------------- > > Key: UIMA-1766 > URL: https://issues.apache.org/jira/browse/UIMA-1766 > Project: UIMA > Issue Type: Bug > Components: Async Scaleout > Affects Versions: 2.3AS > Reporter: Jerry Cwiklik > Assignee: Jerry Cwiklik > > When running an Aggregate with a colocated Cas Multiplier per CAS statist= ics are not being removed from a Map maintained by the Cas Multiplier servi= ce. As more CASes are sent to the CM, instances of ServicePerformance objec= t are added to the Map and never removed leading to a memory leak and event= ual OOM error.=20 --=20 This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. From ohart@example.net Mon May 03 14:47:50 2010 Return-Path: <ohart@example.net> Delivered-To: ohart@example.net Received: (qmail 71537 invoked from network); 3 May 2010 14:47:50 -0000 Received: from unknown (HELO mail.apache.org) (83.161.120.155) by 83.161.120.155 with SMTP; 3 May 2010 14:47:50 -0000 Received: (qmail 15970 invoked by uid 500); 3 May 2010 14:47:50 -0000 Delivered-To: ohart@example.net Received: (qmail 15914 invoked by uid 500); 3 May 2010 14:47:49 -0000 Mailing-List: contact ohart@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:ohart@example.net> List-Unsubscribe: <mailto:ohart@example.net> List-Post: <mailto:ohart@example.net> List-Id: <dev.uima.apache.org> Reply-To: ohart@example.net Delivered-To: mailing list ohart@example.net Received: (qmail 15894 invoked by uid 99); 3 May 2010 14:47:49 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 May 2010 14:47:49 +0000 X-ASF-Spam-Status: No, hits=-0.6 required=10.0 tests=AWL,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of ohart@example.net designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO gateway16.websitewelcome.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with SMTP; Mon, 03 May 2010 14:47:42 +0000 Received: (qmail 24603 invoked from network); 3 May 2010 14:50:30 -0000 Received: from gator74.hostgator.com (83.161.120.155) by gateway16.websitewelcome.com with SMTP; 3 May 2010 14:50:30 -0000 Received: from yktgi01e0-s5.watson.ibm.com ([83.161.120.155]:7814 helo=[83.161.120.155]) by gator74.hostgator.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <ohart@example.net>) id 1O8wvQ-0000Wa-7B for ohart@example.net; Mon, 03 May 2010 09:47:12 -0500 Message-ID: <ohart@example.net> Date: Mon, 03 May 2010 10:47:19 -0400 From: Marshall Schor <ohart@example.net> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:83.161.120.155) Gecko/20100317 Thunderbird/3.0.4 MIME-Version: 1.0 To: uima-dev <ohart@example.net> Subject: eclipse plugin version names with dash X-Enigmail-Version: 1.0.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - gator74.hostgator.com X-AntiAbuse: Original Domain - uima.apache.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - schor.com For our builds, we have been doing extra stuff to have 2 kinds of versions: Maven conventions: 2.3.1-SNAPSHOT and Eclipse plugin conventions: 2.3.1.SNAPSHOT Eclipse appears to have been updated to allow the dash: see https://bugs.eclipse.org/bugs/show_bug.cgi?id=197503 So I'll presume this works and as part of my maven alignment work, remove the special treatment of versions for eclipse & osgi plugins, going forward. -Marshall From ohart@example.net Mon May 03 14:59:28 2010 Return-Path: <ohart@example.net> Delivered-To: ohart@example.net Received: (qmail 74562 invoked from network); 3 May 2010 14:59:28 -0000 Received: from unknown (HELO mail.apache.org) (83.161.120.155) by 83.161.120.155 with SMTP; 3 May 2010 14:59:28 -0000 Received: (qmail 33425 invoked by uid 500); 3 May 2010 14:59:28 -0000 Delivered-To: ohart@example.net Received: (qmail 33364 invoked by uid 500); 3 May 2010 14:59:28 -0000 Mailing-List: contact ohart@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:ohart@example.net> List-Unsubscribe: <mailto:ohart@example.net> List-Post: <mailto:ohart@example.net> List-Id: <dev.uima.apache.org> Reply-To: ohart@example.net Delivered-To: mailing list ohart@example.net Received: (qmail 33356 invoked by uid 99); 3 May 2010 14:59:28 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 May 2010 14:59:28 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of ohart@example.net designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO mail.gmx.net) (83.161.120.155) by apache.org (qpsmtpd/0.29) with SMTP; Mon, 03 May 2010 14:59:20 +0000 Received: (qmail invoked by alias); 03 May 2010 14:58:58 -0000 Received: from deibp9eh1--blueice3n1.emea.ibm.com (EHLO [83.161.120.155]) [83.161.120.155] by mail.gmx.net (mp022) with SMTP; 03 May 2010 16:58:58 +0200 X-Authenticated: #25330878 X-Provags-ID: V01U2FsdGVkX194+hE0uZF4psNJXpv1ZbPtSQAG4JyNSBjPBlTAyK IEkWgFK3+fUd0s Message-ID: <ohart@example.net> Date: Mon, 03 May 2010 16:59:03 +0200 From: Thilo Goetz <ohart@example.net> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:83.161.120.155) Gecko/20100317 Lightning/1.0b1 Thunderbird/3.0.4 MIME-Version: 1.0 To: ohart@example.net Subject: Re: eclipse plugin version names with dash References: <ohart@example.net> In-Reply-To: <ohart@example.net> X-Enigmail-Version: 1.0.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-FuHaFi: 0.64000000000000001 X-Virus-Checked: Checked by ClamAV on apache.org Marshall, 2.3.1-SNAPSHOT is not a valid OSGi version number. Eclipse may be doing funny stuff to get around this, but it's not going to work for other OSGi runtimes. Not sure if that affects Tommaso's work? --Thilo On 5/3/2010 16:47, Marshall Schor wrote: > For our builds, we have been doing extra stuff to have 2 kinds of versions: > > Maven conventions: 2.3.1-SNAPSHOT and > Eclipse plugin conventions: 2.3.1.SNAPSHOT > > Eclipse appears to have been updated to allow the dash: see > https://bugs.eclipse.org/bugs/show_bug.cgi?id=197503 > > So I'll presume this works and as part of my maven alignment work, > remove the special treatment of versions for eclipse & osgi plugins, > going forward. > > -Marshall From ohart@example.net Mon May 03 15:31:17 2010 Return-Path: <ohart@example.net> Delivered-To: ohart@example.net Received: (qmail 82128 invoked from network); 3 May 2010 15:31:17 -0000 Received: from unknown (HELO mail.apache.org) (83.161.120.155) by 83.161.120.155 with SMTP; 3 May 2010 15:31:17 -0000 Received: (qmail 76019 invoked by uid 500); 3 May 2010 15:31:17 -0000 Delivered-To: ohart@example.net Received: (qmail 75930 invoked by uid 500); 3 May 2010 15:31:17 -0000 Mailing-List: contact ohart@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:ohart@example.net> List-Unsubscribe: <mailto:ohart@example.net> List-Post: <mailto:ohart@example.net> List-Id: <dev.uima.apache.org> Reply-To: ohart@example.net Delivered-To: mailing list ohart@example.net Received: (qmail 75922 invoked by uid 99); 3 May 2010 15:31:17 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 May 2010 15:31:17 +0000 X-ASF-Spam-Status: No, hits=-0.6 required=10.0 tests=AWL,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of ohart@example.net designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO gateway12.websitewelcome.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with SMTP; Mon, 03 May 2010 15:31:10 +0000 Received: (qmail 5214 invoked from network); 3 May 2010 15:33:32 -0000 Received: from gator74.hostgator.com (83.161.120.155) by gateway12.websitewelcome.com with SMTP; 3 May 2010 15:33:32 -0000 Received: from yktgi01e0-s5.watson.ibm.com ([83.161.120.155]:49547 helo=[83.161.120.155]) by gator74.hostgator.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <ohart@example.net>) id 1O8xbB-0005u7-SE for ohart@example.net; Mon, 03 May 2010 10:30:21 -0500 Message-ID: <ohart@example.net> Date: Mon, 03 May 2010 11:30:24 -0400 From: Marshall Schor <ohart@example.net> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:83.161.120.155) Gecko/20100317 Thunderbird/3.0.4 MIME-Version: 1.0 To: ohart@example.net Subject: Re: eclipse plugin version names with dash References: <ohart@example.net> <ohart@example.net> In-Reply-To: <ohart@example.net> X-Enigmail-Version: 1.0.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - gator74.hostgator.com X-AntiAbuse: Original Domain - uima.apache.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - schor.com On 5/3/2010 10:59 AM, Thilo Goetz wrote: > Marshall, > > 2.3.1-SNAPSHOT is not a valid OSGi version number. I read on the internet (makes it true :-) ) in the reference link below that " According to OSGi spec 4.1 section 3.5.2 Bundle-SymbolicName has syntax: Bundle-SymbolicName 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4= symbolic-name ( ';' parameter ) * and in 1.3.2 we see the following: symbolic-name 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4= token('.'token)* token 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4= ( alphanum | '_' | '-')+ so '-' is a legal character and therefor eclipse should not warn us Is this incorrect? Or is this an OSGi spec back-level compliance issue? -Marshall > Eclipse > may be doing funny stuff to get around this, but it's not > going to work for other OSGi runtimes. Not sure if that > affects Tommaso's work? > > --Thilo > > On 5/3/2010 16:47, Marshall Schor wrote: > >> For our builds, we have been doing extra stuff to have 2 kinds of versions: >> >> Maven conventions: 2.3.1-SNAPSHOT and >> Eclipse plugin conventions: 2.3.1.SNAPSHOT >> >> Eclipse appears to have been updated to allow the dash: see >> https://bugs.eclipse.org/bugs/show_bug.cgi?id=197503 >> >> So I'll presume this works and as part of my maven alignment work, >> remove the special treatment of versions for eclipse & osgi plugins, >> going forward. >> >> -Marshall >> > > From ohart@example.net Mon May 03 15:41:44 2010 Return-Path: <ohart@example.net> Delivered-To: ohart@example.net Received: (qmail 86300 invoked from network); 3 May 2010 15:41:44 -0000 Received: from unknown (HELO mail.apache.org) (83.161.120.155) by 83.161.120.155 with SMTP; 3 May 2010 15:41:44 -0000 Received: (qmail 99360 invoked by uid 500); 3 May 2010 15:41:44 -0000 Delivered-To: ohart@example.net Received: (qmail 99336 invoked by uid 500); 3 May 2010 15:41:44 -0000 Mailing-List: contact ohart@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:ohart@example.net> List-Unsubscribe: <mailto:ohart@example.net> List-Post: <mailto:ohart@example.net> List-Id: <dev.uima.apache.org> Reply-To: ohart@example.net Delivered-To: mailing list ohart@example.net Received: (qmail 99328 invoked by uid 99); 3 May 2010 15:41:44 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 May 2010 15:41:44 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=10.0 tests=AWL,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of ohart@example.net designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO mail.gmx.net) (83.161.120.155) by apache.org (qpsmtpd/0.29) with SMTP; Mon, 03 May 2010 15:41:38 +0000 Received: (qmail invoked by alias); 03 May 2010 15:41:12 -0000 Received: from deibp9eh1--blueice3n1.emea.ibm.com (EHLO [83.161.120.155]) [83.161.120.155] by mail.gmx.net (mp029) with SMTP; 03 May 2010 17:41:12 +0200 X-Authenticated: #25330878 X-Provags-ID: V01U2FsdGVkX18SD+hCV3kSg17j6gb/pk3t/x4H8WXi+G/xsA5j/5 l1cZi2jUEqSYHp Message-ID: <ohart@example.net> Date: Mon, 03 May 2010 17:41:16 +0200 From: Thilo Goetz <ohart@example.net> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:83.161.120.155) Gecko/20100317 Lightning/1.0b1 Thunderbird/3.0.4 MIME-Version: 1.0 To: ohart@example.net Subject: Re: eclipse plugin version names with dash References: <ohart@example.net> <ohart@example.net> <ohart@example.net> In-Reply-To: <ohart@example.net> X-Enigmail-Version: 1.0.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-FuHaFi: 0.54000000000000004 That's a bundle identifier, such as org.apache.uima.core. I thought we were talking about version numbers. This is from the the OSGi javadocs: version 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4= major('.'minor('.'micro('.'qualifier)?)?)? major 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4= digit+ minor 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4= digit+ micro 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4= digit+ qualifier 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4= (alpha|digit|'_'|'-')+ digit 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4= [0..9] alpha 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4= [a..zA..Z] So you could have 83.161.120.155-SNAPSHOT, but not 2.3.1-SNAPSHOT, if I'm reading this right. (Where OSGi would treat 0-SNAPSHOT as a single, unanalyzed token). I have no problem with the maven convention, and I totally agree we should use the same version string wherever possible. It's just that for OSGi modules other than Eclipse, we may have to do something special after all. --Thilo On 5/3/2010 17:30, Marshall Schor wrote: > > > On 5/3/2010 10:59 AM, Thilo Goetz wrote: >> Marshall, >> >> 2.3.1-SNAPSHOT is not a valid OSGi version number. > > I read on the internet (makes it true :-) ) in the reference link > below that > " > > According to OSGi spec 4.1 section 3.5.2 Bundle-SymbolicName has syntax: > Bundle-SymbolicName 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4= symbolic-name ( ';' parameter ) * > and in 1.3.2 we see the following: > symbolic-name 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4= token('.'token)* > token 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4= ( alphanum | '_' | '-')+ > > so '-' is a legal character and therefor eclipse should not warn us > > Is this incorrect? Or is this an OSGi spec back-level compliance issue? > > -Marshall > >> Eclipse >> may be doing funny stuff to get around this, but it's not >> going to work for other OSGi runtimes. Not sure if that >> affects Tommaso's work? >> >> --Thilo >> >> On 5/3/2010 16:47, Marshall Schor wrote: >> >>> For our builds, we have been doing extra stuff to have 2 kinds of versions: >>> >>> Maven conventions: 2.3.1-SNAPSHOT and >>> Eclipse plugin conventions: 2.3.1.SNAPSHOT >>> >>> Eclipse appears to have been updated to allow the dash: see >>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=197503 >>> >>> So I'll presume this works and as part of my maven alignment work, >>> remove the special treatment of versions for eclipse & osgi plugins, >>> going forward. >>> >>> -Marshall >>> >> >> From ohart@example.net Mon May 03 16:02:39 2010 Return-Path: <ohart@example.net> Delivered-To: ohart@example.net Received: (qmail 91391 invoked from network); 3 May 2010 16:02:39 -0000 Received: from unknown (HELO mail.apache.org) (83.161.120.155) by 83.161.120.155 with SMTP; 3 May 2010 16:02:39 -0000 Received: (qmail 29439 invoked by uid 500); 3 May 2010 16:02:39 -0000 Delivered-To: ohart@example.net Received: (qmail 29407 invoked by uid 500); 3 May 2010 16:02:39 -0000 Mailing-List: contact ohart@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:ohart@example.net> List-Unsubscribe: <mailto:ohart@example.net> List-Post: <mailto:ohart@example.net> List-Id: <dev.uima.apache.org> Reply-To: ohart@example.net Delivered-To: mailing list ohart@example.net Received: (qmail 29399 invoked by uid 99); 3 May 2010 16:02:39 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 May 2010 16:02:39 +0000 X-ASF-Spam-Status: No, hits=-0.2 required=10.0 tests=AWL,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of ohart@example.net designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO mail-bw0-f223.google.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 May 2010 16:02:34 +0000 Received: by bwz23 with SMTP id 23so1704271bwz.6 for <ohart@example.net>; Mon, 03 May 2010 09:02:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=wxKOcQ/HZJzlx13rGsjU1RiF6wYyaLYGULKGQ3GkH9U=; b=dLS8Ds0oJXwXb/3Bozxv3TJi+7Er/Q8mGmw4PNbnEK5bimyRKRVqLDkJMoMiIGCCfX 0yXrG9jRRDTmQYU3wP09CGX3guv0wrFztMz7cfgZMsFn3iWNt98rRY10qY4/QWVABZAH NVVuj/90mxfGKQR4pnDK39nV6dhTy/POqbS0U= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=U/lpHruM/3KkMxFpTkSyX09vZPZQFP+2N9dtfykRpafgZ703uZ+fJGf3VVp3SE0pn4 gYuviljStXNL7hRwUJYBg4SrpjxaUjqytFJ7jBDBZ0mt7xiNKHQkUBeHfqiJW8KaZNED ie+7WXhbvxiKSXZnsJuyKP28/02Gt0z6q9eKo= MIME-Version: 1.0 Received: by 83.161.120.155 with SMTP id h20mr4451592bkv.185.1272902532506; Mon, 03 May 2010 09:02:12 -0700 (PDT) Sender: ohart@example.net Received: by 83.161.120.155 with HTTP; Mon, 3 May 2010 09:02:12 -0700 (PDT) In-Reply-To: <ohart@example.net> References: <ohart@example.net> <ohart@example.net> <ohart@example.net> Date: Mon, 3 May 2010 12:02:12 -0400 X-Google-Sender-Auth: b9d89d4f67367194 Message-ID: <ohart@example.net> Subject: Re: eclipse plugin version names with dash From: Adam Lally <ohart@example.net> To: ohart@example.net Content-Type: multipart/alternative; boundary=0015174780a448a6600485b2b712 --0015174780a448a6600485b2b712 Content-Type: text/plain; charset=ISO-8859-1 On Mon, May 3, 2010 at 11:30 AM, Marshall Schor <ohart@example.net> wrote: > On 5/3/2010 10:59 AM, Thilo Goetz wrote: > > Marshall, > > > > 2.3.1-SNAPSHOT is not a valid OSGi version number. > > I read on the internet (makes it true :-) ) in the reference link > below that > " > > According to OSGi spec 4.1 section 3.5.2 Bundle-SymbolicName has syntax: > Bundle-SymbolicName 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4= symbolic-name ( ';' parameter ) * > and in 1.3.2 we see the following: > symbolic-name 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4= token('.'token)* > token 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4= ( alphanum | '_' | '-')+ > > so '-' is a legal character and therefor eclipse should not warn us > > Is this incorrect? Or is this an OSGi spec back-level compliance issue? > > I think the problem is with the Bundle-Version, not the Bundle-SymbolicName. -Adam --0015174780a448a6600485b2b712-- From ohart@example.net Mon May 03 21:13:20 2010 Return-Path: <ohart@example.net> Delivered-To: ohart@example.net Received: (qmail 11200 invoked from network); 3 May 2010 21:13:20 -0000 Received: from unknown (HELO mail.apache.org) (83.161.120.155) by 83.161.120.155 with SMTP; 3 May 2010 21:13:20 -0000 Received: (qmail 30251 invoked by uid 500); 3 May 2010 21:13:20 -0000 Delivered-To: ohart@example.net Received: (qmail 30232 invoked by uid 500); 3 May 2010 21:13:20 -0000 Mailing-List: contact ohart@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:ohart@example.net> List-Unsubscribe: <mailto:ohart@example.net> List-Post: <mailto:ohart@example.net> List-Id: <dev.uima.apache.org> Reply-To: ohart@example.net Delivered-To: mailing list ohart@example.net Received: (qmail 30224 invoked by uid 99); 3 May 2010 21:13:20 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 May 2010 21:13:20 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO thor.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 May 2010 21:13:18 +0000 Received: from thor (localhost [83.161.120.155]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o43LCuRm002028 for <ohart@example.net>; Mon, 3 May 2010 21:12:56 GMT Message-ID: <9222529.23001272921176250.JavaMail.jira@thor> Date: Mon, 3 May 2010 17:12:56 -0400 (EDT) From: "Marshall Schor (JIRA)" <ohart@example.net> To: ohart@example.net Subject: [jira] Created: (UIMA-1778) improve Javadocs by eliminating Javadoc warnings MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org improve Javadocs by eliminating Javadoc warnings ------------------------------------------------ Key: UIMA-1778 URL: https://issues.apache.org/jira/browse/UIMA-1778 Project: UIMA Issue Type: Improvement Affects Versions: 2.3 Reporter: Marshall Schor Priority: Minor Fix warnings repoted by Javadoc utility. Examples * a @param is not a parameter name * @return tag has no arguments * @return used in method declaring void as return -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. From ohart@example.net Tue May 04 12:57:22 2010 Return-Path: <ohart@example.net> Delivered-To: ohart@example.net Received: (qmail 5513 invoked from network); 4 May 2010 12:57:22 -0000 Received: from unknown (HELO mail.apache.org) (83.161.120.155) by 83.161.120.155 with SMTP; 4 May 2010 12:57:22 -0000 Received: (qmail 10682 invoked by uid 500); 4 May 2010 12:57:22 -0000 Delivered-To: ohart@example.net Received: (qmail 10663 invoked by uid 500); 4 May 2010 12:57:21 -0000 Mailing-List: contact ohart@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:ohart@example.net> List-Unsubscribe: <mailto:ohart@example.net> List-Post: <mailto:ohart@example.net> List-Id: <dev.uima.apache.org> Reply-To: ohart@example.net Delivered-To: mailing list ohart@example.net Received: (qmail 10650 invoked by uid 99); 4 May 2010 12:57:21 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 May 2010 12:57:21 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO thor.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 May 2010 12:57:19 +0000 Received: from thor (localhost [83.161.120.155]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o44Cuv8t010234 for <ohart@example.net>; Tue, 4 May 2010 12:56:57 GMT Message-ID: <1633162.36161272977817313.JavaMail.jira@thor> Date: Tue, 4 May 2010 08:56:57 -0400 (EDT) From: =?utf-8?Q?J=C3=B6rn_Kottmann_=28JIRA=29?= <ohart@example.net> To: ohart@example.net Subject: [jira] Created: (UIMA-1779) UimaAsynchronousEngine should have javadoc for constants MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org UimaAsynchronousEngine should have javadoc for constants -------------------------------------------------------- Key: UIMA-1779 URL: https://issues.apache.org/jira/browse/UIMA-1779 Project: UIMA Issue Type: Improvement Components: Async Scaleout Affects Versions: 2.3AS Reporter: J=C3=B6rn Kottmann Priority: Minor The interface should have javadoc for the static final fields used to confi= gure uima-as. In my case I am especially interested in the difference betwe= en CasPoolSize and ShadowCasPoolSize. --=20 This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. From ohart@example.net Tue May 04 13:34:26 2010 Return-Path: <ohart@example.net> Delivered-To: ohart@example.net Received: (qmail 16043 invoked from network); 4 May 2010 13:34:26 -0000 Received: from unknown (HELO mail.apache.org) (83.161.120.155) by 83.161.120.155 with SMTP; 4 May 2010 13:34:26 -0000 Received: (qmail 72992 invoked by uid 500); 4 May 2010 13:34:26 -0000 Delivered-To: ohart@example.net Received: (qmail 72962 invoked by uid 500); 4 May 2010 13:34:26 -0000 Mailing-List: contact ohart@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:ohart@example.net> List-Unsubscribe: <mailto:ohart@example.net> List-Post: <mailto:ohart@example.net> List-Id: <dev.uima.apache.org> Reply-To: ohart@example.net Delivered-To: mailing list ohart@example.net Received: (qmail 72954 invoked by uid 99); 4 May 2010 13:34:26 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 May 2010 13:34:26 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of ohart@example.net designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO gateway15.websitewelcome.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with SMTP; Tue, 04 May 2010 13:34:18 +0000 Received: (qmail 25338 invoked from network); 4 May 2010 13:37:04 -0000 Received: from gator74.hostgator.com (83.161.120.155) by gateway15.websitewelcome.com with SMTP; 4 May 2010 13:37:04 -0000 Received: from yktgi01e0-s5.watson.ibm.com ([83.161.120.155]:54160 helo=[83.161.120.155]) by gator74.hostgator.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <ohart@example.net>) id 1O9IFm-0006v7-P8 for ohart@example.net; Tue, 04 May 2010 08:33:38 -0500 Message-ID: <ohart@example.net> Date: Tue, 04 May 2010 09:33:52 -0400 From: Marshall Schor <ohart@example.net> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:83.161.120.155) Gecko/20100317 Thunderbird/3.0.4 MIME-Version: 1.0 To: ohart@example.net Subject: Re: eclipse plugin version names with dash References: <ohart@example.net> <ohart@example.net> <ohart@example.net> <ohart@example.net> In-Reply-To: <ohart@example.net> X-Enigmail-Version: 1.0.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - gator74.hostgator.com X-AntiAbuse: Original Domain - uima.apache.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - schor.com X-Virus-Checked: Checked by ClamAV on apache.org Thanks, Thilo (and Adam), for explaining this. I've discovered that the maven builder-helper plugin can parse the version and create a bunch of properties, including osgiVersion - which replaces the first "-" with a ".". So here's the strategy I'm hoping will work: 1) have the maven version number for the project be x.y.z-SNAPSHOT for instance, with the dash. 2) Have the POM set the final build artifact name to be x.y.z.SNAPSHOT for instance, using the osgiVersion property. -Marshall On 5/3/2010 11:41 AM, Thilo Goetz wrote: > That's a bundle identifier, such as org.apache.uima.core. > I thought we were talking about version numbers. This is > from the the OSGi javadocs: > > version 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4= major('.'minor('.'micro('.'qualifier)?)?)? > major 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4= digit+ > minor 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4= digit+ > micro 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4= digit+ > qualifier 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4= (alpha|digit|'_'|'-')+ > digit 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4= [0..9] > alpha 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4= [a..zA..Z] > > So you could have 83.161.120.155-SNAPSHOT, but not 2.3.1-SNAPSHOT, > if I'm reading this right. (Where OSGi would treat 0-SNAPSHOT > as a single, unanalyzed token). > > I have no problem with the maven convention, and I totally > agree we should use the same version string wherever possible. > It's just that for OSGi modules other than Eclipse, we may > have to do something special after all. > > --Thilo > > On 5/3/2010 17:30, Marshall Schor wrote: > >> >> On 5/3/2010 10:59 AM, Thilo Goetz wrote: >> >>> Marshall, >>> >>> 2.3.1-SNAPSHOT is not a valid OSGi version number. >>> >> I read on the internet (makes it true :-) ) in the reference link >> below that >> " >> >> According to OSGi spec 4.1 section 3.5.2 Bundle-SymbolicName has syntax: >> Bundle-SymbolicName 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4= symbolic-name ( ';' parameter ) * >> and in 1.3.2 we see the following: >> symbolic-name 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4= token('.'token)* >> token 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4= ( alphanum | '_' | '-')+ >> >> so '-' is a legal character and therefor eclipse should not warn us >> >> Is this incorrect? Or is this an OSGi spec back-level compliance issue? >> >> -Marshall >> >> >>> Eclipse >>> may be doing funny stuff to get around this, but it's not >>> going to work for other OSGi runtimes. Not sure if that >>> affects Tommaso's work? >>> >>> --Thilo >>> >>> On 5/3/2010 16:47, Marshall Schor wrote: >>> >>> >>>> For our builds, we have been doing extra stuff to have 2 kinds of versions: >>>> >>>> Maven conventions: 2.3.1-SNAPSHOT and >>>> Eclipse plugin conventions: 2.3.1.SNAPSHOT >>>> >>>> Eclipse appears to have been updated to allow the dash: see >>>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=197503 >>>> >>>> So I'll presume this works and as part of my maven alignment work, >>>> remove the special treatment of versions for eclipse & osgi plugins, >>>> going forward. >>>> >>>> -Marshall >>>> >>>> >>> >>> > > From ohart@example.net Tue May 04 13:37:54 2010 Return-Path: <ohart@example.net> Delivered-To: ohart@example.net Received: (qmail 16831 invoked from network); 4 May 2010 13:37:54 -0000 Received: from unknown (HELO mail.apache.org) (83.161.120.155) by 83.161.120.155 with SMTP; 4 May 2010 13:37:54 -0000 Received: (qmail 80228 invoked by uid 500); 4 May 2010 13:37:52 -0000 Delivered-To: ohart@example.net Received: (qmail 80199 invoked by uid 500); 4 May 2010 13:37:52 -0000 Mailing-List: contact ohart@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:ohart@example.net> List-Unsubscribe: <mailto:ohart@example.net> List-Post: <mailto:ohart@example.net> List-Id: <dev.uima.apache.org> Reply-To: ohart@example.net Delivered-To: mailing list ohart@example.net Received: (qmail 80161 invoked by uid 99); 4 May 2010 13:37:52 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 May 2010 13:37:52 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of ohart@example.net designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO gateway16.websitewelcome.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with SMTP; Tue, 04 May 2010 13:37:43 +0000 Received: (qmail 850 invoked from network); 4 May 2010 13:40:31 -0000 Received: from gator74.hostgator.com (83.161.120.155) by gateway16.websitewelcome.com with SMTP; 4 May 2010 13:40:31 -0000 Received: from yktgi01e0-s5.watson.ibm.com ([83.161.120.155]:59210 helo=[83.161.120.155]) by gator74.hostgator.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <ohart@example.net>) id 1O9IIS-0007II-Bz for ohart@example.net; Tue, 04 May 2010 08:36:24 -0500 Message-ID: <ohart@example.net> Date: Tue, 04 May 2010 09:36:38 -0400 From: Marshall Schor <ohart@example.net> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:83.161.120.155) Gecko/20100317 Thunderbird/3.0.4 MIME-Version: 1.0 To: uima-dev <ohart@example.net> Subject: Fwd: Press Release Issued: The Apache Software Foundation Announces New Top-Level Projects X-Enigmail-Version: 1.0.1 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - gator74.hostgator.com X-AntiAbuse: Original Domain - uima.apache.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - schor.com X-Virus-Checked: Checked by ClamAV on apache.org UIMA included in this Apache PR -Marshall -------- Original Message -------- Subject: Press Release Issued: The Apache Software Foundation Announces New Top-Level Projects Date: Tue, 4 May 2010 05:34:49 -0700 (PDT) From: Sally Khudairi <ohart@example.net> Reply-To: ohart@example.net, ohart@example.net To: ASF Marketing & Publicity <ohart@example.net> CC: Apache Board <ohart@example.net> We're live! Thanks, everyone, for your help.=20 Final copy is below in plaintext; we're up on the Foundation blog and on = @TheASF Twitter feed. Cheers, Sally =3D =3D =3D Release headline: The Apache Software Foundation Announces New Top-Level = Projects Word Count: 1646 Product Summary:=20 US1 Technology ReleaseWatch Complimentary Press Release Optimization PR Newswire's Editorial Order Number: 292739-1-1 Release clear time: 04-May-2010 08:01:05 AM =3D =3D =3D The Apache Software Foundation Announces New Top-Level Projects Record Number of Projects Launched via Apache Incubator and Current Initi= atives FOREST HILL, MD =E2=80=93 4 May, 2010 =E2=80=93 The Apache Software Found= ation (ASF) =E2=80=93-the all-volunteer developers, stewards, and incubat= ors of 143 Open Source projects and initiatives-- today announced the cre= ation of six new Top-Level Projects (TLPs), setting an all-time record of= the most new TLPs launched in a single month. A Top-Level Project signifies that a Project's community and products hav= e been well-governed under the ASF's meritocratic, consensus-driven proce= ss and principles. Whilst a project is developing within the Apache Incub= ator or as a sub-project of an existing TLP, it benefits from hands-on me= ntoring from other Apache contributors, as well as the Foundation=E2=80=99= s widely-emulated process, stewardship, outreach, support, and community = events. "Becoming a Top-Level Project is a vote of confidence from the Foundation= at-large, demonstrating a project has proven its ability to be properly = self-governed," said ASF Chairman Jim Jagielski. "We are proud of our Com= mitters' dedication in building robust communities under the ASF process = known as 'The Apache Way'." All Apache Projects are overseen by a self-selected team of active contri= butors to the project. Upon a Project's maturity to a TLP, a Project Mang= ement Committee (PMC) is formed to oversee its day-to-day operations, inc= luding community development and product releases. The six new TLPs include both a graduating project from the Apache Incuba= tor as well as sub-projects of existing TLPs. They are: Graduating from the Apache Incubator - Apache Traffic Server is a richly-featured, fast, scalable, and extensi= ble HTTP/1.1 compliant caching proxy server. Formerly a commercial produc= t, Yahoo! submitted Traffic Server to the Apache Incubator in 2009. Traff= ic Server is widely recognized as an =E2=80=9Cedge=E2=80=9D service in cl= oud computing; an example of its use is to serve static content such as i= mages and JavaScript, CSS, and HTML files, and route requests for dynamic= content to a Web server such as the Apache HTTP Server. Highly performan= t, Apache Traffic Server has been benchmarked to handle in excess of 75,0= 00 requests per second (RPS), and is used in production in large-scale de= ployments such as Yahoo!, where it handles 400 terrabytes of traffic per = day, and serves more than 30 billion objects daily across its various pro= perties including the Yahoo! homepage, and its Sports, Mail, and Finance = sites. Former Sub-projects of Existing Top-Level Projects - Apache Mahout provides scalable implementations of machine learning alg= orithms on top of Apache Hadoop and other technologies. It offers collabo= rative filtering, clustering, classification, feature reduction, data mining algorithms, and more. Begun as a sub-project of Lu= cene in 2008, Mahout's team of nearly a dozen contributors is now activel= y working towards release 0.4.=20 - Apache Tika is an embeddable, lightweight toolkit for content detection= , and analysis. Powering by MIME standards from IANA, advanced language d= etection features and on the ability to rapidly unify existing parser lib= raries, Tika provides a one-stop shop for navigating the modern informati= on landscape. Tika entered the Incubator in 2007 and graduated to a Lucen= e sub-project in 2008. Tika is used in a broad range of Lucene products r= anging from Solr, to Nutch and Mahout and is in deployment at NASA, Day S= oftware, the Internet Archive, and at a number of Web startups including = Bixo labs. - Apache Nutch is a highly-modular, Web searching engine based on Lucene = Java with added Web-specifics, such as a crawler, a link-graph database, = and parsers for HTML and other document formats. Its architecture allows developers to create plugins for media-type parsi= ng, data retrieval, querying, clustering, and more. Following a successf= ul 100 million page demo system, the project graduated the Apache Incubat= or in 2005 to become a sub-project of Apache Lucene. - Apache Avro is a fast data serialization system that includes rich and = dynamic schemas in all its processing. A sub-project of Apache Hadoop, Av= ro features rich data structures; a compact, fast, binary data format; a = container file to store persistent data; remote procedure call (RPC); and= simple integration with dynamic languages. Not only is code generation n= ot required to read or write data files nor to use or implement RPC proto= cols, it is an optional optimization, only worth implementing for statica= lly typed languages. - Apache HBase is a distributed database modeled after Google's Bigtable.= The project started at Powerset and
{'source': 'Apache Software Foundation Public Mail Archives'}