Return-Path: Delivered-To: apmail-geronimo-activemq-commits-archive@www.apache.org Received: (qmail 35844 invoked from network); 6 Mar 2006 12:02:34 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 6 Mar 2006 12:02:34 -0000 Received: (qmail 19543 invoked by uid 500); 6 Mar 2006 12:03:10 -0000 Delivered-To: apmail-geronimo-activemq-commits-archive@geronimo.apache.org Received: (qmail 19512 invoked by uid 500); 6 Mar 2006 12:03:09 -0000 Mailing-List: contact activemq-commits-help@geronimo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: activemq-dev@geronimo.apache.org Delivered-To: mailing list activemq-commits@geronimo.apache.org Received: (qmail 19502 invoked by uid 99); 6 Mar 2006 12:03:09 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Mar 2006 04:03:09 -0800 X-ASF-Spam-Status: No, hits=-9.4 required=10.0 tests=ALL_TRUSTED,NO_REAL_NAME X-Spam-Check-By: apache.org Received: from [209.237.227.194] (HELO minotaur.apache.org) (209.237.227.194) by apache.org (qpsmtpd/0.29) with SMTP; Mon, 06 Mar 2006 04:03:07 -0800 Received: (qmail 35357 invoked by uid 65534); 6 Mar 2006 12:01:46 -0000 Message-ID: <20060306120146.35286.qmail@minotaur.apache.org> Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r383521 [4/30] - in /incubator/activemq/site: ./ rpc/ Date: Mon, 06 Mar 2006 11:52:07 -0000 To: activemq-commits@geronimo.apache.org From: foconer@apache.org X-Mailer: svnmailer-1.0.7 X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Modified: incubator/activemq/site/ActiveMQ+3.0+Release URL: http://svn.apache.org/viewcvs/incubator/activemq/site/ActiveMQ%2B3.0%2BRelease?rev=383521&r1=383520&r2=383521&view=diff ============================================================================== --- incubator/activemq/site/ActiveMQ+3.0+Release (original) +++ incubator/activemq/site/ActiveMQ+3.0+Release Mon Mar 6 03:51:26 2006 @@ -1,1033 +1,21 @@ - - - - - - - ActiveMQ - ActiveMQ 3.0 Release - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - -
- - - -
-
-
- - - - - -
-
-

- Home -

-
-
- -
-
-
-

Overview

- - - - -

Utilities

- - - - -

External Tools

- - - - -

Related Projects

- - - - -

Support

- - - - -

Tools we use

- -

- -
-

Feeds

- -
-
-
-
- Print -
ActiveMQ 3.0 Release
-
- - -
- -
- -
- -

-New and -Noteworthy

-

This new release includes the following

-
    -
  • a new 'discovery' transport - protocol for a pure client-only peer - network - a self discovering cluster which automatically finds - the brokers available on the network (as opposed to the 'peer' - protocol which is a complete peer based JMS network).
  • -
  • migrated from the org.activemq to org.activemq package name - hierarchy
  • -
  • improved support for more JDBC databases for persistence
  • -
  • an optimised wire protocol (which is unfortunately not - compatible with 2.x)
  • -
  • more test cases and fixes of the - JCA Container
  • -
  • various performance enhancements and bug fixes
  • -
-

-Download Here

- - - - - - - - - - - - - - - - - - - - - - - -
DownloadDescription
- - activemq-3.0.zip - - - Binary Distribution in zip - package
- - activemq-3.0-src.zip - - - Source Distribution in zip - package
- - activemq-3.0.tar.gz - - - Binary Distribution in gz - package
- - activemq-3.0-src.tar.gz - - - Source Distribution in gz - package
-

-Changelog

-

For a more detailed view of new features and bug fixes, see the - - release - notes - -

-

