Re: Missing STOMP connections and queues/destinations

test -- View this message in context: http://activemq.2283324.n4.nabble.com/Missing-STOMP-connections-and-queues-destinations-tp4654102p4654107.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

[jira] [Closed] (AMQ-3936) activemq status return codes should be LSB compliant

[ https://issues.apache.org/jira/browse/AMQ-3936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Mathews closed AMQ-3936. > activemq status return codes should be LSB compliant > ---

[jira] [Resolved] (AMQ-3936) activemq status return codes should be LSB compliant

[ https://issues.apache.org/jira/browse/AMQ-3936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Mathews resolved AMQ-3936. -- Resolution: Duplicate Fix Version/s: 5.7.0 > activemq status return codes should be LSB compli

[jira] [Commented] (AMQ-3936) activemq status return codes should be LSB compliant

[ https://issues.apache.org/jira/browse/AMQ-3936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13416580#comment-13416580 ] Ben Mathews commented on AMQ-3936: -- It does seem to be the same. > activem

[jira] [Commented] (AMQ-3931) Memory problems with large transactions

[ https://issues.apache.org/jira/browse/AMQ-3931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13416568#comment-13416568 ] Robert Voliva commented on AMQ-3931: Thanks Fengming, I went through all that documentat

[jira] [Commented] (AMQ-3936) activemq status return codes should be LSB compliant

[ https://issues.apache.org/jira/browse/AMQ-3936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13416555#comment-13416555 ] Timothy Bish commented on AMQ-3936: --- This looks like a duplicate of AMQ-3831 can you check

[jira] [Created] (AMQ-3936) activemq status return codes should be LSB compliant

Ben Mathews created AMQ-3936: Summary: activemq status return codes should be LSB compliant Key: AMQ-3936 URL: https://issues.apache.org/jira/browse/AMQ-3936 Project: ActiveMQ Issue Type: Bug

[jira] [Commented] (AMQ-3933) TransportConnection.dispatchQueue synchronized LinkedList to ConcurrentLinkedQueue

[ https://issues.apache.org/jira/browse/AMQ-3933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13416172#comment-13416172 ] Gary Tully commented on AMQ-3933: - can you attach your test or describe the nature of it?

[jira] [Closed] (AMQ-3926) jms.redeliveryPolicy.redeliveryDelay and jms.redeliveryPolicy.initialRedeliveryDelay options cause a failure on startup

[ https://issues.apache.org/jira/browse/AMQ-3926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-3926. - Resolution: Not A Problem using a non-existent setting is causing the issue. > jms.redeliv

[jira] [Resolved] (AMQ-3934) QueueViewMBean.getMessage throws NullPointerException when message not found

[ https://issues.apache.org/jira/browse/AMQ-3934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-3934. --- Resolution: Fixed Fix Version/s: 5.7.0 Assignee: Timothy Bish Patch applied with thanks

[jira] [Commented] (AMQ-796) Client may shtudown when failover connection is reconnecting. We need to maintain at least 1 non-daemon thread alive.

[ https://issues.apache.org/jira/browse/AMQ-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13416134#comment-13416134 ] Bhanu commented on AMQ-796: --- This issue still persists. attaching the jstack on broker. It still do

[jira] [Updated] (AMQ-796) Client may shtudown when failover connection is reconnecting. We need to maintain at least 1 non-daemon thread alive.

[ https://issues.apache.org/jira/browse/AMQ-796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhanu updated AMQ-796: -- Attachment: jstack_amq_5.6.0 > Client may shtudown when failover connection is reconnecting. We need to > maintain a

[jira] [Resolved] (AMQ-3935) JConsole browse() function does not work if useCache=false

[ https://issues.apache.org/jira/browse/AMQ-3935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully resolved AMQ-3935. - Resolution: Fixed fix in http://svn.apache.org/viewvc?rev=1362462&view=rev > JConsole brow

[jira] [Created] (AMQ-3935) JConsole browse() function does not work if useCache=false

Gary Tully created AMQ-3935: --- Summary: JConsole browse() function does not work if useCache=false Key: AMQ-3935 URL: https://issues.apache.org/jira/browse/AMQ-3935 Project: ActiveMQ Issue Type: Bug

[jira] [Comment Edited] (AMQ-3451) Tomcat 6.0.32 complains that ActiveMQ 5.5 doesn't shutdown a thread

[ https://issues.apache.org/jira/browse/AMQ-3451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13416089#comment-13416089 ] liny edited comment on AMQ-3451 at 7/17/12 11:13 AM: - @Gary Thanks for

[jira] [Comment Edited] (AMQ-3451) Tomcat 6.0.32 complains that ActiveMQ 5.5 doesn't shutdown a thread

[ https://issues.apache.org/jira/browse/AMQ-3451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13416089#comment-13416089 ] liny edited comment on AMQ-3451 at 7/17/12 11:11 AM: - @Gary Thanks for

[jira] [Commented] (AMQ-3451) Tomcat 6.0.32 complains that ActiveMQ 5.5 doesn't shutdown a thread

[ https://issues.apache.org/jira/browse/AMQ-3451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13416089#comment-13416089 ] liny commented on AMQ-3451: --- @Gary Thanks for reply. Directly call below method in my stop() stil

[jira] [Commented] (AMQ-3557) Performance of consumption with JDBC persistance and Microsoft SQL Server

[ https://issues.apache.org/jira/browse/AMQ-3557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13416048#comment-13416048 ] Torsten Mielke commented on AMQ-3557: - There was recently an improvement made to the JDB

[jira] [Commented] (AMQ-3451) Tomcat 6.0.32 complains that ActiveMQ 5.5 doesn't shutdown a thread

[ https://issues.apache.org/jira/browse/AMQ-3451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13416044#comment-13416044 ] Gary Tully commented on AMQ-3451: - @liny, thanks for that test case war. Peeking at the code

[jira] [Updated] (AMQ-3934) QueueViewMBean.getMessage throws NullPointerException when message not found

[ https://issues.apache.org/jira/browse/AMQ-3934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robin Kåveland Hansen updated AMQ-3934: --- Attachment: GetMessageNPETest.java This unit test demonstrates the issue.

[jira] [Updated] (AMQ-3934) QueueViewMBean.getMessage throws NullPointerException when message not found

[ https://issues.apache.org/jira/browse/AMQ-3934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robin Kåveland Hansen updated AMQ-3934: --- Attachment: amqpatch.diff This diff fixes the issue. > QueueViewMBean.

[jira] [Created] (AMQ-3934) QueueViewMBean.getMessage throws NullPointerException when message not found

Robin Kåveland Hansen created AMQ-3934: -- Summary: QueueViewMBean.getMessage throws NullPointerException when message not found Key: AMQ-3934 URL: https://issues.apache.org/jira/browse/AMQ-3934 Pr