Jenkins build is unstable: ActiveMQ » ActiveMQ :: Web Demo #678

See https://builds.apache.org/job/ActiveMQ/org.apache.activemq$activemq-web-demo/678/

Jenkins build is unstable: ActiveMQ » ActiveMQ :: Spring #678

See https://builds.apache.org/job/ActiveMQ/org.apache.activemq$activemq-spring/678/

Jenkins build is unstable: ActiveMQ » ActiveMQ :: Core #678

See https://builds.apache.org/job/ActiveMQ/org.apache.activemq$activemq-core/678/changes

Build failed in Jenkins: ActiveMQ #678

See https://builds.apache.org/job/ActiveMQ/678/changes Changes: [gtully] https://issues.apache.org/jira/browse/AMQ-3289 - fix missing dummy arg for blob in initial insert [tabish] fix for: https://issues.apache.org/jira/browse/AMQ-2524 When destinations are removed via JMX or by auto remove

[jira] [Created] (AMQ-3381) Connections web console page shows two rows per connection (one empty)

Connections web console page shows two rows per connection (one empty) -- Key: AMQ-3381 URL: https://issues.apache.org/jira/browse/AMQ-3381 Project: ActiveMQ Issue Type:

[jira] [Resolved] (AMQ-3381) Connections web console page shows two rows per connection (one empty)

