[jira] [Commented] (AMQ-4237) JMX ObjectNames do not follow JMX Best practices to use a Hierarchical format
[
https://issues.apache.org/jira/browse/AMQ-4237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14225895#comment-14225895
]
Lionel Cons commented on AMQ-4237:
--
FWIW, here are the patterns we use in our monitoring. They only return
destinations, not consumers:
{code}
org.apache.activemq:type=Broker,brokerName=*,destinationType=Topic,destinationName=*
org.apache.activemq:type=Broker,brokerName=*,destinationType=Queue,destinationName=*
{code}
> JMX ObjectNames do not follow JMX Best practices to use a Hierarchical format
> -
>
> Key: AMQ-4237
> URL: https://issues.apache.org/jira/browse/AMQ-4237
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Broker
>Reporter: Rob Davies
>Assignee: Rob Davies
> Fix For: 5.8.0
>
>
> The Current JMX ObjectNames result in a disjointed view from JConsole of the
> managed objects and services of the ActiveMQ Broker. By following best
> practices, it will be easier to find and monitor all the endpoints associated
> with a Destination - for example.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMQ-5078) Typos in stomp/ProtocolConverter.java
[ https://issues.apache.org/jira/browse/AMQ-5078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lionel Cons updated AMQ-5078: - Attachment: ProtocolConverter.patch > Typos in stomp/ProtocolConverter.java > - > > Key: AMQ-5078 > URL: https://issues.apache.org/jira/browse/AMQ-5078 > Project: ActiveMQ > Issue Type: Bug >Reporter: Lionel Cons >Priority: Minor > Attachments: ProtocolConverter.patch > > > There are two typos in > activemq-stomp/src/main/java/org/apache/activemq/transport/stomp/ProtocolConverter.java > that are polluting my logs. I attach a patch to fix them. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (AMQ-5078) Typos in stomp/ProtocolConverter.java
Lionel Cons created AMQ-5078: Summary: Typos in stomp/ProtocolConverter.java Key: AMQ-5078 URL: https://issues.apache.org/jira/browse/AMQ-5078 Project: ActiveMQ Issue Type: Bug Reporter: Lionel Cons Priority: Minor There are two typos in activemq-stomp/src/main/java/org/apache/activemq/transport/stomp/ProtocolConverter.java that are polluting my logs. I attach a patch to fix them. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (AMQ-4963) Typo in journal-data.proto
[
https://issues.apache.org/jira/browse/AMQ-4963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lionel Cons updated AMQ-4963:
-
Description:
There seems to be a typo in
activemq-kahadb-store/src/main/proto/journal-data.proto. This file contains:
{code}
message KahaLocalTransactionId {
required string connection_id=1;
required int64 transaction_id=1;
}
{code}
The second field should be 2.
I wonder why the protobuf compiler does not complain about this. Maybe it
should be fixed to detect and complain about duplicate fields?
was:
There seems to be a typo in
activemq-kahadb-store/src/main/proto/journal-data.proto. This file contains:
message KahaLocalTransactionId {
required string connection_id=1;
required int64 transaction_id=1;
}
The second field should be 2.
I wonder why the protobuf compiler does not complain about this. Maybe it
should be fixed to detect and complain about duplicate fields?
> Typo in journal-data.proto
> --
>
> Key: AMQ-4963
> URL: https://issues.apache.org/jira/browse/AMQ-4963
> Project: ActiveMQ
> Issue Type: Bug
>Reporter: Lionel Cons
>
> There seems to be a typo in
> activemq-kahadb-store/src/main/proto/journal-data.proto. This file contains:
> {code}
> message KahaLocalTransactionId {
> required string connection_id=1;
> required int64 transaction_id=1;
> }
> {code}
> The second field should be 2.
> I wonder why the protobuf compiler does not complain about this. Maybe it
> should be fixed to detect and complain about duplicate fields?
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Created] (AMQ-4963) Typo in journal-data.proto
Lionel Cons created AMQ-4963:
Summary: Typo in journal-data.proto
Key: AMQ-4963
URL: https://issues.apache.org/jira/browse/AMQ-4963
Project: ActiveMQ
Issue Type: Bug
Reporter: Lionel Cons
There seems to be a typo in
activemq-kahadb-store/src/main/proto/journal-data.proto. This file contains:
message KahaLocalTransactionId {
required string connection_id=1;
required int64 transaction_id=1;
}
The second field should be 2.
I wonder why the protobuf compiler does not complain about this. Maybe it
should be fixed to detect and complain about duplicate fields?
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (AMQ-4943) Corrupted KahaDB store: java.lang.NegativeArraySizeException
[ https://issues.apache.org/jira/browse/AMQ-4943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13853837#comment-13853837 ] Lionel Cons commented on AMQ-4943: -- Is there any tool to attempt to recover messages from these corrupted KahaDB files that do not have cheksums? > Corrupted KahaDB store: java.lang.NegativeArraySizeException > > > Key: AMQ-4943 > URL: https://issues.apache.org/jira/browse/AMQ-4943 > Project: ActiveMQ > Issue Type: Bug > Environment: activemq-5.5.1-fuse-10-16 >Reporter: Lionel Cons >Priority: Critical > > One of our brokers went crazy and logged _many_ exceptions looking like this: > 2013-12-19 12:27:09,007 [BrokerService[foobar] Task-13] ERROR > AbstractStoreCursor - > org.apache.activemq.broker.region.cursors.QueueStorePrefetch@654e3615:Consumer.prod.whatever,batchResetNeeded=false,storeHasMessages=true,size=2461725,cacheEnabled=false,maxBatchSize:200 > - Failed to fill batch > java.lang.RuntimeException: java.io.IOException: Invalid location: 43153:28, > : java.lang.NegativeArraySizeException > at > org.apache.activemq.broker.region.cursors.AbstractStoreCursor.fillBatch(AbstractStoreCursor.java:277) > at > org.apache.activemq.broker.region.cursors.AbstractStoreCursor.reset(AbstractStoreCursor.java:110) > at > org.apache.activemq.broker.region.cursors.StoreQueueCursor.reset(StoreQueueCursor.java:157) > at > org.apache.activemq.broker.region.Queue.doPageInForDispatch(Queue.java:1746) > at > org.apache.activemq.broker.region.Queue.pageInMessages(Queue.java:1962) > at org.apache.activemq.broker.region.Queue.iterate(Queue.java:1470) > at > org.apache.activemq.thread.PooledTaskRunner.runTask(PooledTaskRunner.java:122) > at > org.apache.activemq.thread.PooledTaskRunner$1.run(PooledTaskRunner.java:43) > at > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) > at java.lang.Thread.run(Thread.java:662) > Caused by: java.io.IOException: Invalid location: 43153:28, : > java.lang.NegativeArraySizeException > at > org.apache.kahadb.journal.DataFileAccessor.readRecord(DataFileAccessor.java:94) > at org.apache.kahadb.journal.Journal.read(Journal.java:601) > at > org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:908) > at > org.apache.activemq.store.kahadb.KahaDBStore.loadMessage(KahaDBStore.java:1024) > at > org.apache.activemq.store.kahadb.KahaDBStore$KahaDBMessageStore$4.execute(KahaDBStore.java:552) > at org.apache.kahadb.page.Transaction.execute(Transaction.java:771) > at > org.apache.activemq.store.kahadb.KahaDBStore$KahaDBMessageStore.recoverNextMessages(KahaDBStore.java:541) > at > org.apache.activemq.store.ProxyMessageStore.recoverNextMessages(ProxyMessageStore.java:88) > at > org.apache.activemq.broker.region.cursors.QueueStorePrefetch.doFillBatch(QueueStorePrefetch.java:97) > at > org.apache.activemq.broker.region.cursors.AbstractStoreCursor.fillBatch(AbstractStoreCursor.java:274) > ... 10 more > 2013-12-19 12:27:09,007 [BrokerService[foobar] Task-13] ERROR Queue - Failed > to page in more queue messages > java.lang.RuntimeException: java.lang.RuntimeException: java.io.IOException: > Invalid location: 43153:28, : java.lang.NegativeArraySizeException > at > org.apache.activemq.broker.region.cursors.AbstractStoreCursor.reset(AbstractStoreCursor.java:113) > at > org.apache.activemq.broker.region.cursors.StoreQueueCursor.reset(StoreQueueCursor.java:157) > at > org.apache.activemq.broker.region.Queue.doPageInForDispatch(Queue.java:1746) > at > org.apache.activemq.broker.region.Queue.pageInMessages(Queue.java:1962) > at org.apache.activemq.broker.region.Queue.iterate(Queue.java:1470) > at > org.apache.activemq.thread.PooledTaskRunner.runTask(PooledTaskRunner.java:122) > at > org.apache.activemq.thread.PooledTaskRunner$1.run(PooledTaskRunner.java:43) > at > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) > at java.lang.Thread.run(Thread.java:662) > Caused by: java.lang.RuntimeException: java.io.IOException: Invalid location: > 43153:28, : java.lang.NegativeArraySizeException > at > org.apache.activemq.broker.region.cursors.AbstractStoreCursor.fillBatch(AbstractStoreCursor.java:277) > at > org.apache.activemq.broker.region.cursors.AbstractStoreCursor.reset(AbstractStoreCursor.java:110) > ... 9 more > Caused by: java.io.IOException: Invalid location: 43153:28, : >
[jira] [Commented] (AMQ-4943) Corrupted KahaDB store: java.lang.NegativeArraySizeException
[ https://issues.apache.org/jira/browse/AMQ-4943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13852925#comment-13852925 ] Lionel Cons commented on AMQ-4943: -- OK, we will try these options. Is there any way to tell ActiveMQ to check the current corrupted KahaDB store and use the files that are sane? I guess that checkForCorruptJournalFiles does nothing if there are no checksums in the first place, right? > Corrupted KahaDB store: java.lang.NegativeArraySizeException > > > Key: AMQ-4943 > URL: https://issues.apache.org/jira/browse/AMQ-4943 > Project: ActiveMQ > Issue Type: Bug > Environment: activemq-5.5.1-fuse-10-16 >Reporter: Lionel Cons >Priority: Critical > > One of our brokers went crazy and logged _many_ exceptions looking like this: > 2013-12-19 12:27:09,007 [BrokerService[foobar] Task-13] ERROR > AbstractStoreCursor - > org.apache.activemq.broker.region.cursors.QueueStorePrefetch@654e3615:Consumer.prod.whatever,batchResetNeeded=false,storeHasMessages=true,size=2461725,cacheEnabled=false,maxBatchSize:200 > - Failed to fill batch > java.lang.RuntimeException: java.io.IOException: Invalid location: 43153:28, > : java.lang.NegativeArraySizeException > at > org.apache.activemq.broker.region.cursors.AbstractStoreCursor.fillBatch(AbstractStoreCursor.java:277) > at > org.apache.activemq.broker.region.cursors.AbstractStoreCursor.reset(AbstractStoreCursor.java:110) > at > org.apache.activemq.broker.region.cursors.StoreQueueCursor.reset(StoreQueueCursor.java:157) > at > org.apache.activemq.broker.region.Queue.doPageInForDispatch(Queue.java:1746) > at > org.apache.activemq.broker.region.Queue.pageInMessages(Queue.java:1962) > at org.apache.activemq.broker.region.Queue.iterate(Queue.java:1470) > at > org.apache.activemq.thread.PooledTaskRunner.runTask(PooledTaskRunner.java:122) > at > org.apache.activemq.thread.PooledTaskRunner$1.run(PooledTaskRunner.java:43) > at > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) > at java.lang.Thread.run(Thread.java:662) > Caused by: java.io.IOException: Invalid location: 43153:28, : > java.lang.NegativeArraySizeException > at > org.apache.kahadb.journal.DataFileAccessor.readRecord(DataFileAccessor.java:94) > at org.apache.kahadb.journal.Journal.read(Journal.java:601) > at > org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:908) > at > org.apache.activemq.store.kahadb.KahaDBStore.loadMessage(KahaDBStore.java:1024) > at > org.apache.activemq.store.kahadb.KahaDBStore$KahaDBMessageStore$4.execute(KahaDBStore.java:552) > at org.apache.kahadb.page.Transaction.execute(Transaction.java:771) > at > org.apache.activemq.store.kahadb.KahaDBStore$KahaDBMessageStore.recoverNextMessages(KahaDBStore.java:541) > at > org.apache.activemq.store.ProxyMessageStore.recoverNextMessages(ProxyMessageStore.java:88) > at > org.apache.activemq.broker.region.cursors.QueueStorePrefetch.doFillBatch(QueueStorePrefetch.java:97) > at > org.apache.activemq.broker.region.cursors.AbstractStoreCursor.fillBatch(AbstractStoreCursor.java:274) > ... 10 more > 2013-12-19 12:27:09,007 [BrokerService[foobar] Task-13] ERROR Queue - Failed > to page in more queue messages > java.lang.RuntimeException: java.lang.RuntimeException: java.io.IOException: > Invalid location: 43153:28, : java.lang.NegativeArraySizeException > at > org.apache.activemq.broker.region.cursors.AbstractStoreCursor.reset(AbstractStoreCursor.java:113) > at > org.apache.activemq.broker.region.cursors.StoreQueueCursor.reset(StoreQueueCursor.java:157) > at > org.apache.activemq.broker.region.Queue.doPageInForDispatch(Queue.java:1746) > at > org.apache.activemq.broker.region.Queue.pageInMessages(Queue.java:1962) > at org.apache.activemq.broker.region.Queue.iterate(Queue.java:1470) > at > org.apache.activemq.thread.PooledTaskRunner.runTask(PooledTaskRunner.java:122) > at > org.apache.activemq.thread.PooledTaskRunner$1.run(PooledTaskRunner.java:43) > at > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) > at java.lang.Thread.run(Thread.java:662) > Caused by: java.lang.RuntimeException: java.io.IOException: Invalid location: > 43153:28, : java.lang.NegativeArraySizeException > at > org.apache.activemq.broker.region.cursors.AbstractStoreCursor.fillBatch(AbstractStoreCursor.java:277) > at > org.apache.activemq.broker.region.cursors.
[jira] [Commented] (AMQ-4943) Corrupted KahaDB store: java.lang.NegativeArraySizeException
[ https://issues.apache.org/jira/browse/AMQ-4943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13852911#comment-13852911 ] Lionel Cons commented on AMQ-4943: -- We do not set these parameters (yet). Is there a significant performance penalty in enabling checksumJournalFiles? > Corrupted KahaDB store: java.lang.NegativeArraySizeException > > > Key: AMQ-4943 > URL: https://issues.apache.org/jira/browse/AMQ-4943 > Project: ActiveMQ > Issue Type: Bug > Environment: activemq-5.5.1-fuse-10-16 >Reporter: Lionel Cons >Priority: Critical > > One of our brokers went crazy and logged _many_ exceptions looking like this: > 2013-12-19 12:27:09,007 [BrokerService[foobar] Task-13] ERROR > AbstractStoreCursor - > org.apache.activemq.broker.region.cursors.QueueStorePrefetch@654e3615:Consumer.prod.whatever,batchResetNeeded=false,storeHasMessages=true,size=2461725,cacheEnabled=false,maxBatchSize:200 > - Failed to fill batch > java.lang.RuntimeException: java.io.IOException: Invalid location: 43153:28, > : java.lang.NegativeArraySizeException > at > org.apache.activemq.broker.region.cursors.AbstractStoreCursor.fillBatch(AbstractStoreCursor.java:277) > at > org.apache.activemq.broker.region.cursors.AbstractStoreCursor.reset(AbstractStoreCursor.java:110) > at > org.apache.activemq.broker.region.cursors.StoreQueueCursor.reset(StoreQueueCursor.java:157) > at > org.apache.activemq.broker.region.Queue.doPageInForDispatch(Queue.java:1746) > at > org.apache.activemq.broker.region.Queue.pageInMessages(Queue.java:1962) > at org.apache.activemq.broker.region.Queue.iterate(Queue.java:1470) > at > org.apache.activemq.thread.PooledTaskRunner.runTask(PooledTaskRunner.java:122) > at > org.apache.activemq.thread.PooledTaskRunner$1.run(PooledTaskRunner.java:43) > at > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) > at java.lang.Thread.run(Thread.java:662) > Caused by: java.io.IOException: Invalid location: 43153:28, : > java.lang.NegativeArraySizeException > at > org.apache.kahadb.journal.DataFileAccessor.readRecord(DataFileAccessor.java:94) > at org.apache.kahadb.journal.Journal.read(Journal.java:601) > at > org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:908) > at > org.apache.activemq.store.kahadb.KahaDBStore.loadMessage(KahaDBStore.java:1024) > at > org.apache.activemq.store.kahadb.KahaDBStore$KahaDBMessageStore$4.execute(KahaDBStore.java:552) > at org.apache.kahadb.page.Transaction.execute(Transaction.java:771) > at > org.apache.activemq.store.kahadb.KahaDBStore$KahaDBMessageStore.recoverNextMessages(KahaDBStore.java:541) > at > org.apache.activemq.store.ProxyMessageStore.recoverNextMessages(ProxyMessageStore.java:88) > at > org.apache.activemq.broker.region.cursors.QueueStorePrefetch.doFillBatch(QueueStorePrefetch.java:97) > at > org.apache.activemq.broker.region.cursors.AbstractStoreCursor.fillBatch(AbstractStoreCursor.java:274) > ... 10 more > 2013-12-19 12:27:09,007 [BrokerService[foobar] Task-13] ERROR Queue - Failed > to page in more queue messages > java.lang.RuntimeException: java.lang.RuntimeException: java.io.IOException: > Invalid location: 43153:28, : java.lang.NegativeArraySizeException > at > org.apache.activemq.broker.region.cursors.AbstractStoreCursor.reset(AbstractStoreCursor.java:113) > at > org.apache.activemq.broker.region.cursors.StoreQueueCursor.reset(StoreQueueCursor.java:157) > at > org.apache.activemq.broker.region.Queue.doPageInForDispatch(Queue.java:1746) > at > org.apache.activemq.broker.region.Queue.pageInMessages(Queue.java:1962) > at org.apache.activemq.broker.region.Queue.iterate(Queue.java:1470) > at > org.apache.activemq.thread.PooledTaskRunner.runTask(PooledTaskRunner.java:122) > at > org.apache.activemq.thread.PooledTaskRunner$1.run(PooledTaskRunner.java:43) > at > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) > at java.lang.Thread.run(Thread.java:662) > Caused by: java.lang.RuntimeException: java.io.IOException: Invalid location: > 43153:28, : java.lang.NegativeArraySizeException > at > org.apache.activemq.broker.region.cursors.AbstractStoreCursor.fillBatch(AbstractStoreCursor.java:277) > at > org.apache.activemq.broker.region.cursors.AbstractStoreCursor.reset(AbstractStoreCursor.java:110) > ... 9 more > Caused by: java.io.IOException: Invalid location: 43153:28,
[jira] [Commented] (AMQ-4943) Corrupted KahaDB store: java.lang.NegativeArraySizeException
[ https://issues.apache.org/jira/browse/AMQ-4943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13852877#comment-13852877 ] Lionel Cons commented on AMQ-4943: -- The previous errors are: 2013-12-18 21:12:00,482 [ActiveMQ Journal Checkpoint Worker] ERROR MessageDatabase - KahaDB failed to store to Journal java.io.FileNotFoundException: /activemq/data/kahadb/db-43153.log (Too many open files) at java.io.RandomAccessFile.open(Native Method) at java.io.RandomAccessFile.(RandomAccessFile.java:216) at org.apache.kahadb.journal.DataFile.openRandomAccessFile(DataFile.java:70) at org.apache.kahadb.journal.DataFileAppender.processQueue(DataFileAppender.java:324) at org.apache.kahadb.journal.DataFileAppender$2.run(DataFileAppender.java:203) 2013-12-18 21:12:25,510 [ActiveMQ Journal Checkpoint Worker] INFO DefaultIOExceptionHandler - Stopping the broker due to exception, java.io.FileNotFoundException: /activemq/data/kahadb/db-43153.log (Too many open files) java.io.FileNotFoundException: /activemq/data/kahadb/db-43153.log (Too many open files) at java.io.RandomAccessFile.open(Native Method) at java.io.RandomAccessFile.(RandomAccessFile.java:216) at org.apache.kahadb.journal.DataFile.openRandomAccessFile(DataFile.java:70) at org.apache.kahadb.journal.DataFileAppender.processQueue(DataFileAppender.java:324) at org.apache.kahadb.journal.DataFileAppender$2.run(DataFileAppender.java:203) FWIW, we had "Too many open files" errors because we had too many sockets in CLOSE_WAIT state. > Corrupted KahaDB store: java.lang.NegativeArraySizeException > > > Key: AMQ-4943 > URL: https://issues.apache.org/jira/browse/AMQ-4943 > Project: ActiveMQ > Issue Type: Bug > Environment: activemq-5.5.1-fuse-10-16 >Reporter: Lionel Cons >Priority: Critical > > One of our brokers went crazy and logged _many_ exceptions looking like this: > 2013-12-19 12:27:09,007 [BrokerService[foobar] Task-13] ERROR > AbstractStoreCursor - > org.apache.activemq.broker.region.cursors.QueueStorePrefetch@654e3615:Consumer.prod.whatever,batchResetNeeded=false,storeHasMessages=true,size=2461725,cacheEnabled=false,maxBatchSize:200 > - Failed to fill batch > java.lang.RuntimeException: java.io.IOException: Invalid location: 43153:28, > : java.lang.NegativeArraySizeException > at > org.apache.activemq.broker.region.cursors.AbstractStoreCursor.fillBatch(AbstractStoreCursor.java:277) > at > org.apache.activemq.broker.region.cursors.AbstractStoreCursor.reset(AbstractStoreCursor.java:110) > at > org.apache.activemq.broker.region.cursors.StoreQueueCursor.reset(StoreQueueCursor.java:157) > at > org.apache.activemq.broker.region.Queue.doPageInForDispatch(Queue.java:1746) > at > org.apache.activemq.broker.region.Queue.pageInMessages(Queue.java:1962) > at org.apache.activemq.broker.region.Queue.iterate(Queue.java:1470) > at > org.apache.activemq.thread.PooledTaskRunner.runTask(PooledTaskRunner.java:122) > at > org.apache.activemq.thread.PooledTaskRunner$1.run(PooledTaskRunner.java:43) > at > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) > at java.lang.Thread.run(Thread.java:662) > Caused by: java.io.IOException: Invalid location: 43153:28, : > java.lang.NegativeArraySizeException > at > org.apache.kahadb.journal.DataFileAccessor.readRecord(DataFileAccessor.java:94) > at org.apache.kahadb.journal.Journal.read(Journal.java:601) > at > org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:908) > at > org.apache.activemq.store.kahadb.KahaDBStore.loadMessage(KahaDBStore.java:1024) > at > org.apache.activemq.store.kahadb.KahaDBStore$KahaDBMessageStore$4.execute(KahaDBStore.java:552) > at org.apache.kahadb.page.Transaction.execute(Transaction.java:771) > at > org.apache.activemq.store.kahadb.KahaDBStore$KahaDBMessageStore.recoverNextMessages(KahaDBStore.java:541) > at > org.apache.activemq.store.ProxyMessageStore.recoverNextMessages(ProxyMessageStore.java:88) > at > org.apache.activemq.broker.region.cursors.QueueStorePrefetch.doFillBatch(QueueStorePrefetch.java:97) > at > org.apache.activemq.broker.region.cursors.AbstractStoreCursor.fillBatch(AbstractStoreCursor.java:274) > ... 10 more > 2013-12-19 12:27:09,007 [BrokerService[foobar] Task-13] ERROR Queue - Failed > to page in more queue messages > java.lang.RuntimeException: java.lang.RuntimeException: java.io.IOException: > Invalid location: 43153:28, : java.lang.NegativeArraySizeException > at > org.apache.acti
[jira] [Created] (AMQ-4943) Corrupted KahaDB store: java.lang.NegativeArraySizeException
Lionel Cons created AMQ-4943: Summary: Corrupted KahaDB store: java.lang.NegativeArraySizeException Key: AMQ-4943 URL: https://issues.apache.org/jira/browse/AMQ-4943 Project: ActiveMQ Issue Type: Bug Environment: activemq-5.5.1-fuse-10-16 Reporter: Lionel Cons Priority: Critical One of our brokers went crazy and logged _many_ exceptions looking like this: 2013-12-19 12:27:09,007 [BrokerService[foobar] Task-13] ERROR AbstractStoreCursor - org.apache.activemq.broker.region.cursors.QueueStorePrefetch@654e3615:Consumer.prod.whatever,batchResetNeeded=false,storeHasMessages=true,size=2461725,cacheEnabled=false,maxBatchSize:200 - Failed to fill batch java.lang.RuntimeException: java.io.IOException: Invalid location: 43153:28, : java.lang.NegativeArraySizeException at org.apache.activemq.broker.region.cursors.AbstractStoreCursor.fillBatch(AbstractStoreCursor.java:277) at org.apache.activemq.broker.region.cursors.AbstractStoreCursor.reset(AbstractStoreCursor.java:110) at org.apache.activemq.broker.region.cursors.StoreQueueCursor.reset(StoreQueueCursor.java:157) at org.apache.activemq.broker.region.Queue.doPageInForDispatch(Queue.java:1746) at org.apache.activemq.broker.region.Queue.pageInMessages(Queue.java:1962) at org.apache.activemq.broker.region.Queue.iterate(Queue.java:1470) at org.apache.activemq.thread.PooledTaskRunner.runTask(PooledTaskRunner.java:122) at org.apache.activemq.thread.PooledTaskRunner$1.run(PooledTaskRunner.java:43) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) at java.lang.Thread.run(Thread.java:662) Caused by: java.io.IOException: Invalid location: 43153:28, : java.lang.NegativeArraySizeException at org.apache.kahadb.journal.DataFileAccessor.readRecord(DataFileAccessor.java:94) at org.apache.kahadb.journal.Journal.read(Journal.java:601) at org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:908) at org.apache.activemq.store.kahadb.KahaDBStore.loadMessage(KahaDBStore.java:1024) at org.apache.activemq.store.kahadb.KahaDBStore$KahaDBMessageStore$4.execute(KahaDBStore.java:552) at org.apache.kahadb.page.Transaction.execute(Transaction.java:771) at org.apache.activemq.store.kahadb.KahaDBStore$KahaDBMessageStore.recoverNextMessages(KahaDBStore.java:541) at org.apache.activemq.store.ProxyMessageStore.recoverNextMessages(ProxyMessageStore.java:88) at org.apache.activemq.broker.region.cursors.QueueStorePrefetch.doFillBatch(QueueStorePrefetch.java:97) at org.apache.activemq.broker.region.cursors.AbstractStoreCursor.fillBatch(AbstractStoreCursor.java:274) ... 10 more 2013-12-19 12:27:09,007 [BrokerService[foobar] Task-13] ERROR Queue - Failed to page in more queue messages java.lang.RuntimeException: java.lang.RuntimeException: java.io.IOException: Invalid location: 43153:28, : java.lang.NegativeArraySizeException at org.apache.activemq.broker.region.cursors.AbstractStoreCursor.reset(AbstractStoreCursor.java:113) at org.apache.activemq.broker.region.cursors.StoreQueueCursor.reset(StoreQueueCursor.java:157) at org.apache.activemq.broker.region.Queue.doPageInForDispatch(Queue.java:1746) at org.apache.activemq.broker.region.Queue.pageInMessages(Queue.java:1962) at org.apache.activemq.broker.region.Queue.iterate(Queue.java:1470) at org.apache.activemq.thread.PooledTaskRunner.runTask(PooledTaskRunner.java:122) at org.apache.activemq.thread.PooledTaskRunner$1.run(PooledTaskRunner.java:43) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) at java.lang.Thread.run(Thread.java:662) Caused by: java.lang.RuntimeException: java.io.IOException: Invalid location: 43153:28, : java.lang.NegativeArraySizeException at org.apache.activemq.broker.region.cursors.AbstractStoreCursor.fillBatch(AbstractStoreCursor.java:277) at org.apache.activemq.broker.region.cursors.AbstractStoreCursor.reset(AbstractStoreCursor.java:110) ... 9 more Caused by: java.io.IOException: Invalid location: 43153:28, : java.lang.NegativeArraySizeException at org.apache.kahadb.journal.DataFileAccessor.readRecord(DataFileAccessor.java:94) at org.apache.kahadb.journal.Journal.read(Journal.java:601) at org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:908) at org.apache.activemq.store.kahadb.KahaDBStore.loadMessage(KahaDBStore.java:1024) at org.apache.activemq.store.kahadb.Kah
[jira] [Created] (AMQ-4940) Update the version of Jetty used
Lionel Cons created AMQ-4940: Summary: Update the version of Jetty used Key: AMQ-4940 URL: https://issues.apache.org/jira/browse/AMQ-4940 Project: ActiveMQ Issue Type: Improvement Environment: activemq-5.10-20131214.063224-32 Reporter: Lionel Cons When trying the latest 5.10 snapshot, I was surprised to see a quite old version of Jetty: 2013-12-16 14:41:10,665 [WrapperSimpleAppMain] INFO Server - jetty-7.6.9.v20130131 Why is ActiveMQ using Jetty 7 instead of Jetty 8 or 9? In any case, could ActiveMQ use a more recent version of Jetty like 7.6.14.v20131031 (if it must stick to Jetty 7)? -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (AMQ-4677) LevelDB can't move all message data logs that are no longer used
[ https://issues.apache.org/jira/browse/AMQ-4677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13803987#comment-13803987 ] Lionel Cons commented on AMQ-4677: -- This seems related to https://issues.apache.org/jira/browse/AMQ-4810. Note the Apollo issue linked from AMQ-4810... > LevelDB can't move all message data logs that are no longer used > > > Key: AMQ-4677 > URL: https://issues.apache.org/jira/browse/AMQ-4677 > Project: ActiveMQ > Issue Type: Bug > Components: activemq-leveldb-store >Affects Versions: 5.8.0 > Environment: OS: > Windows 7 Professional > MQ: > > > >Reporter: Hank.X.Hua >Assignee: Timothy Bish > Fix For: 5.x > > Attachments: AMQ4677Test.java > > > Producers and consumers of a single thread to send and consume 50,000 > messages, each message size is 600K, capacity of 28G or so; > Problem: after the message is sent and consumption, there are 7G about the > file is not clear. > By the way, kahaDB have an attribute "cleanupInterval", Why levelDB without > this? -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (AMQ-4810) LevelDB store does not seem to garbage collect its files
Lionel Cons created AMQ-4810: Summary: LevelDB store does not seem to garbage collect its files Key: AMQ-4810 URL: https://issues.apache.org/jira/browse/AMQ-4810 Project: ActiveMQ Issue Type: Bug Environment: activemq-5.9-20131011.032953-115 Reporter: Lionel Cons Trying the LevelDB store on a recent ActiveMQ 5.9 snapshot, it seems that the broker does not remove useless files. I currently have a broker with no messages at all (all queues are empty and the TotalMessageCount is at 0) but plenty of LevelDB files: # du -ks leveldb 1388380 leveldb # find leveldb -type f | wc -l 2419 Maybe this is related to https://issues.apache.org/jira/browse/APLO-245? -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (AMQ-4784) Upgrade Jolokia to 1.1.4
Lionel Cons created AMQ-4784: Summary: Upgrade Jolokia to 1.1.4 Key: AMQ-4784 URL: https://issues.apache.org/jira/browse/AMQ-4784 Project: ActiveMQ Issue Type: Task Components: Broker Reporter: Lionel Cons Jolokia 1.1.4 has just been released. This version fixes a problem when accessing a busy ActiveMQ server (https://github.com/rhuss/jolokia/issues/117). Please upgrade ActiveMQ to use this version. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (AMQ-4754) Add connection counters at broker level
Lionel Cons created AMQ-4754: Summary: Add connection counters at broker level Key: AMQ-4754 URL: https://issues.apache.org/jira/browse/AMQ-4754 Project: ActiveMQ Issue Type: Improvement Reporter: Lionel Cons Priority: Minor Apollo has aggregated connection counters at broker level: 'connected' for the number of existing connections and 'connection_counter' for the total number of connections since reset, allowing to derive from it a connection rate. It would be very useful to expose similar counters for ActiveMQ to improve what can be monitored. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (AMQ-4737) Missing help files in hawtio's console
Lionel Cons created AMQ-4737: Summary: Missing help files in hawtio's console Key: AMQ-4737 URL: https://issues.apache.org/jira/browse/AMQ-4737 Project: ActiveMQ Issue Type: Bug Environment: apache-activemq-5.9-20130919.101342-100 Reporter: Lionel Cons When using hawtio's console from the latest snapshot, the browser complains about missing files: HEAD https://foo/bar/app/apollo/doc/help.md 404 (Not Found) jquery-1.8.2.min.js:2 HEAD https://foo/bar/app/hawtioCore/doc/help.md 404 (Not Found) jquery-1.8.2.min.js:2 HEAD https://foo/bar/app/datatable/doc/help.md 404 (Not Found) jquery-1.8.2.min.js:2 HEAD https://foo/bar/app/hawtio-forms/doc/help.md 404 (Not Found) jquery-1.8.2.min.js:2 HEAD https://foo/bar/app/insight/doc/help.md 404 (Not Found) jquery-1.8.2.min.js:2 HEAD https://foo/bar/app/karaf/doc/help.md 404 (Not Found) jquery-1.8.2.min.js:2 HEAD https://foo/bar/app/osgi/doc/help.md 404 (Not Found) jquery-1.8.2.min.js:2 HEAD https://foo/bar/app/source/doc/help.md 404 (Not Found) jquery-1.8.2.min.js:2 HEAD https://foo/bar/app/tree/doc/help.md 404 (Not Found) jquery-1.8.2.min.js:2 HEAD https://foo/bar/app/hawtio-ui/doc/help.md 404 (Not Found) jquery-1.8.2.min.js:2 Indeed, the snapshot tarball only contains: webapps/hawtio/app/activemq/doc/help.md webapps/hawtio/app/camel/doc/help.md webapps/hawtio/app/dashboard/doc/help.md webapps/hawtio/app/dozer/doc/help.md webapps/hawtio/app/fabric/doc/help.md webapps/hawtio/app/health/doc/help.md webapps/hawtio/app/infinispan/doc/help.md webapps/hawtio/app/jboss/doc/help.md webapps/hawtio/app/jclouds/doc/help.md webapps/hawtio/app/jetty/doc/help.md webapps/hawtio/app/jmx/doc/help.md webapps/hawtio/app/jvm/doc/help.md webapps/hawtio/app/log/doc/help.md webapps/hawtio/app/maven/doc/help.md webapps/hawtio/app/openejb/doc/help.md webapps/hawtio/app/tomcat/doc/help.md webapps/hawtio/app/wiki/doc/help.md -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (AMQ-4736) External dependency (Google Maps) in hawtio's console
Lionel Cons created AMQ-4736: Summary: External dependency (Google Maps) in hawtio's console Key: AMQ-4736 URL: https://issues.apache.org/jira/browse/AMQ-4736 Project: ActiveMQ Issue Type: Bug Environment: apache-activemq-5.9-20130919.101342-100 Reporter: Lionel Cons When using hawtio's console through https, the browser complains with: [blocked] The page at https://foo/bar/#/jmx/charts?nid=root-org.apache.activemq-Broker-foo ran insecure content from http://maps.googleapis.com/maps/api/js?sensor=false. This comes from an external JS file being used in webapps/hawtio/index.html: http://maps.googleapis.com/maps/api/js?sensor=false"; type="text/javascript"> Google Maps can probably be safely removed from ActiveMQ's console... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQ-4735) LinkageError in latest 5.9 snapshot
[ https://issues.apache.org/jira/browse/AMQ-4735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13776090#comment-13776090 ] Lionel Cons commented on AMQ-4735: -- There is no newer snapshot in https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/apache-activemq/5.9-SNAPSHOT/. I will try the next one... > LinkageError in latest 5.9 snapshot > --- > > Key: AMQ-4735 > URL: https://issues.apache.org/jira/browse/AMQ-4735 > Project: ActiveMQ > Issue Type: Bug > Environment: activemq-5.9-20130919.101342-100 >Reporter: Lionel Cons > Attachments: activemq.log > > > When upgrading a test broker to the latest 5.9 snapshot I get: > java.lang.LinkageError: loader constraint violation: when resolving method > "org.slf4j.impl.StaticLoggerBinder.getLoggerFactory()Lorg/slf4j/ILoggerFactory;" > the class loader (instance of org/eclipse/jetty/webapp/WebAppClassLoader) of > the current class, org/slf4j/LoggerFactory, and the class loader (instance of > java/net/URLClassLoader) for resolved class, > org/slf4j/impl/StaticLoggerBinder, have different Class objects for the type > org/slf4j/ILoggerFactory used in the signature -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQ-4735) LinkageError in latest 5.9 snapshot
[ https://issues.apache.org/jira/browse/AMQ-4735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13776057#comment-13776057 ] Lionel Cons commented on AMQ-4735: -- We run ActiveMQ as a standalone application, started by the Java Service Wrapper. BTW, in this snapshot, 1.6 seems to be used: activemq-5.9-20130919.101342-100/webapps/hawtio/WEB-INF/lib/slf4j-api-1.6.6.jar activemq-5.9-20130919.101342-100/lib/jcl-over-slf4j-1.6.6.jar activemq-5.9-20130919.101342-100/lib/optional/slf4j-log4j12-1.6.6.jar activemq-5.9-20130919.101342-100/lib/slf4j-api-1.6.6.jar > LinkageError in latest 5.9 snapshot > --- > > Key: AMQ-4735 > URL: https://issues.apache.org/jira/browse/AMQ-4735 > Project: ActiveMQ > Issue Type: Bug > Environment: activemq-5.9-20130919.101342-100 >Reporter: Lionel Cons > Attachments: activemq.log > > > When upgrading a test broker to the latest 5.9 snapshot I get: > java.lang.LinkageError: loader constraint violation: when resolving method > "org.slf4j.impl.StaticLoggerBinder.getLoggerFactory()Lorg/slf4j/ILoggerFactory;" > the class loader (instance of org/eclipse/jetty/webapp/WebAppClassLoader) of > the current class, org/slf4j/LoggerFactory, and the class loader (instance of > java/net/URLClassLoader) for resolved class, > org/slf4j/impl/StaticLoggerBinder, have different Class objects for the type > org/slf4j/ILoggerFactory used in the signature -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (AMQ-4735) LinkageError in latest 5.9 snapshot
[ https://issues.apache.org/jira/browse/AMQ-4735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lionel Cons updated AMQ-4735: - Attachment: activemq.log > LinkageError in latest 5.9 snapshot > --- > > Key: AMQ-4735 > URL: https://issues.apache.org/jira/browse/AMQ-4735 > Project: ActiveMQ > Issue Type: Bug > Environment: activemq-5.9-20130919.101342-100 >Reporter: Lionel Cons > Attachments: activemq.log > > > When upgrading a test broker to the latest 5.9 snapshot I get: > java.lang.LinkageError: loader constraint violation: when resolving method > "org.slf4j.impl.StaticLoggerBinder.getLoggerFactory()Lorg/slf4j/ILoggerFactory;" > the class loader (instance of org/eclipse/jetty/webapp/WebAppClassLoader) of > the current class, org/slf4j/LoggerFactory, and the class loader (instance of > java/net/URLClassLoader) for resolved class, > org/slf4j/impl/StaticLoggerBinder, have different Class objects for the type > org/slf4j/ILoggerFactory used in the signature -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (AMQ-4735) LinkageError in latest 5.9 snapshot
Lionel Cons created AMQ-4735: Summary: LinkageError in latest 5.9 snapshot Key: AMQ-4735 URL: https://issues.apache.org/jira/browse/AMQ-4735 Project: ActiveMQ Issue Type: Bug Environment: activemq-5.9-20130919.101342-100 Reporter: Lionel Cons When upgrading a test broker to the latest 5.9 snapshot I get: java.lang.LinkageError: loader constraint violation: when resolving method "org.slf4j.impl.StaticLoggerBinder.getLoggerFactory()Lorg/slf4j/ILoggerFactory;" the class loader (instance of org/eclipse/jetty/webapp/WebAppClassLoader) of the current class, org/slf4j/LoggerFactory, and the class loader (instance of java/net/URLClassLoader) for resolved class, org/slf4j/impl/StaticLoggerBinder, have different Class objects for the type org/slf4j/ILoggerFactory used in the signature -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (AMQ-4734) Upgrade Jolokia to 1.1.3
Lionel Cons created AMQ-4734: Summary: Upgrade Jolokia to 1.1.3 Key: AMQ-4734 URL: https://issues.apache.org/jira/browse/AMQ-4734 Project: ActiveMQ Issue Type: Improvement Reporter: Lionel Cons ActiveMQ currently uses Jolokia 1.0.6 while the latest version is 1.1.3. It would be good to upgraded Jolokia before the 5.9.0 release. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (AMQ-4437) JUnit deprecation warnings
Lionel Cons created AMQ-4437:
Summary: JUnit deprecation warnings
Key: AMQ-4437
URL: https://issues.apache.org/jira/browse/AMQ-4437
Project: ActiveMQ
Issue Type: Bug
Reporter: Lionel Cons
When compiling the ActiveMQ trunk using Java 7, I get:
{quote}
[WARNING]
~activemq/activemq-stomp/src/test/java/org/apache/activemq/transport/stomp/StompVirtualTopicTest.java:[31,22]
[deprecation] Assert in junit.framework has been deprecated
[WARNING]
~activemq/activemq-stomp/src/test/java/org/apache/activemq/transport/stomp/StompVirtualTopicTest.java:[133,12]
[deprecation] Assert in junit.framework has been deprecated
[WARNING]
~activemq/activemq-stomp/src/test/java/org/apache/activemq/transport/stomp/StompVirtualTopicTest.java:[192,20]
[deprecation] Assert in junit.framework has been deprecated
[WARNING]
~activemq/activemq-pool/src/test/java/org/apache/activemq/pool/PooledConnectionFactoryTest.java:[30,22]
[deprecation] Assert in junit.framework has been deprecated
[WARNING]
~activemq/activemq-pool/src/test/java/org/apache/activemq/pool/PooledConnectionFactoryMaximumActiveTest.java:[19,22]
[deprecation] Assert in junit.framework has been deprecated
[WARNING]
~activemq/activemq-pool/src/test/java/org/apache/activemq/pool/PooledConnectionTest.java:[73,3]
[deprecation] Assert in junit.framework has been deprecated
[WARNING]
~activemq/activemq-pool/src/test/java/org/apache/activemq/pool/PooledConnectionTest.java:[84,3]
[deprecation] Assert in junit.framework has been deprecated
[WARNING]
~activemq/activemq-pool/src/test/java/org/apache/activemq/pool/PooledConnectionTest.java:[98,2]
[deprecation] Assert in junit.framework has been deprecated
[WARNING]
~activemq/activemq-pool/src/test/java/org/apache/activemq/pool/PooledConnectionFactoryTest.java:[216,12]
[deprecation] Assert in junit.framework has been deprecated
[WARNING]
~activemq/activemq-pool/src/test/java/org/apache/activemq/pool/PooledConnectionFactoryTest.java:[251,20]
[deprecation] Assert in junit.framework has been deprecated
[WARNING]
~activemq/activemq-pool/src/test/java/org/apache/activemq/pool/PooledConnectionFactoryMaximumActiveTest.java:[112,8]
[deprecation] Assert in junit.framework has been deprecated
[WARNING]
~activemq/activemq-pool/src/test/java/org/apache/activemq/pool/PooledConnectionFactoryMaximumActiveTest.java:[115,8]
[deprecation] Assert in junit.framework has been deprecated
[WARNING]
~activemq/activemq-spring/src/test/java/org/apache/activemq/usecases/AMQDeadlockTest3.java:[37,22]
[deprecation] Assert in junit.framework has been deprecated
[WARNING]
~activemq/activemq-spring/src/test/java/org/apache/activemq/usecases/AMQFailoverIssue.java:[95,12]
[deprecation] Assert in junit.framework has been deprecated
[WARNING]
~activemq/activemq-spring/src/test/java/org/apache/activemq/usecases/AMQDeadlockTest3.java:[114,12]
[deprecation] Assert in junit.framework has been deprecated
[WARNING]
~activemq/activemq-spring/src/test/java/org/apache/activemq/usecases/AMQDeadlockTest3.java:[165,12]
[deprecation] Assert in junit.framework has been deprecated
[WARNING]
~activemq/activemq-spring/src/test/java/org/apache/activemq/usecases/AMQDeadlockTest3.java:[217,12]
[deprecation] Assert in junit.framework has been deprecated
[WARNING]
~activemq/activemq-unit-tests/src/test/java/org/apache/activemq/network/NetworkLoopBackTest.java:[26,29]
[deprecation] Assert in junit.framework has been deprecated
[WARNING]
~activemq/activemq-fileserver/src/test/java/org/apache/activemq/util/HttpBlobTest.java:[57,8]
[deprecation] Assert in junit.framework has been deprecated
[WARNING]
~activemq/activemq-fileserver/src/test/java/org/apache/activemq/util/HttpBlobTest.java:[68,8]
[deprecation] Assert in junit.framework has been deprecated
{quote}
This is probably something worth fixing...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (AMQ-4436) LevelDB compilation warnings
Lionel Cons created AMQ-4436:
Summary: LevelDB compilation warnings
Key: AMQ-4436
URL: https://issues.apache.org/jira/browse/AMQ-4436
Project: ActiveMQ
Issue Type: Bug
Reporter: Lionel Cons
When compiling the ActiveMQ trunk using Java 7, I get:
{quote}
[INFO] --- scala-maven-plugin:3.1.0:compile (default) @ activemq-leveldb-store
---
[INFO] ~activemq/activemq-leveldb-store/src/main/java:-1: info: compiling
[INFO] ~activemq/activemq-leveldb-store/target/generated-sources/proto:-1:
info: compiling
[INFO] ~activemq/activemq-leveldb-store/src/main/scala:-1: info: compiling
[INFO] Compiling 21 source files to
~activemq/activemq-leveldb-store/target/classes at 1365083049736
[INFO] compiler plugin:
BasicArtifact(org.fusesource.jvmassert,jvmassert,1.4,null)
[WARNING]
~activemq/activemq-leveldb-store/src/main/scala/org/apache/activemq/leveldb/DBManager.scala:255:
warning: non-variable type argument Long in type pattern (Long, Int) is
unchecked since it is eliminated by erasure
[WARNING] case x:(Long, Int) =>
[WARNING] ^
[WARNING]
~activemq/activemq-leveldb-store/src/main/scala/org/apache/activemq/leveldb/LevelDBClient.scala:1103:
warning: non-variable type argument Long in type pattern (Long, Int) is
unchecked since it is eliminated by erasure
[WARNING] case x:(Long, Int) => x
[WARNING]^
[WARNING]
~activemq/activemq-leveldb-store/src/main/scala/org/apache/activemq/leveldb/LevelDBClient.scala:1124:
warning: non-variable type argument Long in type pattern (Long, Int) is
unchecked since it is eliminated by erasure
[WARNING] case x:(Long, Int) => x
[WARNING]^
[WARNING]
~activemq/activemq-leveldb-store/src/main/scala/org/apache/activemq/leveldb/LevelDBClient.scala:1167:
warning: non-variable type argument Long in type pattern (Long, Int) is
unchecked since it is eliminated by erasure
[WARNING] case x:(Long, Int) => x
[WARNING]^
[WARNING] warning: there were 6 feature warnings; re-run with -feature for
details
[WARNING] 5 warnings found
{quote}
This is probably something that is worth fixing...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (AMQ-4364) Cannot delete queue via JMX or JConsole
[ https://issues.apache.org/jira/browse/AMQ-4364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lionel Cons updated AMQ-4364: - Attachment: AMQ4126Test.patch > Cannot delete queue via JMX or JConsole > --- > > Key: AMQ-4364 > URL: https://issues.apache.org/jira/browse/AMQ-4364 > Project: ActiveMQ > Issue Type: Bug > Environment: activemq-5.9-20130308.055714-20 >Reporter: Lionel Cons > Attachments: AMQ4126Test.patch > > > When using the latest 5.9 snapshot, we noticed that queues cannot be deleted > via JMX or JConsole. When invoking the removeQueue() method, we get a success > status but the queue is not removed. > This may have been present in older versions and not only this particular > snapshot. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQ-4364) Cannot delete queue via JMX or JConsole
[ https://issues.apache.org/jira/browse/AMQ-4364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13615404#comment-13615404 ] Lionel Cons commented on AMQ-4364: -- jaasDualAuthenticationPlugin is quite complex to setup. I've tried to patch activemq-unit-tests/src/test/java/org/apache/activemq/bugs/AMQ4126Test.java for it (see attached). The new test fails on the last assert, indicating that the queue still exists. BTW, I also had to modify activemq-unit-tests/src/test/resources/org/apache/activemq/bugs/amq4126/JaasStompSSLBroker.xml to set useJmx=true... > Cannot delete queue via JMX or JConsole > --- > > Key: AMQ-4364 > URL: https://issues.apache.org/jira/browse/AMQ-4364 > Project: ActiveMQ > Issue Type: Bug > Environment: activemq-5.9-20130308.055714-20 >Reporter: Lionel Cons > > When using the latest 5.9 snapshot, we noticed that queues cannot be deleted > via JMX or JConsole. When invoking the removeQueue() method, we get a success > status but the queue is not removed. > This may have been present in older versions and not only this particular > snapshot. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQ-4364) Cannot delete queue via JMX or JConsole
[ https://issues.apache.org/jira/browse/AMQ-4364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13608990#comment-13608990 ] Lionel Cons commented on AMQ-4364: -- Via trial and error, it seems that the following line is causing us problems: Without it, queue deletion works. With it, it does not. Do you see the same behavior? > Cannot delete queue via JMX or JConsole > --- > > Key: AMQ-4364 > URL: https://issues.apache.org/jira/browse/AMQ-4364 > Project: ActiveMQ > Issue Type: Bug > Environment: activemq-5.9-20130308.055714-20 >Reporter: Lionel Cons > > When using the latest 5.9 snapshot, we noticed that queues cannot be deleted > via JMX or JConsole. When invoking the removeQueue() method, we get a success > status but the queue is not removed. > This may have been present in older versions and not only this particular > snapshot. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQ-4364) Cannot delete queue via JMX or JConsole
[ https://issues.apache.org/jira/browse/AMQ-4364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13607367#comment-13607367 ] Lionel Cons commented on AMQ-4364: -- Could this be linked to the message store? We use kahaDB with the following parameters: > Cannot delete queue via JMX or JConsole > --- > > Key: AMQ-4364 > URL: https://issues.apache.org/jira/browse/AMQ-4364 > Project: ActiveMQ > Issue Type: Bug > Environment: activemq-5.9-20130308.055714-20 >Reporter: Lionel Cons > > When using the latest 5.9 snapshot, we noticed that queues cannot be deleted > via JMX or JConsole. When invoking the removeQueue() method, we get a success > status but the queue is not removed. > This may have been present in older versions and not only this particular > snapshot. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQ-4364) Cannot delete queue via JMX or JConsole
[ https://issues.apache.org/jira/browse/AMQ-4364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13606222#comment-13606222 ] Lionel Cons commented on AMQ-4364: -- FWIW, I've tried again with a more recent snapshot (activemq-5.9-20130315.115006-23) and the problem is still present. To reproduce it: - wipe out the message store - start the broker - start test clients to use some queues, wait until they finish - delete the queues via JMX or JConsole -> they do not get removed > Cannot delete queue via JMX or JConsole > --- > > Key: AMQ-4364 > URL: https://issues.apache.org/jira/browse/AMQ-4364 > Project: ActiveMQ > Issue Type: Bug > Environment: activemq-5.9-20130308.055714-20 >Reporter: Lionel Cons > > When using the latest 5.9 snapshot, we noticed that queues cannot be deleted > via JMX or JConsole. When invoking the removeQueue() method, we get a success > status but the queue is not removed. > This may have been present in older versions and not only this particular > snapshot. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (AMQ-4374) Add information about why a given message has been sent to the DLQ
[ https://issues.apache.org/jira/browse/AMQ-4374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lionel Cons closed AMQ-4374. Resolution: Invalid Wrong manipulation, it should have gone to Apollo... Sorry. I now created https://issues.apache.org/jira/browse/APLO-311 > Add information about why a given message has been sent to the DLQ > -- > > Key: AMQ-4374 > URL: https://issues.apache.org/jira/browse/AMQ-4374 > Project: ActiveMQ > Issue Type: Improvement >Reporter: Lionel Cons > > Poison and expired messages may end up in a DLQ. It would be very useful to > record why a given messages reached the DLQ. This could end up in ad-hoc > header(s) in the message. > FWIW, ActiveMQ has a similar feature: > https://issues.apache.org/jira/browse/AMQ-3236. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (AMQ-4374) Add information about why a given message has been sent to the DLQ
Lionel Cons created AMQ-4374: Summary: Add information about why a given message has been sent to the DLQ Key: AMQ-4374 URL: https://issues.apache.org/jira/browse/AMQ-4374 Project: ActiveMQ Issue Type: Improvement Reporter: Lionel Cons Poison and expired messages may end up in a DLQ. It would be very useful to record why a given messages reached the DLQ. This could end up in ad-hoc header(s) in the message. FWIW, ActiveMQ has a similar feature: https://issues.apache.org/jira/browse/AMQ-3236. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQ-4364) Cannot delete queue via JMX or JConsole
[ https://issues.apache.org/jira/browse/AMQ-4364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13597113#comment-13597113 ] Lionel Cons commented on AMQ-4364: -- Gary, the broker has no clients using the queues we tried to delete. Could it be some kind of corruption of the store (KahaDB for us)? > Cannot delete queue via JMX or JConsole > --- > > Key: AMQ-4364 > URL: https://issues.apache.org/jira/browse/AMQ-4364 > Project: ActiveMQ > Issue Type: Bug > Environment: activemq-5.9-20130308.055714-20 >Reporter: Lionel Cons > > When using the latest 5.9 snapshot, we noticed that queues cannot be deleted > via JMX or JConsole. When invoking the removeQueue() method, we get a success > status but the queue is not removed. > This may have been present in older versions and not only this particular > snapshot. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (AMQ-4364) Cannot delete queue via JMX or JConsole
Lionel Cons created AMQ-4364: Summary: Cannot delete queue via JMX or JConsole Key: AMQ-4364 URL: https://issues.apache.org/jira/browse/AMQ-4364 Project: ActiveMQ Issue Type: Bug Environment: activemq-5.9-20130308.055714-20 Reporter: Lionel Cons When using the latest 5.9 snapshot, we noticed that queues cannot be deleted via JMX or JConsole. When invoking the removeQueue() method, we get a success status but the queue is not removed. This may have been present in older versions and not only this particular snapshot. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQ-4135) Bug in stomp+nio+ssl
[
https://issues.apache.org/jira/browse/AMQ-4135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13570159#comment-13570159
]
Lionel Cons commented on AMQ-4135:
--
Tim, any progress on this one?
> Bug in stomp+nio+ssl
>
>
> Key: AMQ-4135
> URL: https://issues.apache.org/jira/browse/AMQ-4135
> Project: ActiveMQ
> Issue Type: Bug
>Reporter: Massimo Paladin
> Attachments: StompLoadTest.diff
>
>
> We have seen a new bug in the stomp+nio+ssl connector (reproducible), the
> same error has been seen with stomp+ssl as well (not reproducible for now).
> Setup:
> - one producer send ~1 as N messages of different sizes to a queue
> - different sequential consumers (> 3) consume 1/Nth of the messages from the
> queue
> The unit test provided add a test to StompLoadTest, with this new test:
> - StompLoadTest always succeed
> - StompSSLLoadTest succeeded but we noticed {{bad record MAC}} error in a
> deployed broker
> - StompNIOSSLLoadTest always fails with one of the two exceptions reported
> below
> {noformat}
> testStompSlice(org.apache.activemq.transport.stomp.StompNIOSSLLoadTest) Time
> elapsed: 13.551 sec <<< ERROR!
> javax.net.ssl.SSLException: Invalid padding
> at sun.security.ssl.Alerts.getSSLException(Alerts.java:208)
> at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1902)
> at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:981)
> at
> sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:884)
> at sun.security.ssl.AppInputStream.read(AppInputStream.java:102)
> at sun.security.ssl.AppInputStream.read(AppInputStream.java:69)
> at java.io.DataInputStream.readByte(DataInputStream.java:265)
> at
> org.apache.activemq.transport.stomp.StompWireFormat.unmarshal(StompWireFormat.java:123)
> at
> org.apache.activemq.transport.stomp.StompConnection.receive(StompConnection.java:77)
> at
> org.apache.activemq.transport.stomp.StompLoadTest.testStompSlice(StompLoadTest.java:261)
> {noformat}
> {noformat}
> testStompSlice(org.apache.activemq.transport.stomp.StompNIOSSLLoadTest) Time
> elapsed: 14.86 sec <<< ERROR!
> javax.net.ssl.SSLException: bad record MAC
> at sun.security.ssl.Alerts.getSSLException(Alerts.java:208)
> at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1902)
> at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1855)
> at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:988)
> at
> sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:884)
> at sun.security.ssl.AppInputStream.read(AppInputStream.java:102)
> at sun.security.ssl.AppInputStream.read(AppInputStream.java:69)
> at java.io.DataInputStream.readByte(DataInputStream.java:265)
> at
> org.apache.activemq.transport.stomp.StompWireFormat.readHeaderLine(StompWireFormat.java:155)
> at
> org.apache.activemq.transport.stomp.StompWireFormat.readLine(StompWireFormat.java:148)
> at
> org.apache.activemq.transport.stomp.StompWireFormat.parseAction(StompWireFormat.java:170)
> at
> org.apache.activemq.transport.stomp.StompWireFormat.unmarshal(StompWireFormat.java:98)
> at
> org.apache.activemq.transport.stomp.StompConnection.receive(StompConnection.java:77)
> at
> org.apache.activemq.transport.stomp.StompLoadTest.testStompSlice(StompLoadTest.java:261)
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (AMQ-4247) Jolokia error in latest 5.8 snapshot
[ https://issues.apache.org/jira/browse/AMQ-4247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lionel Cons closed AMQ-4247. Resolution: Fixed With the classpath: prefix trick I can now use Jolokia without problems. The only thing left is the MBean names changes but this is being tracked/discussed in AMQ-4237. > Jolokia error in latest 5.8 snapshot > > > Key: AMQ-4247 > URL: https://issues.apache.org/jira/browse/AMQ-4247 > Project: ActiveMQ > Issue Type: Bug > Environment: activemq-5.8-20130105.031543-65 >Reporter: Lionel Cons > > Using the latest ActiveMQ 5.8 snapshot, I'm getting errors when trying to > access /j4p: > HTTP ERROR 503 > Problem accessing /j4p/. Reason: > java.lang.IllegalStateException: Cannot load extractor > org.jolokia.converter.json.simplifier.ClassSimplifier defined in > jar:file:/usr/activemq/lib/web/jolokia-core-1.0.6.jar!/META-INF/simplifiers-default > : java.lang.ClassCastException: > org.jolokia.converter.json.simplifier.ClassSimplifier cannot be cast to > org.jmx4perl.converter.json.Extractor. Aborting > Is this a known problem? Is there any documentation on how to use and/or > configure Jolokia with ActiveMQ? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQ-4247) Jolokia error in latest 5.8 snapshot
[
https://issues.apache.org/jira/browse/AMQ-4247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13548385#comment-13548385
]
Lionel Cons commented on AMQ-4247:
--
In fact, even with the Java service wrapper, ${activemq.conf} is indeed in the
classpath so a value of "classpath:foo" indeed points to "foo" under
${activemq.conf}. Thanks!
> Jolokia error in latest 5.8 snapshot
>
>
> Key: AMQ-4247
> URL: https://issues.apache.org/jira/browse/AMQ-4247
> Project: ActiveMQ
> Issue Type: Bug
> Environment: activemq-5.8-20130105.031543-65
>Reporter: Lionel Cons
>
> Using the latest ActiveMQ 5.8 snapshot, I'm getting errors when trying to
> access /j4p:
> HTTP ERROR 503
> Problem accessing /j4p/. Reason:
> java.lang.IllegalStateException: Cannot load extractor
> org.jolokia.converter.json.simplifier.ClassSimplifier defined in
> jar:file:/usr/activemq/lib/web/jolokia-core-1.0.6.jar!/META-INF/simplifiers-default
> : java.lang.ClassCastException:
> org.jolokia.converter.json.simplifier.ClassSimplifier cannot be cast to
> org.jmx4perl.converter.json.Extractor. Aborting
> Is this a known problem? Is there any documentation on how to use and/or
> configure Jolokia with ActiveMQ?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQ-4247) Jolokia error in latest 5.8 snapshot
[ https://issues.apache.org/jira/browse/AMQ-4247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13547737#comment-13547737 ] Lionel Cons commented on AMQ-4247: -- Dejan, I will investigate further but it seems that conf is not in the classpath. We use the service wrapper and your conf/wrapper.conf contains only: wrapper.java.classpath.1=%ACTIVEMQ_HOME%/bin/wrapper.jar wrapper.java.classpath.2=%ACTIVEMQ_HOME%/bin/activemq.jar > Jolokia error in latest 5.8 snapshot > > > Key: AMQ-4247 > URL: https://issues.apache.org/jira/browse/AMQ-4247 > Project: ActiveMQ > Issue Type: Bug > Environment: activemq-5.8-20130105.031543-65 >Reporter: Lionel Cons > > Using the latest ActiveMQ 5.8 snapshot, I'm getting errors when trying to > access /j4p: > HTTP ERROR 503 > Problem accessing /j4p/. Reason: > java.lang.IllegalStateException: Cannot load extractor > org.jolokia.converter.json.simplifier.ClassSimplifier defined in > jar:file:/usr/activemq/lib/web/jolokia-core-1.0.6.jar!/META-INF/simplifiers-default > : java.lang.ClassCastException: > org.jolokia.converter.json.simplifier.ClassSimplifier cannot be cast to > org.jmx4perl.converter.json.Extractor. Aborting > Is this a known problem? Is there any documentation on how to use and/or > configure Jolokia with ActiveMQ? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQ-4247) Jolokia error in latest 5.8 snapshot
[ https://issues.apache.org/jira/browse/AMQ-4247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13546764#comment-13546764 ] Lionel Cons commented on AMQ-4247: -- In fact, there is a third problem, linked to MBean names too. In 5.5, we can see: org.apache.activemq:BrokerName=,Type=Queue,Destination=ActiveMQ.DLQ But in 5.8: org.apache.activemq:type=Broker,brokerName=,destinationType=Queue,destinationName=ActiveMQ.DLQ Why do we have type=Broker for a queue? > Jolokia error in latest 5.8 snapshot > > > Key: AMQ-4247 > URL: https://issues.apache.org/jira/browse/AMQ-4247 > Project: ActiveMQ > Issue Type: Bug > Environment: activemq-5.8-20130105.031543-65 >Reporter: Lionel Cons > > Using the latest ActiveMQ 5.8 snapshot, I'm getting errors when trying to > access /j4p: > HTTP ERROR 503 > Problem accessing /j4p/. Reason: > java.lang.IllegalStateException: Cannot load extractor > org.jolokia.converter.json.simplifier.ClassSimplifier defined in > jar:file:/usr/activemq/lib/web/jolokia-core-1.0.6.jar!/META-INF/simplifiers-default > : java.lang.ClassCastException: > org.jolokia.converter.json.simplifier.ClassSimplifier cannot be cast to > org.jmx4perl.converter.json.Extractor. Aborting > Is this a known problem? Is there any documentation on how to use and/or > configure Jolokia with ActiveMQ? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQ-4247) Jolokia error in latest 5.8 snapshot
[
https://issues.apache.org/jira/browse/AMQ-4247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13546747#comment-13546747
]
Lionel Cons commented on AMQ-4247:
--
Dejan,
Thanks for your reply and the link to some doc.
The error came in fact from an old installation on jmx4perl (agent). I've now
cleaned it. The /j4p/ path is because we use a proxy with this path, ActiveMQ
is queried with /api/jolokia/.
I can now access JMX information via Jolokia but I still have two problems.
(1) I tried to use ${activemq.conf} in web.xml to specify which access file
Jolokia should use but this syntax does not seem to be accepted. Is there a way
to put Java property names in web.xml? IMHO, it would make sense to configure
Jolokia from files under ${activemq.conf}.
(2) It seems the MBean paths have changed and this kills our Nagios monitoring.
For instance, to get the broker version, we have to use:
- for ActiveMQ 5.5: org.apache.activemq:Type=Broker,BrokerName=
- for ActiveMQ 5.8: org.apache.activemq:type=Broker,brokerName=
Is this case change intentional?
> Jolokia error in latest 5.8 snapshot
>
>
> Key: AMQ-4247
> URL: https://issues.apache.org/jira/browse/AMQ-4247
> Project: ActiveMQ
> Issue Type: Bug
> Environment: activemq-5.8-20130105.031543-65
>Reporter: Lionel Cons
>
> Using the latest ActiveMQ 5.8 snapshot, I'm getting errors when trying to
> access /j4p:
> HTTP ERROR 503
> Problem accessing /j4p/. Reason:
> java.lang.IllegalStateException: Cannot load extractor
> org.jolokia.converter.json.simplifier.ClassSimplifier defined in
> jar:file:/usr/activemq/lib/web/jolokia-core-1.0.6.jar!/META-INF/simplifiers-default
> : java.lang.ClassCastException:
> org.jolokia.converter.json.simplifier.ClassSimplifier cannot be cast to
> org.jmx4perl.converter.json.Extractor. Aborting
> Is this a known problem? Is there any documentation on how to use and/or
> configure Jolokia with ActiveMQ?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (AMQ-4247) Jolokia error in latest 5.8 snapshot
Lionel Cons created AMQ-4247: Summary: Jolokia error in latest 5.8 snapshot Key: AMQ-4247 URL: https://issues.apache.org/jira/browse/AMQ-4247 Project: ActiveMQ Issue Type: Bug Environment: activemq-5.8-20130105.031543-65 Reporter: Lionel Cons Using the latest ActiveMQ 5.8 snapshot, I'm getting errors when trying to access /j4p: HTTP ERROR 503 Problem accessing /j4p/. Reason: java.lang.IllegalStateException: Cannot load extractor org.jolokia.converter.json.simplifier.ClassSimplifier defined in jar:file:/usr/activemq/lib/web/jolokia-core-1.0.6.jar!/META-INF/simplifiers-default : java.lang.ClassCastException: org.jolokia.converter.json.simplifier.ClassSimplifier cannot be cast to org.jmx4perl.converter.json.Extractor. Aborting Is this a known problem? Is there any documentation on how to use and/or configure Jolokia with ActiveMQ? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQ-4135) Bug in stomp+nio+ssl
[
https://issues.apache.org/jira/browse/AMQ-4135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13484740#comment-13484740
]
Lionel Cons commented on AMQ-4135:
--
FWIW, I also get similar errors using a Perl client. Here is what gets logged:
{code}
2012-10-26 08:26:02,971 [ActiveMQ NIO Worker 49] WARN Transport - Transport
Connection to: tcp://1.1.4.3:34160 failed: javax.net.ssl.SSLException: Received
fatal alert: bad_record_mac
2012-10-26 08:26:02,979 [ActiveMQ NIO Worker 48] WARN Transport - Transport
Connection to: tcp://1.1.4.3:34161 failed: javax.net.ssl.SSLException: Received
fatal alert: bad_record_mac
2012-10-26 08:26:03,006 [ActiveMQ NIO Worker 48] WARN Transport - Transport
Connection to: tcp://1.1.4.3:34162 failed: javax.net.ssl.SSLException: Received
fatal alert: bad_record_mac
2012-10-26 08:26:14,780 [ActiveMQ NIO Worker 49] WARN Transport - Transport
Connection to: tcp://1.1.4.3:34190 failed: javax.net.ssl.SSLException: Inbound
closed before receiving peer's close_notify: possible truncation attack?
{code}
> Bug in stomp+nio+ssl
>
>
> Key: AMQ-4135
> URL: https://issues.apache.org/jira/browse/AMQ-4135
> Project: ActiveMQ
> Issue Type: Bug
>Reporter: Massimo Paladin
> Attachments: StompLoadTest.diff
>
>
> We have seen a new bug in the stomp+nio+ssl connector (reproducible), the
> same error has been seen with stomp+ssl as well (not reproducible for now).
> Setup:
> - one producer send ~1 as N messages of different sizes to a queue
> - different sequential consumers (> 3) consume 1/Nth of the messages from the
> queue
> The unit test provided add a test to StompLoadTest, with this new test:
> - StompLoadTest always succeed
> - StompSSLLoadTest succeeded but we noticed {{bad record MAC}} error in a
> deployed broker
> - StompNIOSSLLoadTest always fails with one of the two exceptions reported
> below
> {noformat}
> testStompSlice(org.apache.activemq.transport.stomp.StompNIOSSLLoadTest) Time
> elapsed: 13.551 sec <<< ERROR!
> javax.net.ssl.SSLException: Invalid padding
> at sun.security.ssl.Alerts.getSSLException(Alerts.java:208)
> at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1902)
> at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:981)
> at
> sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:884)
> at sun.security.ssl.AppInputStream.read(AppInputStream.java:102)
> at sun.security.ssl.AppInputStream.read(AppInputStream.java:69)
> at java.io.DataInputStream.readByte(DataInputStream.java:265)
> at
> org.apache.activemq.transport.stomp.StompWireFormat.unmarshal(StompWireFormat.java:123)
> at
> org.apache.activemq.transport.stomp.StompConnection.receive(StompConnection.java:77)
> at
> org.apache.activemq.transport.stomp.StompLoadTest.testStompSlice(StompLoadTest.java:261)
> {noformat}
> {noformat}
> testStompSlice(org.apache.activemq.transport.stomp.StompNIOSSLLoadTest) Time
> elapsed: 14.86 sec <<< ERROR!
> javax.net.ssl.SSLException: bad record MAC
> at sun.security.ssl.Alerts.getSSLException(Alerts.java:208)
> at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1902)
> at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1855)
> at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:988)
> at
> sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:884)
> at sun.security.ssl.AppInputStream.read(AppInputStream.java:102)
> at sun.security.ssl.AppInputStream.read(AppInputStream.java:69)
> at java.io.DataInputStream.readByte(DataInputStream.java:265)
> at
> org.apache.activemq.transport.stomp.StompWireFormat.readHeaderLine(StompWireFormat.java:155)
> at
> org.apache.activemq.transport.stomp.StompWireFormat.readLine(StompWireFormat.java:148)
> at
> org.apache.activemq.transport.stomp.StompWireFormat.parseAction(StompWireFormat.java:170)
> at
> org.apache.activemq.transport.stomp.StompWireFormat.unmarshal(StompWireFormat.java:98)
> at
> org.apache.activemq.transport.stomp.StompConnection.receive(StompConnection.java:77)
> at
> org.apache.activemq.transport.stomp.StompLoadTest.testStompSlice(StompLoadTest.java:261)
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQ-4133) Different behaviour with similar connectors with identical option, URI validation would be nice to have
[
https://issues.apache.org/jira/browse/AMQ-4133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13483924#comment-13483924
]
Lionel Cons commented on AMQ-4133:
--
ActiveMQ already performs strict XML validation to detect incorrect
configuration items before starting the broker, this is very good.
It should IMHO also strictly validate the options given via the URI syntax and
that therefore escape standard schema based validation.
> Different behaviour with similar connectors with identical option, URI
> validation would be nice to have
> ---
>
> Key: AMQ-4133
> URL: https://issues.apache.org/jira/browse/AMQ-4133
> Project: ActiveMQ
> Issue Type: Bug
>Reporter: Massimo Paladin
> Attachments: AMQ4133.tgz
>
>
> Hello,
> we noticed an inconsistent behaviour of stomp+ssl and stomp+nio+ssl with same
> connector options.
> - stomp+ssl works with both {{transport.needClientAuth=true}} and
> {{needClientAuth=true}} options
> - stomp+nio+ssl works with {{transport.needClientAuth=true}} but not with
> {{needClientAuth=true}}
> In this last case it fails with a non-obvious exception:
> {noformat}
> junit.framework.ComparisonFailure: java.lang.SecurityException: Unable to
> authenticate transport without SSL certificate.
> at
> org.apache.activemq.security.JaasCertificateAuthenticationBroker.addConnection(JaasCertificateAuthenticationBroker.java:74)
> at
> org.apache.activemq.security.JaasDualAuthenticationBroker.addConnection(JaasDualAuthenticationBroker.java:98)
> {noformat}
> It would be nice to have a URI parameters validation or the same behaviour
> with similar connectors.
> What do you think?
> Unit test which shows the problem attached, sorry for reusing pieces from
> another bug.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQ-3996) NIO + SSL: Client certificates are null
[
https://issues.apache.org/jira/browse/AMQ-3996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13479657#comment-13479657
]
Lionel Cons commented on AMQ-3996:
--
Christian/Tim, in our setup, we use the jaasDualAuthenticationPlugin. Its code
contains:
{code}
isSSL = (transportConnector.getServer() instanceof SslTransportServer);
{code}
This does not seem to be correct with NIO. Could you please check if you can
make cert auth work with jaasDualAuthenticationPlugin?
> NIO + SSL: Client certificates are null
> ---
>
> Key: AMQ-3996
> URL: https://issues.apache.org/jira/browse/AMQ-3996
> Project: ActiveMQ
> Issue Type: Bug
>Affects Versions: 5.6.0, 5.7.0
>Reporter: Francesco Romano
>Assignee: Timothy Bish
> Fix For: 5.8.0
>
> Attachments: broker-jaas-ssl-nio.xml, nio+ssl.png,
> NIOSSLTransportWithJaasCertificateAuthBrokerTest.java,
> NIOSSLTransportWithJaasCertificateAuthBrokerTest.java,
> NIOSSLTransportWithJaasCertificateAuthBrokerTest.java, ssl.png
>
>
> If using protocol nio+ssl, the ConnectionInfo transportContext property does
> not contains peer certificates (which are present in the plain tcp ssl
> transport).
> The problem is that in the NIO transport, calling
> sslSession.getPeerCertificates() returns null.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQ-3996) NIO + SSL: Client certificates are null
[ https://issues.apache.org/jira/browse/AMQ-3996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13478998#comment-13478998 ] Lionel Cons commented on AMQ-3996: -- Christian, in our case the exact same user.properties file works fine without NIO. It is strange that enabling NIO would change the certificate format... What did you change to have your tests pass? > NIO + SSL: Client certificates are null > --- > > Key: AMQ-3996 > URL: https://issues.apache.org/jira/browse/AMQ-3996 > Project: ActiveMQ > Issue Type: Bug >Affects Versions: 5.6.0, 5.7.0 >Reporter: Francesco Romano >Assignee: Timothy Bish > Fix For: 5.8.0 > > Attachments: broker-jaas-ssl-nio.xml, nio+ssl.png, > NIOSSLTransportWithJaasCertificateAuthBrokerTest.java, > NIOSSLTransportWithJaasCertificateAuthBrokerTest.java, > NIOSSLTransportWithJaasCertificateAuthBrokerTest.java, ssl.png > > > If using protocol nio+ssl, the ConnectionInfo transportContext property does > not contains peer certificates (which are present in the plain tcp ssl > transport). > The problem is that in the NIO transport, calling > sslSession.getPeerCertificates() returns null. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQ-3996) NIO + SSL: Client certificates are null
[ https://issues.apache.org/jira/browse/AMQ-3996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13478701#comment-13478701 ] Lionel Cons commented on AMQ-3996: -- Tim, could you please be a bit more specific in what is needed in terms of configuration? We use the jaasDualAuthenticationPlugin with two domains configured in login.config (one with SSL, the other one without) and this works fine with stomp+ssl. Changing the connector to stomp+nio+ssl breaks the authentication (we get java.lang.SecurityException: User name [null] or password is invalid). Do we need to add configuration bits that are specific to NIO? > NIO + SSL: Client certificates are null > --- > > Key: AMQ-3996 > URL: https://issues.apache.org/jira/browse/AMQ-3996 > Project: ActiveMQ > Issue Type: Bug >Affects Versions: 5.6.0, 5.7.0 >Reporter: Francesco Romano >Assignee: Timothy Bish > Fix For: 5.8.0 > > Attachments: broker-jaas-ssl-nio.xml, nio+ssl.png, > NIOSSLTransportWithJaasCertificateAuthBrokerTest.java, > NIOSSLTransportWithJaasCertificateAuthBrokerTest.java, > NIOSSLTransportWithJaasCertificateAuthBrokerTest.java, ssl.png > > > If using protocol nio+ssl, the ConnectionInfo transportContext property does > not contains peer certificates (which are present in the plain tcp ssl > transport). > The problem is that in the NIO transport, calling > sslSession.getPeerCertificates() returns null. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQ-4110) Web console can't send messages to the secured broker
[
https://issues.apache.org/jira/browse/AMQ-4110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13476907#comment-13476907
]
Lionel Cons commented on AMQ-4110:
--
Since the web console seems to use NIO, this issue is maybe the same one as
AMQ-3996.
> Web console can't send messages to the secured broker
> -
>
> Key: AMQ-4110
> URL: https://issues.apache.org/jira/browse/AMQ-4110
> Project: ActiveMQ
> Issue Type: Bug
>Affects Versions: 5.7.0
>Reporter: Dejan Bosanac
>Assignee: Dejan Bosanac
> Fix For: 5.8.0
>
>
> When trying to send a message to the secured broker from web console you'll
> get the
> {code}javax.jms.JMSException: User name [null] or password is invalid.{code}
> error, meaning that's the only operation that doesn't use proper credentials
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQ-3996) NIO + SSL: Client certificates are null
[ https://issues.apache.org/jira/browse/AMQ-3996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13476878#comment-13476878 ] Lionel Cons commented on AMQ-3996: -- We use X.509 authentication on our SSL connectors. Because of this bug, STOMP+NIO+SSL authentication always fails with: java.lang.SecurityException: User name [null] or password is invalid. > NIO + SSL: Client certificates are null > --- > > Key: AMQ-3996 > URL: https://issues.apache.org/jira/browse/AMQ-3996 > Project: ActiveMQ > Issue Type: Bug >Affects Versions: 5.6.0 >Reporter: Francesco Romano >Assignee: Timothy Bish > Fix For: 5.8.0 > > Attachments: broker-jaas-ssl-nio.xml, nio+ssl.png, > NIOSSLTransportWithJaasCertificateAuthBrokerTest.java, > NIOSSLTransportWithJaasCertificateAuthBrokerTest.java, ssl.png > > > If using protocol nio+ssl, the ConnectionInfo transportContext property does > not contains peer certificates (which are present in the plain tcp ssl > transport). > The problem is that in the NIO transport, calling > sslSession.getPeerCertificates() returns null. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQ-3626) Add support for fast codecs when compressing messages
[ https://issues.apache.org/jira/browse/AMQ-3626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13259401#comment-13259401 ] Lionel Cons commented on AMQ-3626: -- FWIW, LZ4 (http://code.google.com/p/lz4/) looks like a very fast and good enough compression library. > Add support for fast codecs when compressing messages > - > > Key: AMQ-3626 > URL: https://issues.apache.org/jira/browse/AMQ-3626 > Project: ActiveMQ > Issue Type: Improvement >Affects Versions: 5.5.0 >Reporter: Dejan Bosanac > > When using "useCompression", we should support fast codes like lzf instead of > standard deflate -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQ-3318) "Detected store dropped message" errors when broker is run against the stomp-benchmark
[
https://issues.apache.org/jira/browse/AMQ-3318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13032855#comment-13032855
]
Lionel Cons commented on AMQ-3318:
--
Since it occurred only once during ten consecutive runs, it's likely a hard to
reproduce race condition...
My machine has 8 cores and 16 GB of RAM. I started Apollo with
{code}
JVM_FLAGS="-server -Xmx8192m -Xms4096m"
{code}
Here is what stomp-benchmark recorded:
{code}
"benchmark_settings": {
"broker_name": "run1",
"host": "localhost",
"port": 61613,
"sample_count": 30,
"sample_interval": 2000,
"warm_up_count": 5,
"scenario_connection_scale_rate": 50
},
{code}
> "Detected store dropped message" errors when broker is run against the
> stomp-benchmark
> --
>
> Key: AMQ-3318
> URL: https://issues.apache.org/jira/browse/AMQ-3318
> Project: ActiveMQ
> Issue Type: Bug
> Components: Apollo, Broker
>Reporter: Hiram Chirino
>Assignee: Hiram Chirino
>
> Lionel Cons wrote:
> {quote}
> ran stomp-benchmark several times in a row against Apollo
> 20110505.135118-111 and it worked fine with one exception.
> During less than one second, it logged several messages like this:
> 2011-05-11 05:54:09,661 | INFO | Detected store dropped message at seq:
> 467787239 | org.apache.activemq.apollo.broker.QueueEntry | bdb store io read
> 2011-05-11 05:54:09,661 | INFO | Detected store dropped message at seq:
> 467787240 | org.apache.activemq.apollo.broker.QueueEntry | bdb store io read
> 2011-05-11 05:54:09,662 | INFO | Detected store dropped message at seq:
> 467787241 | org.apache.activemq.apollo.broker.QueueEntry | bdb store io read
> [...]
> 2011-05-11 05:54:09,681 | INFO | Detected store dropped message at seq:
> 467787325 | org.apache.activemq.apollo.broker.QueueEntry | bdb store io read
> 2011-05-11 05:54:09,681 | INFO | Detected store dropped message at seq:
> 467787326 | org.apache.activemq.apollo.broker.QueueEntry | bdb store io read
> 2011-05-11 05:54:09,681 | INFO | Detected store dropped message at seq:
> 467787327 | org.apache.activemq.apollo.broker.QueueEntry | bdb store io read
> {quote}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQ-3248) Allow for easy externalization of ActiveMQ configuration
[
https://issues.apache.org/jira/browse/AMQ-3248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012447#comment-13012447
]
Lionel Cons commented on AMQ-3248:
--
Currently we have in the activemq script:
activemq.home = ${ACTIVEMQ_HOME}
activemq.base = ${ACTIVEMQ_BASE}
It would make sense to use ACTIVEMQ_CONF instead of ACTIVEMQ_CONFIG_DIR to have
the more natural:
activemq.conf = ${ACTIVEMQ_CONF}
And while at it, we could also add:
activemq.data = ${ACTIVEMQ_DATA}
This would allow to use for instance instead of .
> Allow for easy externalization of ActiveMQ configuration
>
>
> Key: AMQ-3248
> URL: https://issues.apache.org/jira/browse/AMQ-3248
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Broker
>Affects Versions: 5.4.2
>Reporter: Torsten Mielke
> Labels: configuration
> Attachments: AMQ-3248.patch
>
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> Currently many of the AMQ configuration files use the property activemq.base
> to load in other configuration files, e.g.
> activemq.xml:
> {code:title=activmeq.xml}
>
> file:${activemq.base}/conf/credentials.properties
>
> {code}
> jetty.xml:
> {code:title=jetty.xml}
> class="org.eclipse.jetty.security.HashLoginService">
>
>value="${activemq.base}/conf/jetty-realm.properties" />
>
> {code}
> webconsole-embedded.xml:
> {code:title=webconsole-embedded.xml}
>
> file:${activemq.base}/conf/credentials.properties
>
> {code}
> and others.
> In case where you want to externalize the entire ActiveMQ configuration into
> a folder that is not a sub folder of AMQ, there is the need to change
> multiple configuration files. This is error prone.
> In order to make the use of external AMQ configuration more easy to use, I
> suggest to
> 1. Make use of the already existing environment variable ACTIVEMQ_CONFIG_DIR
> which points to ${ACTIVEMQ_BASE}/conf by default in bin/activemq script.
> 2. Map the environment variable to the Java variable activemq.conf in
> bin/activemq script
> 2. Replace all occurences of ${activemq.base}/conf with {$activemq.conf} in
> all XML configuration files (including those in webapps/ folder)
> That way one can simply point to an external ActiveMQ conf folder by setting
> the shell environment variable ACTIVE_CONFIG_DIR to that folder. It does not
> have to be set in the bin/activemq script, it can be set directly on the
> shell.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-3086) Add a perl example to the apollo distro
[ https://issues.apache.org/jira/browse/AMQ-3086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lionel Cons updated AMQ-3086: - Attachment: examples.perl.tgz Simple example scripts using Net::STOMP::Client (http://search.cpan.org/dist/Net-STOMP-Client). > Add a perl example to the apollo distro > --- > > Key: AMQ-3086 > URL: https://issues.apache.org/jira/browse/AMQ-3086 > Project: ActiveMQ > Issue Type: New Feature > Components: Apollo >Reporter: Hiram Chirino >Assignee: Hiram Chirino > Attachments: examples.perl.tgz > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
