[jira] [Created] (AMQ-4496) Error formatting macro on how to use SSL page
Kot Kot created AMQ-4496: Summary: Error formatting macro on how to use SSL page Key: AMQ-4496 URL: https://issues.apache.org/jira/browse/AMQ-4496 Project: ActiveMQ Issue Type: Bug Components: Documentation Reporter: Kot Kot Error formatting macro: snippet: java.lang.IndexOutOfBoundsException: Index: 20, Size: 20 http://activemq.apache.org/how-do-i-use-ssl.html -- 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-4496) Error formatting macro on how to use SSL page
[ https://issues.apache.org/jira/browse/AMQ-4496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13645341#comment-13645341 ] Kot Kot commented on AMQ-4496: -- Also link to SslTransportFactory.java right after the code snippet is broken Error formatting macro on how to use SSL page - Key: AMQ-4496 URL: https://issues.apache.org/jira/browse/AMQ-4496 Project: ActiveMQ Issue Type: Bug Components: Documentation Reporter: Kot Kot Error formatting macro: snippet: java.lang.IndexOutOfBoundsException: Index: 20, Size: 20 http://activemq.apache.org/how-do-i-use-ssl.html -- 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-4497) Shared File System Master/Slave function broken with NFSv4 after network back stable
Eden Chen created AMQ-4497: -- Summary: Shared File System Master/Slave function broken with NFSv4 after network back stable Key: AMQ-4497 URL: https://issues.apache.org/jira/browse/AMQ-4497 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 5.5.1 Environment: NFSv4 Reporter: Eden Chen In the experiment, I used kahaDB to be the persistenceAdapter. The setting is like: persistenceAdapter kahaDB directory=/nfs4/server/data/kahadb/ /persistenceAdapter There are 2 brokers in different machines, and the NFS server is installed in one of the machines. I will use broker1 to present the one without out NFS server and broker2 for the other one. I start broker1 earlier then brokerQ2, so the broker1 grab the file lock and be the master, broker2 be slave brokers and sit in a loop trying to grab the lock from the master broker. Then I disconnect broker1's network, broker2 can grab the file lock and start working after a while, Broker1 is still alive and don't show any error message. After broker2 starting working, I enable broker1's network, both broker1 and broker2 can serve client's request at the same time (I can use webconsole to send message for both brokers). Both master and slave broker can grab the same file lock and receive client's request, this can cause losing message or restart AMQ failed. -- 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-4498) After Brutal shutdown ActiveMQ throw java.io.StreamCorruptedException
Almog Shunim created AMQ-4498: - Summary: After Brutal shutdown ActiveMQ throw java.io.StreamCorruptedException Key: AMQ-4498 URL: https://issues.apache.org/jira/browse/AMQ-4498 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 5.4.2 Environment: Red hat linux 6.2, java 1.6.0_30 Reporter: Almog Shunim Fix For: 5.x After Brutal shutdown to machine where ActiveMQ is working, I'm trying to start the activemq and I'm getting the following exception: 2013-04-29 12:20:26,599 | INFO | Transport failed: java.io.EOFException | org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ Transport: tcp:///1.9.36.15:58082 2013-04-29 17:10:04,613 | INFO | Refreshing org.apache.activemq.xbean.XBeanBrokerFactory$1@5488e2dd: startup date [Mon Apr 29 17:10:04 IDT 2013]; root of context hierarchy | org.apache.activemq.xbean.XBeanBrokerFactory$1 | main 2013-04-29 17:10:15,315 | WARN | destroyApplicationContextOnStop parameter is deprecated, please use shutdown hooks instead | org.apache.activemq.xbean.XBeanBrokerService | main 2013-04-29 17:10:15,633 | INFO | PListStore:/opt/ccih/BDRE/0.10/apache-activemq-5.4.2/data/localhost/tmp_storage started | org.apache.activemq.store.kahadb.plist.PListStore | main 2013-04-29 17:10:15,841 | INFO | Using Persistence Adapter: KahaDBPersistenceAdapter[/opt/ccih/BDRE/0.10/apache-activemq-5.4.2/data/kahadb] | org.apache.activemq.broker.BrokerService | main 2013-04-29 17:10:19,229 | INFO | KahaDB is version 3 | org.apache.activemq.store.kahadb.MessageDatabase | main 2013-04-29 17:10:19,843 | ERROR | Failed to start ActiveMQ JMS Message Broker. Reason: java.io.StreamCorruptedException: invalid type code: 00 | org.apache.activemq.broker.BrokerService | main java.io.StreamCorruptedException: invalid type code: 00 at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1355) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:350) at java.util.LinkedList.readObject(LinkedList.java:964) at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:974) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1848) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1752) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1328) at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1946) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1870) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1752) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1328) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:350) at java.util.HashMap.readObject(HashMap.java:1030) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:974) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1848) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1752) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1328) at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1946) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1870) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1752) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1328) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:350) at org.apache.activemq.store.kahadb.MessageDatabase.recoverProducerAudit(MessageDatabase.java:487) at org.apache.activemq.store.kahadb.MessageDatabase.recover(MessageDatabase.java:438) at org.apache.activemq.store.kahadb.MessageDatabase.open(MessageDatabase.java:315) at org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:357) at org.apache.activemq.store.kahadb.MessageDatabase.doStart(MessageDatabase.java:222) at org.apache.activemq.store.kahadb.KahaDBStore.doStart(KahaDBStore.java:180) at org.apache.activemq.util.ServiceSupport.start(ServiceSupport.java:53) at
[jira] [Commented] (AMQ-4489) Newly received messages with higher priority are never consumed, until broker is restarted
[ https://issues.apache.org/jira/browse/AMQ-4489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13645373#comment-13645373 ] metatech commented on AMQ-4489: --- Gary, thanks for looking into this. I just tried with the ZIP from Hudson build ActiveMQ-Java7 #187 and the problem is still present. Beware that the asserts have been disabled in the test driver, otherwise it is impossible to see how many messages are not sorted according to priority (it aborts on the first failed one). The easiest way to see it is to change the parameter redirectTestOutputToFile in the root pom.xml to false, and launch the following command : mvn -Dtest=JDBCMessagePriorityTest#testQueues test. Newly received messages with higher priority are never consumed, until broker is restarted -- Key: AMQ-4489 URL: https://issues.apache.org/jira/browse/AMQ-4489 Project: ActiveMQ Issue Type: Bug Components: Broker, Message Store Affects Versions: 5.5.1 Environment: ServiceMix 4.4.2, using Camel producers/consumers Reporter: metatech Attachments: MessagePriorityTest_frozen.java, MessagePriorityTest.java, MessagePriorityTest_workaround.java We configured message prioritization according to the following page : http://activemq.apache.org/how-can-i-support-priority-queues.html We use a JDBC adapter for message persistence, in an Oracle database. Prioritisation is enabled on the queue with the prioritizedMessages option, and we also specify a memory limit for the queue (24 MB) We use ActiveMQ 5.5.1 within ServiceMix 4.4.2, and use Camel JMS producers/consumers. Message can have 2 priorities : 4 (normal) for non-business hours and 9 (high) for business hours. The scenario to reproduce the problem is the following : 1. Enqueue 1000 normal and 1000 high messages. 2. All high messages are consumed first. 3. After a few normal messages are consumed, enqueue additional 1000 high messages. 4. All normal messages are consumed before high messages. 5. All additional high 1000 messages are never consumed. 6. Restart broker. 7. All additional high 1000 messages start getting consumed. In production, we have a producer with high peaks during the night (10,000-100,000 messages/hour), and 6 consumers (about 5,000-10,000 messages/hour), so the queue can reach 100,000-200,000 messages at some periods of the day. Messages are small (200 bytes). We enabled SQL query tracing on the broker (with log4jdbc), and we see that the logic with which the findNextMessagesByPriorityStatement query is called does not seem correct in the JDBCMessageStore.recoverNextMessages method : At step 2, we see the following query being executed : SELECT ID, MSG FROM ACTIVEMQ_MSGS WHERE CONTAINER='priorityQueue' AND ((ID 200 AND PRIORITY = 9) OR PRIORITY 9) ORDER BY PRIORITY DESC, ID At step 4, we see the following query being executed : SELECT ID, MSG FROM ACTIVEMQ_MSGS WHERE CONTAINER='priorityQueue' AND ((ID 1200 AND PRIORITY = 4) OR PRIORITY 4) ORDER BY PRIORITY DESC, ID The problem is that the value for the last priority stored in the lastRecoveredPriority variable of the JDBCMessageStore stays permanently to 4, until step 6, where it is reset to 9. We tried changing the priority to constant '9' in the query. It works OK until step 3, where only 200 messages are consumed Our understanding is that there should be one lastRecoveredSequenceId variable for each priority level, so that the last consumed message but not yet removed from the DB is memorized, and also the priority should probably also be reset to 9 every time the query is executed. Can you have a look please ? -- 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
Build failed in Jenkins: ActiveMQ-Java7 » ActiveMQ :: MQTT Protocol #188
See https://builds.apache.org/job/ActiveMQ-Java7/org.apache.activemq$activemq-mqtt/188/ -- [INFO] [INFO] [INFO] Building ActiveMQ :: MQTT Protocol 5.9-SNAPSHOT [INFO] Downloading: http://repo.maven.apache.org/maven2/org/eclipse/jetty/maven-jetty-plugin/7.6.7.v20120910/maven-jetty-plugin-7.6.7.v20120910.pom [WARNING] The POM for org.eclipse.jetty:maven-jetty-plugin:jar:7.6.7.v20120910 is missing, no dependency information available [WARNING] Failed to retrieve plugin descriptor for org.eclipse.jetty:maven-jetty-plugin:7.6.7.v20120910: Plugin org.eclipse.jetty:maven-jetty-plugin:7.6.7.v20120910 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.eclipse.jetty:maven-jetty-plugin:jar:7.6.7.v20120910 [INFO] [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ activemq-mqtt --- [INFO] [INFO] --- maven-enforcer-plugin:1.0.1:enforce (default) @ activemq-mqtt --- [INFO] [INFO] --- maven-bundle-plugin:2.3.7:cleanVersions (cleanVersions) @ activemq-mqtt --- [INFO] [WARNING] No proto files found in directory: https://builds.apache.org/job/ActiveMQ-Java7/org.apache.activemq$activemq-mqtt/ws/src/main/proto [INFO] --- activemq-protobuf:1.1:compile (default) @ activemq-mqtt --- [INFO] [INFO] --- maven-remote-resources-plugin:1.3:process (default) @ activemq-mqtt --- [debug] execute contextualize [INFO] [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 5 resources [INFO] skip non existing resourceDirectory https://builds.apache.org/job/ActiveMQ-Java7/org.apache.activemq$activemq-mqtt/ws/src/main/filtered-resources [INFO] Copying 3 resources [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ activemq-mqtt --- [INFO] [INFO] Compiling 16 source files to https://builds.apache.org/job/ActiveMQ-Java7/org.apache.activemq$activemq-mqtt/ws/target/classes [INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ activemq-mqtt --- [debug] execute contextualize [INFO] [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 3 resources [INFO] Copying 3 resources [INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ activemq-mqtt --- [INFO] [INFO] Compiling 6 source files to https://builds.apache.org/job/ActiveMQ-Java7/org.apache.activemq$activemq-mqtt/ws/target/test-classes [INFO] --- maven-compiler-plugin:2.5.1:testCompile (default-testCompile) @ activemq-mqtt --- [INFO] [INFO] Surefire report directory: https://builds.apache.org/job/ActiveMQ-Java7/org.apache.activemq$activemq-mqtt/ws/target/surefire-reports --- T E S T S --- --- T E S T S --- [INFO] --- maven-surefire-plugin:2.10:test (default-test) @ activemq-mqtt --- Running org.apache.activemq.transport.mqtt.MQTTNioTest Tests run: 15, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 148.016 sec Running org.apache.activemq.transport.mqtt.MQTTSSLTest Tests run: 14, Failures: 0, Errors: 14, Skipped: 0, Time elapsed: 3,939.715 sec FAILURE! Running org.apache.activemq.transport.mqtt.MQTTTest Tests run: 14, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 146.315 sec Results : Tests in error: testDefaultKeepAliveWhenClientSpecifiesZero(org.apache.activemq.transport.mqtt.MQTTSSLTest): test timed out after 3 milliseconds testReuseConnection(org.apache.activemq.transport.mqtt.MQTTSSLTest): test timed out after 30 milliseconds testPingKeepsInactivityMonitorAlive(org.apache.activemq.transport.mqtt.MQTTSSLTest): test timed out after 30 milliseconds testTurnOffInactivityMonitor(org.apache.activemq.transport.mqtt.MQTTSSLTest): test timed out after 30 milliseconds testSendAndReceiveAtLeastOnce(org.apache.activemq.transport.mqtt.MQTTSSLTest): test timed out after 30 milliseconds testSendAtLeastOnceReceiveAtMostOnce(org.apache.activemq.transport.mqtt.MQTTSSLTest): test timed out after 30 milliseconds testSendAtMostOnceReceiveExactlyOnce(org.apache.activemq.transport.mqtt.MQTTSSLTest): test timed out after 30 milliseconds testSendAndReceiveExactlyOnce(org.apache.activemq.transport.mqtt.MQTTSSLTest): test timed out after 30 milliseconds testSendMQTTReceiveJMS(org.apache.activemq.transport.mqtt.MQTTSSLTest): test timed out after 30 milliseconds testSendAndReceiveAtMostOnce(org.apache.activemq.transport.mqtt.MQTTSSLTest): test timed out after 30 milliseconds testSendAtLeastOnceReceiveExactlyOnce(org.apache.activemq.transport.mqtt.MQTTSSLTest): test timed out after 30 milliseconds
Build failed in Jenkins: ActiveMQ-Java7 #188
See https://builds.apache.org/job/ActiveMQ-Java7/188/changes Changes: [chirino] Added an new ElectingLevelDBStore which handles the M/S election bits using ZooKeeper. -- [...truncated 7106 lines...] [INFO] ActiveMQ :: Web Console ... SKIPPED [INFO] ActiveMQ :: Karaf Integration Tests ... SKIPPED [INFO] ActiveMQ :: Integration Test :: Spring 3.1 SKIPPED [INFO] ActiveMQ :: Assembly .. SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 2:17:21.189s [INFO] Finished at: Tue Apr 30 09:49:02 UTC 2013 [INFO] Final Memory: 77M/970M [INFO] [JENKINS] Archiving https://builds.apache.org/job/ActiveMQ-Java7/ws/activemq-client/pom.xml to /home/hudson/hudson/jobs/ActiveMQ-Java7/modules/org.apache.activemq$activemq-client/builds/2013-04-30_07-31-09/archive/org.apache.activemq/activemq-client/5.9-SNAPSHOT/activemq-client-5.9-SNAPSHOT.pom [JENKINS] Archiving https://builds.apache.org/job/ActiveMQ-Java7/ws/activemq-client/target/activemq-client-5.9-SNAPSHOT.jar to /home/hudson/hudson/jobs/ActiveMQ-Java7/modules/org.apache.activemq$activemq-client/builds/2013-04-30_07-31-09/archive/org.apache.activemq/activemq-client/5.9-SNAPSHOT/activemq-client-5.9-SNAPSHOT.jar [JENKINS] Archiving https://builds.apache.org/job/ActiveMQ-Java7/ws/activemq-client/target/activemq-client-5.9-SNAPSHOT-sources.jar to /home/hudson/hudson/jobs/ActiveMQ-Java7/modules/org.apache.activemq$activemq-client/builds/2013-04-30_07-31-09/archive/org.apache.activemq/activemq-client/5.9-SNAPSHOT/activemq-client-5.9-SNAPSHOT-sources.jar [JENKINS] Archiving https://builds.apache.org/job/ActiveMQ-Java7/ws/activemq-camel/pom.xml to /home/hudson/hudson/jobs/ActiveMQ-Java7/modules/org.apache.activemq$activemq-camel/builds/2013-04-30_07-31-11/archive/org.apache.activemq/activemq-camel/5.9-SNAPSHOT/activemq-camel-5.9-SNAPSHOT.pom [JENKINS] Archiving https://builds.apache.org/job/ActiveMQ-Java7/ws/pom.xml to /home/hudson/hudson/jobs/ActiveMQ-Java7/modules/org.apache.activemq$activemq-parent/builds/2013-04-30_07-31-09/archive/org.apache.activemq/activemq-parent/5.9-SNAPSHOT/activemq-parent-5.9-SNAPSHOT.pom [JENKINS] Archiving https://builds.apache.org/job/ActiveMQ-Java7/ws/assembly/pom.xml to /home/hudson/hudson/jobs/ActiveMQ-Java7/modules/org.apache.activemq$apache-activemq/builds/2013-04-30_07-31-15/archive/org.apache.activemq/apache-activemq/5.9-SNAPSHOT/apache-activemq-5.9-SNAPSHOT.pom [JENKINS] Archiving https://builds.apache.org/job/ActiveMQ-Java7/ws/activemq-tooling/pom.xml to /home/hudson/hudson/jobs/ActiveMQ-Java7/modules/org.apache.activemq.tooling$activemq-tooling/builds/2013-04-30_07-31-13/archive/org.apache.activemq.tooling/activemq-tooling/5.9-SNAPSHOT/activemq-tooling-5.9-SNAPSHOT.pom [JENKINS] Archiving https://builds.apache.org/job/ActiveMQ-Java7/ws/activemq-pool/pom.xml to /home/hudson/hudson/jobs/ActiveMQ-Java7/modules/org.apache.activemq$activemq-pool/builds/2013-04-30_07-31-12/archive/org.apache.activemq/activemq-pool/5.9-SNAPSHOT/activemq-pool-5.9-SNAPSHOT.pom [JENKINS] Archiving https://builds.apache.org/job/ActiveMQ-Java7/ws/activemq-pool/target/activemq-pool-5.9-SNAPSHOT.jar to /home/hudson/hudson/jobs/ActiveMQ-Java7/modules/org.apache.activemq$activemq-pool/builds/2013-04-30_07-31-12/archive/org.apache.activemq/activemq-pool/5.9-SNAPSHOT/activemq-pool-5.9-SNAPSHOT.jar [JENKINS] Archiving https://builds.apache.org/job/ActiveMQ-Java7/ws/activemq-pool/target/activemq-pool-5.9-SNAPSHOT-sources.jar to /home/hudson/hudson/jobs/ActiveMQ-Java7/modules/org.apache.activemq$activemq-pool/builds/2013-04-30_07-31-12/archive/org.apache.activemq/activemq-pool/5.9-SNAPSHOT/activemq-pool-5.9-SNAPSHOT-sources.jar [JENKINS] Archiving https://builds.apache.org/job/ActiveMQ-Java7/ws/activemq-karaf-itest/pom.xml to /home/hudson/hudson/jobs/ActiveMQ-Java7/modules/org.apache.activemq$activemq-karaf-itest/builds/2013-04-30_07-31-15/archive/org.apache.activemq/activemq-karaf-itest/5.9-SNAPSHOT/activemq-karaf-itest-5.9-SNAPSHOT.pom [JENKINS] Archiving https://builds.apache.org/job/ActiveMQ-Java7/ws/activemq-broker/pom.xml to /home/hudson/hudson/jobs/ActiveMQ-Java7/modules/org.apache.activemq$activemq-broker/builds/2013-04-30_07-31-09/archive/org.apache.activemq/activemq-broker/5.9-SNAPSHOT/activemq-broker-5.9-SNAPSHOT.pom [JENKINS] Archiving https://builds.apache.org/job/ActiveMQ-Java7/ws/activemq-broker/target/activemq-broker-5.9-SNAPSHOT.jar to /home/hudson/hudson/jobs/ActiveMQ-Java7/modules/org.apache.activemq$activemq-broker/builds/2013-04-30_07-31-09/archive/org.apache.activemq/activemq-broker/5.9-SNAPSHOT/activemq-broker-5.9-SNAPSHOT.jar [JENKINS] Archiving
[jira] [Commented] (AMQCPP-476) Reading of Stomp Frame with content length may throw excecption
[ https://issues.apache.org/jira/browse/AMQCPP-476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13645433#comment-13645433 ] Jeremy Leung commented on AMQCPP-476: - Is the fix okay? Reading of Stomp Frame with content length may throw excecption --- Key: AMQCPP-476 URL: https://issues.apache.org/jira/browse/AMQCPP-476 Project: ActiveMQ C++ Client Issue Type: Bug Components: Stomp Affects Versions: 3.6.0 Environment: Solaris 10 Apollo AMQ Reporter: Jeremy Leung Assignee: Timothy Bish Attachments: consumer.cpp, Publisher.java, StompFrame.cpp.patch.txt, unit_test.txt -- HOW TO REPRODUCE -- 1) Setup a consumer to listen for messages on Topic XXX using CMS with stomp. 2) Setup a publisher to send a messages from java JMS interface to Topic XXX continually. (with org.fusesource.stomp.jms.*) 3) An exception is thrown in consumer from StompWireFormat::readStompBody() with description Read Content Length, and no trailing null -- BLOCK DIAGRAM -- All components are in different hosts and all run under Solaris 10 environment. | C++ CONSUMER | - | APOLLO 1.6 / AMQ 5.4.2 | - | JAVA PUBLISHER | or | C++ CONSUMER | - | APOLLO 1.6 / AMQ 5.4.2 | - | C++ PUBLISHER | -- 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
Jenkins build is back to normal : ActiveMQ-Trunk-Deploy #765
See https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/765/changes
[jira] [Resolved] (AMQ-4494) Cursor hasSpace() doesn't check system usage
[ https://issues.apache.org/jira/browse/AMQ-4494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dejan Bosanac resolved AMQ-4494. Resolution: Duplicate Cursor hasSpace() doesn't check system usage Key: AMQ-4494 URL: https://issues.apache.org/jira/browse/AMQ-4494 Project: ActiveMQ Issue Type: Bug Affects Versions: 5.8.0 Reporter: Dejan Bosanac Assignee: Dejan Bosanac Fix For: 5.9.0 When checking for space, every cursor checks its destinations memory usage. Unfortunately, that doesn't check the parent (system usage) so with large number of destinations when total sum of per destination limits is larger than total system memory usage, we can brake the system usage memory limit. -- 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] [Resolved] (AMQ-4467) Memory usage percent can be exceeded much if PFC is disabled
[ https://issues.apache.org/jira/browse/AMQ-4467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dejan Bosanac resolved AMQ-4467. Resolution: Fixed Assignee: Dejan Bosanac This is now fixed with svn revision 1477574. Thanks for raising the issue and providing the test case. Memory usage percent can be exceeded much if PFC is disabled Key: AMQ-4467 URL: https://issues.apache.org/jira/browse/AMQ-4467 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 5.x Reporter: SuoNayi Assignee: Dejan Bosanac Fix For: 5.9.0 Attachments: AMQ-4467.patch If PFC is disabled, when the store cursor checks limits, it checks only the memory percentage of its own MemoryUsage and compares it to the high water mark. Otherwise if PFC is enabled, it checks whether the MemoryUsage is full but the isFull method also checks its parents. This issue arrises when you have memory limits set on queues higher than the overall system limit, as well as if you have multiple queues who's memory limits combined are higher than the overall system limit. These settings must be taken into account. The original form can be found at http://activemq.2283324.n4.nabble.com/What-can-be-reason-of-460-memory-usage-limit-td4665651.html -- 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
Build failed in Jenkins: ActiveMQ #1276
See https://builds.apache.org/job/ActiveMQ/1276/changes Changes: [dejanb] https://issues.apache.org/jira/browse/AMQ-4467 - cursor memory usage when pfc is off [chirino] Added an new ElectingLevelDBStore which handles the M/S election bits using ZooKeeper. -- [...truncated 5437 lines...] [WARNING] The POM for org.eclipse.jetty:maven-jetty-plugin:jar:7.6.7.v20120910 is missing, no dependency information available [WARNING] Failed to retrieve plugin descriptor for org.eclipse.jetty:maven-jetty-plugin:7.6.7.v20120910: Plugin org.eclipse.jetty:maven-jetty-plugin:7.6.7.v20120910 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.eclipse.jetty:maven-jetty-plugin:jar:7.6.7.v20120910 [INFO] [INFO] Building ActiveMQ :: JAAS 5.9-SNAPSHOT [INFO] [INFO] [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ activemq-jaas --- [INFO] [INFO] --- maven-enforcer-plugin:1.0.1:enforce (default) @ activemq-jaas --- [INFO] [INFO] --- maven-bundle-plugin:2.3.7:cleanVersions (cleanVersions) @ activemq-jaas --- [INFO] [INFO] --- maven-remote-resources-plugin:1.3:process (default) @ activemq-jaas --- [debug] execute contextualize [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory https://builds.apache.org/job/ActiveMQ/ws/activemq-jaas/src/main/resources [INFO] Copying 3 resources [INFO] [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ activemq-jaas --- [INFO] [INFO] Compiling 12 source files to https://builds.apache.org/job/ActiveMQ/ws/activemq-jaas/target/classes [INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ activemq-jaas --- [debug] execute contextualize [INFO] [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 6 resources [INFO] Copying 3 resources [INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ activemq-jaas --- [INFO] [INFO] Compiling 9 source files to https://builds.apache.org/job/ActiveMQ/ws/activemq-jaas/target/test-classes [INFO] --- maven-compiler-plugin:2.5.1:testCompile (default-testCompile) @ activemq-jaas --- [INFO] [INFO] Surefire report directory: https://builds.apache.org/job/ActiveMQ/ws/activemq-jaas/target/surefire-reports --- T E S T S --- [INFO] --- maven-surefire-plugin:2.10:test (default-test) @ activemq-jaas --- Running org.apache.activemq.jaas.UserPrincipalTest Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.029 sec Running org.apache.activemq.jaas.LDAPLoginModuleTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.993 sec Running org.apache.activemq.jaas.GroupPrincipalTest Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec Running org.apache.activemq.jaas.CertificateLoginModuleTest Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec Running org.apache.activemq.jaas.LDAPModuleRoleExpansionTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.739 sec Running org.apache.activemq.jaas.PropertiesLoginModuleTest Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.005 sec Running org.apache.activemq.jaas.GuestLoginModuleTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 sec Running org.apache.activemq.jaas.PropertiesLoginModuleRaceConditionTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 19.95 sec Results : Tests run: 19, Failures: 0, Errors: 0, Skipped: 0 [JENKINS] Recording test results [INFO] [INFO] Building jar: https://builds.apache.org/job/ActiveMQ/ws/activemq-jaas/target/activemq-jaas-5.9-SNAPSHOT.jar [INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ activemq-jaas --- [INFO] [INFO] --- maven-site-plugin:3.1:attach-descriptor (attach-descriptor) @ activemq-jaas --- [INFO] [INFO] Checking legal files in: activemq-jaas-5.9-SNAPSHOT.jar [INFO] --- ianal-maven-plugin:1.0-alpha-1:verify-legal-files (default) @ activemq-jaas --- [INFO] [INFO] Installing https://builds.apache.org/job/ActiveMQ/ws/activemq-jaas/target/activemq-jaas-5.9-SNAPSHOT.jar to /home/jenkins/jenkins-slave/maven-repositories/0/org/apache/activemq/activemq-jaas/5.9-SNAPSHOT/activemq-jaas-5.9-SNAPSHOT.jar [INFO] --- maven-install-plugin:2.3.1:install (default-install) @ activemq-jaas --- [INFO] Installing https://builds.apache.org/job/ActiveMQ/ws/activemq-jaas/pom.xml to /home/jenkins/jenkins-slave/maven-repositories/0/org/apache/activemq/activemq-jaas/5.9-SNAPSHOT/activemq-jaas-5.9-SNAPSHOT.pom [INFO] [INFO] --- maven-enforcer-plugin:1.0.1:enforce (default) @ activemq-jaas --- [INFO] [INFO] ---
[jira] [Created] (AMQ-4499) nhance the web console
hengyunabc created AMQ-4499: --- Summary: nhance the web console Key: AMQ-4499 URL: https://issues.apache.org/jira/browse/AMQ-4499 Project: ActiveMQ Issue Type: Improvement Reporter: hengyunabc 1. https://issues.apache.org/jira/browse/AMQ-4393 AMQ-4393 fix one error about the objectname of MBean, there are some other objectnames of MBean are not correct. 2. I found that the web console do not show the info of producers, I do not know why, so I try to enhance the web console. 3. I try to enable control the connector in the web console. Considering such scene: there are tow ports in a broker: inputPort and outputPort. When I want to upgrade the activemq totally, I can jsut stop the inputPort ,and wait for the queue/topic to be consumered through the outputPort. Then, stop the activemq, rm all old activemq files(include data files). Finally, deploy the new activemq, a clear upgrade finish. -- 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-4499) Enhance the web console
[ https://issues.apache.org/jira/browse/AMQ-4499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] hengyunabc updated AMQ-4499: Priority: Trivial (was: Major) Affects Version/s: 5.8.0 Summary: Enhance the web console (was: nhance the web console) Enhance the web console --- Key: AMQ-4499 URL: https://issues.apache.org/jira/browse/AMQ-4499 Project: ActiveMQ Issue Type: Improvement Affects Versions: 5.8.0 Reporter: hengyunabc Priority: Trivial 1. https://issues.apache.org/jira/browse/AMQ-4393 AMQ-4393 fix one error about the objectname of MBean, there are some other objectnames of MBean are not correct. 2. I found that the web console do not show the info of producers, I do not know why, so I try to enhance the web console. 3. I try to enable control the connector in the web console. Considering such scene: there are tow ports in a broker: inputPort and outputPort. When I want to upgrade the activemq totally, I can jsut stop the inputPort ,and wait for the queue/topic to be consumered through the outputPort. Then, stop the activemq, rm all old activemq files(include data files). Finally, deploy the new activemq, a clear upgrade finish. -- 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-4499) Enhance the web console
[ https://issues.apache.org/jira/browse/AMQ-4499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] hengyunabc updated AMQ-4499: Attachment: activemq-web-console_patch.txt activemq-web_path.txt activemq-broker_patch.txt connectors2.png topic2.png topic_active_producers2.png queue2.png connection2.png Enhance the web console --- Key: AMQ-4499 URL: https://issues.apache.org/jira/browse/AMQ-4499 Project: ActiveMQ Issue Type: Improvement Affects Versions: 5.8.0 Reporter: hengyunabc Priority: Trivial Attachments: activemq-broker_patch.txt, activemq-web-console_patch.txt, activemq-web_path.txt, connection2.png, connectors2.png, queue2.png, topic2.png, topic_active_producers2.png 1. https://issues.apache.org/jira/browse/AMQ-4393 AMQ-4393 fix one error about the objectname of MBean, there are some other objectnames of MBean are not correct. 2. I found that the web console do not show the info of producers, I do not know why, so I try to enhance the web console. 3. I try to enable control the connector in the web console. Considering such scene: there are tow ports in a broker: inputPort and outputPort. When I want to upgrade the activemq totally, I can jsut stop the inputPort ,and wait for the queue/topic to be consumered through the outputPort. Then, stop the activemq, rm all old activemq files(include data files). Finally, deploy the new activemq, a clear upgrade finish. -- 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
Jenkins build is unstable: ActiveMQ-Java7 #189
See https://builds.apache.org/job/ActiveMQ-Java7/189/changes
[jira] [Created] (AMQ-4500) Changes to AMQ2832Test cause SparseAckReplayAfterStoreCleanupLevelDBStoreTest to fail
Kevin Earls created AMQ-4500: Summary: Changes to AMQ2832Test cause SparseAckReplayAfterStoreCleanupLevelDBStoreTest to fail Key: AMQ-4500 URL: https://issues.apache.org/jira/browse/AMQ-4500 Project: ActiveMQ Issue Type: Bug Components: Test Cases Reporter: Kevin Earls Priority: Minor SparseAckReplayAfterStoreCleanupLevelDBStoreTest extends AMQ2832Test but uses LevelDB. The test case testAlternateLossScenario is dependent on KahaDB, so it fails under SparseAckReplayAfterStoreCleanupLevelDBStoreTest. I'll add a patch which skips this test when using LevelDB. -- 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-4500) Changes to AMQ2832Test cause SparseAckReplayAfterStoreCleanupLevelDBStoreTest to fail
[ https://issues.apache.org/jira/browse/AMQ-4500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Earls updated AMQ-4500: - Attachment: AMQ-4500.patch Changes to AMQ2832Test cause SparseAckReplayAfterStoreCleanupLevelDBStoreTest to fail - Key: AMQ-4500 URL: https://issues.apache.org/jira/browse/AMQ-4500 Project: ActiveMQ Issue Type: Bug Components: Test Cases Reporter: Kevin Earls Priority: Minor Attachments: AMQ-4500.patch SparseAckReplayAfterStoreCleanupLevelDBStoreTest extends AMQ2832Test but uses LevelDB. The test case testAlternateLossScenario is dependent on KahaDB, so it fails under SparseAckReplayAfterStoreCleanupLevelDBStoreTest. I'll add a patch which skips this test when using LevelDB. -- 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] [Resolved] (AMQ-4500) Changes to AMQ2832Test cause SparseAckReplayAfterStoreCleanupLevelDBStoreTest to fail
[ https://issues.apache.org/jira/browse/AMQ-4500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-4500. --- Resolution: Fixed patch applied, thanks. Changes to AMQ2832Test cause SparseAckReplayAfterStoreCleanupLevelDBStoreTest to fail - Key: AMQ-4500 URL: https://issues.apache.org/jira/browse/AMQ-4500 Project: ActiveMQ Issue Type: Bug Components: Test Cases Reporter: Kevin Earls Priority: Minor Attachments: AMQ-4500.patch SparseAckReplayAfterStoreCleanupLevelDBStoreTest extends AMQ2832Test but uses LevelDB. The test case testAlternateLossScenario is dependent on KahaDB, so it fails under SparseAckReplayAfterStoreCleanupLevelDBStoreTest. I'll add a patch which skips this test when using LevelDB. -- 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] [Resolved] (AMQNET-434) FailoverTransport Memory Leak with TransactionState
[ https://issues.apache.org/jira/browse/AMQNET-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQNET-434. - Resolution: Fixed patch applied, thanks FailoverTransport Memory Leak with TransactionState --- Key: AMQNET-434 URL: https://issues.apache.org/jira/browse/AMQNET-434 Project: ActiveMQ .Net Issue Type: Bug Affects Versions: 1.5.6 Reporter: Daniel Marbach Assignee: Timothy Bish Fix For: 1.6.0 Attachments: ConnectionStateTrackerMemoryLeak.cs I'm hunting down a possible memory leak. We have the following problem in production: when the consumer/subscriber endpoint runs for a long time with failover transport enabled the memory grows indefinitely. I used YouTrack and AntsProfiler to hunt down the issues. The retention path I see in production is the following: The FailoverTransport nested class FailoverTask has two ConnectionStateTrackers this keeps a dictionary which links the ConnectionId to the ConnectionState. The ConnectionState itself has a dictionary which links the transactionId to the TransactionState. The TranscationState tracks commands. BUT these commands are never freed up from the transaction state and stay there forever which will blow up the memory some time. I'm currently investigation how to fix this but must first properly understand the code. I opened up this issue in the hope that it will ring a bell for you guys. Daniel -- 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] (AMQNET-437) Add ConnectTimeout property to TcpTransportFactory
Timothy Bish created AMQNET-437:
---
Summary: Add ConnectTimeout property to TcpTransportFactory
Key: AMQNET-437
URL: https://issues.apache.org/jira/browse/AMQNET-437
Project: ActiveMQ .Net
Issue Type: New Feature
Components: ActiveMQ
Affects Versions: 1.5.6
Reporter: Timothy Bish
Assignee: Jim Gomes
Priority: Minor
Fix For: 1.6.0
Add a connect timeout option (default 30secs) to the TcpTransportFactory to
allow fine grained control of how long a socket connect blocks before giving
up. This can be accomplished using the async connection style and a simple
wait on the result object from BeginConnect().
Allows for Uri syntax
{noformat}
tcp://127.0.0.1:61616?transport.connectTimeout=5000
{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] [Resolved] (AMQNET-437) Add ConnectTimeout property to TcpTransportFactory
[
https://issues.apache.org/jira/browse/AMQNET-437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQNET-437.
-
Resolution: Fixed
Assignee: Timothy Bish (was: Jim Gomes)
Fixed on trunk.
Add ConnectTimeout property to TcpTransportFactory
--
Key: AMQNET-437
URL: https://issues.apache.org/jira/browse/AMQNET-437
Project: ActiveMQ .Net
Issue Type: New Feature
Components: ActiveMQ
Affects Versions: 1.5.6
Reporter: Timothy Bish
Assignee: Timothy Bish
Priority: Minor
Fix For: 1.6.0
Add a connect timeout option (default 30secs) to the TcpTransportFactory to
allow fine grained control of how long a socket connect blocks before giving
up. This can be accomplished using the async connection style and a simple
wait on the result object from BeginConnect().
Allows for Uri syntax
{noformat}
tcp://127.0.0.1:61616?transport.connectTimeout=5000
{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] [Resolved] (AMQNET-436) Pull Consumers can return immediately when connection is not active when a timed receive is called.
[ https://issues.apache.org/jira/browse/AMQNET-436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQNET-436. - Resolution: Fixed This is now fixed on trunk. Pull Consumers can return immediately when connection is not active when a timed receive is called. --- Key: AMQNET-436 URL: https://issues.apache.org/jira/browse/AMQNET-436 Project: ActiveMQ .Net Issue Type: Improvement Components: ActiveMQ Affects Versions: 1.5.6 Reporter: Timothy Bish Assignee: Timothy Bish Priority: Minor Fix For: 1.6.0 For Connections that use Failover and MessageConsumers that have a zero prefetch a timed receive can simply return immediately instead of blocking or throwing am exception if a send timeout is configured. -- 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] (AMQNET-425) Add support for updateClusterClients to Failover Transport
[
https://issues.apache.org/jira/browse/AMQNET-425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13646024#comment-13646024
]
Timothy Bish commented on AMQNET-425:
-
I've improved this on trunk, would be good if you could try out a trunk build
(1.6.0) and see if this now works as you expect.
Add support for updateClusterClients to Failover Transport
--
Key: AMQNET-425
URL: https://issues.apache.org/jira/browse/AMQNET-425
Project: ActiveMQ .Net
Issue Type: Improvement
Components: NMS
Affects Versions: 1.5.5, 1.5.6
Environment: We have developed a NET4.0 application (Producer
Consumer) using:
-Apache.NMS 1.5.0
-Apache.NMS.activeMQ 1.5.5
vmware vsphere 4.1
-CentOS 6 32bits (AQsrv1 AQsrv2)
-JRE6
-Fuse Message Broker v5.5.1
Reporter: Marc Rodrigues
Assignee: Timothy Bish
Fix For: 1.6.0
Hello,
The NMS failover client does not yet support the updateClusterClients
options, so it won't respond to the list of brokers provided by the server.
The workaround is to provide the static list or use some other discovery
mechanism like multicast.
Issue reported via forum :
Our goal is to use a network of brokers with failover and dynamic discovery
(production environment will have around 100 brokers).
So we have configured 2 CentOS virtual machine for test:
vmware vsphere 4.1
-CentOS 6 32bits (AQsrv1 AQsrv2)
-JRE6
-Fuse Message Broker v5.5.1 (see activemq.xml configuration at the end)
We have developed a NET4.0 application (Producer Consumer) using:
-Apache.NMS 1.5.0
-Apache.NMS.activeMQ 1.5.5
If I use the following URI to connect:
activemq:failover://(tcp://AQsrv1:61616,tcp://AQsrv2:61616)?transport.randomize=truetransport.startupMaxReconnectAttempts=0transport.timeout=2000nms.AsyncSend=true
- when I stop the activeMQ process on AQsrv1: the failover works fine and
application continue to send/consume messages on AQsrv2.
Now If I use the following URI:
activemq:failover://(tcp://AQsrv1:61616)?transport.randomize=truetransport.startupMaxReconnectAttempts=0transport.timeout=2000nms.AsyncSend=true
- when I stop the activeMQ process on AQsrv1: the failover seems to not work
anymore and my application is not able to connect to AQsrv2 automatically.
As I'm supposed to received a list of brokers (so AQsrv2) from AQsrv1
activemq.xml on both servers
networkConnectors
networkConnector
name=ncelab-activeMQ
uri=multicast://default?group=ncelab
dynamicOnly=true
networkTTL=2
duplex=true
prefetchSize=1
decreaseNetworkConsumerPriority=false /
/networkConnectors
persistenceAdapter
kahaDB directory=${activemq.data}/kahadb/
/persistenceAdapter
transportConnectors
transportConnector name=openwire
uri=tcp://0.0.0.0:61616
discoveryUri=multicast://default?group=ncelab
enableStatusMonitor=true
rebalanceClusterClients=true
updateClusterClients=true
updateClusterClientsOnRemove=true /
/transportConnectors
--
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] (AMQNET-403) Add support for priortiy URIs to Failover transport
[ https://issues.apache.org/jira/browse/AMQNET-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13646059#comment-13646059 ] Timothy Bish commented on AMQNET-403: - This feature is now implemented on trunk. Could stand to have some testing done if you want to try out a trunk build and see how it works for you. Add support for priortiy URIs to Failover transport --- Key: AMQNET-403 URL: https://issues.apache.org/jira/browse/AMQNET-403 Project: ActiveMQ .Net Issue Type: New Feature Components: ActiveMQ Reporter: Boris Rybalkin Assignee: Timothy Bish Priority: Minor Fix For: 1.6.0 Currently priorityBackup parameter is not supported in NMS library. Is it possible to have similar to what java library has: failover:(tcp://local:61616,tcp://remote:61616)?priorityBackup=true -- 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] [Resolved] (AMQNET-403) Add support for priortiy URIs to Failover transport
[ https://issues.apache.org/jira/browse/AMQNET-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQNET-403. - Resolution: Fixed Fixed on trunk Add support for priortiy URIs to Failover transport --- Key: AMQNET-403 URL: https://issues.apache.org/jira/browse/AMQNET-403 Project: ActiveMQ .Net Issue Type: New Feature Components: ActiveMQ Reporter: Boris Rybalkin Assignee: Timothy Bish Priority: Minor Fix For: 1.6.0 Currently priorityBackup parameter is not supported in NMS library. Is it possible to have similar to what java library has: failover:(tcp://local:61616,tcp://remote:61616)?priorityBackup=true -- 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] [Resolved] (AMQNET-425) Add support for updateClusterClients to Failover Transport
[
https://issues.apache.org/jira/browse/AMQNET-425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQNET-425.
-
Resolution: Fixed
Fixed on trunk.
Add support for updateClusterClients to Failover Transport
--
Key: AMQNET-425
URL: https://issues.apache.org/jira/browse/AMQNET-425
Project: ActiveMQ .Net
Issue Type: Improvement
Components: NMS
Affects Versions: 1.5.5, 1.5.6
Environment: We have developed a NET4.0 application (Producer
Consumer) using:
-Apache.NMS 1.5.0
-Apache.NMS.activeMQ 1.5.5
vmware vsphere 4.1
-CentOS 6 32bits (AQsrv1 AQsrv2)
-JRE6
-Fuse Message Broker v5.5.1
Reporter: Marc Rodrigues
Assignee: Timothy Bish
Fix For: 1.6.0
Hello,
The NMS failover client does not yet support the updateClusterClients
options, so it won't respond to the list of brokers provided by the server.
The workaround is to provide the static list or use some other discovery
mechanism like multicast.
Issue reported via forum :
Our goal is to use a network of brokers with failover and dynamic discovery
(production environment will have around 100 brokers).
So we have configured 2 CentOS virtual machine for test:
vmware vsphere 4.1
-CentOS 6 32bits (AQsrv1 AQsrv2)
-JRE6
-Fuse Message Broker v5.5.1 (see activemq.xml configuration at the end)
We have developed a NET4.0 application (Producer Consumer) using:
-Apache.NMS 1.5.0
-Apache.NMS.activeMQ 1.5.5
If I use the following URI to connect:
activemq:failover://(tcp://AQsrv1:61616,tcp://AQsrv2:61616)?transport.randomize=truetransport.startupMaxReconnectAttempts=0transport.timeout=2000nms.AsyncSend=true
- when I stop the activeMQ process on AQsrv1: the failover works fine and
application continue to send/consume messages on AQsrv2.
Now If I use the following URI:
activemq:failover://(tcp://AQsrv1:61616)?transport.randomize=truetransport.startupMaxReconnectAttempts=0transport.timeout=2000nms.AsyncSend=true
- when I stop the activeMQ process on AQsrv1: the failover seems to not work
anymore and my application is not able to connect to AQsrv2 automatically.
As I'm supposed to received a list of brokers (so AQsrv2) from AQsrv1
activemq.xml on both servers
networkConnectors
networkConnector
name=ncelab-activeMQ
uri=multicast://default?group=ncelab
dynamicOnly=true
networkTTL=2
duplex=true
prefetchSize=1
decreaseNetworkConsumerPriority=false /
/networkConnectors
persistenceAdapter
kahaDB directory=${activemq.data}/kahadb/
/persistenceAdapter
transportConnectors
transportConnector name=openwire
uri=tcp://0.0.0.0:61616
discoveryUri=multicast://default?group=ncelab
enableStatusMonitor=true
rebalanceClusterClients=true
updateClusterClients=true
updateClusterClientsOnRemove=true /
/transportConnectors
--
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] (AMQNET-403) Add support for priortiy URIs to Failover transport
[ https://issues.apache.org/jira/browse/AMQNET-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13646144#comment-13646144 ] Boris Rybalkin commented on AMQNET-403: --- do you have a build? Add support for priortiy URIs to Failover transport --- Key: AMQNET-403 URL: https://issues.apache.org/jira/browse/AMQNET-403 Project: ActiveMQ .Net Issue Type: New Feature Components: ActiveMQ Reporter: Boris Rybalkin Assignee: Timothy Bish Priority: Minor Fix For: 1.6.0 Currently priorityBackup parameter is not supported in NMS library. Is it possible to have similar to what java library has: failover:(tcp://local:61616,tcp://remote:61616)?priorityBackup=true -- 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] (AMQNET-403) Add support for priortiy URIs to Failover transport
[ https://issues.apache.org/jira/browse/AMQNET-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13646152#comment-13646152 ] Timothy Bish commented on AMQNET-403: - Not currently, you'd need to run your own by building trunk of Apache.NMS and Apache.NMS.ActiveMQ. Add support for priortiy URIs to Failover transport --- Key: AMQNET-403 URL: https://issues.apache.org/jira/browse/AMQNET-403 Project: ActiveMQ .Net Issue Type: New Feature Components: ActiveMQ Reporter: Boris Rybalkin Assignee: Timothy Bish Priority: Minor Fix For: 1.6.0 Currently priorityBackup parameter is not supported in NMS library. Is it possible to have similar to what java library has: failover:(tcp://local:61616,tcp://remote:61616)?priorityBackup=true -- 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] (AMQCPP-476) Reading of Stomp Frame with content length may throw excecption
[ https://issues.apache.org/jira/browse/AMQCPP-476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13646158#comment-13646158 ] Timothy Bish commented on AMQCPP-476: - Have had time to really look at it, will see if I can get it done tomorrow. From a quick glance it looks ok. Reading of Stomp Frame with content length may throw excecption --- Key: AMQCPP-476 URL: https://issues.apache.org/jira/browse/AMQCPP-476 Project: ActiveMQ C++ Client Issue Type: Bug Components: Stomp Affects Versions: 3.6.0 Environment: Solaris 10 Apollo AMQ Reporter: Jeremy Leung Assignee: Timothy Bish Attachments: consumer.cpp, Publisher.java, StompFrame.cpp.patch.txt, unit_test.txt -- HOW TO REPRODUCE -- 1) Setup a consumer to listen for messages on Topic XXX using CMS with stomp. 2) Setup a publisher to send a messages from java JMS interface to Topic XXX continually. (with org.fusesource.stomp.jms.*) 3) An exception is thrown in consumer from StompWireFormat::readStompBody() with description Read Content Length, and no trailing null -- BLOCK DIAGRAM -- All components are in different hosts and all run under Solaris 10 environment. | C++ CONSUMER | - | APOLLO 1.6 / AMQ 5.4.2 | - | JAVA PUBLISHER | or | C++ CONSUMER | - | APOLLO 1.6 / AMQ 5.4.2 | - | C++ PUBLISHER | -- 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-4501) Failover priorityBackup doesn't work if client accepts updates to its list of known URIs from the broker.
Carlos de la Torre created AMQ-4501: --- Summary: Failover priorityBackup doesn't work if client accepts updates to its list of known URIs from the broker. Key: AMQ-4501 URL: https://issues.apache.org/jira/browse/AMQ-4501 Project: ActiveMQ Issue Type: Bug Components: JMS client Affects Versions: 5.8.0, 5.9.0 Environment: Mac OSX 10.6.8 java version 1.6.0_43 Reporter: Carlos de la Torre Fix For: 5.9.0, 5.8.0 If a client has priorityBackup enabled and connects to a broker in a cluster with updateClusterClients=true in its transport connector, the client ignores the priorityBackup flag it connects to any URI received from the broker, even if that URI doesn't have priority. This is easy to reproduce adding a test case to the activemq-unit-tests/src/test/java/org/apache/activemq/transport/failover/FailoverPriorityTest.java test suite. -- 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-4501) Failover priorityBackup doesn't work if client accepts updates to its list of known URIs from the broker.
[ https://issues.apache.org/jira/browse/AMQ-4501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos de la Torre updated AMQ-4501: Attachment: AMQ-4501-TestcaseToReproduce.diff This test case is very similar to testPriorityBackup. The only difference is that when the transport connectors are created, the cluster flag is set to true which basically creates the connector with updateClusterClients=true rebalanceClusterClients=true updateClusterClientsOnRemove=true. Failover priorityBackup doesn't work if client accepts updates to its list of known URIs from the broker. - Key: AMQ-4501 URL: https://issues.apache.org/jira/browse/AMQ-4501 Project: ActiveMQ Issue Type: Bug Components: JMS client Affects Versions: 5.8.0, 5.9.0 Environment: Mac OSX 10.6.8 java version 1.6.0_43 Reporter: Carlos de la Torre Fix For: 5.8.0, 5.9.0 Attachments: AMQ-4501-TestcaseToReproduce.diff If a client has priorityBackup enabled and connects to a broker in a cluster with updateClusterClients=true in its transport connector, the client ignores the priorityBackup flag it connects to any URI received from the broker, even if that URI doesn't have priority. This is easy to reproduce adding a test case to the activemq-unit-tests/src/test/java/org/apache/activemq/transport/failover/FailoverPriorityTest.java test suite. -- 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-4501) Failover priorityBackup doesn't work if client accepts updates to its list of known URIs from the broker.
[ https://issues.apache.org/jira/browse/AMQ-4501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos de la Torre updated AMQ-4501: Attachment: (was: AMQ-4501-TestcaseToReproduce.diff) Failover priorityBackup doesn't work if client accepts updates to its list of known URIs from the broker. - Key: AMQ-4501 URL: https://issues.apache.org/jira/browse/AMQ-4501 Project: ActiveMQ Issue Type: Bug Components: JMS client Affects Versions: 5.8.0, 5.9.0 Environment: Mac OSX 10.6.8 java version 1.6.0_43 Reporter: Carlos de la Torre Fix For: 5.8.0, 5.9.0 If a client has priorityBackup enabled and connects to a broker in a cluster with updateClusterClients=true in its transport connector, the client ignores the priorityBackup flag it connects to any URI received from the broker, even if that URI doesn't have priority. This is easy to reproduce adding a test case to the activemq-unit-tests/src/test/java/org/apache/activemq/transport/failover/FailoverPriorityTest.java test suite. -- 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-4501) Failover priorityBackup doesn't work if client accepts updates to its list of known URIs from the broker.
[ https://issues.apache.org/jira/browse/AMQ-4501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos de la Torre updated AMQ-4501: Attachment: AMQ-4501-TestcaseToReproduce.patch Failover priorityBackup doesn't work if client accepts updates to its list of known URIs from the broker. - Key: AMQ-4501 URL: https://issues.apache.org/jira/browse/AMQ-4501 Project: ActiveMQ Issue Type: Bug Components: JMS client Affects Versions: 5.8.0, 5.9.0 Environment: Mac OSX 10.6.8 java version 1.6.0_43 Reporter: Carlos de la Torre Fix For: 5.8.0, 5.9.0 If a client has priorityBackup enabled and connects to a broker in a cluster with updateClusterClients=true in its transport connector, the client ignores the priorityBackup flag it connects to any URI received from the broker, even if that URI doesn't have priority. This is easy to reproduce adding a test case to the activemq-unit-tests/src/test/java/org/apache/activemq/transport/failover/FailoverPriorityTest.java test suite. -- 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-4501) Failover priorityBackup doesn't work if client accepts updates to its list of known URIs from the broker.
[ https://issues.apache.org/jira/browse/AMQ-4501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos de la Torre updated AMQ-4501: Attachment: (was: AMQ-4501-TestcaseToReproduce.patch) Failover priorityBackup doesn't work if client accepts updates to its list of known URIs from the broker. - Key: AMQ-4501 URL: https://issues.apache.org/jira/browse/AMQ-4501 Project: ActiveMQ Issue Type: Bug Components: JMS client Affects Versions: 5.8.0, 5.9.0 Environment: Mac OSX 10.6.8 java version 1.6.0_43 Reporter: Carlos de la Torre Fix For: 5.8.0, 5.9.0 If a client has priorityBackup enabled and connects to a broker in a cluster with updateClusterClients=true in its transport connector, the client ignores the priorityBackup flag it connects to any URI received from the broker, even if that URI doesn't have priority. This is easy to reproduce adding a test case to the activemq-unit-tests/src/test/java/org/apache/activemq/transport/failover/FailoverPriorityTest.java test suite. -- 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-4501) Failover priorityBackup doesn't work if client accepts updates to its list of known URIs from the broker.
[ https://issues.apache.org/jira/browse/AMQ-4501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos de la Torre updated AMQ-4501: Attachment: AMQ-4501-TestcaseToReproduce.patch Failover priorityBackup doesn't work if client accepts updates to its list of known URIs from the broker. - Key: AMQ-4501 URL: https://issues.apache.org/jira/browse/AMQ-4501 Project: ActiveMQ Issue Type: Bug Components: JMS client Affects Versions: 5.8.0, 5.9.0 Environment: Mac OSX 10.6.8 java version 1.6.0_43 Reporter: Carlos de la Torre Fix For: 5.8.0, 5.9.0 Attachments: AMQ-4501-TestcaseToReproduce.patch If a client has priorityBackup enabled and connects to a broker in a cluster with updateClusterClients=true in its transport connector, the client ignores the priorityBackup flag it connects to any URI received from the broker, even if that URI doesn't have priority. This is easy to reproduce adding a test case to the activemq-unit-tests/src/test/java/org/apache/activemq/transport/failover/FailoverPriorityTest.java test suite. -- 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