[ https://issues.apache.org/jira/browse/AMQ-3381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dejan Bosanac resolved AMQ-3381. Resolution: Fixed Fixed with svn revision 1141034 Connections web console page shows two rows per

Apollo queue browsing violates the STOMP 1.1 spec

Hiram, The end of browse message used in Apollo's queue browsing: MESSAGE subscription:mysub browser:end violates the STOMP 1.1 specification since it does not contain two of the mandatory MESSAGE fields: message-id and destination. A strict STOMP library (such as mine) could reject such

[jira] [Commented] (AMQ-3373) Pure master/slave connection state error on the master machine.

[ https://issues.apache.org/jira/browse/AMQ-3373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13057185#comment-13057185 ] Jose Guerra commented on AMQ-3373: -- Hi, It was just to add a the master log since the

[jira] [Issue Comment Edited] (AMQ-3373) Pure master/slave connection state error on the master machine.

[ https://issues.apache.org/jira/browse/AMQ-3373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13057185#comment-13057185 ] Jose Guerra edited comment on AMQ-3373 at 6/29/11 11:51 AM: Hi,

Apollo selector vs. STOMP header fields

Hiram, I've tested the message selectors in Apollo and they seem to work fine for some header fields. However, they seem to fail with fields containing a dash. What I see is identical to what is seen in ActiveMQ, see https://issues.apache.org/jira/browse/AMQ-3355. Are header fields containing a

Re: Apollo selector vs. STOMP header fields

Yeah.. we started off with the same selector parser so we will end up with the same issues. I've opened up: https://issues.apache.org/jira/browse/APLO-59 Regards, Hiram FuseSource Web: http://fusesource.com/ On Wed, Jun 29, 2011 at 8:18 AM, Lionel Cons lionel.c...@cern.ch wrote: Hiram,

Re: Apollo queue browsing violates the STOMP 1.1 spec

Opened: https://issues.apache.org/jira/browse/APLO-58 Regards, Hiram FuseSource Web: http://fusesource.com/ On Wed, Jun 29, 2011 at 7:44 AM, Lionel Cons lionel.c...@cern.ch wrote: Hiram, The end of browse message used in Apollo's queue browsing:  MESSAGE  subscription:mysub  

[jira] [Assigned] (AMQ-2922) Add ability for KahaDB log files to be created on a per-destination basis.

[ https://issues.apache.org/jira/browse/AMQ-2922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully reassigned AMQ-2922: --- Assignee: Gary Tully Add ability for KahaDB log files to be created on a per-destination basis.

[jira] [Closed] (AMQ-1198) implement a Stomp client transport for ActiveMQ so we have a JMS client that talks Stomp like NMS

[ https://issues.apache.org/jira/browse/AMQ-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-1198. - Resolution: Won't Fix The StompJMS java client can handle this as it supports operation with Stomp 1.0

[jira] [Closed] (AMQ-1312) SpringIDE extension plugin for configuration namespace

[ https://issues.apache.org/jira/browse/AMQ-1312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-1312. - Resolution: Won't Fix Fix Version/s: (was: 5.6.0) OBE SpringIDE extension plugin for

[jira] [Closed] (AMQ-1718) broker don't delivery message to consumer

[ https://issues.apache.org/jira/browse/AMQ-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-1718. - Resolution: Incomplete Fix Version/s: (was: NEEDS_REVIEWED) Not test case or additional

[jira] [Closed] (AMQ-1806) Selectors are not working properly

[ https://issues.apache.org/jira/browse/AMQ-1806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-1806. - Resolution: Incomplete Fix Version/s: (was: NEEDS_REVIEWED) Issue lacks a test case to validate

[jira] [Resolved] (AMQ-1906) create ProducerViewMBean so we can see producer activity in JMX

[ https://issues.apache.org/jira/browse/AMQ-1906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-1906. --- Resolution: Fixed Fix Version/s: (was: NEEDS_REVIEWED) 5.6.0 This issue

[jira] [Closed] (AMQ-2031) Intermittent test failure - InactivityMonitorTest

[ https://issues.apache.org/jira/browse/AMQ-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-2031. - Resolution: Cannot Reproduce Test is passing consistently in Jenkins builds as well as locally.

[jira] [Commented] (AMQ-2126) Expired messages not being removed from the queue

[ https://issues.apache.org/jira/browse/AMQ-2126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13057249#comment-13057249 ] Timothy Bish commented on AMQ-2126: --- Automatic removal of expired messages was implemented

[jira] [Closed] (AMQ-2126) Expired messages not being removed from the queue

[ https://issues.apache.org/jira/browse/AMQ-2126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-2126. - Resolution: Fixed Expired messages not being removed from the queue

[jira] [Closed] (AMQ-1941) Broker hangs on a STOMP client asking for receipts

[ https://issues.apache.org/jira/browse/AMQ-1941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-1941. - Resolution: Cannot Reproduce Not able to reproduce this on a 5.5 broker. Broker hangs on a STOMP client

[jira] [Resolved] (AMQ-2301) Connection view in ActiveMQ web console lists empty lines.

[ https://issues.apache.org/jira/browse/AMQ-2301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-2301. --- Resolution: Duplicate This issue is fixed by AMQ-3381 Connection view in ActiveMQ web console lists

[jira] [Closed] (AMQ-2294) MessageProducer hangs when using many concurrent sessions

[ https://issues.apache.org/jira/browse/AMQ-2294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-2294. - Resolution: Incomplete Need a test case to help reproduce this, reopen if its still an issue

[jira] [Created] (AMQ-3382) staticallyIncludedDestinations should always be forwarded

staticallyIncludedDestinations should always be forwarded -- Key: AMQ-3382 URL: https://issues.apache.org/jira/browse/AMQ-3382 Project: ActiveMQ Issue Type: Bug Affects Versions:

[jira] [Resolved] (AMQ-3382) staticallyIncludedDestinations should always be forwarded

[ https://issues.apache.org/jira/browse/AMQ-3382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dejan Bosanac resolved AMQ-3382. Resolution: Fixed Fixed with svn revision 1141124 staticallyIncludedDestinations should always be

[jira] [Closed] (AMQ-2517) Client stops receiving messages from topic after about 30 minutes of inactivity

[ https://issues.apache.org/jira/browse/AMQ-2517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-2517. - Resolution: Cannot Reproduce This could be related to issues that were fixed in the NMS client. Reopen if

[jira] [Commented] (AMQ-3375) stomp consumer might not receive all msgs of a queue

[ https://issues.apache.org/jira/browse/AMQ-3375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13057380#comment-13057380 ] Timothy Bish commented on AMQ-3375: --- A reliable way to make this test case always pass is

[jira] [Commented] (AMQ-3290) Wire format negotiation timeout: peer did not send his wire format

[ https://issues.apache.org/jira/browse/AMQ-3290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13057397#comment-13057397 ] Timothy Bish commented on AMQ-3290: --- You should attempt to create a test case to

[jira] [Closed] (AMQ-3243) prioritizedMessages=false does not disable message ordering of prioritized topic messages

[ https://issues.apache.org/jira/browse/AMQ-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-3243. - Resolution: Not A Problem Issue seems to be related to configuration of the client, no input from the

Jenkins build is still unstable: ActiveMQ » ActiveMQ :: Spring #679

See https://builds.apache.org/job/ActiveMQ/org.apache.activemq$activemq-spring/679/

Jenkins build is still unstable: ActiveMQ » ActiveMQ :: Core #679

See https://builds.apache.org/job/ActiveMQ/org.apache.activemq$activemq-core/changes

Jenkins build is still unstable: ActiveMQ » ActiveMQ :: Web Demo #679

See https://builds.apache.org/job/ActiveMQ/org.apache.activemq$activemq-web-demo/679/

Jenkins build is unstable: ActiveMQ #679

See https://builds.apache.org/job/ActiveMQ/679/changes

[jira] [Updated] (AMQ-3383) Add a string property (token) to ConnectionControl so the broker could potentially communicate a security token to a client after it authenticates

[ https://issues.apache.org/jira/browse/AMQ-3383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stan Lewis updated AMQ-3383: Attachment: AMQ-3383.diff Add a string property (token) to ConnectionControl so the broker could

[jira] [Created] (AMQ-3383) Add a string property (token) to ConnectionControl so the broker could potentially communicate a security token to a client after it authenticates

Add a string property (token) to ConnectionControl so the broker could potentially communicate a security token to a client after it authenticates --

[jira] [Commented] (AMQ-2565) Consumer skips messages in a queue when invoked from another queue

[ https://issues.apache.org/jira/browse/AMQ-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13057477#comment-13057477 ] Timothy Bish commented on AMQ-2565: --- The test fails because the JMSTemplate creates a new

[jira] [Closed] (AMQ-2593) Slow cunsumer

[ https://issues.apache.org/jira/browse/AMQ-2593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-2593. - Resolution: Cannot Reproduce Closed for now, if problem reoccurs using a current release please reopen.

[jira] [Closed] (AMQ-2703) Mix of Persistent and Non-Persistent producers on the same queue breaks producer flow control

[ https://issues.apache.org/jira/browse/AMQ-2703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-2703. - Resolution: Cannot Reproduce Unable to reproduce this using current release. Mix of Persistent and

[jira] [Closed] (AMQ-2759) Nullpointer-Exception in Queue.send

[ https://issues.apache.org/jira/browse/AMQ-2759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-2759. - Resolution: Incomplete Not enough information to reproduce or test the issue. Nullpointer-Exception in

[jira] [Closed] (AMQ-2778) Memory leak with ManagedRegionBroker

[ https://issues.apache.org/jira/browse/AMQ-2778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-2778. - Resolution: Incomplete Not test case or information allowing this to be tested or reproduced. Memory

[jira] [Resolved] (AMQ-2783) Need to add an extra property to record reason for persistent messages in the DeadLetter queue

[ https://issues.apache.org/jira/browse/AMQ-2783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-2783. --- Resolution: Fixed This issue is fixed by AMQ-3236 Need to add an extra property to record reason for

[jira] [Closed] (AMQ-2820) Deadlock occur in the RegionBroker.java when remove stale connection

[ https://issues.apache.org/jira/browse/AMQ-2820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-2820. - Resolution: Not A Problem works as designed. Deadlock occur in the RegionBroker.java when remove stale

[VOTE] Release Apache Apollo 1.0 Beta 4

Hi Everyone, It's been several weeks since the last Apollo beta release. Since then several new and noteworthy features have been implementing including: * APLO-17 - Support message expiration * APLO-39 - Apply configuration updates to a broker without needing a restart * APLO-40 - Web

[jira] [Commented] (AMQ-3383) Add a string property (token) to ConnectionControl so the broker could potentially communicate a security token to a client after it authenticates

[ https://issues.apache.org/jira/browse/AMQ-3383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13057513#comment-13057513 ] Timothy Bish commented on AMQ-3383: --- Would it make more sense here to use a byte array

[jira] [Resolved] (AMQ-2858) ConnectionInfo does not override toString to stop logging actual Password in case of Warning.

[ https://issues.apache.org/jira/browse/AMQ-2858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-2858. --- Resolution: Fixed Fix Version/s: 5.3.1 Fixed by AMQ-2499 The IntrospectionSupport class maps

Re: Apollo schema validation

Done. You should add an validation='strict' attribute to the broker element to auto stop a broker which has an XML file which has validation errors. Regards, Hiram FuseSource Web: http://fusesource.com/ On Tue, Jun 21, 2011 at 6:45 AM, Hiram Chirino hi...@hiramchirino.com wrote: Ok that

[jira] [Closed] (AMQ-2918) ActiveMQMapMessage stay in memory causing leaks

[ https://issues.apache.org/jira/browse/AMQ-2918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-2918. - Resolution: Incomplete No test case provided and I can't reproduce any leaks using the information given.

[jira] [Commented] (AMQ-2947) After a performance the server stop working. No errors send to the client.

[ https://issues.apache.org/jira/browse/AMQ-2947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13057521#comment-13057521 ] Timothy Bish commented on AMQ-2947: --- Do you have a test case for this that can reproduce

[jira] [Closed] (AMQ-2951) Connection reset by peer Exception in Stomp in Linux (in Windows Ok...) wenn Client führt connection.disconnect() sofort nach connection.send(..); connection.commit(..) ohn

[ https://issues.apache.org/jira/browse/AMQ-2951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-2951. - Resolution: Not A Problem Given the description it sounds like a timing issue where the broker is still

[jira] [Commented] (AMQ-2974) Set ClientID - InvalidClientIDException with stomp

[ https://issues.apache.org/jira/browse/AMQ-2974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13057532#comment-13057532 ] Timothy Bish commented on AMQ-2974: --- ActiveMQ 5.x implements Stomp 1.0 which has no

[jira] [Closed] (AMQ-2991) ActiveMQ leaks memory for a typical request/response pattern (temporary queues)

[ https://issues.apache.org/jira/browse/AMQ-2991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-2991. - Resolution: Not A Problem Working as designed. A temp destination exists for the life of the Connection.

[jira] [Resolved] (AMQ-3214) InactivityMonitor Async Task threads leaking

[ https://issues.apache.org/jira/browse/AMQ-3214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-3214. --- Resolution: Fixed Added the call to allowCoreThreadTimeOut(true) since it shouldn't affect the code

[jira] [Closed] (AMQ-3232) Where is the subversion Id for a 5.5 SNAPSHOT?

[ https://issues.apache.org/jira/browse/AMQ-3232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-3232. - Resolution: Won't Fix The current release process doesn't track the SVN rev for a SNAPSHOT build as these

Re: [VOTE] Release Apache Apollo 1.0 Beta 4

+1 On Wed, Jun 29, 2011 at 3:10 PM, Hiram Chirino hi...@hiramchirino.comwrote: Hi Everyone, It's been several weeks since the last Apollo beta release. Since then several new and noteworthy features have been implementing including: * APLO-17 - Support message expiration * APLO-39 -