Re: Message Priority test

get it connection.MessagePrioritySupported = true -- View this message in context: http://activemq.2283324.n4.nabble.com/Message-Priority-test-tp4723158p4723280.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

Message Priority test

import javax.jms.Connection; import javax.jms.ConnectionFactory; import javax.jms.Destination; import javax.jms.JMSException; import javax.jms.Message; import javax.jms.MessageConsumer; import javax.jms.MessageListener; import javax.jms.MessageProducer; import javax.jms.Session; import javax.jms.Te

[jira] [Commented] (AMQ-5733) kill -9 always results in failure signal

[ https://issues.apache.org/jira/browse/AMQ-5733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14504480#comment-14504480 ] James Green commented on AMQ-5733: -- Briefly reading http://stackoverflow.com/quest

[jira] [Commented] (AMQ-5733) kill -9 always results in failure signal

[ https://issues.apache.org/jira/browse/AMQ-5733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14503023#comment-14503023 ] James Green commented on AMQ-5733: -- Also, after using kill we do not erase the PID

[jira] [Created] (AMQ-5733) kill -9 always results in failure signal

James Green created AMQ-5733: Summary: kill -9 always results in failure signal Key: AMQ-5733 URL: https://issues.apache.org/jira/browse/AMQ-5733 Project: ActiveMQ Issue Type: Bug

Efforts to construct distribution binaries?

Speaking as someone who has had to use fpm to create a .deb from the ActiveMQ zip, is there any effort under way or planned to automate this as part of the build / release process? Thanks, James

Re: [VOTE] Apache ActiveMQ 5.11.0

Are you aware that the list of resolved issues includes issues marked "Unresolved"? See AMQ-5217 and AMQ-5537 for instance. On 27 January 2015 at 11:37, Krzysztof Sobkowiak wrote: > Hi > > +1 (non-

Re: Doc page and bug

I've updated the page having found a note from Gary Tully confirming it. Suggest the api usage matter also reported should become a bug. On 17 September 2014 13:47, N B wrote: > Hi all, > > At work we were looking for a solution to get the scheduled folder shared > between two brokers. It failed

Re: ActiveMQ web console localization

My understanding is that the web console will likely be superseded with a non-hosted solution. Such a solution already exists with AMQ 5.8.0+ in that it ships with Jolokia which can be connected to by hawt.io. On 23 September 2014 16:07, abelov wrote: > Good day! > > Is it possible to use differ

[jira] [Created] (AMQ-5285) Add Debian packaging to end of build pipeline

James Green created AMQ-5285: Summary: Add Debian packaging to end of build pipeline Key: AMQ-5285 URL: https://issues.apache.org/jira/browse/AMQ-5285 Project: ActiveMQ Issue Type: Task

[jira] [Commented] (AMQ-4805) IllegalStateException during thread.Scheduler.schedualPeriodically

[ https://issues.apache.org/jira/browse/AMQ-4805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13895209#comment-13895209 ] Brandon Green commented on AMQ-4805: We also just started seeing this same error in

[jira] [Created] (AMQNET-466) Nuget Apache.NMS.ActiveMQ 1.6.2 built against higher version of Apache.NMS than available

Brandon Green created AMQNET-466: Summary: Nuget Apache.NMS.ActiveMQ 1.6.2 built against higher version of Apache.NMS than available Key: AMQNET-466 URL: https://issues.apache.org/jira/browse/AMQNET-466

[jira] [Resolved] (AMQ-4141) Semi-stuck queue until server restart

[ https://issues.apache.org/jira/browse/AMQ-4141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Green resolved AMQ-4141. -- Resolution: Not A Problem Marking this resolved. We did two things to resolve our case: 1. We increased

[jira] [Commented] (AMQ-4141) Semi-stuck queue until server restart

[ https://issues.apache.org/jira/browse/AMQ-4141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13486138#comment-13486138 ] James Green commented on AMQ-4141: -- One of the dispatch servers is now queueing mess

[jira] [Created] (AMQ-4141) Semi-stuck queue until server restart

James Green created AMQ-4141: Summary: Semi-stuck queue until server restart Key: AMQ-4141 URL: https://issues.apache.org/jira/browse/AMQ-4141 Project: ActiveMQ Issue Type: Bug

Unable to build (SelectorParser not found)

I have the SVN anonymous check-out and imported into IntelliJ. Trying to build but apparently the following package is not found: import org.apache.activemq.selector.SelectorParser; When I look, all I find is an activemq > selector > Package.html whereas the other packages have .java source files

[jira] [Created] (AMQ-3852) Stomp transport allows durable topic subscriber to subscribe to a queue

James Green created AMQ-3852: Summary: Stomp transport allows durable topic subscriber to subscribe to a queue Key: AMQ-3852 URL: https://issues.apache.org/jira/browse/AMQ-3852 Project: ActiveMQ

[jira] [Created] (AMQ-3540) gcInactiveDestinations causes data loss

11.04 64-bit java version "1.6.0_22" OpenJDK Runtime Environment (IcedTea6 1.10.2) (6b22-1.10.2-0ubuntu1~11.04.1) OpenJDK Client VM (build 20.0-b11, mixed mode, sharing) Reporter: James Green With gcInactiveDestinations switched on we (two staffers testing) noticed some mes

[jira] [Commented] (AMQ-3453) Tool for reading messages in journal files

[ https://issues.apache.org/jira/browse/AMQ-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13085781#comment-13085781 ] James Green commented on AMQ-3453: -- http://activemq.2283324.n4.nabble.com/KahaDB-sto

[jira] [Commented] (AMQ-3424) AMQ data dir not cleaning up even after messages getting consumed.

[ https://issues.apache.org/jira/browse/AMQ-3424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13073468#comment-13073468 ] James Green commented on AMQ-3424: -- This was a known issue that was fixed in the

[jira] [Created] (AMQ-3392) Doc change to http://activemq.apache.org/javalangoutofmemory.html

Components: Documentation Reporter: James Green Priority: Trivial The bullet points could I think be clearer: -Xmx: If your OS has more available memory, consider increasing the total heap memory available to the broker JVM. Note that the JVM will require

[jira] [Commented] (AMQ-2923) Clients are sent messages out of producer-order

[ https://issues.apache.org/jira/browse/AMQ-2923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13059490#comment-13059490 ] James Green commented on AMQ-2923: -- This is a non-issue, having discussed the stomp

[jira] [Commented] (AMQ-2879) Queues and Topics are becoming confused

[ https://issues.apache.org/jira/browse/AMQ-2879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13059423#comment-13059423 ] James Green commented on AMQ-2879: -- May as well close this issue - I originally repo

[jira] [Created] (AMQ-3349) Web console tooltips should not have transparent background

Versions: 5.5.0 Reporter: James Green Priority: Trivial When viewing AMQ through the web console, you can hover over many items for a tooltip to be shown. Problem is the background is partly transparent which makes the foreground text in many places almost unreadable

[jira] [Created] (AMQ-3269) ACTIVEMQ_OPTS_MEMORY is ignored

ACTIVEMQ_OPTS_MEMORY is ignored --- Key: AMQ-3269 URL: https://issues.apache.org/jira/browse/AMQ-3269 Project: ActiveMQ Issue Type: Bug Affects Versions: 5.5.0 Reporter: James Green

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

: Ubuntu Linux Reporter: James Green Priority: Minor See http://activemq.2283324.n4.nabble.com/Setup-writes-wrong-default-JMX-port-td3425002.html for the question and request for JIRA issue. Change the line: ACTIVEMQ_SUNJMX_START="-Dcom.sun.management.jmxremote.port=

[jira] Commented: (AMQ-2736) KahaDB doesn't clean up old files

[ https://issues.apache.org/jira/browse/AMQ-2736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12985827#action_12985827 ] James Green commented on AMQ-2736: -- Hmm something's not right on our 5.4.2 instan

[jira] Updated: (AMQ-2923) Clients are sent messages out of producer-order

[ https://issues.apache.org/jira/browse/AMQ-2923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Green updated AMQ-2923: - Component/s: Broker Switching component to 'broker'. Having switched on full broker debugging

[jira] Commented: (AMQ-2923) Clients are sent messages out of producer-order

[ https://issues.apache.org/jira/browse/AMQ-2923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978788#action_12978788 ] James Green commented on AMQ-2923: -- With concurrentStoreAndDispatchQueues="false&q

[jira] Updated: (AMQ-2923) Clients are sent messages out of producer-order

[ https://issues.apache.org/jira/browse/AMQ-2923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Green updated AMQ-2923: - Affects Version/s: 5.4.1 5.4.2 > Clients are sent messages out of producer-or

[jira] Updated: (AMQ-2923) Clients are sent messages out of producer-order

[ https://issues.apache.org/jira/browse/AMQ-2923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Green updated AMQ-2923: - Attachment: amq.gif Screenshot showing web console with messages listed out of order. Notice 90 seconds

[jira] Commented: (AMQ-2923) Clients are sent messages out of producer-order

[ https://issues.apache.org/jira/browse/AMQ-2923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978763#action_12978763 ] James Green commented on AMQ-2923: -- Issue is still present in 5.4.2. I am about to try

[jira] Created: (AMQ-3060) java.lang.ClassCastException: org.apache.activemq.broker.region.QueueSubscription cannot be cast to org.apache.activemq.broker.region.DurableTopicSubscription

-- Key: AMQ-3060 URL: https://issues.apache.org/jira/browse/AMQ-3060 Project: ActiveMQ Issue Type: Improvement Affects Versions: 5.4.1 Reporter: James Green I've been asked to create an issue about

[jira] Created: (AMQ-3057) Transport failed: java.net.SocketException: Connection reset

Versions: 5.4.1 Environment: Ubuntu 9.04 Reporter: James Green Had a report that some of our application services were inactive. Found this in the logs of an affected server: 2010-11-29 09:49:26,323 | INFO | Transport failed: java.net.SocketException: Connection reset

[jira] Commented: (AMQ-3042) Default broker name to be machine's hostname

[ https://issues.apache.org/activemq/browse/AMQ-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63405#action_63405 ] James Green commented on AMQ-3042: -- Which is why the AMQ config itself needs to be neu

[jira] Created: (AMQ-3042) Default broker name to be machine's hostname

roker Affects Versions: 5.4.1 Reporter: James Green Priority: Trivial In many scenarios, including ours, there is one AMQ broker per host. They connect to each other but must have unique brokerName values. It would therefore make sense to send into AMQ at launch the current hos

[jira] Created: (AMQ-3001) Ghost durable topic subscribers

Reporter: James Green Priority: Minor Listed on the Durable Topic Subscribers within the web interface I now have: Client ID: NC_ubuntu_inbound_blofeld Subscription Name: NC-DS_blofeld_Account.Requests Connection ID: ID:blofeld-37576-1288168498890-3:1 I did have a subscription

[jira] Commented: (AMQ-2780) ActiveMQ not preserving Message Order

[ https://issues.apache.org/activemq/browse/AMQ-2780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61872#action_61872 ] James Green commented on AMQ-2780: -- This might be the same as my newly-posted AMQ-

[jira] Updated: (AMQ-2923) Clients are sent messages out of producer-order

[ https://issues.apache.org/activemq/browse/AMQ-2923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Green updated AMQ-2923: - Summary: Clients are sent messages out of producer-order (was: Clients are send messages out of

[jira] Updated: (AMQ-2923) Clients are send messages out of producer-order

[ https://issues.apache.org/activemq/browse/AMQ-2923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Green updated AMQ-2923: - Attachment: stomp.log Stomp trace showing a two messages received to a single queue, being sent in

[jira] Created: (AMQ-2923) Clients are send messages out of producer-order

Environment: Ubuntu 10.04. Reporter: James Green Priority: Critical On a single host: Producer P1 posts message M1 to Queue Q. Producer P2 posts message M2 to Queue Q a few seconds later. Consumer C1 comes a few seconds further along along and begins reading from Queue Q

[jira] Created: (AMQ-2879) Queues and Topics are becoming confused

10.04 Intel 64. ii sun-java6-bin 6.20dlj-1ubuntu3 Sun Java(TM) Runtime Environment (JRE) 6 (ar ii sun-java6-jre 6.20dlj-1ubuntu3 Sun Java(TM) Runtime Environment (JRE) 6 (ar Reporter: James Green We have a hub

[jira] Commented: (AMQ-2808) connection blocked when using stomp or stomp+ssl

[ https://issues.apache.org/activemq/browse/AMQ-2808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61041#action_61041 ] James Green commented on AMQ-2808: -- I think I'm seeing this issue. For me I ha

[jira] Issue Comment Edited: (AMQ-2808) connection blocked when using stomp or stomp+ssl

[ https://issues.apache.org/activemq/browse/AMQ-2808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61041#action_61041 ] James Green edited comment on AMQ-2808 at 8/3/10 10:12 AM: --- I t