[jira] [Assigned] (AMQ-3904) InactivityMonitor doc
[ https://issues.apache.org/jira/browse/AMQ-3904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Torsten Mielke reassigned AMQ-3904: --- Assignee: Torsten Mielke InactivityMonitor doc - Key: AMQ-3904 URL: https://issues.apache.org/jira/browse/AMQ-3904 Project: ActiveMQ Issue Type: Improvement Components: Documentation Reporter: Pat Fox Assignee: Torsten Mielke Priority: Minor Labels: documentation Attachments: InactivityMonitor.html I created a doc for the InactivityMonitor. Perhaps it could be added to the activemq docs? -- 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-3897) Stomp 1.1 keep alive does not work with stomp+nio
[
https://issues.apache.org/jira/browse/AMQ-3897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13403890#comment-13403890
]
R.I.Pienaar commented on AMQ-3897:
--
Thanks for sorting this out! I see it's targeted for 5.7.x, could this be 5.6.x
instead? its just a bug fix and would be awesome to get this working before
5.7.0
Stomp 1.1 keep alive does not work with stomp+nio
-
Key: AMQ-3897
URL: https://issues.apache.org/jira/browse/AMQ-3897
Project: ActiveMQ
Issue Type: Bug
Components: Broker, stomp
Affects Versions: 5.6.0
Environment: centos 6, OpenJDK 64-Bit Server VM (build 20.0-b12,
mixed mode)
Reporter: R.I.Pienaar
Assignee: Timothy Bish
Fix For: 5.7.0
using the transport:
{quote}
transportConnector name=stomp+nio uri=stomp+nio://0.0.0.0:6163/
{quote}
When connecting a stomp 1.1 client I see this using tcpdump (tcpdump output
so new lines etc):
{quote}
send...
CONNECT
.passcode:xxx.host:kvm4.content-length:0.heart-beat:3,3.content-type:text/plain;
charset=UTF-8.login:rip.accept-version:1.1,1.0...
...receive
CONNECTED.heart-beat:0,0.session:ID:kvm4-55239-1340217683781-3:10008.server:ActiveMQ/5.6.0.version:1.1
{quote}
Notice that I send the heart-beat header requesting 3,3 heartbeats
but then ActiveMQ replies with 0,0
If I change the stomp transport to stomp and not stomp+nio and not changing
my code or what I send in CONNECT request I get the correct heartbeats.
It seems stomp+nio does not have heartbeat support for protocol 1.1
--
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] [Created] (AMQ-3905) Karaf: activemq:create-broker results in only locally visible broker
Jürgen Kindler created AMQ-3905: --- Summary: Karaf: activemq:create-broker results in only locally visible broker Key: AMQ-3905 URL: https://issues.apache.org/jira/browse/AMQ-3905 Project: ActiveMQ Issue Type: Bug Affects Versions: 5.5.0 Reporter: Jürgen Kindler Priority: Minor When I start ActiveMQ with default config on console I get a broker that is visible by other machines as well as the default config uses 0.0.0.0 as publish address. Surprisingly when I embed it inside a Karaf instance the config generated from activemq:create-broker generates a broker that is only visible on my local machine. It would be better, if both default ways would work the same: Also when starting ActiveMQ inside Karaf, it should publish the broker at 0.0.0.0 -- 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-3904) InactivityMonitor doc
[ https://issues.apache.org/jira/browse/AMQ-3904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13403942#comment-13403942 ] Torsten Mielke commented on AMQ-3904: - Many thanks to Pat Fox for providing this documentation. It has been added to the ActiveMQ documentation set and is also linked from some of the transport reference pages. https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+InactivityMonitor InactivityMonitor doc - Key: AMQ-3904 URL: https://issues.apache.org/jira/browse/AMQ-3904 Project: ActiveMQ Issue Type: Improvement Components: Documentation Reporter: Pat Fox Assignee: Torsten Mielke Priority: Minor Labels: documentation Attachments: InactivityMonitor.html I created a doc for the InactivityMonitor. Perhaps it could be added to the activemq docs? -- 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] [Resolved] (AMQ-3904) InactivityMonitor doc
[ https://issues.apache.org/jira/browse/AMQ-3904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Torsten Mielke resolved AMQ-3904. - Resolution: Fixed https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+InactivityMonitor Give it a few hours to appear on the live site. InactivityMonitor doc - Key: AMQ-3904 URL: https://issues.apache.org/jira/browse/AMQ-3904 Project: ActiveMQ Issue Type: Improvement Components: Documentation Reporter: Pat Fox Assignee: Torsten Mielke Priority: Minor Labels: documentation Attachments: InactivityMonitor.html I created a doc for the InactivityMonitor. Perhaps it could be added to the activemq docs? -- 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
Failure to build
Link actually. I get the error libtool: link: require no space between `-L' and `-R', which is found in all 3 Makefiles. I also noticed that in the XXX_LIB declarations in the Makefile we're getting -L/usr/lib6464 rather than -L/usr/lib64 Sorry if this is a repeat or the wrong forum, it's my first post. For the details, I get the same message on versions 3.4.1 and 3.4.4. Other version information: autoconf 2.63 libtool 2.2.6b automake 1.11.1 gcc 4.4.6 (doesn't matter but...) on a Redhat Linux platform, uname details below: Linux ceilidh.ait.psu.edu 2.6.32-220.17.1.el6.x86_64 #1 SMP Thu Apr 26 13:37:13 EDT 2012 x86_64 x86_64 x86_64 GNU/Linux Cheers, Shawn -- View this message in context: http://activemq.2283324.n4.nabble.com/Failure-to-build-tp4653673.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
[jira] [Created] (AMQ-3906) repeated error message regarding chunk stream logged
Rajib Rashid created AMQ-3906:
-
Summary: repeated error message regarding chunk stream logged
Key: AMQ-3906
URL: https://issues.apache.org/jira/browse/AMQ-3906
Project: ActiveMQ
Issue Type: Bug
Components: Broker
Affects Versions: 5.6.0
Environment: ActiveMQ 5.6.0 running on Linux FC10 x86
Reporter: Rajib Rashid
Attachments: activemq.xml
after running normally for ~24 hours, warning messages/errors like below are
logged every 30 seconds:
{code}
2012-06-27 14:33:31,532 org.apache.activemq.broker.region.Topic[ActiveMQ
Broker[ZyrionMessageBus] Scheduler]: (WARN) Failed to browse Topic:
remoteUpdateP2PTopic
java.io.EOFException: Chunk stream does not exist, page: 50 is marked free
at org.apache.kahadb.page.Transaction$2.readPage(Transaction.java:460)
at org.apache.kahadb.page.Transaction$2.init(Transaction.java:437)
at
org.apache.kahadb.page.Transaction.openInputStream(Transaction.java:434)
at org.apache.kahadb.page.Transaction.load(Transaction.java:410)
at org.apache.kahadb.page.Transaction.load(Transaction.java:367)
at org.apache.kahadb.index.BTreeIndex.loadNode(BTreeIndex.java:262)
at org.apache.kahadb.index.BTreeIndex.getRoot(BTreeIndex.java:174)
at org.apache.kahadb.index.BTreeIndex.iterator(BTreeIndex.java:232)
at
org.apache.activemq.store.kahadb.MessageDatabase$MessageOrderIndex$MessageOrderIterator.init(MessageDatabase.java:2714)
at
org.apache.activemq.store.kahadb.MessageDatabase$MessageOrderIndex.iterator(MessageDatabase.java:2696)
at
org.apache.activemq.store.kahadb.KahaDBStore$KahaDBMessageStore$3.execute(KahaDBStore.java:525)
at org.apache.kahadb.page.Transaction.execute(Transaction.java:769)
at
org.apache.activemq.store.kahadb.KahaDBStore$KahaDBMessageStore.recover(KahaDBStore.java:521)
at
org.apache.activemq.store.ProxyTopicMessageStore.recover(ProxyTopicMessageStore.java:62)
at org.apache.activemq.broker.region.Topic.doBrowse(Topic.java:559)
at org.apache.activemq.broker.region.Topic.access$100(Topic.java:62)
at org.apache.activemq.broker.region.Topic$6.run(Topic.java:684)
at
org.apache.activemq.thread.SchedulerTimerTask.run(SchedulerTimerTask.java:33)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
{code}
since then the warning has been logged 6000+ times. not sure if this is due to
the fact that we have enabled expiration of queued messages for offline
subscribers.
{code}
% ls -l apps/activemq/data/kahadb/
total 32068
-rw-r--r-- 1 root root 33030144 2012-06-29 14:44 db-14.log
-rw-r--r-- 1 root root 339968 2012-06-29 14:44 db.data
-rw-r--r-- 1 root root 196984 2012-06-29 14:44 db.redo
-rw-r--r-- 1 root root0 2012-06-26 16:40 lock
{code}
--
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] [Updated] (AMQ-3906) repeated error message regarding chunk stream logged
[
https://issues.apache.org/jira/browse/AMQ-3906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajib Rashid updated AMQ-3906:
--
Attachment: activemq.xml
configuration file
repeated error message regarding chunk stream logged
Key: AMQ-3906
URL: https://issues.apache.org/jira/browse/AMQ-3906
Project: ActiveMQ
Issue Type: Bug
Components: Broker
Affects Versions: 5.6.0
Environment: ActiveMQ 5.6.0 running on Linux FC10 x86
Reporter: Rajib Rashid
Attachments: activemq.xml
after running normally for ~24 hours, warning messages/errors like below are
logged every 30 seconds:
{code}
2012-06-27 14:33:31,532 org.apache.activemq.broker.region.Topic[ActiveMQ
Broker[ZyrionMessageBus] Scheduler]: (WARN) Failed to browse Topic:
remoteUpdateP2PTopic
java.io.EOFException: Chunk stream does not exist, page: 50 is marked free
at org.apache.kahadb.page.Transaction$2.readPage(Transaction.java:460)
at org.apache.kahadb.page.Transaction$2.init(Transaction.java:437)
at
org.apache.kahadb.page.Transaction.openInputStream(Transaction.java:434)
at org.apache.kahadb.page.Transaction.load(Transaction.java:410)
at org.apache.kahadb.page.Transaction.load(Transaction.java:367)
at org.apache.kahadb.index.BTreeIndex.loadNode(BTreeIndex.java:262)
at org.apache.kahadb.index.BTreeIndex.getRoot(BTreeIndex.java:174)
at org.apache.kahadb.index.BTreeIndex.iterator(BTreeIndex.java:232)
at
org.apache.activemq.store.kahadb.MessageDatabase$MessageOrderIndex$MessageOrderIterator.init(MessageDatabase.java:2714)
at
org.apache.activemq.store.kahadb.MessageDatabase$MessageOrderIndex.iterator(MessageDatabase.java:2696)
at
org.apache.activemq.store.kahadb.KahaDBStore$KahaDBMessageStore$3.execute(KahaDBStore.java:525)
at org.apache.kahadb.page.Transaction.execute(Transaction.java:769)
at
org.apache.activemq.store.kahadb.KahaDBStore$KahaDBMessageStore.recover(KahaDBStore.java:521)
at
org.apache.activemq.store.ProxyTopicMessageStore.recover(ProxyTopicMessageStore.java:62)
at org.apache.activemq.broker.region.Topic.doBrowse(Topic.java:559)
at org.apache.activemq.broker.region.Topic.access$100(Topic.java:62)
at org.apache.activemq.broker.region.Topic$6.run(Topic.java:684)
at
org.apache.activemq.thread.SchedulerTimerTask.run(SchedulerTimerTask.java:33)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
{code}
since then the warning has been logged 6000+ times. not sure if this is due
to the fact that we have enabled expiration of queued messages for offline
subscribers.
{code}
% ls -l apps/activemq/data/kahadb/
total 32068
-rw-r--r-- 1 root root 33030144 2012-06-29 14:44 db-14.log
-rw-r--r-- 1 root root 339968 2012-06-29 14:44 db.data
-rw-r--r-- 1 root root 196984 2012-06-29 14:44 db.redo
-rw-r--r-- 1 root root0 2012-06-26 16:40 lock
{code}
--
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
