Build failed in Jenkins: ActiveMQ-Apollo #171

See -- [...truncated 1032 lines...] A apollo-dto/src/main/java/org/apache/activemq/apollo/dto/StompDTO.java A apollo-dto/src/main/java/org/apache/activemq/apollo/dto/BrokerAclDTO.ja

Build failed in Jenkins: ActiveMQ-Apollo-Deploy #77

See -- Started by an SCM change Building remotely on ubuntu2 FATAL: cannot assign instance of hudson.model.StreamBuildListener to field hudson.scm.subversion.WorkspaceUpdater$UpdateTask.liste

Build failed in Jenkins: ActiveMQ-Apollo #170

See -- Started by an SCM change Building remotely on ubuntu2 FATAL: cannot assign instance of hudson.model.StreamBuildListener to field hudson.scm.subversion.WorkspaceUpdater$UpdateTask.listener of

Build failed in Jenkins: ActiveMQ-Trunk-Deploy #275

See -- Started by user gtully Building remotely on ubuntu2 FATAL: cannot assign instance of hudson.model.StreamBuildListener to field hudson.scm.subversion.WorkspaceUpdater$UpdateTask.listene

Re: [VOTE] Release Apollo 1.0 Beta 1 (2nd Attempt)

+1 on the Getting Started guides. I like that style of layered approach. On Mon, Apr 4, 2011 at 8:54 AM, Bruce Snyder wrote: > On Mon, Apr 4, 2011 at 7:45 AM, Hiram Chirino > wrote: > > Yeah I guess the gettings started guide is complicated by a couple of > > extra steps. > > > > I think once

[jira] [Resolved] (AMQCPP-360) C Runtime Error when a consumer is created for Advisory messages on "ActiveMQ.Advisory.Connection" topic

[ https://issues.apache.org/jira/browse/AMQCPP-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQCPP-360. - Resolution: Cannot Reproduce Can't reproduce this one, reopen if you can provide a test case that

[jira] [Commented] (AMQCPP-360) C Runtime Error when a consumer is created for Advisory messages on "ActiveMQ.Advisory.Connection" topic

[ https://issues.apache.org/jira/browse/AMQCPP-360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015488#comment-13015488 ] Timothy Bish commented on AMQCPP-360: - Added a test case in trunk that creates a consu

Re: [VOTE] Release Apollo 1.0 Beta 1 (2nd Attempt)

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 f

Re: [VOTE] Release Apollo 1.0 Beta 1 (2nd Attempt)

On Mon, Apr 4, 2011 at 7:45 AM, Hiram Chirino 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

[jira] [Commented] (AMQ-3254) Can't use updateURIsURL, because the entry is missing in the xsd and so the activeMq instance cannot start

[ https://issues.apache.org/jira/browse/AMQ-3254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015463#comment-13015463 ] Claudio Corsi commented on AMQ-3254: Just do the following: This should work. > Can

Re: [VOTE] Release Apollo 1.0 Beta 1 (2nd Attempt)

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 B

Re: [VOTE] Release Apollo 1.0 Beta 1 (2nd Attempt)

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/br

[jira] [Created] (AMQ-3267) Make it able run Apollo without setting env variables

Make it able run Apollo without setting env variables - Key: AMQ-3267 URL: https://issues.apache.org/jira/browse/AMQ-3267 Project: ActiveMQ Issue Type: Improvement Components: Apo

[jira] [Created] (AMQ-3266) Remove SNAPSHOT dependencies from Apollo Java examples

Remove SNAPSHOT dependencies from Apollo Java examples -- Key: AMQ-3266 URL: https://issues.apache.org/jira/browse/AMQ-3266 Project: ActiveMQ Issue Type: Bug Components: Apollo

[jira] [Created] (AMQ-3265) Apollo listener examples should display a message when started

Apollo listener examples should display a message when started -- Key: AMQ-3265 URL: https://issues.apache.org/jira/browse/AMQ-3265 Project: ActiveMQ Issue Type: Improvement

[jira] [Created] (AMQ-3264) Add an "bin/apollo --help"

Add an "bin/apollo --help" -- Key: AMQ-3264 URL: https://issues.apache.org/jira/browse/AMQ-3264 Project: ActiveMQ Issue Type: Task Components: Apollo Reporter: Hiram Chirino Assignee:

[jira] [Resolved] (AMQ-3263) ActiveMQ LoggingBrokerPlugin too verbose

[ https://issues.apache.org/jira/browse/AMQ-3263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully resolved AMQ-3263. - Resolution: Fixed Fix Version/s: 5.6.0 patch applied with thanks in r http://svn.apache.org/viewvc?r

[jira] [Assigned] (AMQ-3263) ActiveMQ LoggingBrokerPlugin too verbose

[ https://issues.apache.org/jira/browse/AMQ-3263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully reassigned AMQ-3263: --- Assignee: Gary Tully > ActiveMQ LoggingBrokerPlugin too verbose > -

[jira] [Updated] (AMQ-3263) ActiveMQ LoggingBrokerPlugin too verbose

[ https://issues.apache.org/jira/browse/AMQ-3263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sargis Harutyunyan updated AMQ-3263: Description: Hi all, I am using Apache ActiveMQ v5.4.2-fuse-02-00 and I want to log events r

[jira] [Updated] (AMQ-3263) ActiveMQ LoggingBrokerPlugin too verbose

[ https://issues.apache.org/jira/browse/AMQ-3263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sargis Harutyunyan updated AMQ-3263: Description: Hi all, I am using Apache ActiveMQ v5.4.2-fuse-02-00 and I want to log events r

[jira] [Updated] (AMQ-3263) ActiveMQ LoggingBrokerPlugin too verbose

[ https://issues.apache.org/jira/browse/AMQ-3263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sargis Harutyunyan updated AMQ-3263: Description: Hi all, I am using Apache ActiveMQ v5.4.2-fuse-02-00 and I want to log events r

[jira] [Updated] (AMQ-3263) ActiveMQ LoggingBrokerPlugin too verbose

[ https://issues.apache.org/jira/browse/AMQ-3263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sargis Harutyunyan updated AMQ-3263: Attachment: logging_session_events.patch > ActiveMQ LoggingBrokerPlugin too verbose > ---

[jira] [Created] (AMQ-3263) ActiveMQ LoggingBrokerPlugin too verbose

ActiveMQ LoggingBrokerPlugin too verbose Key: AMQ-3263 URL: https://issues.apache.org/jira/browse/AMQ-3263 Project: ActiveMQ Issue Type: Improvement Components: Broker Affects Versions:

[jira] [Resolved] (AMQ-3262) Browser closed while iterating changes message delivery order

[ https://issues.apache.org/jira/browse/AMQ-3262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dejan Bosanac resolved AMQ-3262. Resolution: Fixed Fixed in svn revision 1088593 > Browser closed while iterating changes message del

[jira] [Created] (AMQ-3262) Browser closed while iterating changes message delivery order

Browser closed while iterating changes message delivery order - Key: AMQ-3262 URL: https://issues.apache.org/jira/browse/AMQ-3262 Project: ActiveMQ Issue Type: Bug Affects Versi

Re: [VOTE] Release Apollo 1.0 Beta 1 (2nd Attempt)

+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 APOLL

[jira] [Created] (AMQ-3261) setup writes incorrect jmx port

setup writes incorrect jmx port --- Key: AMQ-3261 URL: https://issues.apache.org/jira/browse/AMQ-3261 Project: ActiveMQ Issue Type: Bug Components: JMX Affects Versions: 5.5.0 Environment: U