- -

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - jira.activemq.org - - (25 issues)
TKeySummaryAssigneeReporterPrStatusResCreatedUpdatedDue
- - Bug - - - AMQ-231 - - reliable:tcp://localhost - Transport does not reconnect a consumer when broker - failed. - UnassignedHiram Chirino - Major - - ResolvedResolvedFIXEDApr 08, 2005Apr 08, 2005 -
- - Bug - - - AMQ-230 - - Reliable - protocol + tcp Connector does not reconnect on restarted - external broker - UnassignedPaul Smith - Major - - ResolvedResolvedFIXEDApr 08, 2005Apr 08, 2005 -
- - Bug - - - AMQ-228 - - Eclipse - project for Core not working - UnassignedStefan Kleineikenscheidt - Trivial - - ResolvedResolvedFIXEDApr 07, 2005Apr 07, 2005 -
- - Bug - - - AMQ-227 - - Duplicate - clientid error when using the - ActiveMQInitialContextFactory - UnassignedHiram Chirino - Major - - ResolvedResolvedFIXEDApr 06, 2005Apr 13, 2005 -
- - Bug - - - AMQ-226 - - Monitor - lock conflict during shutdown - UnassignedDennis Cook - Major - - ResolvedResolvedFIXEDApr 04, 2005Apr 06, 2005 -
- - Bug - - - AMQ-225 - - DB - Auto-detect expects "Oracle_JDBC_Driver" but Oracle driver - returns "Oracle_JDBC_driver" - UnassignedTravis Carlson - Minor - - ResolvedResolvedFIXEDMar 29, 2005Apr 04, 2005 -
- - Bug - - - AMQ-223 - - Memory - Leak in TcpTransportServerChannel - UnassignedYuri Schimke - Critical - - ResolvedResolvedFIXEDMar 24, 2005Apr 06, 2005 -
- - Bug - - - AMQ-222 - - Apparent - Memory Leak - Unassignedkris wehner - Major - - ResolvedResolvedFIXEDMar 22, 2005Apr 04, 2005 -
- - Bug - - - AMQ-221 - - Missing - queue messages - james strachanDennis Cook - Blocker - - ResolvedResolvedFIXEDMar 22, 2005Mar 22, 2005 -
- - Improvement - - - AMQ-217 - - Change - the journal code to only print info messages if it finds - something interesting during checkpointing - Hiram ChirinoHiram Chirino - Major - - ResolvedResolvedFIXEDMar 15, 2005Mar 16, 2005 -
- - Bug - - - AMQ-216 - - Maven - fails to complete for 2.1 - Unassignedandrew cooke - Major - - ResolvedResolvedFIXEDMar 14, 2005Apr 06, 2005 -
- - Bug - - - AMQ-215 - - No - Connected event generated by CompositeTransferChannel - UnassignedDennis Cook - Major - - ResolvedResolvedFIXEDMar 11, 2005Mar 11, 2005 -
- - Bug - - - AMQ-214 - - ObjectMessage - inputstream needs to handle loading class[] too. - UnassignedHiram Chirino - Major - - ResolvedResolvedFIXEDMar 10, 2005Mar 11, 2005 -
- - Bug - - - AMQ-213 - - toString() - of TransportStatusEvent needs update - UnassignedDennis Cook - Minor - - ResolvedResolvedFIXEDMar 09, 2005Mar 11, 2005 -
- - Bug - - - AMQ-212 - - useAsyncSend - parameter ignored for client connection - UnassignedDennis Cook - Major - - ResolvedResolvedFIXEDMar 08, 2005Mar 11, 2005 -
- - Bug - - - AMQ-211 - - Reliable - reconnection process is broken - UnassignedDennis Cook - Critical - - ResolvedResolvedFIXEDMar 08, 2005Mar 11, 2005 -
- - Bug - - - AMQ-210 - - Server - reconnect is not detected with peer protocol (2 peer setup - only) - UnassignedIgor Kaplansky - Critical - - ResolvedResolvedCANNOT REPRODUCEMar 08, 2005Apr 13, 2005 -
- - Bug - - - AMQ-209 - - Unable - fora durable subscriber to retreive persistent message - UnassignedFrancois Courtault - Major - - ResolvedResolvedFIXEDMar 08, 2005Apr 04, 2005 -
- - Bug - - - AMQ-208 - - Undead - threads in broker when TCP clients disconnect - UnassignedBenjamin Loo - Major - - ResolvedResolvedFIXEDMar 08, 2005Apr 08, 2005 -
- - Bug - - - AMQ-207 - - Timeout - increment logic is incorrect - UnassignedNeil Clayton - Major - - ResolvedResolvedFIXEDMar 05, 2005Apr 04, 2005 -
- - Bug - - - AMQ-204 - - Queue - Browser behaves differently on non-persisten/persitent - messages in a transacted session. - Hiram ChirinoHiram Chirino - Major - - ClosedClosedFIXEDMar 01, 2005Mar 17, 2005 -
- - Bug - - - AMQ-203 - - Batch - Startup Script Fails - Hiram ChirinoSeth Ladd - Major - - ClosedClosedFIXEDFeb 28, 2005Mar 17, 2005 -
- - Bug - - - AMQ-202 - - Doing - a rollback when using journal could cause messge to not get - redelivered. - Hiram ChirinoHiram Chirino - Major - - ClosedClosedFIXEDFeb 27, 2005Mar 17, 2005 -
- - Bug - - - AMQ-198 - - Exception - occurs using derby and journal on startup - Hiram ChirinoCameron Braid - Major - - ClosedClosedFIXEDFeb 22, 2005Mar 17, 2005 -
- - Bug - - - AMQ-194 - - Missing - overrides for getStatistics() in session, consumer and - producer - StewieDennis Cook - Major - - ResolvedResolvedFIXEDFeb 11, 2005Mar 21, 2005 -
-
-
-

You may also want to look at -the previous Changelog

-
-
- - -
-
-
- -
Powered by Atlassian Confluence
- -
-
- +Server returned HTTP response code: 500 for URL: http://docs.codehaus.org/rpc/xmlrpc com.openxource.unity.providers.confluence.ConfluencePageProviderImpl.getPage(ConfluencePageProviderImpl.java:78) + com.openxource.unity.beans.impl.UnityPageRendererImpl.getFragment(UnityPageRendererImpl.java:249) + com.openxource.unity.beans.impl.UnityPageRendererImpl.renderPage(UnityPageRendererImpl.java:155) + com.openxource.unity.servlets.ContentServlet.doGet(ContentServlet.java:69) + javax.servlet.http.HttpServlet.service(HttpServlet.java:689) + javax.servlet.http.HttpServlet.service(HttpServlet.java:802) + org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) + org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) + org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) + org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) + org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) + org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) + org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) + org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) + org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:199) + org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:282) + org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:744) + org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:674) + org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:866) + org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) + java.lang.Thread.run(Thread.java:595)