You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by Hiram Chirino <hi...@hiramchirino.com> on 2011/04/01 17:57:02 UTC
[VOTE] Release Apollo 1.0 Beta 1 (2nd Attempt)
Hi all,
The first release attempt had a fatal flaw (it did not run properly on
linux) so I've recut a
Apollo 1.0 beta 1 release candiate which addresses that issue.
The new release candidate has been staged to nexus under:
https://repository.apache.org/content/repositories/orgapacheactivemq-059/
Binary distros can be found at:
https://repository.apache.org/content/repositories/orgapacheactivemq-059/org/apache/activemq/apache-apollo/1.0-beta1/
Source code distros can be found at:
https://repository.apache.org/content/repositories/orgapacheactivemq-059/org/apache/activemq/apollo-project/1.0-beta1/
The build was tagged at:
http://svn.apache.org/repos/asf/activemq/activemq-apollo/tags/apollo-project-1.0-beta1/
The project website for that version has been staged to:
http://activemq.apache.org/apollo/versions/1.0-beta1/website/index.html
Please vote to approve this release
[ ] +1 Release the binary as Apache ActiveMQ 5.5.0
[ ] -1 Veto the release (provide specific comments)
Here's my +1
Regards,
Hiram
FuseSource
Web: http://fusesource.com/
Re: [VOTE] Release Apollo 1.0 Beta 1 (2nd Attempt)
Posted by Hiram Chirino <hi...@hiramchirino.com>.
Hi Bruce, Dejan,
Awesome feedback. I've opened up several issues to try to address the
short comings you guys identified:
https://issues.apache.org/jira/browse/AMQ-3264
https://issues.apache.org/jira/browse/AMQ-3265
https://issues.apache.org/jira/browse/AMQ-3266
https://issues.apache.org/jira/browse/AMQ-3267
Let me know if I missed anything.
BTW.. I've also opened a infra task to create a JIRA project for
apollo https://issues.apache.org/jira/browse/INFRA-3560
since it's release cycle is independent of ActiveMQ.
Regards,
Hiram
FuseSource
Web: http://fusesource.com/
Regards,
Hiram
FuseSource
Web: http://fusesource.com/
Re: [VOTE] Release Apollo 1.0 Beta 1 (2nd Attempt)
Posted by Dejan Bosanac <de...@nighttale.net>.
+1
my only suggestion for improvement would be to make it able run the broker
without setting env variables, We can do that by
1. distributing 'apollo' script when the new broker is created and modify
apollo-broker to execute it from the same dir
2. modify local apollo script so that it set APOLLO_HOME to the appropriate
value (if it's not already set). This can be done in create process as well.
Think this will make it easier to run the broker (and play with multiple
brokers on the same host) without sacrificing conf+data and installation
separation.
Regards
--
Dejan Bosanac - http://twitter.com/dejanb
-----------------
The experts in open source integration and messaging - http://fusesource.com
ActiveMQ in Action - http://www.manning.com/snyder/
Blog - http://www.nighttale.net
Connect at CamelOne <http://camelone.com/> May 24-26
The Open Source Integration Conference
On Sun, Apr 3, 2011 at 8:19 AM, Rob Davies <ra...@gmail.com> wrote:
> +!
> On 1 Apr 2011, at 16:57, Hiram Chirino wrote:
>
> > Hi all,
> >
> > The first release attempt had a fatal flaw (it did not run properly on
> > linux) so I've recut a
> > Apollo 1.0 beta 1 release candiate which addresses that issue.
> >
> > The new release candidate has been staged to nexus under:
> >
> https://repository.apache.org/content/repositories/orgapacheactivemq-059/
> >
> > Binary distros can be found at:
> >
> https://repository.apache.org/content/repositories/orgapacheactivemq-059/org/apache/activemq/apache-apollo/1.0-beta1/
> >
> > Source code distros can be found at:
> >
> https://repository.apache.org/content/repositories/orgapacheactivemq-059/org/apache/activemq/apollo-project/1.0-beta1/
> >
> > The build was tagged at:
> >
> http://svn.apache.org/repos/asf/activemq/activemq-apollo/tags/apollo-project-1.0-beta1/
> >
> > The project website for that version has been staged to:
> > http://activemq.apache.org/apollo/versions/1.0-beta1/website/index.html
> >
> > Please vote to approve this release
> >
> > [ ] +1 Release the binary as Apache ActiveMQ 5.5.0
> > [ ] -1 Veto the release (provide specific comments)
> >
> > Here's my +1
> >
> >
> > Regards,
> > Hiram
> >
> > FuseSource
> > Web: http://fusesource.com/
>
>
Re: [VOTE] Release Apollo 1.0 Beta 1 (2nd Attempt)
Posted by Rob Davies <ra...@gmail.com>.
+!
On 1 Apr 2011, at 16:57, Hiram Chirino wrote:
> Hi all,
>
> The first release attempt had a fatal flaw (it did not run properly on
> linux) so I've recut a
> Apollo 1.0 beta 1 release candiate which addresses that issue.
>
> The new release candidate has been staged to nexus under:
> https://repository.apache.org/content/repositories/orgapacheactivemq-059/
>
> Binary distros can be found at:
> https://repository.apache.org/content/repositories/orgapacheactivemq-059/org/apache/activemq/apache-apollo/1.0-beta1/
>
> Source code distros can be found at:
> https://repository.apache.org/content/repositories/orgapacheactivemq-059/org/apache/activemq/apollo-project/1.0-beta1/
>
> The build was tagged at:
> http://svn.apache.org/repos/asf/activemq/activemq-apollo/tags/apollo-project-1.0-beta1/
>
> The project website for that version has been staged to:
> http://activemq.apache.org/apollo/versions/1.0-beta1/website/index.html
>
> Please vote to approve this release
>
> [ ] +1 Release the binary as Apache ActiveMQ 5.5.0
> [ ] -1 Veto the release (provide specific comments)
>
> Here's my +1
>
>
> Regards,
> Hiram
>
> FuseSource
> Web: http://fusesource.com/
Re: [VOTE] Release Apollo 1.0 Beta 1 (2nd Attempt)
Posted by Jim Gomes <e....@gmail.com>.
+1 on the Getting Started guides. I like that style of layered approach.
On Mon, Apr 4, 2011 at 8:54 AM, Bruce Snyder <br...@gmail.com> wrote:
> On Mon, Apr 4, 2011 at 7:45 AM, Hiram Chirino <hi...@hiramchirino.com>
> wrote:
> > Yeah I guess the gettings started guide is complicated by a couple of
> > extra steps.
> >
> > I think once we implement:
> > https://issues.apache.org/jira/browse/AMQ-3267
> > Which is dejan's suggestion, it should become more streamlined.
> >
> > We could also remove the BDB part, but I'd hesitate to do that because
> > the BDB store implementation does provide a much smoother performance
> > characteristic than the included JDBM. And one of the first thing
> > folks are going to want to do with a new broker is see how it
> > performs.
> >
> > I don't really care if it's called beta or alpha. The reason I picked
> > beta is because I don't see us putting any more major features into
> > the release. It just needs go through a couple QA cycles to clean out
> > bugs / streamline the user experience.
>
> Agreed, and we should elaborate on those suggested changes so that so
> that we are leading folks down a path to success. My advice is that we
> provide a series of guides:
>
> 1) A 'Getting Started With Apollo in 10 Minutes' guide. This guide
> serves as the first time user's guide to getting started with Apollo.
> It's basically a smoke test for Apollo in your environment.
>
> 2) A 'How to Make Apollo Screaming Fast in 10 More Minutes' guide.
> This guide is focused on improving Apollo's speed. It provides
> suggestions on which items to change, how to change them and the
> expected benefits of making such changes.
>
> 3) A 'Diving Deeper With Apollo' guide. This gives people a
> thinking-in-Apollo mindset, provides a high level diagram of the
> internals, explains extension points, areas to extend, etc.
>
> We need to provide some dead simple steps to getting started as well
> as taking the next steps to dive deeper in . Without this, the
> experience winds up being a needle-in-a-haystack chase for new users,
> even if they have already used ActiveMQ. I'd really like to see many
> different guides get created over time, each with a different focus
> (e.g., different app quality of service requirements, different
> business areas, different broker environments, etc.).
>
> Again, I'm very willing to begin working on this stuff. As I dig into
> Apollo to learn what it's all about, I can begin to create these
> guides on the wiki with the intention that they live and change as
> appropriate. These are only some initial suggestions.
>
> Bruce
> --
> perl -e 'print
> unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
> );'
>
> ActiveMQ in Action: http://bit.ly/2je6cQ
> Blog: http://bruceblog.org/
> Twitter: http://twitter.com/brucesnyder
>
Re: [VOTE] Release Apollo 1.0 Beta 1 (2nd Attempt)
Posted by Hiram Chirino <hi...@hiramchirino.com>.
Hi Bruce that sounds good to me. Apollo is storing it's documentation
along with the project under the apollo-website module so that we can
keep the documentation versioned in lock step with the project. It
also makes it easier to include the same documentation in the binary
distribution. Feel free to add more guides :)
Regards,
Hiram
FuseSource
Web: http://fusesource.com/
Connect at CamelOne May 24-26
The Open Source Integration Conference
On Mon, Apr 4, 2011 at 11:54 AM, Bruce Snyder <br...@gmail.com> wrote:
> On Mon, Apr 4, 2011 at 7:45 AM, Hiram Chirino <hi...@hiramchirino.com> wrote:
>> Yeah I guess the gettings started guide is complicated by a couple of
>> extra steps.
>>
>> I think once we implement:
>> https://issues.apache.org/jira/browse/AMQ-3267
>> Which is dejan's suggestion, it should become more streamlined.
>>
>> We could also remove the BDB part, but I'd hesitate to do that because
>> the BDB store implementation does provide a much smoother performance
>> characteristic than the included JDBM. And one of the first thing
>> folks are going to want to do with a new broker is see how it
>> performs.
>>
>> I don't really care if it's called beta or alpha. The reason I picked
>> beta is because I don't see us putting any more major features into
>> the release. It just needs go through a couple QA cycles to clean out
>> bugs / streamline the user experience.
>
> Agreed, and we should elaborate on those suggested changes so that so
> that we are leading folks down a path to success. My advice is that we
> provide a series of guides:
>
> 1) A 'Getting Started With Apollo in 10 Minutes' guide. This guide
> serves as the first time user's guide to getting started with Apollo.
> It's basically a smoke test for Apollo in your environment.
>
> 2) A 'How to Make Apollo Screaming Fast in 10 More Minutes' guide.
> This guide is focused on improving Apollo's speed. It provides
> suggestions on which items to change, how to change them and the
> expected benefits of making such changes.
>
> 3) A 'Diving Deeper With Apollo' guide. This gives people a
> thinking-in-Apollo mindset, provides a high level diagram of the
> internals, explains extension points, areas to extend, etc.
>
> We need to provide some dead simple steps to getting started as well
> as taking the next steps to dive deeper in . Without this, the
> experience winds up being a needle-in-a-haystack chase for new users,
> even if they have already used ActiveMQ. I'd really like to see many
> different guides get created over time, each with a different focus
> (e.g., different app quality of service requirements, different
> business areas, different broker environments, etc.).
>
> Again, I'm very willing to begin working on this stuff. As I dig into
> Apollo to learn what it's all about, I can begin to create these
> guides on the wiki with the intention that they live and change as
> appropriate. These are only some initial suggestions.
>
> Bruce
> --
> perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
> );'
>
> ActiveMQ in Action: http://bit.ly/2je6cQ
> Blog: http://bruceblog.org/
> Twitter: http://twitter.com/brucesnyder
>
Re: [VOTE] Release Apollo 1.0 Beta 1 (2nd Attempt)
Posted by Bruce Snyder <br...@gmail.com>.
On Mon, Apr 4, 2011 at 7:45 AM, Hiram Chirino <hi...@hiramchirino.com> wrote:
> Yeah I guess the gettings started guide is complicated by a couple of
> extra steps.
>
> I think once we implement:
> https://issues.apache.org/jira/browse/AMQ-3267
> Which is dejan's suggestion, it should become more streamlined.
>
> We could also remove the BDB part, but I'd hesitate to do that because
> the BDB store implementation does provide a much smoother performance
> characteristic than the included JDBM. And one of the first thing
> folks are going to want to do with a new broker is see how it
> performs.
>
> I don't really care if it's called beta or alpha. The reason I picked
> beta is because I don't see us putting any more major features into
> the release. It just needs go through a couple QA cycles to clean out
> bugs / streamline the user experience.
Agreed, and we should elaborate on those suggested changes so that so
that we are leading folks down a path to success. My advice is that we
provide a series of guides:
1) A 'Getting Started With Apollo in 10 Minutes' guide. This guide
serves as the first time user's guide to getting started with Apollo.
It's basically a smoke test for Apollo in your environment.
2) A 'How to Make Apollo Screaming Fast in 10 More Minutes' guide.
This guide is focused on improving Apollo's speed. It provides
suggestions on which items to change, how to change them and the
expected benefits of making such changes.
3) A 'Diving Deeper With Apollo' guide. This gives people a
thinking-in-Apollo mindset, provides a high level diagram of the
internals, explains extension points, areas to extend, etc.
We need to provide some dead simple steps to getting started as well
as taking the next steps to dive deeper in . Without this, the
experience winds up being a needle-in-a-haystack chase for new users,
even if they have already used ActiveMQ. I'd really like to see many
different guides get created over time, each with a different focus
(e.g., different app quality of service requirements, different
business areas, different broker environments, etc.).
Again, I'm very willing to begin working on this stuff. As I dig into
Apollo to learn what it's all about, I can begin to create these
guides on the wiki with the intention that they live and change as
appropriate. These are only some initial suggestions.
Bruce
--
perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'
ActiveMQ in Action: http://bit.ly/2je6cQ
Blog: http://bruceblog.org/
Twitter: http://twitter.com/brucesnyder
Re: [VOTE] Release Apollo 1.0 Beta 1 (2nd Attempt)
Posted by Hiram Chirino <hi...@hiramchirino.com>.
Yeah I guess the gettings started guide is complicated by a couple of
extra steps.
I think once we implement:
https://issues.apache.org/jira/browse/AMQ-3267
Which is dejan's suggestion, it should become more streamlined.
We could also remove the BDB part, but I'd hesitate to do that because
the BDB store implementation does provide a much smoother performance
characteristic than the included JDBM. And one of the first thing
folks are going to want to do with a new broker is see how it
performs.
I don't really care if it's called beta or alpha. The reason I picked
beta is because I don't see us putting any more major features into
the release. It just needs go through a couple QA cycles to clean out
bugs / streamline the user experience.
Regards,
Hiram
FuseSource
Web: http://fusesource.com/
On Sun, Apr 3, 2011 at 2:44 PM, Bruce Snyder <br...@gmail.com> wrote:
> On Fri, Apr 1, 2011 at 9:57 AM, Hiram Chirino <hi...@hiramchirino.com> wrote:
>> Hi all,
>>
>> The first release attempt had a fatal flaw (it did not run properly on
>> linux) so I've recut a
>> Apollo 1.0 beta 1 release candiate which addresses that issue.
>>
>> The new release candidate has been staged to nexus under:
>> https://repository.apache.org/content/repositories/orgapacheactivemq-059/
>>
>> Binary distros can be found at:
>> https://repository.apache.org/content/repositories/orgapacheactivemq-059/org/apache/activemq/apache-apollo/1.0-beta1/
>>
>> Source code distros can be found at:
>> https://repository.apache.org/content/repositories/orgapacheactivemq-059/org/apache/activemq/apollo-project/1.0-beta1/
>>
>> The build was tagged at:
>> http://svn.apache.org/repos/asf/activemq/activemq-apollo/tags/apollo-project-1.0-beta1/
>>
>> The project website for that version has been staged to:
>> http://activemq.apache.org/apollo/versions/1.0-beta1/website/index.html
>>
>> Please vote to approve this release
>>
>> [ ] +1 Release the binary as Apache ActiveMQ 5.5.0
>> [ ] -1 Veto the release (provide specific comments)
>
> I haven't ever run Apollo, so here's what I did:
>
> 1) wget <url-to-tarball>
> 2) tar zxvf <path-to-tarball>
> 3) Look for help command:
>
> $ ./bin/apollo --help
> Command not found: --help
>
> 4) open readme.html
> 5) Click 'Getting Started Guide'
> 6) Read 'Installation' section; Set the APOLLO_HOME:
>
> $ export APOLLO_HOME=`pwd`
> $ echo $APOLLO_HOME
> /Users/bsnyder/amq/apache-apollo-1.0-beta1
>
> $ export PATH=$PATH:$APOLLO_HOME/bin
>
> 7) Read 'Install BDB'; Do I really need to install BDB first?; Skip
> this for now
> 8) Read 'Creating a Broker Instance'; Hmm, I guess I need to do this:
>
> $ ./bin/apollo create mybroker
> Creating apollo instance at: mybroker
> Generating ssl keystore...
> Make sure the following directory is on your path:
>
> /Users/bsnyder/amq/apache-apollo-1.0-beta1/bin/bin
>
> Then run the broker by executing:
>
> /Users/bsnyder/amq/apache-apollo-1.0-beta1/mybroker/bin/apollo-broker run
>
> 9) Read 'Updating the Configuration to use BDB'; Do I really need to
> configure BDB?; Skip this for now
> 10) Read 'Running a Broker Instance'; Notice it sorta matches the
> output from step 7 above; Run the broker:
>
> $ ./mybroker/bin/apollo-broker run
>
> _____ .__ .__
> / _ \ ______ ____ | | | | ____
> / /_\ \\____ \ / _ \| | | | / _ \
> / | \ |_> > <_> ) |_| |_( <_> )
> \____|__ / __/ \____/|____/____/\____/
> \/|__| Apache Apollo (1.0-beta1)
>
>
> Loading configuration file
> '/Users/bsnyder/amq/apache-apollo-1.0-beta1/mybroker/etc/apollo.xml'.
> INFO | OS : Mac OS X 10.6.7
> INFO | JVM : Java HotSpot(TM) 64-Bit Server VM 1.6.0_24 (Apple Inc.)
> INFO | Apollo : 1.0-beta1
> INFO | OS is restricting the open file limit to: 10240
> INFO | Starting store: jdbm2 store at
> /Users/bsnyder/amq/apache-apollo-1.0-beta1/mybroker/data
> INFO | Store started
> INFO | Accepting connections at: tls://0.0.0.0:61614
> INFO | Accepting connections at: tcp://0.0.0.0:61613
> INFO | broker startup is taking a long time (1 seconds). Waiting on
> jetty webserver
> INFO | Administration interface available at: http://127.0.0.1:61680/
>
> OK, the broker is running.
>
> 11) Read the 'Verification' section. I guess I'll try to run the Ruby
> examples, that's usually pretty easy.
> 12) Open another terminal
> 13) Install the Stomp gem:
>
> $ gem install stomp
> WARNING: Installing to ~/.gem since /Library/Ruby/Gems/1.8 and
> /usr/bin aren't both writable.
> WARNING: You don't have /Users/bsnyder/.gem/ruby/1.8/bin in your PATH,
> gem executables will not run.
> Successfully installed stomp-1.1.8
> 1 gem installed
> Installing ri documentation for stomp-1.1.8...
> Installing RDoc documentation for stomp-1.1.8...
>
> 14) Move into the examples/ruby dir to run the listener:
>
> $ cd /Users/bsnyder/amq/apache-apollo-1.0-beta1/examples/ruby
> $ ruby listener.rb
>
> (No output) Is it running correctly?? I guess I'll run the publisher to see.
>
> 15) Open another terminal
> 16) Move into the examples/ruby dir to run the publisher:
>
> $ cd /Users/bsnyder/amq/apache-apollo-1.0-beta1/examples/ruby
> $ ruby publisher.rb
> Sent 1000 messages
> Sent 2000 messages
> Sent 3000 messages
> Sent 4000 messages
> Sent 5000 messages
> Sent 6000 messages
> Sent 7000 messages
> Sent 8000 messages
> Sent 9000 messages
> Sent 10000 messages
>
> Ahh, OK, some output.
>
> 17) Switch back to the terminal where the listener is running and see output:
>
> Received 1000 messages.
> Received 2000 messages.
> Received 3000 messages.
> Received 4000 messages.
> Received 5000 messages.
> Received 6000 messages.
> Received 7000 messages.
> Received 8000 messages.
> Received 9000 messages.
> Received 10000 messages.
> Received 10000 in 2.125227 seconds
>
> OK, it seems to have run correctly. That probably means success.
>
> 18) Read the 'Web Administration' section
> 19) Click on the URL to see the web UI; not a lot here yet
> 20) Try to run the Java examples.
>
> $ mvn install
> ...
> Missing:
> ----------
> 1) org.fusesource.hawtbuf:hawtbuf:jar:1.3-SNAPSHOT
>
> Try downloading the file manually from the project website.
>
> Then, install it using the command:
> mvn install:install-file -DgroupId=org.fusesource.hawtbuf
> -DartifactId=hawtbuf -Dversion=1.3-SNAPSHOT -Dpackaging=jar
> -Dfile=/path/to/file
>
> Alternatively, if you host your own repository you can deploy the file there:
> mvn deploy:deploy-file -DgroupId=org.fusesource.hawtbuf
> -DartifactId=hawtbuf -Dversion=1.3-SNAPSHOT -Dpackaging=jar
> -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
>
> Path to dependency:
> 1) example:example:jar:1.0-SNAPSHOT
> 2) org.fusesource.stompjms:stompjms-client:jar:1.0-SNAPSHOT
> 3) org.fusesource.hawtbuf:hawtbuf:jar:1.3-SNAPSHOT
>
> ----------
> 1 required artifact is missing.
>
> for artifact:
> example:example:jar:1.0-SNAPSHOT
>
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2),
> Fusesource Snapshots
> (http://repo.fusesource.com/nexus/content/repositories/snapshots)
>
> Oh good grief.
>
>
> A simple README document should provide new users a deterministic,
> step-by-step guide so that they know exactly what commands to run and
> what to expect from those commands. I had to do a fair amount of
> meandering to figure out how to get the broker running.
>
> Are you sure you want to label this as a beta release? This should be
> an alpha release, i.e., allow developers to kick the tires, make it
> clear that it is not polished yet. I'm willing to help contribute to
> these items, but this will take some time. I don't think that it
> should be labeled as a beta release.
>
> Just my $.02.
>
> Bruce
> --
> perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
> );'
>
> ActiveMQ in Action: http://bit.ly/2je6cQ
> Blog: http://bruceblog.org/
> Twitter: http://twitter.com/brucesnyder
>
Re: [VOTE] Release Apollo 1.0 Beta 1 (2nd Attempt)
Posted by Bruce Snyder <br...@gmail.com>.
On Fri, Apr 1, 2011 at 9:57 AM, Hiram Chirino <hi...@hiramchirino.com> wrote:
> Hi all,
>
> The first release attempt had a fatal flaw (it did not run properly on
> linux) so I've recut a
> Apollo 1.0 beta 1 release candiate which addresses that issue.
>
> The new release candidate has been staged to nexus under:
> https://repository.apache.org/content/repositories/orgapacheactivemq-059/
>
> Binary distros can be found at:
> https://repository.apache.org/content/repositories/orgapacheactivemq-059/org/apache/activemq/apache-apollo/1.0-beta1/
>
> Source code distros can be found at:
> https://repository.apache.org/content/repositories/orgapacheactivemq-059/org/apache/activemq/apollo-project/1.0-beta1/
>
> The build was tagged at:
> http://svn.apache.org/repos/asf/activemq/activemq-apollo/tags/apollo-project-1.0-beta1/
>
> The project website for that version has been staged to:
> http://activemq.apache.org/apollo/versions/1.0-beta1/website/index.html
>
> Please vote to approve this release
>
> [ ] +1 Release the binary as Apache ActiveMQ 5.5.0
> [ ] -1 Veto the release (provide specific comments)
I haven't ever run Apollo, so here's what I did:
1) wget <url-to-tarball>
2) tar zxvf <path-to-tarball>
3) Look for help command:
$ ./bin/apollo --help
Command not found: --help
4) open readme.html
5) Click 'Getting Started Guide'
6) Read 'Installation' section; Set the APOLLO_HOME:
$ export APOLLO_HOME=`pwd`
$ echo $APOLLO_HOME
/Users/bsnyder/amq/apache-apollo-1.0-beta1
$ export PATH=$PATH:$APOLLO_HOME/bin
7) Read 'Install BDB'; Do I really need to install BDB first?; Skip
this for now
8) Read 'Creating a Broker Instance'; Hmm, I guess I need to do this:
$ ./bin/apollo create mybroker
Creating apollo instance at: mybroker
Generating ssl keystore...
Make sure the following directory is on your path:
/Users/bsnyder/amq/apache-apollo-1.0-beta1/bin/bin
Then run the broker by executing:
/Users/bsnyder/amq/apache-apollo-1.0-beta1/mybroker/bin/apollo-broker run
9) Read 'Updating the Configuration to use BDB'; Do I really need to
configure BDB?; Skip this for now
10) Read 'Running a Broker Instance'; Notice it sorta matches the
output from step 7 above; Run the broker:
$ ./mybroker/bin/apollo-broker run
_____ .__ .__
/ _ \ ______ ____ | | | | ____
/ /_\ \\____ \ / _ \| | | | / _ \
/ | \ |_> > <_> ) |_| |_( <_> )
\____|__ / __/ \____/|____/____/\____/
\/|__| Apache Apollo (1.0-beta1)
Loading configuration file
'/Users/bsnyder/amq/apache-apollo-1.0-beta1/mybroker/etc/apollo.xml'.
INFO | OS : Mac OS X 10.6.7
INFO | JVM : Java HotSpot(TM) 64-Bit Server VM 1.6.0_24 (Apple Inc.)
INFO | Apollo : 1.0-beta1
INFO | OS is restricting the open file limit to: 10240
INFO | Starting store: jdbm2 store at
/Users/bsnyder/amq/apache-apollo-1.0-beta1/mybroker/data
INFO | Store started
INFO | Accepting connections at: tls://0.0.0.0:61614
INFO | Accepting connections at: tcp://0.0.0.0:61613
INFO | broker startup is taking a long time (1 seconds). Waiting on
jetty webserver
INFO | Administration interface available at: http://127.0.0.1:61680/
OK, the broker is running.
11) Read the 'Verification' section. I guess I'll try to run the Ruby
examples, that's usually pretty easy.
12) Open another terminal
13) Install the Stomp gem:
$ gem install stomp
WARNING: Installing to ~/.gem since /Library/Ruby/Gems/1.8 and
/usr/bin aren't both writable.
WARNING: You don't have /Users/bsnyder/.gem/ruby/1.8/bin in your PATH,
gem executables will not run.
Successfully installed stomp-1.1.8
1 gem installed
Installing ri documentation for stomp-1.1.8...
Installing RDoc documentation for stomp-1.1.8...
14) Move into the examples/ruby dir to run the listener:
$ cd /Users/bsnyder/amq/apache-apollo-1.0-beta1/examples/ruby
$ ruby listener.rb
(No output) Is it running correctly?? I guess I'll run the publisher to see.
15) Open another terminal
16) Move into the examples/ruby dir to run the publisher:
$ cd /Users/bsnyder/amq/apache-apollo-1.0-beta1/examples/ruby
$ ruby publisher.rb
Sent 1000 messages
Sent 2000 messages
Sent 3000 messages
Sent 4000 messages
Sent 5000 messages
Sent 6000 messages
Sent 7000 messages
Sent 8000 messages
Sent 9000 messages
Sent 10000 messages
Ahh, OK, some output.
17) Switch back to the terminal where the listener is running and see output:
Received 1000 messages.
Received 2000 messages.
Received 3000 messages.
Received 4000 messages.
Received 5000 messages.
Received 6000 messages.
Received 7000 messages.
Received 8000 messages.
Received 9000 messages.
Received 10000 messages.
Received 10000 in 2.125227 seconds
OK, it seems to have run correctly. That probably means success.
18) Read the 'Web Administration' section
19) Click on the URL to see the web UI; not a lot here yet
20) Try to run the Java examples.
$ mvn install
...
Missing:
----------
1) org.fusesource.hawtbuf:hawtbuf:jar:1.3-SNAPSHOT
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.fusesource.hawtbuf
-DartifactId=hawtbuf -Dversion=1.3-SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file there:
mvn deploy:deploy-file -DgroupId=org.fusesource.hawtbuf
-DartifactId=hawtbuf -Dversion=1.3-SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) example:example:jar:1.0-SNAPSHOT
2) org.fusesource.stompjms:stompjms-client:jar:1.0-SNAPSHOT
3) org.fusesource.hawtbuf:hawtbuf:jar:1.3-SNAPSHOT
----------
1 required artifact is missing.
for artifact:
example:example:jar:1.0-SNAPSHOT
from the specified remote repositories:
central (http://repo1.maven.org/maven2),
Fusesource Snapshots
(http://repo.fusesource.com/nexus/content/repositories/snapshots)
Oh good grief.
A simple README document should provide new users a deterministic,
step-by-step guide so that they know exactly what commands to run and
what to expect from those commands. I had to do a fair amount of
meandering to figure out how to get the broker running.
Are you sure you want to label this as a beta release? This should be
an alpha release, i.e., allow developers to kick the tires, make it
clear that it is not polished yet. I'm willing to help contribute to
these items, but this will take some time. I don't think that it
should be labeled as a beta release.
Just my $.02.
Bruce
--
perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'
ActiveMQ in Action: http://bit.ly/2je6cQ
Blog: http://bruceblog.org/
Twitter: http://twitter.com/brucesnyder
Re: [VOTE] Release Apollo 1.0 Beta 1 (2nd Attempt)
Posted by Gary Tully <ga...@gmail.com>.
+1
was able to get up and running with just the command line help. nice :-)
On 1 April 2011 16:57, Hiram Chirino <hi...@hiramchirino.com> wrote:
> Hi all,
>
> The first release attempt had a fatal flaw (it did not run properly on
> linux) so I've recut a
> Apollo 1.0 beta 1 release candiate which addresses that issue.
>
> The new release candidate has been staged to nexus under:
> https://repository.apache.org/content/repositories/orgapacheactivemq-059/
>
> Binary distros can be found at:
> https://repository.apache.org/content/repositories/orgapacheactivemq-059/org/apache/activemq/apache-apollo/1.0-beta1/
>
> Source code distros can be found at:
> https://repository.apache.org/content/repositories/orgapacheactivemq-059/org/apache/activemq/apollo-project/1.0-beta1/
>
> The build was tagged at:
> http://svn.apache.org/repos/asf/activemq/activemq-apollo/tags/apollo-project-1.0-beta1/
>
> The project website for that version has been staged to:
> http://activemq.apache.org/apollo/versions/1.0-beta1/website/index.html
>
> Please vote to approve this release
>
> [ ] +1 Release the binary as Apache ActiveMQ 5.5.0
> [ ] -1 Veto the release (provide specific comments)
>
> Here's my +1
>
>
> Regards,
> Hiram
>
> FuseSource
> Web: http://fusesource.com/
>
--
http://blog.garytully.com
http://fusesource.com