[jira] Commented: (AMQ-1078) Messages consumed with the Resource Adapter are intermittently not delivered
[ https://issues.apache.org/activemq/browse/AMQ-1078?page=comments#action_37604 ] Hiram Chirino commented on AMQ-1078: fix in 4.1 branch rev 480862 Messages consumed with the Resource Adapter are intermittently not delivered Key: AMQ-1078 URL: https://issues.apache.org/activemq/browse/AMQ-1078 Project: ActiveMQ Issue Type: Bug Components: Broker, Connector Affects Versions: 4.0 Reporter: Hiram Chirino Assigned To: Hiram Chirino Fix For: 4.2.0, 4.1.1 The cause is that the ActiveMQSessionExecutor was starting and using it's dispatch thread instead of the Thread managed by the resource adapter. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (AMQ-1052) Connection is not released by broker when client is killed when client is sending to a queue that is full
Connection is not released by broker when client is killed when client is sending to a queue that is full - Key: AMQ-1052 URL: https://issues.apache.org/activemq/browse/AMQ-1052 Project: ActiveMQ Issue Type: Bug Affects Versions: 4.0 Reporter: Hiram Chirino Assigned To: Hiram Chirino Fix For: 4.1.1, 4.1.2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (AMQ-1016) 4.1 RC1: META-INF/spring.schemas refers to building user file:/Users/chirino/
[ https://issues.apache.org/activemq/browse/AMQ-1016?page=all ] Hiram Chirino resolved AMQ-1016. Fix Version/s: 4.1.1 4.2.0 Resolution: Fixed Assignee: Hiram Chirino Fix applied in trunk rev 474872 and in 4.1 branch rev 474876 4.1 RC1: META-INF/spring.schemas refers to building user file:/Users/chirino/ --- Key: AMQ-1016 URL: https://issues.apache.org/activemq/browse/AMQ-1016 Project: ActiveMQ Issue Type: Bug Affects Versions: 4.1.0 Environment: n/a Reporter: Endre Stølsvik Assigned To: Hiram Chirino Priority: Minor Fix For: 4.1.1, 4.2.0 Referring to the 4.1 RC1 posted by Hiram Chirino Oct 06, here: http://www.nabble.com/ActiveMQ-4.1-RC-1-tf2397970.html#a6686974 The META-INF file spring.schemas have the single line. http\://activemq.org/config/1.0=file:/Users/chirino/sandbox/activemq-4.1/activemq-core/target/activemq.xsd Notice file:/ and Users/chirino. Referring to org.springframework.beans.factory.xml.PluggableSchemaResolver's javadoc: schema-location should also be a schema file in the classpath, and that no-one can tell what structure I will have on my fs, this must be wrong. In addition, I most probably won't have a user name chirino. PS: In addition, the doc at http://www.activemq.org/site/how-do-i-embed-a-broker-inside-a-connection.html refers as such: xmlns:amq=http://activemq.org/config/1.0; .. and .. xsi:schemaLocation=http://activemq.org/config/1.0 http://people.apache.org/repository/org.apache.activemq/xsds/activemq-core-4.1-incubator-SNAPSHOT.xsd; Wouldn't it be nice if this was put at a better place than such a snapshot-build URI? It could be put where it will reside when 4.1 actually is out, w/o anyone being to angry about changes during the finalization period, I personally believe. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-1036) web-console broken (queue browsing).
[ https://issues.apache.org/activemq/browse/AMQ-1036?page=all ]
Hiram Chirino updated AMQ-1036:
---
Fix Version/s: 4.1.1
4.2.0
(was: 4.1.0)
web-console broken (queue browsing).
Key: AMQ-1036
URL: https://issues.apache.org/activemq/browse/AMQ-1036
Project: ActiveMQ
Issue Type: Bug
Affects Versions: incubation
Reporter: Dave Syer
Assigned To: Adrian Co
Fix For: 4.2.0, 4.1.1
I managed to build and launch the web-console from svn, but the queue
browsing page is broken - queue.jsp uses properties of Queue e.g. ${row.size}
that do not exist. When I hacked queue.jsp to remove references to those
properties I got another error on trying to purge a queue:
RequestURI=/activemq-web-console/purgeDestination.action
Caused by:
java.lang.IllegalArgumentException: Target bean must not be null
at org.springframework.util.Assert.notNull(Assert.java:113)
at
org.springframework.validation.BeanPropertyBindingResult.(BeanPropertyBindingResult.java:58)
at
org.springframework.validation.DataBinder.initBeanPropertyAccess(DataBinder.java:167)
at
org.springframework.validation.DataBinder.getInternalBindingResult(DataBinder.java:186)
at
org.springframework.validation.DataBinder.getPropertyAccessor(DataBinder.java:196)
at
org.springframework.validation.DataBinder.applyPropertyValues(DataBinder.java:515)
at org.springframework.validation.DataBinder.doBind(DataBinder.java:417)
at
org.springframework.web.bind.WebDataBinder.doBind(WebDataBinder.java:146)
at
org.springframework.web.bind.ServletRequestDataBinder.bind(ServletRequestDataBinder.java:108)
at
org.apache.activemq.web.handler.BindingBeanNameUrlHandlerMapping.getHandlerInternal(BindingBeanNameUrlHandlerMapping.java:43)
...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-910) backoffMultiplier should be a double value
[ https://issues.apache.org/activemq/browse/AMQ-910?page=all ] Hiram Chirino updated AMQ-910: -- Fix Version/s: 4.2.0 (was: 4.0.1) backoffMultiplier should be a double value -- Key: AMQ-910 URL: https://issues.apache.org/activemq/browse/AMQ-910 Project: ActiveMQ Issue Type: Improvement Reporter: Daniel Aioanei Fix For: 4.2.0 Having org.apache.activemq.ra.ActiveMQActivationSpec.backOffMultiplier as a short value is too limiting. I think a double value would be more appropriate. For instance, I'd like to set it to about 1.1 but that's not possible at the time being. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-734) Network connections do not reconnect when using static: with failover=true
[ https://issues.apache.org/activemq/browse/AMQ-734?page=all ] Hiram Chirino updated AMQ-734: -- Fix Version/s: 4.1.1 (was: 4.0.1) I've got a feeling that this was related to the timing issues addressed in issue: https://issues.apache.org/activemq/browse/AMQ-1044 which is now fixed. Could one you guys retest against a source build from the 4.1 branch and let me know if it resolves this issue? Network connections do not reconnect when using static: with failover=true -- Key: AMQ-734 URL: https://issues.apache.org/activemq/browse/AMQ-734 Project: ActiveMQ Issue Type: Bug Components: Connector Affects Versions: 4.0 Environment: winxp java1.5.6 Reporter: tao Assigned To: Hiram Chirino Priority: Critical Fix For: 4.2.0, 4.1.1 If I pull out RJ45 port from net card ,waiting a time ,then put RJ45 port net card .Network is resume.Other computer always throw errors and net channel can't work. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (AMQ-1046) Consolidate the ActiveMQ admin scripts to a single command line script
[ https://issues.apache.org/activemq/browse/AMQ-1046?page=all ] Hiram Chirino reassigned AMQ-1046: -- Assignee: Adrian Co (was: Fritz Oconer) Consolidate the ActiveMQ admin scripts to a single command line script -- Key: AMQ-1046 URL: https://issues.apache.org/activemq/browse/AMQ-1046 Project: ActiveMQ Issue Type: Improvement Reporter: Hiram Chirino Assigned To: Adrian Co Fix For: 4.2.0 Right now we have serveral command line scripts in the ActiveMQ bin directory of the binary distribution. They are used for admin purposes. They are less than ideal because some of them have very generic names and might clash with existing commands if the activemq bin directory is added to the PATH of a unix system. I think it would be more idea if we consolidated all the command so that are executed using just 1 script. Something like: $ activemq-admin list $ activemq-admin stat $ activemq-admin browse etc. etc. etc. This way only 2 executable scripts are added to the path: (1) activemq - the binary that starts up ActiveMQ (2) activemq-admin - the binary used to manage the ActiveMQ instance. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-1047) ActiveMQ admin scripts should hide JMX from the user as much as possible.
[ https://issues.apache.org/activemq/browse/AMQ-1047?page=all ] Hiram Chirino updated AMQ-1047: --- Assignee: Adrian Co (was: Hiram Chirino) ActiveMQ admin scripts should hide JMX from the user as much as possible. - Key: AMQ-1047 URL: https://issues.apache.org/activemq/browse/AMQ-1047 Project: ActiveMQ Issue Type: Improvement Reporter: Hiram Chirino Assigned To: Adrian Co Fix For: 4.2.0 The fact that JMX is being used to access the management functions of the Broker should be hidden from the user of the admin scripts as much as possible. For example, users should not be displayed objects names of a list of subscriptions. They should be shown the subscription ids of the subscriptions. The same goes for connections and so forth. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (AMQ-1047) ActiveMQ admin scripts should hide JMX from the user as much as possible.
ActiveMQ admin scripts should hide JMX from the user as much as possible. - Key: AMQ-1047 URL: https://issues.apache.org/activemq/browse/AMQ-1047 Project: ActiveMQ Issue Type: Improvement Reporter: Hiram Chirino Assigned To: Hiram Chirino Fix For: 4.2.0 The fact that JMX is being used to access the management functions of the Broker should be hidden from the user of the admin scripts as much as possible. For example, users should not be displayed objects names of a list of subscriptions. They should be shown the subscription ids of the subscriptions. The same goes for connections and so forth. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-1013) Web console does not escape message details (/activemq-web-console/message.jsp)
[ https://issues.apache.org/activemq/browse/AMQ-1013?page=all ] Hiram Chirino updated AMQ-1013: --- Fix Version/s: 4.2 (was: 4.1.0) Web console does not escape message details (/activemq-web-console/message.jsp) --- Key: AMQ-1013 URL: https://issues.apache.org/activemq/browse/AMQ-1013 Project: ActiveMQ Issue Type: Improvement Environment: OS X 10.4.8 / Java 1.5 / ActiveMQ 4.1-SNAPSHOT Reporter: Stefan Arentz Fix For: 4.2.0 The web console does not html-escape the message contents on the /message.jsp page which makes it difficult to see a xml test message. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-1010) Simplify SimpleAuthenticationPlugin Configuration
[ https://issues.apache.org/activemq/browse/AMQ-1010?page=all ] Hiram Chirino updated AMQ-1010: --- Fix Version/s: 4.2 (was: 4.1.0) Simplify SimpleAuthenticationPlugin Configuration - Key: AMQ-1010 URL: https://issues.apache.org/activemq/browse/AMQ-1010 Project: ActiveMQ Issue Type: Improvement Components: Broker Affects Versions: 4.1.0 Reporter: Dejan Bosanac Fix For: 4.2.0 Attachments: simple-auth.patch In order to be useful, SimpleAuthenticationPlugin has to be easy to configure and well documented. I added some additional logic in order to make it play well with XBean. The patch also contains an additional class (AuthenticationUser) and the appropriate test suite. The example configuration is as follows (taken from simple-auth-broker.xml): simpleAuthenticationPlugin users authenticationUser username=system password=manager group=users,admins/ authenticationUser username=user password=password group=users/ authenticationUser username=guest password=password group=guests/ /users /simpleAuthenticationPlugin I will make a proper documentation for the Security page if this functionality ever gets committed in the repository. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-1002) org.apache.activemq.spring.SpringTest.testSenderWithSpringXmlUsingSpring2NamespacesWithEmbeddedBrokerConfiguredViaXml
[ https://issues.apache.org/activemq/browse/AMQ-1002?page=all ] Hiram Chirino updated AMQ-1002: --- Fix Version/s: 4.2 (was: 4.1.0) org.apache.activemq.spring.SpringTest.testSenderWithSpringXmlUsingSpring2NamespacesWithEmbeddedBrokerConfiguredViaXml - Key: AMQ-1002 URL: https://issues.apache.org/activemq/browse/AMQ-1002 Project: ActiveMQ Issue Type: Test Reporter: Hiram Chirino Fix For: 4.2.0 Upgrading to spring 2.0 broker this test. Commenting out till we can fix it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-998) add support for stomp+ssl
[ https://issues.apache.org/activemq/browse/AMQ-998?page=all ] Hiram Chirino updated AMQ-998: -- Fix Version/s: 4.2 (was: 4.1.0) add support for stomp+ssl - Key: AMQ-998 URL: https://issues.apache.org/activemq/browse/AMQ-998 Project: ActiveMQ Issue Type: New Feature Components: Transport Reporter: james strachan Fix For: 4.2.0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-984) make the slave status of a broker available through JMX (in jdbc-master-slave mode)
[ https://issues.apache.org/activemq/browse/AMQ-984?page=all ] Hiram Chirino updated AMQ-984: -- Fix Version/s: 4.2 (was: 4.1.0) make the slave status of a broker available through JMX (in jdbc-master-slave mode) - Key: AMQ-984 URL: https://issues.apache.org/activemq/browse/AMQ-984 Project: ActiveMQ Issue Type: Improvement Components: Broker Affects Versions: 4.1.0 Reporter: Renaud Bruyeron Priority: Minor Fix For: 4.2.0 Right now, it is not possible to know that a broker is in Attempting to acquire the exclusive lock to become the Master broker mode via JMX, even though this would be a natural place to find out. Do you think it would be possible to expose the DatabaseLocker or the JDBCPersistenceAdapter over JMX so that a simple boolean isMaster() can be queried? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-962) Messages are read from queue but not removed
[ https://issues.apache.org/activemq/browse/AMQ-962?page=all ] Hiram Chirino updated AMQ-962: -- Fix Version/s: 4.2 (was: 4.1.0) Messages are read from queue but not removed Key: AMQ-962 URL: https://issues.apache.org/activemq/browse/AMQ-962 Project: ActiveMQ Issue Type: Bug Components: JMS client, Broker Affects Versions: 4.0.1 Environment: Java Virtual Machine: Java HotSpot(TM) Server VM version 1.5.0_06-b05JIT compiler: HotSpot Server Compiler Operating System: Windows XP 5.1 Architecture: x86 Number of processors: 1 Total physical memory: 1,048,048 kbytes Free physical memory: 107,240 kbytes Committed virtual memory: 374,048 kbytes Total swap space: 2,518,944 kbytes Free swap space: 721,416 kbytes Reporter: Randy Priority: Critical Fix For: 4.2.0 Using Spring, configured a VM message broker (non-persistant) and a message consumer that reads messages from queue. Messages are read from queue, but despite calling message.acknowledge(); messages remain on the queue (and consume memory). I turned off optimiseAcknowledge. May be related to bug# AMQ-716. amq:broker id=broker useJmx=true persistent=false amq:transportConnectors amq:transportConnector uri=tcp://localhost:0 / /amq:transportConnectors /amq:broker !-- a pooling based JMS provider -- bean id=jmsFactory class=org.apache.activemq.pool.PooledConnectionFactory property name=connectionFactory bean class=org.apache.activemq.ActiveMQConnectionFactory property name=brokerURL valuevm://localhost/value /property property name=optimizeAcknowledge valuefalse/value /property /bean /property /bean bean id=simpleJmsTemplate class=org.springframework.jms.core.JmsTemplate property name=connectionFactory ref local=jmsFactory / /property /bean -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-967) setting maximumRedeliveries to -1 is equivalent to maximumRedeliveries=0, but doc says otherwise
[ https://issues.apache.org/activemq/browse/AMQ-967?page=all ] Hiram Chirino updated AMQ-967: -- Fix Version/s: 4.2 (was: 4.1.0) setting maximumRedeliveries to -1 is equivalent to maximumRedeliveries=0, but doc says otherwise Key: AMQ-967 URL: https://issues.apache.org/activemq/browse/AMQ-967 Project: ActiveMQ Issue Type: Bug Components: Connector Affects Versions: 4.1.0, 4.0.2 Reporter: Renaud Bruyeron Fix For: 4.2.0, 4.0.3 Attachments: patch.txt The documentation (http://incubator.apache.org/activemq/resource-adapter-properties.html) suggests that setting maximumRedeliveries to -1 means no maximum, i.e. infinite retries. However, my tests (and the code) show that -1 is equivalent to 0 (i.e. no redelivery). The patch attempts to fix this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-943) Pluggable Stomp Message Mapping
[ https://issues.apache.org/activemq/browse/AMQ-943?page=all ] Hiram Chirino updated AMQ-943: -- Fix Version/s: 4.2 (was: 4.1.0) Pluggable Stomp Message Mapping --- Key: AMQ-943 URL: https://issues.apache.org/activemq/browse/AMQ-943 Project: ActiveMQ Issue Type: Improvement Components: Transport Affects Versions: 4.1.0 Reporter: Dejan Bosanac Assigned To: Brian McCallister Fix For: 4.2.0 Attachments: protocol-mapping.patch I have finally found time to finish this. Here's the draft version of the Pluggable Stomp Message Mapping implementation. Few notes: - New interface has been defined: ProtocolMapping (I wanted to use the same name as the message header that we check) - There are two implementations of this interface: DefaultProtocolMapping and ByteProtocolMapping - I used FactoryFinder to create appropriate mapper. The finder use the following path to find keys: META-INF/services/org/apache/activemq/transport/mapping/ (we can change this if you want) - The appropriate mapper is used according to the protocol-mapping header in the CONNECT message. For example protocol-mapping:byte for ByteProtocolMapping handler. - Currently I have implemented only the mapper for BytesMessage since I wasn't sure whether you want to integrate JSON mapper for MapMessages or distribute it in a separate library. - I have changed the test case that tests subscription for byte messages - This solution is not compatible with current mapping for byte messages. If you want backward compatibility, I can hard-code it in a ProtocolConverter class (as it was) since it could not be implemented through this mechanism. TODO: - test it more (create more unit test cases and test it more in a real environment) - create a proper documentation so others can create their handlers. - create a proper JavaDoc documentation for key interfaces and classes - create JSON mapper (integrated or external) - fix STOMP client(s) Give it a try and let me know your impressions Dejan Bosanac -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-876) Kaha DB cannot locate queue data files
[ https://issues.apache.org/activemq/browse/AMQ-876?page=all ] Hiram Chirino updated AMQ-876: -- Fix Version/s: 4.2 (was: 4.1.0) Kaha DB cannot locate queue data files -- Key: AMQ-876 URL: https://issues.apache.org/activemq/browse/AMQ-876 Project: ActiveMQ Issue Type: Bug Components: Message Store Affects Versions: 4.1.0 Environment: WinXP Reporter: Vadim Pesochinskiy Assigned To: Rob Davies Fix For: 4.2.0 Attachments: test.zip Keep getting exception below. Note that you are looking for queue-data-1, but actual file name is data-queue-data-1 $ pwd /cygdrive/d/amq/activemq-kaha/kaha.db $ ls data-kaha-1 data-queue-data-1 index-kaha index-queue-data index-transactions javax.jms.JMSException: java.io.IOException: Could not locate data file queue-data-1 at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:46) at org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1154) at org.apache.activemq.TransactionContext.commit(TransactionContext.java:260) at org.apache.activemq.ActiveMQSession.commit(ActiveMQSession.java:464) at com.barra.cp.common.io.MultiQueueReceiver.onMessage(MultiQueueReceiver.java:163) at com.barra.cp.common.io.SingleMessageMultiQueueReceiver$OneMessageAtATime.runMultiQueue(SingleMessageMultiQueueReceiver.java:176) at com.barra.cp.common.io.SingleMessageMultiQueueReceiver$OneMessageAtATime.doRun(SingleMessageMultiQueueReceiver.java:143) at com.barra.cp.common.io.SingleMessageMultiQueueReceiver$OneMessageAtATime.run(SingleMessageMultiQueueReceiver.java:124) at java.lang.Thread.run(Unknown Source) Caused by: org.apache.activemq.kaha.RuntimeStoreException: java.io.IOException: Could not locate data file queue-data-1 at org.apache.activemq.kaha.impl.MapContainerImpl.getValue(MapContainerImpl.java:340) at org.apache.activemq.kaha.impl.MapContainerImpl.remove(MapContainerImpl.java:265) at org.apache.activemq.store.kahadaptor.KahaMessageStore.removeMessage(KahaMessageStore.java:68) at org.apache.activemq.store.kahadaptor.KahaTransaction.commit(KahaTransaction.java:92) at org.apache.activemq.store.kahadaptor.KahaTransactionStore.commit(KahaTransactionStore.java:95) at org.apache.activemq.transaction.LocalTransaction.commit(LocalTransaction.java:68) at org.apache.activemq.broker.TransactionBroker.commitTransaction(TransactionBroker.java:154) at org.apache.activemq.broker.BrokerFilter.commitTransaction(BrokerFilter.java:92) at org.apache.activemq.broker.BrokerFilter.commitTransaction(BrokerFilter.java:92) at org.apache.activemq.broker.MutableBrokerFilter.commitTransaction(MutableBrokerFilter.java:102) at org.apache.activemq.broker.AbstractConnection.processCommitTransactionOnePhase(AbstractConnection.java:330) at org.apache.activemq.command.TransactionInfo.visit(TransactionInfo.java:99) at org.apache.activemq.broker.AbstractConnection.service(AbstractConnection.java:228) at org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:63) at org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:92) at org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:67) at org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:123) at org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:123) at org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:88) at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:127) ... 1 more Caused by: java.io.IOException: Could not locate data file queue-data-1 at org.apache.activemq.kaha.impl.DataManager.getDataFile(DataManager.java:117) at org.apache.activemq.kaha.impl.StoreDataReader.readItem(StoreDataReader.java:62) at org.apache.activemq.kaha.impl.DataManager.readItem(DataManager.java:121) at org.apache.activemq.kaha.impl.MapContainerImpl.getValue(MapContainerImpl.java:337) ... 20 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-908) Authorization plugin should have configurable principal classes
[ https://issues.apache.org/activemq/browse/AMQ-908?page=all ]
Hiram Chirino updated AMQ-908:
--
Fix Version/s: 4.2
(was: 4.1.0)
Authorization plugin should have configurable principal classes
---
Key: AMQ-908
URL: https://issues.apache.org/activemq/browse/AMQ-908
Project: ActiveMQ
Issue Type: Improvement
Components: Broker
Affects Versions: 4.0.1
Reporter: Aaron Mulder
Fix For: 4.2.0, 4.0.3
Currently, if you configure the authorization plugin, it assumes that all
principals listed should be of type
{{org.apache.activemq.jaas.GroupPrincipal}}. This is OK if you're using
ActiveMQ LoginModules, but since there's a fairly small supply of those, it
would be great if you could use arbitrary login modules and tell the
authorization plugin which principal classes to use. For example,
{{groupClass=weblogic.security.principal.WLSGroupImpl}} or something like
that. A good first step would be to let you change the group class. A good
second step would be to let you specify user and group classes and then
somehow indicate which names are which (e.g.
{{admin=administrators,user:aaron,user:bob}} or whatever). Someday maybe
it will be nice to support any arbitrary combination of principal classes but
that seems far away.
When instantiating the principal classes, I imagine we should use a
constructor with a single String argument if available, or else a default
constructor plus a setName method, or else I guess bail.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-821) Openwire code (from HEAD) doesn't compile on .Net 1.1 - uses sizeof(int)
[ https://issues.apache.org/activemq/browse/AMQ-821?page=all ]
Hiram Chirino updated AMQ-821:
--
Fix Version/s: 4.2
(was: 4.1.0)
Openwire code (from HEAD) doesn't compile on .Net 1.1 - uses sizeof(int)
Key: AMQ-821
URL: https://issues.apache.org/activemq/browse/AMQ-821
Project: ActiveMQ
Issue Type: Bug
Components: JMS client
Environment: Net 1.1
Reporter: Dan Haywood
Priority: Minor
Fix For: 4.2.0
Attachments: ActiveMQTextMessage.cs.diff, nant.build.diff
sizeof(int) is unsafe code on Net-1.1.
I've attached patches to put the code in unsafe { ... } block, plus fix to
nant.build. Same code also (still) compiles on 2.0.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-804) Use of Temporary Destinations over broker networks can cause the network bridges to die.
[ https://issues.apache.org/activemq/browse/AMQ-804?page=all ] Hiram Chirino updated AMQ-804: -- Fix Version/s: 4.2 (was: 4.1.0) Use of Temporary Destinations over broker networks can cause the network bridges to die. Key: AMQ-804 URL: https://issues.apache.org/activemq/browse/AMQ-804 Project: ActiveMQ Issue Type: Bug Components: Broker Reporter: Hiram Chirino Assigned To: Rob Davies Fix For: 4.2.0 And when the bridge dies, it is not re-established. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-815) generate a warning by default if a client connects via openwire using a different release version of the broker
[ https://issues.apache.org/activemq/browse/AMQ-815?page=all ] Hiram Chirino updated AMQ-815: -- Fix Version/s: 4.2 (was: 4.1.0) generate a warning by default if a client connects via openwire using a different release version of the broker --- Key: AMQ-815 URL: https://issues.apache.org/activemq/browse/AMQ-815 Project: ActiveMQ Issue Type: Improvement Reporter: james strachan Assigned To: Hiram Chirino Fix For: 4.2.0 While we can be quite liberal in supporting backwards compatible clients, the default should be to warn folks if they connect via different versions - as thats often an indication of classpath issues. Maybe have 3 options - lenient (try to work with anything), warning (just log warning on connection), strict (disconnect non-similar version clients) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-796) Client may shtudown when failover connection is reconnecting. We need to maintain at least 1 non-daemon thread alive.
[ https://issues.apache.org/activemq/browse/AMQ-796?page=all ] Hiram Chirino updated AMQ-796: -- Fix Version/s: 4.2 (was: 4.1.0) Client may shtudown when failover connection is reconnecting. We need to maintain at least 1 non-daemon thread alive. -- Key: AMQ-796 URL: https://issues.apache.org/activemq/browse/AMQ-796 Project: ActiveMQ Issue Type: Bug Affects Versions: 4.0 Reporter: Hiram Chirino Fix For: 4.2.0, 4.0.3 Dejan Reported on the User lists: Hi, after some experiments I found that this problem only exists if there are no other threads in the application. It seems like connection thread dies before it manages to reconnect. By starting another thread in the application, it succeeds to recover from master failure and reconnect to the slave broker. So I have a workaround for now, but it would be nice to make this work even for simple (single-threaded) clients. Regards, Dejan -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-734) Network connections do not reconnect when using static: with failover=true
[ https://issues.apache.org/activemq/browse/AMQ-734?page=all ] Hiram Chirino updated AMQ-734: -- Fix Version/s: 4.2 (was: 4.1.0) Network connections do not reconnect when using static: with failover=true -- Key: AMQ-734 URL: https://issues.apache.org/activemq/browse/AMQ-734 Project: ActiveMQ Issue Type: Bug Components: Connector Affects Versions: 4.0 Environment: winxp java1.5.6 Reporter: tao Assigned To: Hiram Chirino Priority: Critical Fix For: 4.0.1, 4.2.0 If I pull out RJ45 port from net card ,waiting a time ,then put RJ45 port net card .Network is resume.Other computer always throw errors and net channel can't work. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-616) SpringTest hangs
[ https://issues.apache.org/activemq/browse/AMQ-616?page=all ] Hiram Chirino updated AMQ-616: -- Fix Version/s: 4.2 (was: 4.1.0) SpringTest hangs Key: AMQ-616 URL: https://issues.apache.org/activemq/browse/AMQ-616 Project: ActiveMQ Issue Type: Test Components: Test Cases Affects Versions: 4.0 RC2 Reporter: Darwin Flores Assigned To: Rob Davies Fix For: 4.2.0 The SpringTest appears to be hanging in Linux platform -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-730) 4.x Javadoc
[ https://issues.apache.org/activemq/browse/AMQ-730?page=all ] Hiram Chirino updated AMQ-730: -- Fix Version/s: 4.2 (was: 4.1.0) 4.x Javadoc --- Key: AMQ-730 URL: https://issues.apache.org/activemq/browse/AMQ-730 Project: ActiveMQ Issue Type: Wish Components: Documentation Affects Versions: 4.0 Reporter: jason evans Fix For: 4.2.0 While ActiveMQ proves to be a high quality open-source JMS implementation the incomplete Javadoc decreases developer understanding, development and test time, and overall confidence of the adoption of each implementation. Although I have submitted this as a wish I would like to see an effort to beef up the documentation. I believe the community will benefit tremendously! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-720) Use the Apache Commons CLI to parse the command line
[ https://issues.apache.org/activemq/browse/AMQ-720?page=all ] Hiram Chirino updated AMQ-720: -- Fix Version/s: 4.2 (was: 4.1.0) Use the Apache Commons CLI to parse the command line Key: AMQ-720 URL: https://issues.apache.org/activemq/browse/AMQ-720 Project: ActiveMQ Issue Type: Improvement Affects Versions: 4.1.0 Reporter: Adrian Co Assigned To: Adrian Co Fix For: 4.2.0 Change the current way of parsing command line to use the apache commons cli for a more standard format. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-644) create Java Service Wrapper for ActiveMQ
[ https://issues.apache.org/activemq/browse/AMQ-644?page=all ] Hiram Chirino updated AMQ-644: -- Fix Version/s: 4.2 (was: 4.1.0) create Java Service Wrapper for ActiveMQ Key: AMQ-644 URL: https://issues.apache.org/activemq/browse/AMQ-644 Project: ActiveMQ Issue Type: New Feature Components: Broker Reporter: james strachan Assigned To: Joseph Dennis Gapuz Priority: Minor Fix For: 4.2.0 Attachments: wrapper.conf http://wrapper.tanukisoftware.org/doc/english/introduction.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-631) verify that HttpsTransportBrokerTest won't hang on other environment
[ https://issues.apache.org/activemq/browse/AMQ-631?page=all ] Hiram Chirino updated AMQ-631: -- Fix Version/s: 4.2 (was: 4.1.0) verify that HttpsTransportBrokerTest won't hang on other environment Key: AMQ-631 URL: https://issues.apache.org/activemq/browse/AMQ-631 Project: ActiveMQ Issue Type: Task Components: Test Cases Affects Versions: 4.0 RC2 Reporter: Adrian Co Assigned To: Adrian Co Fix For: 4.2.0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-594) SimpleNetworkTest hangs
[ https://issues.apache.org/activemq/browse/AMQ-594?page=all ] Hiram Chirino updated AMQ-594: -- Fix Version/s: 4.2 (was: 4.1.0) SimpleNetworkTest hangs --- Key: AMQ-594 URL: https://issues.apache.org/activemq/browse/AMQ-594 Project: ActiveMQ Issue Type: Bug Components: Test Cases Affects Versions: 4.0 RC2 Reporter: Darwin Flores Assigned To: Rob Davies Fix For: 4.2.0 The SimpleNetworkTest appears to be hanging in Linux platform -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-546) Network brokers have long reconnect times and they receive duplicate messages
[ https://issues.apache.org/activemq/browse/AMQ-546?page=all ] Hiram Chirino updated AMQ-546: -- Fix Version/s: 4.2 (was: 4.1.0) Network brokers have long reconnect times and they receive duplicate messages - Key: AMQ-546 URL: https://issues.apache.org/activemq/browse/AMQ-546 Project: ActiveMQ Issue Type: Bug Affects Versions: 3.2, 4.0 M4 Reporter: Hiram Chirino Fix For: 4.2.0 Initially reported at: http://forums.activemq.org/posts/list/202.page Notice that the forum has a JUnit test case that demonstrates the problem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-693) STOMP C client ready for Sun Workshop 6 and above on Solaris
[ https://issues.apache.org/activemq/browse/AMQ-693?page=all ] Hiram Chirino updated AMQ-693: -- Fix Version/s: 4.2 (was: 4.1.0) STOMP C client ready for Sun Workshop 6 and above on Solaris Key: AMQ-693 URL: https://issues.apache.org/activemq/browse/AMQ-693 Project: ActiveMQ Issue Type: Improvement Components: JMS client Affects Versions: 4.0 RC2 Environment: Sun Workshop 6 and above on Solaris 8 and above Reporter: vik dhawan Priority: Minor Fix For: 4.2.0 Attachments: stompc.tar Here i modified STOMP C client so it can run on Solaris platform. I saparated producer and concumer for distributed tracking purposes. Thanks! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-528) 4.0 M4 NullPointerException while shutting down
[ https://issues.apache.org/activemq/browse/AMQ-528?page=all ] Hiram Chirino updated AMQ-528: -- Fix Version/s: 4.2 (was: 4.1.0) 4.0 M4 NullPointerException while shutting down --- Key: AMQ-528 URL: https://issues.apache.org/activemq/browse/AMQ-528 Project: ActiveMQ Issue Type: Bug Affects Versions: 4.0 Environment: RedHat Linux Enterprise Server 3, Tomcat 5.5.15, MySQL 5.0.18 for Linux Reporter: Leon Hu Priority: Critical Fix For: 4.2.0, 4.0.3 Setup: 3 networked brokers, B1, B2, and B3, on 3 servers, connected using multicast discovery. activemq.xml: broker useJmx=false brokerName=B1 persistenceAdapter journaledJDBC journalLogFiles=5 dataDirectory=foo dataSource=#mysql-ds/ /persistenceAdapter transportConnectors transportConnector uri=tcp://localhost:61616 discoveryUri=multicast://default/ /transportConnectors networkConnectors networkConnector uri=multicast://default/ /networkConnectors /broker bean id=mysql-ds class=org.apache.commons.dbcp.BasicDataSource destroy-method=close property name=driverClassName value=com.mysql.jdbc.Driver/ property name=url value=jdbc:mysql://localhost/activemq?relaxAutoCommit=true/ property name=username value=activemqUser/ property name=password value=activemqPwd/ property name=poolPreparedStatements value=true/ /bean Similar for B2 and B3. Two queues: Q1 and Q2. Two producers, one for each queue, both producers connected to B1. One Q1 cosumer connected to B1, another Q1 consumer on B2. One Q2 consumer connected to B2, another Q2 consumer connected to B3. Steps: Start the brokers and start sending messages to the queue. After a while, stop the brokers (Sequence does not matter) See the errors in catalina.out of the Tomcat that has a broker with both producers and consumers connected The problems: 1. Exception in thread ActiveMQ Scheduler java.lang.NullPointerException at edu.emory.mathcs.backport.java.util.concurrent.helpers.Utils$SunPerfProvider.nanoTime(Utils.java:219) at edu.emory.mathcs.backport.java.util.concurrent.helpers.Utils.nanoTime(Utils.java:99) at edu.emory.mathcs.backport.java.util.concurrent.ScheduledThreadPoolExecutor.now(ScheduledThreadPoolExecutor.java:88) at edu.emory.mathcs.backport.java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.getDelay(ScheduledThreadPoolExecutor.java:137) Exception in thread ActiveMQ Scheduler Exception in thread ActiveMQ Scheduler Exception in thread ActiveMQ Scheduler at edu.emory.mathcs.backport.java.util.concurrent.DelayQueue.take(DelayQueue.java:154) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:470) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:667) at java.lang.Thread.run(Thread.java:595) java.lang.NullPointerException at edu.emory.mathcs.backport.java.util.concurrent.helpers.Utils$SunPerfProvider.nanoTime(Utils.java:219) Exception in thread ActiveMQ Scheduler Exception in thread ActiveMQ Scheduler Exception in thread ActiveMQ Scheduler at edu.emory.mathcs.backport.java.util.concurrent.helpers.Utils.nanoTime(Utils.java:99) at edu.emory.mathcs.backport.java.util.concurrent.ScheduledThreadPoolExecutor.now(ScheduledThreadPoolExecutor.java:88) at edu.emory.mathcs.backport.java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.getDelay(ScheduledThreadPoolExecutor.java:137) at edu.emory.mathcs.backport.java.util.concurrent.DelayQueue.take(DelayQueue.java:154) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:470) Exception in thread ActiveMQ Scheduler Exception in thread ActiveMQ Scheduler at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:667) at java.lang.Thread.run(Thread.java:595) 2. The same exception is logged to the log file (in my case catalina.out) for hundreds of times, resulting a log file exceeding 150 MB in 2 minutes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-512) enhance the command line tools to allow messages on queues to be browsed, queues to be purged, messages deleted, dead letter queues to be redispatched to orginal queues etc
[ https://issues.apache.org/activemq/browse/AMQ-512?page=all ] Hiram Chirino updated AMQ-512: -- Fix Version/s: 4.2 (was: 4.1.0) enhance the command line tools to allow messages on queues to be browsed, queues to be purged, messages deleted, dead letter queues to be redispatched to orginal queues etc Key: AMQ-512 URL: https://issues.apache.org/activemq/browse/AMQ-512 Project: ActiveMQ Issue Type: New Feature Reporter: james strachan Assigned To: Adrian Co Fix For: 4.2.0 You should be able to reuse the MBeans for the operations of these commands -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-468) Queue load balancing - optionally give highest priority to the local connection, then local broker then networks
[ https://issues.apache.org/activemq/browse/AMQ-468?page=all ] Hiram Chirino updated AMQ-468: -- Fix Version/s: 4.2 (was: 4.1.0) Queue load balancing - optionally give highest priority to the local connection, then local broker then networks Key: AMQ-468 URL: https://issues.apache.org/activemq/browse/AMQ-468 Project: ActiveMQ Issue Type: Improvement Reporter: Rob Davies Fix For: 4.2.0 For Queues, as an option assign the highest priority for dispatching to the local connection, then the local broker, then the cluster etc. Right now we favour consumers on the local broker above consumers on remote brokers. However we should prioritise consumers on the same session, connection or VM transport above consumers in other processes etc -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-488) Broker side message redelivery due to client death should be tracked so that the message can be sent to the DLQ.
[ https://issues.apache.org/activemq/browse/AMQ-488?page=all ] Hiram Chirino updated AMQ-488: -- Fix Version/s: 4.2 (was: 4.1.0) Broker side message redelivery due to client death should be tracked so that the message can be sent to the DLQ. Key: AMQ-488 URL: https://issues.apache.org/activemq/browse/AMQ-488 Project: ActiveMQ Issue Type: Improvement Reporter: Hiram Chirino Fix For: 4.2.0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-453) Clustering subscriptions
[ https://issues.apache.org/activemq/browse/AMQ-453?page=all ] Hiram Chirino updated AMQ-453: -- Fix Version/s: 4.2 (was: 4.1.0) Clustering subscriptions Key: AMQ-453 URL: https://issues.apache.org/activemq/browse/AMQ-453 Project: ActiveMQ Issue Type: New Feature Reporter: Guillaume Nodet Fix For: 4.2.0 To be able to use ServiceMix WS-Notification in a cluster, we need to be able to: * attach some data to the subscription * provide a way to retrieve subscription informations from the NotificationBroker (using consumer advisory ?) * cluster subscriptions (sticky durable subscriber ?) See irc log from 21/12/2005 from 21:14 http://servlet.uwyn.com/drone/log/hausbot/servicemix/20051221 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-567) Time in queue statistics handy
[ https://issues.apache.org/activemq/browse/AMQ-567?page=all ] Hiram Chirino updated AMQ-567: -- Fix Version/s: 4.2 (was: 4.1.0) Time in queue statistics handy -- Key: AMQ-567 URL: https://issues.apache.org/activemq/browse/AMQ-567 Project: ActiveMQ Issue Type: New Feature Components: Broker Affects Versions: 4.0 M4 Environment: any Reporter: Scott Ellsworth Fix For: 4.2.0 It would be very keen if the JMX console exposed queue statistics, such as average length of time in queue for current messages, longest/shortest time in queue for current messages, average time in queue for serviced messages (as opposed to those waiting), longestlshortest time for same, and a list of messages in the queue with when they were posted, and how long they have been waiting. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-378) add pluggable Policy which is fired in a background Timer to detect slow consumers for non-durable topics and kill them (maybe with a pre-warning of being slow a little befor
[ https://issues.apache.org/activemq/browse/AMQ-378?page=all ] Hiram Chirino updated AMQ-378: -- Fix Version/s: 4.2 (was: 4.1.0) add pluggable Policy which is fired in a background Timer to detect slow consumers for non-durable topics and kill them (maybe with a pre-warning of being slow a little before being killed) - Key: AMQ-378 URL: https://issues.apache.org/activemq/browse/AMQ-378 Project: ActiveMQ Issue Type: New Feature Reporter: james strachan Fix For: 4.2.0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-404) winxp sp2 and mysql4.1.15 throw error
[ https://issues.apache.org/activemq/browse/AMQ-404?page=all ] Hiram Chirino updated AMQ-404: -- Fix Version/s: 4.2 (was: 4.1.0) winxp sp2 and mysql4.1.15 throw error -- Key: AMQ-404 URL: https://issues.apache.org/activemq/browse/AMQ-404 Project: ActiveMQ Issue Type: Bug Components: Message Store Affects Versions: 3.2 Reporter: tao Fix For: 4.2.0 2005-11-04 11:24:17,909 [Cleanup Timmer ] ERROR JDBCPersistenceAdapter - Error in cleanup due to: com.mysql.jdbc.CommunicationsException: Communications link failure due to underlying exception: ** BEGIN NESTED EXCEPTION ** java.net.SocketException MESSAGE: java.net.BindException: Address already in use: connect STACKTRACE: java.net.SocketException: java.net.BindException: Address already in use: connect at com.mysql.jdbc.StandardSocketFactory.connect(StandardSocketFactory.java:156) at com.mysql.jdbc.MysqlIO.init(MysqlIO.java:284) at com.mysql.jdbc.Connection.createNewIO(Connection.java:2541) at com.mysql.jdbc.Connection.init(Connection.java:1474) at com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:266) at org.apache.commons.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:37) at org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:290) at org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:771) at org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:95) at org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:544) at org.activemq.store.jdbc.JDBCPersistenceAdapter.getConnection(JDBCPersistenceAdapter.java:418) at org.activemq.store.jdbc.JDBCPersistenceAdapter.cleanup(JDBCPersistenceAdapter.java:267) at org.activemq.store.jdbc.JDBCPersistenceAdapter$1.run(JDBCPersistenceAdapter.java:257) at EDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(Unknown Source) at java.lang.Thread.run(Thread.java:534) ** END NESTED EXCEPTION ** Last packet sent to the server was 0 ms ago. com.mysql.jdbc.CommunicationsException: Communications link failure due to underlying exception: ** BEGIN NESTED EXCEPTION ** java.net.SocketException MESSAGE: java.net.BindException: Address already in use: connect STACKTRACE: java.net.SocketException: java.net.BindException: Address already in use: connect at com.mysql.jdbc.StandardSocketFactory.connect(StandardSocketFactory.java:156) at com.mysql.jdbc.MysqlIO.init(MysqlIO.java:284) at com.mysql.jdbc.Connection.createNewIO(Connection.java:2541) at com.mysql.jdbc.Connection.init(Connection.java:1474) at com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:266) at org.apache.commons.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:37) at org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:290) at org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:771) at org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:95) at org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:544) at org.activemq.store.jdbc.JDBCPersistenceAdapter.getConnection(JDBCPersistenceAdapter.java:418) at org.activemq.store.jdbc.JDBCPersistenceAdapter.cleanup(JDBCPersistenceAdapter.java:267) at org.activemq.store.jdbc.JDBCPersistenceAdapter$1.run(JDBCPersistenceAdapter.java:257) at EDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(Unknown Source) at java.lang.Thread.run(Thread.java:534) ** END NESTED EXCEPTION ** Last packet sent to the server was 0 ms ago. at com.mysql.jdbc.Connection.createNewIO(Connection.java:2607) at com.mysql.jdbc.Connection.init(Connection.java:1474) at com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:266) at org.apache.commons.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:37) at org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:290) at org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:771) at org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:95) at org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:544) at org.activemq.store.jdbc.JDBCPersistenceAdapter.getConnection(JDBCPersistenceAdapter.java:418) at org.activemq.store.jdbc.JDBCPersistenceAdapter.cleanup(JDBCPersistenceAdapter.java:267)
[jira] Updated: (AMQ-767) avoid use of XHTML in activemq-web-console so things work great in IE 6
[ https://issues.apache.org/activemq/browse/AMQ-767?page=all ] Hiram Chirino updated AMQ-767: -- Fix Version/s: 4.2 (was: 4.1.0) avoid use of XHTML in activemq-web-console so things work great in IE 6 --- Key: AMQ-767 URL: https://issues.apache.org/activemq/browse/AMQ-767 Project: ActiveMQ Issue Type: Bug Affects Versions: 4.0.1 Reporter: james strachan Fix For: 4.2.0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-751) Extend ExceptionListener mechanism by creating a custom AMQ exception which would provide more detail about the exception
[ https://issues.apache.org/activemq/browse/AMQ-751?page=all ] Hiram Chirino updated AMQ-751: -- Fix Version/s: 4.2 (was: 4.1.0) Extend ExceptionListener mechanism by creating a custom AMQ exception which would provide more detail about the exception - Key: AMQ-751 URL: https://issues.apache.org/activemq/browse/AMQ-751 Project: ActiveMQ Issue Type: Improvement Components: JMS client, Broker Reporter: Massive Boisson Priority: Minor Fix For: 4.2.0 To quote James: I wonder if we could add a neater non-JMS extension to ActiveMQ to make it easier to be notified asynchronously of which Message objects could not be sent? I guess we could just use the ExceptionListener and use a custom type of Exception which contained the Message object? I think this would greatly increase the usefulness of async sends. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-376) security plugin which can use, say, LDAP to authenticate the user, then use a custom database table to associate roles to users and destinations to roles
[ https://issues.apache.org/activemq/browse/AMQ-376?page=all ] Hiram Chirino updated AMQ-376: -- Fix Version/s: 4.2 (was: 4.1.0) security plugin which can use, say, LDAP to authenticate the user, then use a custom database table to associate roles to users and destinations to roles - Key: AMQ-376 URL: https://issues.apache.org/activemq/browse/AMQ-376 Project: ActiveMQ Issue Type: New Feature Reporter: james strachan Fix For: 4.2.0 BTW have added org.activemq.security.SecurityAdminMBean as a simple MBean API to the admin of these things. Note we wanna cache the security state; then have a notification (via JMS Topic) to flush/reload the data when folks change it - so performance is great and the security configuration is highly dynamic -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-340) allow topics in particular but also queues to have a 'namespace URI' like WS-Notification
[ https://issues.apache.org/activemq/browse/AMQ-340?page=all ] Hiram Chirino updated AMQ-340: -- Fix Version/s: 4.2 (was: 4.1.0) allow topics in particular but also queues to have a 'namespace URI' like WS-Notification - Key: AMQ-340 URL: https://issues.apache.org/activemq/browse/AMQ-340 Project: ActiveMQ Issue Type: New Feature Reporter: james strachan Assigned To: james strachan Fix For: 4.2.0 This would allow a real clean mapping from WS-N topics and ActiveMQ at the protocol level. We could use the namespace as a level of indirection to map to a broker, a cluster of brokers or even a particular area of a network etc. The namespace could be a broker's name too. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-361) duplicate delivery, already consumed messages are reconsumed after server restart
[ https://issues.apache.org/activemq/browse/AMQ-361?page=all ] Hiram Chirino updated AMQ-361: -- Fix Version/s: 4.2 (was: 4.1.0) duplicate delivery, already consumed messages are reconsumed after server restart - Key: AMQ-361 URL: https://issues.apache.org/activemq/browse/AMQ-361 Project: ActiveMQ Issue Type: Bug Components: Broker, Message Store, JCA Container Affects Versions: 4.0 Environment: windows xp, jdk 1.5, embedded activemq 3.1 broker, jboss 4.02, persistent messages with derby db. Reporter: Gokturk Ozer Fix For: 4.2.0 Attachments: 1.log I am running an embedded activemq broker inside jboss server, I send 1000 messages with ~10K size each to a queue, these messages are consumed by MDBs. After all the messages are consumed, I check the queue via hermes, it also shows no message in the queue. Everything works perfect up to this point. I observe the problem after I stop the jboss server. I connect to derby database via networkserver, I still see some messages in activemq_msgs table. I shutdown derby networkserver and start jboss again, I see from the log that some of the messages which were consumed previously, are being consumed again. If I start the server without deploying the MDB and check the queue via hermes, I see some but not all the messages which were consumed previously still in the queue, before restart hermes was showing no messages. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-431) only send a message once for multiple consumers on the same connection (for topics)
[ https://issues.apache.org/activemq/browse/AMQ-431?page=all ] Hiram Chirino updated AMQ-431: -- Fix Version/s: 4.2 (was: 4.1.0) only send a message once for multiple consumers on the same connection (for topics) --- Key: AMQ-431 URL: https://issues.apache.org/activemq/browse/AMQ-431 Project: ActiveMQ Issue Type: Improvement Reporter: james strachan Fix For: 4.2.0 in 3.x we sent a message once with a list of all the MessageConsumers on it so that we could avoid sending multiple messages over a socket when several consumers are on the same connection. We should add back that optimisation -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-371) auto protocol switch from openwire to stomp on JMS client in case some 4.0 JMS client cannot work with some late version (like 8.3) of ActiveMQ server - we can always move ba
[ https://issues.apache.org/activemq/browse/AMQ-371?page=all ] Hiram Chirino updated AMQ-371: -- Fix Version/s: 4.2 (was: 4.1.0) auto protocol switch from openwire to stomp on JMS client in case some 4.0 JMS client cannot work with some late version (like 8.3) of ActiveMQ server - we can always move back to stomp - Key: AMQ-371 URL: https://issues.apache.org/activemq/browse/AMQ-371 Project: ActiveMQ Issue Type: Improvement Components: JMS client Reporter: james strachan Fix For: 4.2.0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-367) Axis/JMS/ActiveMQ demo
[ https://issues.apache.org/activemq/browse/AMQ-367?page=all ] Hiram Chirino updated AMQ-367: -- Fix Version/s: 4.2 (was: 4.1.0) Axis/JMS/ActiveMQ demo -- Key: AMQ-367 URL: https://issues.apache.org/activemq/browse/AMQ-367 Project: ActiveMQ Issue Type: New Feature Affects Versions: 3.1 Reporter: Chris Berry Fix For: 4.2.0 Attachments: axis-jms-demo.zip I have created a self-contained demo of using Axis/JMS/ActiveMQ James suggested that I pass it along for possible inclusion in the examples All of the code is in the enclosed ZIP Cheers, -- Chris -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-375) advisory and MBean notification if a slow consumer is killed (with access to the userName in in the message)
[ https://issues.apache.org/activemq/browse/AMQ-375?page=all ] Hiram Chirino updated AMQ-375: -- Fix Version/s: 4.2 (was: 4.1.0) advisory and MBean notification if a slow consumer is killed (with access to the userName in in the message) - Key: AMQ-375 URL: https://issues.apache.org/activemq/browse/AMQ-375 Project: ActiveMQ Issue Type: New Feature Components: Broker Reporter: james strachan Fix For: 4.2.0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-132) Remotting logging of clients under flow control
[ https://issues.apache.org/activemq/browse/AMQ-132?page=all ] Hiram Chirino updated AMQ-132: -- Fix Version/s: 4.2 (was: 4.1.0) Remotting logging of clients under flow control --- Key: AMQ-132 URL: https://issues.apache.org/activemq/browse/AMQ-132 Project: ActiveMQ Issue Type: New Feature Reporter: Barry Kaplan Fix For: 4.2.0 When performance testing a system (or troubleshooting slowdowns in production) it would be very helpful to know when any client has come under flow control. This information would be logged (via jmx events?) including the identification of the broker(s) that cannot keep up, and the corresponding client(s) that have been throttled. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-327) Orphanded/lost queue messages in various failover tests in two broker configuration
[ https://issues.apache.org/activemq/browse/AMQ-327?page=all ] Hiram Chirino updated AMQ-327: -- Fix Version/s: 4.2 (was: 4.1.0) Orphanded/lost queue messages in various failover tests in two broker configuration --- Key: AMQ-327 URL: https://issues.apache.org/activemq/browse/AMQ-327 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 4.0 Environment: w2k RH 9.0 jdk1.4.2 Reporter: Dennis Cook Assigned To: John Heitmann Fix For: 4.2.0 Attachments: AMQ-327.tar.gz Seems like the messages being passed to a broker where no client is connected when the failed broker is re-established. This message is lost until a client is connected to this broker. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-382) Security plugin using database tables for user, role, destination mapping; along with an MBean to administer them and a JMS subscription notification of when they change so
[ https://issues.apache.org/activemq/browse/AMQ-382?page=all ] Hiram Chirino updated AMQ-382: -- Fix Version/s: 4.2 (was: 4.1.0) Security plugin using database tables for user, role, destination mapping; along with an MBean to administer them and a JMS subscription notification of when they change so we can reload the cache -- Key: AMQ-382 URL: https://issues.apache.org/activemq/browse/AMQ-382 Project: ActiveMQ Issue Type: New Feature Reporter: james strachan Fix For: 4.2.0 So the idea is its cached in RAM for speed; then it gets reloaded from the database if folks change it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (AMQ-1031) Message delivered out of order to a MessageListener when session is transced and a rollback occurs.
Message delivered out of order to a MessageListener when session is transced and a rollback occurs. --- Key: AMQ-1031 URL: https://issues.apache.org/activemq/browse/AMQ-1031 Project: ActiveMQ Issue Type: Bug Affects Versions: 4.0 Reporter: Hiram Chirino Assigned To: Hiram Chirino Fix For: 4.1 This is actually spotted by a message in the broker log saying that Acknowledgment out of sync (Normally occurs when failover connection reconnects) or in some previous version of ActiveMQ, an async exception being delivered to the client with a similar error message. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (AMQ-1032) Avoid a delivery delay on the first redelivery.
Avoid a delivery delay on the first redelivery. --- Key: AMQ-1032 URL: https://issues.apache.org/activemq/browse/AMQ-1032 Project: ActiveMQ Issue Type: Improvement Affects Versions: 4.0 Reporter: Hiram Chirino Assigned To: Hiram Chirino Fix For: 4.1 The first time a message is redelivered, it always waits at the initial redelivery delay. Since logic may be different to handle a message that has the redelivered flag enabled, there is a chance that the first time that a message is redeliver it will not fail the same way the original delivery failed. We should only start using a redelivery delay on subsequent redeliveries. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (AMQ-1032) Avoid a delivery delay on the first redelivery.
[ https://issues.apache.org/activemq/browse/AMQ-1032?page=all ] Hiram Chirino resolved AMQ-1032. Resolution: Fixed Implemented in trunk revision 472345 Avoid a delivery delay on the first redelivery. --- Key: AMQ-1032 URL: https://issues.apache.org/activemq/browse/AMQ-1032 Project: ActiveMQ Issue Type: Improvement Affects Versions: 4.0 Reporter: Hiram Chirino Assigned To: Hiram Chirino Fix For: 4.1 The first time a message is redelivered, it always waits at the initial redelivery delay. Since logic may be different to handle a message that has the redelivered flag enabled, there is a chance that the first time that a message is redeliver it will not fail the same way the original delivery failed. We should only start using a redelivery delay on subsequent redeliveries. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (AMQ-997) Use the ACTIVEMQ_BASE environment variable to support running multiple broker instances from he same activemq install
Use the ACTIVEMQ_BASE environment variable to support running multiple broker
instances from he same activemq install
-
Key: AMQ-997
URL: https://issues.apache.org/activemq/browse/AMQ-997
Project: ActiveMQ
Issue Type: New Feature
Reporter: Hiram Chirino
Assigned To: Hiram Chirino
Fix For: 4.1
The activemq startup shell scripts are allready using / find the ACTIVEMQ_HOME
which is where AcitiveMQ has been installed. Currently, you can only run one
instance of the broker per ActiveMQ installation directory. We should support
running multiple broker instances using that same ACTIVEMQ_HOME. All the per
broker instance variable data should be relative to a new ACTIVEMQ_BASE
enviroment variable.
By default the ACTIVEMQ_BASE == ACTIVEMQ_HOME so that sarting up the default
activemq instance continues to behave as it allways has.
Createing a new per instance directory, as admin should only have to do:
{code}
export ACTIVEMQ_BASE=/path/to/new/directory
mkdir -p ${ACTIVEMQ_BASE}
cp -R ${ACTIVEMQ_HOME}/conf ${ACTIVEMQ_BASE}
{code}
customize the ${ACTIVEMQ_BASE}/conf/activemq.xml file
And to run the new instance:
{code}
export ACTIVEMQ_BASE=/path/to/new/directory
${ACTIVEMQ_HOME}/bin/activemq
{code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (AMQ-997) Use the ACTIVEMQ_BASE environment variable to support running multiple broker instances from he same activemq install
[ https://issues.apache.org/activemq/browse/AMQ-997?page=all ]
Hiram Chirino resolved AMQ-997.
---
Resolution: Fixed
implemented.
Use the ACTIVEMQ_BASE environment variable to support running multiple broker
instances from he same activemq install
-
Key: AMQ-997
URL: https://issues.apache.org/activemq/browse/AMQ-997
Project: ActiveMQ
Issue Type: New Feature
Reporter: Hiram Chirino
Assigned To: Hiram Chirino
Fix For: 4.1
The activemq startup shell scripts are allready using / find the
ACTIVEMQ_HOME which is where AcitiveMQ has been installed. Currently, you
can only run one instance of the broker per ActiveMQ installation directory.
We should support running multiple broker instances using that same
ACTIVEMQ_HOME. All the per broker instance variable data should be relative
to a new ACTIVEMQ_BASE enviroment variable.
By default the ACTIVEMQ_BASE == ACTIVEMQ_HOME so that sarting up the default
activemq instance continues to behave as it allways has.
Createing a new per instance directory, as admin should only have to do:
{code}
export ACTIVEMQ_BASE=/path/to/new/directory
mkdir -p ${ACTIVEMQ_BASE}
cp -R ${ACTIVEMQ_HOME}/conf ${ACTIVEMQ_BASE}
{code}
customize the ${ACTIVEMQ_BASE}/conf/activemq.xml file
And to run the new instance:
{code}
export ACTIVEMQ_BASE=/path/to/new/directory
${ACTIVEMQ_HOME}/bin/activemq
{code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Reopened: (AMQ-978) No Messaged delivery when mixing Perl stomp client Producer/Consumer and Java JMS Producer/Consumer
[ https://issues.apache.org/activemq/browse/AMQ-978?page=all ] Hiram Chirino reopened AMQ-978: --- Assignee: Hiram Chirino No Messaged delivery when mixing Perl stomp client Producer/Consumer and Java JMS Producer/Consumer --- Key: AMQ-978 URL: https://issues.apache.org/activemq/browse/AMQ-978 Project: ActiveMQ Issue Type: Bug Components: Connector Environment: This problem seems platform independent: It happens in Linux, Mac OSX, and Windows. Software Used: ActiveMQ 4.0, Java 5.0, JMS, Perl 5.8.7, Perl CPAN module Net-Stomp-0.31 Reporter: Sileshi Kassa Assigned To: Hiram Chirino Attachments: Publisher.pl, Subscriber.pl Facts: Perl Stomp client Producer and Consumer works fine Java JMS client Producer and Consumer works fine I have also used other Perl Stomp protocol implementation with no problem. The problem happens when I mix Java and Perl clients Scenario Test 1: A. Perl Stomp client Consumer B. Java JMS client Producer Scenario Test 2: A. Java JMS client Consumer B. Perl Stomp client Producer I have looked into it via Java JMX management jconsole, and it seems to me there is a wall between the stomp server and default server. It the stomp server only passes messages coming from stomp lients and default server also does the same. If this is truly the case, and this is by design, I will be very disappointed. There should not be any wall. A message is message irrespective of its source and should be delivered to any one that is listening on the same destination. I will attach the Perl clients testcases. For Java client, a simple JMS client Producer and Consumer with the same topic used as the perl side will do the job. The topic I used on the perl side: /topic/Test.CrossDelivery and the Java side topic is Test.CrossDelivery This problem is a show stopper for us. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-978) No Messaged delivery when mixing Perl stomp client Producer/Consumer and Java JMS Producer/Consumer
[ https://issues.apache.org/activemq/browse/AMQ-978?page=all ] Hiram Chirino updated AMQ-978: -- Attachment: Net-Stomp-0.31-bytemessage-support.patch I've made a modification to the Net::Stomp 0.31 package so that it can support receiving TextMessage and ByteMessages. We need to feed this back to the upstream maintainer so that it can get back on CPAN. No Messaged delivery when mixing Perl stomp client Producer/Consumer and Java JMS Producer/Consumer --- Key: AMQ-978 URL: https://issues.apache.org/activemq/browse/AMQ-978 Project: ActiveMQ Issue Type: Bug Components: Connector Environment: This problem seems platform independent: It happens in Linux, Mac OSX, and Windows. Software Used: ActiveMQ 4.0, Java 5.0, JMS, Perl 5.8.7, Perl CPAN module Net-Stomp-0.31 Reporter: Sileshi Kassa Assigned To: Hiram Chirino Attachments: Net-Stomp-0.31-bytemessage-support.patch, Publisher.pl, Subscriber.pl Facts: Perl Stomp client Producer and Consumer works fine Java JMS client Producer and Consumer works fine I have also used other Perl Stomp protocol implementation with no problem. The problem happens when I mix Java and Perl clients Scenario Test 1: A. Perl Stomp client Consumer B. Java JMS client Producer Scenario Test 2: A. Java JMS client Consumer B. Perl Stomp client Producer I have looked into it via Java JMX management jconsole, and it seems to me there is a wall between the stomp server and default server. It the stomp server only passes messages coming from stomp lients and default server also does the same. If this is truly the case, and this is by design, I will be very disappointed. There should not be any wall. A message is message irrespective of its source and should be delivered to any one that is listening on the same destination. I will attach the Perl clients testcases. For Java client, a simple JMS client Producer and Consumer with the same topic used as the perl side will do the job. The topic I used on the perl side: /topic/Test.CrossDelivery and the Java side topic is Test.CrossDelivery This problem is a show stopper for us. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (AMQ-960) Improved error reporting for SSL and transports. Changed Username for SSL cert to the DN
[ https://issues.apache.org/activemq/browse/AMQ-960?page=comments#action_37202 ] Hiram Chirino commented on AMQ-960: --- Thanks Kelly! patch applied in trunk rev 464659 Improved error reporting for SSL and transports. Changed Username for SSL cert to the DN Key: AMQ-960 URL: https://issues.apache.org/activemq/browse/AMQ-960 Project: ActiveMQ Issue Type: Improvement Components: Transport Affects Versions: 4.1 Environment: all Reporter: Kelly Campbell Fix For: 4.1 Attachments: activemq-patch-20061006-1.patch, activemq-patch-20061006-2.patch The attached patch provides better error reporting for transport errors by reporting the host which was trying to connect. It also provides a toString for SslTransport to distinguish it from the regular tcp transport, and includes some improved javadoc for the new SSL client certificate authentication feature. Additionally, it changes the username reported through the JMSXUserId field to be the full distinguished name rather than the username mapped in the users properties file. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (AMQ-960) Improved error reporting for SSL and transports. Changed Username for SSL cert to the DN
[ https://issues.apache.org/activemq/browse/AMQ-960?page=all ] Hiram Chirino resolved AMQ-960. --- Resolution: Fixed Assignee: Hiram Chirino Improved error reporting for SSL and transports. Changed Username for SSL cert to the DN Key: AMQ-960 URL: https://issues.apache.org/activemq/browse/AMQ-960 Project: ActiveMQ Issue Type: Improvement Components: Transport Affects Versions: 4.1 Environment: all Reporter: Kelly Campbell Assigned To: Hiram Chirino Fix For: 4.1 Attachments: activemq-patch-20061006-1.patch, activemq-patch-20061006-2.patch The attached patch provides better error reporting for transport errors by reporting the host which was trying to connect. It also provides a toString for SslTransport to distinguish it from the regular tcp transport, and includes some improved javadoc for the new SSL client certificate authentication feature. Additionally, it changes the username reported through the JMSXUserId field to be the full distinguished name rather than the username mapped in the users properties file. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (AMQ-923) Add the ability to remove network connectors dynamically
Add the ability to remove network connectors dynamically Key: AMQ-923 URL: https://issues.apache.org/activemq/browse/AMQ-923 Project: ActiveMQ Issue Type: Improvement Reporter: Hiram Chirino Assigned To: Hiram Chirino Fix For: 4.1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (AMQ-923) Add the ability to remove network connectors dynamically
[ https://issues.apache.org/activemq/browse/AMQ-923?page=all ] Hiram Chirino resolved AMQ-923. --- Resolution: Fixed Done in trunk rev 434068 Add the ability to remove network connectors dynamically Key: AMQ-923 URL: https://issues.apache.org/activemq/browse/AMQ-923 Project: ActiveMQ Issue Type: Improvement Reporter: Hiram Chirino Assigned To: Hiram Chirino Fix For: 4.1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-922) Add the ability to remove transport connectors dynamically
[ https://issues.apache.org/activemq/browse/AMQ-922?page=all ] Hiram Chirino updated AMQ-922: -- Summary: Add the ability to remove transport connectors dynamically (was: Add a removeConnector() to BrokerServer to remove added transport connectors.) Description: Add a removeConnector() to BrokerServer to remove added transport connectors. Add the ability to remove transport connectors dynamically --- Key: AMQ-922 URL: https://issues.apache.org/activemq/browse/AMQ-922 Project: ActiveMQ Issue Type: Improvement Reporter: Hiram Chirino Assigned To: Hiram Chirino Fix For: 4.1 Add a removeConnector() to BrokerServer to remove added transport connectors. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (AMQ-915) Failover transport does not replay all the transaction operations on failover.
[ https://issues.apache.org/activemq/browse/AMQ-915?page=comments#action_36952 ] Hiram Chirino commented on AMQ-915: --- Applied patch to to 4.0 branch rev 443423 Failover transport does not replay all the transaction operations on failover. -- Key: AMQ-915 URL: https://issues.apache.org/activemq/browse/AMQ-915 Project: ActiveMQ Issue Type: Bug Affects Versions: 4.0 Reporter: Hiram Chirino Assigned To: Adrian Co Fix For: 4.1 If transactions are being used on a connection that is using failover.. these is a small chance that the transaction will fail or the connection will fail due to a partial tx being run when the client reconnects. I will change the failover transport to buffer up all the tx operations that are run against the broker and on failure, replay those operations. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Work stopped: (AMQ-912) ActiveMQ support for SSL authentication and authorization
[ https://issues.apache.org/activemq/browse/AMQ-912?page=all ] Work on AMQ-912 stopped by Hiram Chirino. ActiveMQ support for SSL authentication and authorization - Key: AMQ-912 URL: https://issues.apache.org/activemq/browse/AMQ-912 Project: ActiveMQ Issue Type: Improvement Components: Test Cases, Transport Reporter: Sepand Mavandadi Assigned To: Hiram Chirino Attachments: ssl_certifiacte_auth_patch.txt, svn_diff.txt Original Estimate: 0 minutes Remaining Estimate: 0 minutes This patch adds new Transports, Brokers, and Plugins needed for authentication and authorization based on SSL certificates. It also adds a few unit tests for the mentioned classes. The new (or heavily modified) SslTransport, SslTransportServer, and SslTransportFactory classes allow for access to the underlying socket's need and want client auth settings. If a certificate is found, it is set as the transportContext of the created connection. The JaasCertificateAuthenticationBroker uses the new CertificateLoginModule to authenticate certificates (this class is abstract to allow for different backends for certificate authentication, a concrete class is TextFileCertificateLoginModule). JaasCertificateAuthenticationBroker also sets the security context's user name to that provided for the certificate by the login module. This allows for authorization using the existing authorization broker. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (AMQ-911) Transient connection failure with Failover transport can cause InvalidClientIDException
Transient connection failure with Failover transport can cause InvalidClientIDException --- Key: AMQ-911 URL: https://issues.apache.org/activemq/browse/AMQ-911 Project: ActiveMQ Issue Type: Bug Affects Versions: 4.0 Reporter: Hiram Chirino Assigned To: Hiram Chirino Fix For: 4.1, 4.0.2 It shows up as errors on the broker log: Error occured while processing sync command: javax.jms.InvalidClientIDException: Broker: localhost - Client: ID:hchirino-mac.local-51624-1157486953862-2:0 already connected -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (AMQ-855) Add support for prefetchSize = 0
[ https://issues.apache.org/activemq/browse/AMQ-855?page=comments#action_36898 ] Hiram Chirino commented on AMQ-855: --- Thanks Vadim, patch applied in trunk rev 439804. Test case passes without error. Add support for prefetchSize = 0 Key: AMQ-855 URL: https://issues.apache.org/activemq/browse/AMQ-855 Project: ActiveMQ Issue Type: New Feature Components: Broker Affects Versions: 4.0, 4.0.1, 4.0.2 Environment: any Reporter: Vadim Pesochinskiy Assigned To: Hiram Chirino Priority: Critical Fix For: 4.1 Attachments: ActiveMQMessageConsumer.patch, ActiveMQMessageConsumer.patch2, PrefetchSubscription.patch, region.QueueSubscription.java.patch, ZeroPrefetchConsumerTest.java.patch This feature would enable to support following test case: 2 servers are processing 3 submitted jobs with following processing times 10 min, 1 min, 1 min. This sequence should finish in 10 minutes as one service will pick up the 10 minutes job, meanwhile the other one should manage the two 1 minute jobs. Since I cannot set prefetchSize=0, one of the 1 minute jobs is sitting in prefetch buffer and the jobs are processed in 11 minutes instead of 10. This is simplification of the real scenario where I have about 30 consumers submitting jobs to 20 consumers through AMQ 4.0.1. I have following problems: Messages are sitting in prefetch buffer are not available to processors, which results in a lot of idle time. Order of processing is random. For some reason Job # 20 is processed after Job # 1500. Since senders are synchronously blocked this can result in time-outs. Some requests are real-time, i.e. there is a user waiting, so the system cannot wait, so AMQ-850 does not fix this issue. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (AMQ-875) TCP connector (server) will stop accepting connection if an invalid connection is made to him.
TCP connector (server) will stop accepting connection if an invalid connection is made to him. -- Key: AMQ-875 URL: https://issues.apache.org/activemq/browse/AMQ-875 Project: ActiveMQ Issue Type: Bug Components: Transport Affects Versions: 4.0 Reporter: Hiram Chirino Assigned To: Hiram Chirino Charles reported on the mailing list: Hi All, We've just had a nasty situation : our ActiveMQ Server standalone plain vanilla TCP Transport, no persistency, no nuffink) on one of our live installations suddenly refused to accept any new connections - no clients could connect. All currently connected clients were fine, and messages were being processed sent and received fine. Just no-one else could connect. After 20 minutes, new connections were suddenly allowed. The following exception was in our log. 2006-Aug-11 12:17:47.726 aqualive [ActiveMQ Transport Server: tcp://blah:61616] ERROR org.apache.activemq.broker.TransportConnector - Could not accept connection: java.net.SocketException: Connection reset by peer: socket write error java.net.SocketException: Connection reset by peer: socket write error at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at org.apache.activemq.transport.tcp.TcpBufferedOutputStream.flush(TcpBufferedO utputStream.java:108) at java.io.DataOutputStream.flush(DataOutputStream.java:101) at org.apache.activemq.transport.tcp.TcpTransport.oneway(TcpTransport.java:125) at org.apache.activemq.transport.InactivityMonitor.oneway(InactivityMonitor.jav a:141) at org.apache.activemq.transport.WireFormatNegotiator.sendWireFormat(WireFormat Negotiator.java:128) at org.apache.activemq.transport.WireFormatNegotiator.start(WireFormatNegotiato r.java:64) at org.apache.activemq.transport.TransportFilter.start(TransportFilter.java:52) at org.apache.activemq.transport.TransportFilter.start(TransportFilter.java:52) at org.apache.activemq.broker.TransportConnection.start(TransportConnection.jav a:75) at org.apache.activemq.broker.TransportConnector$1.onAccept(TransportConnector. java:136) at org.apache.activemq.transport.tcp.TcpTransportServer.run(TcpTransportServer. java:137) at java.lang.Thread.run(Thread.java:534) My interpretation of the above that something (port scanner maybe ? Our curious IT department ?) is connecting to the listening socket, and the TransportServer is trying to tell the connecting process what the wireformat is - and the connection process is just sitting there, not responding, acknlowedging, or doing anything at all - yet not closing the connection. Therefore, the transport server is blocked, preventing anyone else connecting. After 20 mins - which I am guessing is somekind of lowlevel timeout, seeing as all the default AMQ timeouts seen to be of the order of 1 - 30 secs - a low level TCP exception is thrown, freeing the whole shebang up. I notice there is an InactivityMonitor, and looking at the code there is the following comment // Disable inactivity monitoring while processing a command. Could this be the case ? That - until the wireformat has been negotiated - there is no timeout configured ? Is there anything we can do to reduce this timeout from 20 mins ? Or have I completed gone down the wrong track ? This is AMQ 4.0, Win2K, JRE 1.4.2 Cheers, Charles -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (AMQ-815) generate a warning by default if a client connects via openwire using a different release version of the broker
[ https://issues.apache.org/activemq/browse/AMQ-815?page=all ] Hiram Chirino reassigned AMQ-815: - Assignee: Hiram Chirino generate a warning by default if a client connects via openwire using a different release version of the broker --- Key: AMQ-815 URL: https://issues.apache.org/activemq/browse/AMQ-815 Project: ActiveMQ Issue Type: Improvement Reporter: james strachan Assigned To: Hiram Chirino Fix For: 4.1 While we can be quite liberal in supporting backwards compatible clients, the default should be to warn folks if they connect via different versions - as thats often an indication of classpath issues. Maybe have 3 options - lenient (try to work with anything), warning (just log warning on connection), strict (disconnect non-similar version clients) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-732) Infinite recovery loop.
[ https://issues.apache.org/activemq/browse/AMQ-732?page=all ]
Hiram Chirino updated AMQ-732:
--
Fix Version/s: 4.0.3
(was: 4.0.2)
Infinite recovery loop.
---
Key: AMQ-732
URL: https://issues.apache.org/activemq/browse/AMQ-732
Project: ActiveMQ
Issue Type: Bug
Components: Broker
Affects Versions: 4.0
Environment: Linux RHEL 3
Reporter: Maxim Fateev
Assigned To: Hiram Chirino
Fix For: 4.1, 4.0.3
Attachments: activemq-data-1-journal.tar.gz,
activemq-data-2-journal.tar.gz
The simplest way to reproduce the problem:
1. Remove storage directory.
2. Start broker using the following code:
public static void main(String[] args) throws Exception {
BrokerService broker = new BrokerService();
broker.setPersistent(true);
DefaultPersistenceAdapterFactory pFactory = new
DefaultPersistenceAdapterFactory();
pFactory.setJournalLogFiles(1);
pFactory.setJournalLogFileSize(2048);
broker.setPersistenceFactory(pFactory);
broker.setUseJmx(false);
broker.addConnector(tcp://localhost:61616);
broker.start();
Thread.sleep(1l);
}
3. Shutdown the broker.
4. Start broker.
It enters infinite loop
[ main] BrokerService INFO
ActiveMQ null JMS Message Broker (localhost) is starting
[ main] BrokerService INFO For
help or more information please see: http://incubator.apache.org/activemq/
[ main] JDBCPersistenceAdapter INFO
Database driver recognized: [apache_derby_embedded_jdbc_driver]
[ main] DefaultJDBCAdapter DEBUG
Executing SQL: CREATE TABLE ACTIVEMQ_MSGS(ID INTEGER NOT NULL, CONTAINER
VARCHAR(250), MSGID_PROD VARCHAR(250), MSGID_SEQ INTEGER, EXPIRATION BIGINT,
MSG BLOB, PRIMARY KEY ( ID ) )
[ main] DefaultJDBCAdapter DEBUG Could
not create JDBC tables; The message table already existed. Failure was:
CREATE TABLE ACTIVEMQ_MSGS(ID INTEGER NOT NULL, CONTAINER VARCHAR(250),
MSGID_PROD VARCHAR(250), MSGID_SEQ INTEGER, EXPIRATION BIGINT, MSG BLOB,
PRIMARY KEY ( ID ) ) Message: Table/View 'ACTIVEMQ_MSGS' already exists in
Schema 'APP'. SQLState: X0Y32 Vendor code: 2
[ main] DefaultJDBCAdapter DEBUG
Executing SQL: CREATE INDEX ACTIVEMQ_MSGS_MIDX ON ACTIVEMQ_MSGS
(MSGID_PROD,MSGID_SEQ)
[ main] DefaultJDBCAdapter DEBUG
Executing SQL: CREATE INDEX ACTIVEMQ_MSGS_CIDX ON ACTIVEMQ_MSGS (CONTAINER)
[ main] DefaultJDBCAdapter DEBUG
Executing SQL: CREATE INDEX ACTIVEMQ_MSGS_EIDX ON ACTIVEMQ_MSGS (EXPIRATION)
[ main] DefaultJDBCAdapter DEBUG
Executing SQL: CREATE TABLE ACTIVEMQ_ACKS(CONTAINER VARCHAR(250) NOT NULL,
CLIENT_ID VARCHAR(250) NOT NULL, SUB_NAME VARCHAR(250) NOT NULL, SELECTOR
VARCHAR(250), LAST_ACKED_ID INTEGER, PRIMARY KEY ( CONTAINER, CLIENT_ID,
SUB_NAME))
[ main] DefaultJDBCAdapter DEBUG Could
not create JDBC tables; The message table already existed. Failure was:
CREATE TABLE ACTIVEMQ_ACKS(CONTAINER VARCHAR(250) NOT NULL, CLIENT_ID
VARCHAR(250) NOT NULL, SUB_NAME VARCHAR(250) NOT NULL, SELECTOR VARCHAR(250),
LAST_ACKED_ID INTEGER, PRIMARY KEY ( CONTAINER, CLIENT_ID, SUB_NAME))
Message: Table/View 'ACTIVEMQ_ACKS' already exists in Schema 'APP'. SQLState:
X0Y32 Vendor code: 2
[ main] JDBCPersistenceAdapter DEBUG
Cleaning up old messages.
[ main] DefaultJDBCAdapter DEBUG
Executing SQL: DELETE FROM ACTIVEMQ_MSGS WHERE ( EXPIRATION0 AND
EXPIRATION?) OR ID = ( SELECT min(ACTIVEMQ_ACKS.LAST_ACKED_ID) FROM
ACTIVEMQ_ACKS WHERE ACTIVEMQ_ACKS.CONTAINER=ACTIVEMQ_MSGS.CONTAINER)
[ main] DefaultJDBCAdapter DEBUG Deleted
0 old message(s).
[ main] JDBCPersistenceAdapter DEBUG Cleanup
done.
[ main] JournalPersistenceAdapter INFO Journal
Recovery Started from: Active Journal: using 1 x 0.001953125 Megs at:
/workplace/fateev/install/activemq-4.0-SNAPSHOT/activemq-core/activemq-data/journal
[ main] JournalPersistenceAdapter DEBUG TRACE
Entry: RECOVERED
[Journal Writer] LogFileManager DEBUG
getNextDataRecordLocation offset=53
[Journal Writer] LogFileManager DEBUG
getNextDataRecordLocation offset=97
[Journal Writer] LogFileManager DEBUG
[jira] Updated: (AMQ-528) 4.0 M4 NullPointerException while shutting down
[ https://issues.apache.org/activemq/browse/AMQ-528?page=all ] Hiram Chirino updated AMQ-528: -- Fix Version/s: 4.0.3 (was: 4.0.2) 4.0 M4 NullPointerException while shutting down --- Key: AMQ-528 URL: https://issues.apache.org/activemq/browse/AMQ-528 Project: ActiveMQ Issue Type: Bug Affects Versions: 4.0 Environment: RedHat Linux Enterprise Server 3, Tomcat 5.5.15, MySQL 5.0.18 for Linux Reporter: Leon Hu Priority: Critical Fix For: 4.0.3, 4.1 Setup: 3 networked brokers, B1, B2, and B3, on 3 servers, connected using multicast discovery. activemq.xml: broker useJmx=false brokerName=B1 persistenceAdapter journaledJDBC journalLogFiles=5 dataDirectory=foo dataSource=#mysql-ds/ /persistenceAdapter transportConnectors transportConnector uri=tcp://localhost:61616 discoveryUri=multicast://default/ /transportConnectors networkConnectors networkConnector uri=multicast://default/ /networkConnectors /broker bean id=mysql-ds class=org.apache.commons.dbcp.BasicDataSource destroy-method=close property name=driverClassName value=com.mysql.jdbc.Driver/ property name=url value=jdbc:mysql://localhost/activemq?relaxAutoCommit=true/ property name=username value=activemqUser/ property name=password value=activemqPwd/ property name=poolPreparedStatements value=true/ /bean Similar for B2 and B3. Two queues: Q1 and Q2. Two producers, one for each queue, both producers connected to B1. One Q1 cosumer connected to B1, another Q1 consumer on B2. One Q2 consumer connected to B2, another Q2 consumer connected to B3. Steps: Start the brokers and start sending messages to the queue. After a while, stop the brokers (Sequence does not matter) See the errors in catalina.out of the Tomcat that has a broker with both producers and consumers connected The problems: 1. Exception in thread ActiveMQ Scheduler java.lang.NullPointerException at edu.emory.mathcs.backport.java.util.concurrent.helpers.Utils$SunPerfProvider.nanoTime(Utils.java:219) at edu.emory.mathcs.backport.java.util.concurrent.helpers.Utils.nanoTime(Utils.java:99) at edu.emory.mathcs.backport.java.util.concurrent.ScheduledThreadPoolExecutor.now(ScheduledThreadPoolExecutor.java:88) at edu.emory.mathcs.backport.java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.getDelay(ScheduledThreadPoolExecutor.java:137) Exception in thread ActiveMQ Scheduler Exception in thread ActiveMQ Scheduler Exception in thread ActiveMQ Scheduler at edu.emory.mathcs.backport.java.util.concurrent.DelayQueue.take(DelayQueue.java:154) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:470) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:667) at java.lang.Thread.run(Thread.java:595) java.lang.NullPointerException at edu.emory.mathcs.backport.java.util.concurrent.helpers.Utils$SunPerfProvider.nanoTime(Utils.java:219) Exception in thread ActiveMQ Scheduler Exception in thread ActiveMQ Scheduler Exception in thread ActiveMQ Scheduler at edu.emory.mathcs.backport.java.util.concurrent.helpers.Utils.nanoTime(Utils.java:99) at edu.emory.mathcs.backport.java.util.concurrent.ScheduledThreadPoolExecutor.now(ScheduledThreadPoolExecutor.java:88) at edu.emory.mathcs.backport.java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.getDelay(ScheduledThreadPoolExecutor.java:137) at edu.emory.mathcs.backport.java.util.concurrent.DelayQueue.take(DelayQueue.java:154) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:470) Exception in thread ActiveMQ Scheduler Exception in thread ActiveMQ Scheduler at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:667) at java.lang.Thread.run(Thread.java:595) 2. The same exception is logged to the log file (in my case catalina.out) for hundreds of times, resulting a log file exceeding 150 MB in 2 minutes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-796) Client may shtudown when failover connection is reconnecting. We need to maintain at least 1 non-daemon thread alive.
[ https://issues.apache.org/activemq/browse/AMQ-796?page=all ] Hiram Chirino updated AMQ-796: -- Fix Version/s: 4.0.3 (was: 4.0.2) Client may shtudown when failover connection is reconnecting. We need to maintain at least 1 non-daemon thread alive. -- Key: AMQ-796 URL: https://issues.apache.org/activemq/browse/AMQ-796 Project: ActiveMQ Issue Type: Bug Affects Versions: 4.0 Reporter: Hiram Chirino Fix For: 4.1, 4.0.3 Dejan Reported on the User lists: Hi, after some experiments I found that this problem only exists if there are no other threads in the application. It seems like connection thread dies before it manages to reconnect. By starting another thread in the application, it succeeds to recover from master failure and reconnect to the slave broker. So I have a workaround for now, but it would be nice to make this work even for simple (single-threaded) clients. Regards, Dejan -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (AMQ-789) WireFormatNegotiator could hang a client or server connection if the peer disconnects before sending the wire format info
[ https://issues.apache.org/activemq/browse/AMQ-789?page=all ] Hiram Chirino resolved AMQ-789. --- Fix Version/s: 4.0.2 Resolution: Fixed commited in 4.0 branch in rev 423792 WireFormatNegotiator could hang a client or server connection if the peer disconnects before sending the wire format info - Key: AMQ-789 URL: https://issues.apache.org/activemq/browse/AMQ-789 Project: ActiveMQ Issue Type: Bug Affects Versions: 4.0 Reporter: Hiram Chirino Assigned To: Hiram Chirino Fix For: 4.0.2, 4.1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Reopened: (AMQ-789) WireFormatNegotiator could hang a client or server connection if the peer disconnects before sending the wire format info
[ https://issues.apache.org/activemq/browse/AMQ-789?page=all ] Hiram Chirino reopened AMQ-789: --- This should also be backported to 4.0 branch WireFormatNegotiator could hang a client or server connection if the peer disconnects before sending the wire format info - Key: AMQ-789 URL: https://issues.apache.org/activemq/browse/AMQ-789 Project: ActiveMQ Issue Type: Bug Affects Versions: 4.0 Reporter: Hiram Chirino Assigned To: Hiram Chirino Fix For: 4.1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (AMQ-701) Unix scripts in distro should have mode 755
[ https://issues.apache.org/activemq/browse/AMQ-701?page=all ] Hiram Chirino resolved AMQ-701: --- Resolution: Fixed Fixed.. commited in trunk rev 421654. The zip is now tunned for windows and the tar.* packages are tunned for unix. The zip file bin directory only contains .bat files and all text files use dos line endings. the tar file bin directory only contains the shell files and all text files use the unix line endings. Unix scripts in distro should have mode 755 --- Key: AMQ-701 URL: https://issues.apache.org/activemq/browse/AMQ-701 Project: ActiveMQ Type: Improvement Components: Broker Versions: 4.0 RC3, 4.0 RC2, 4.0 M4 Reporter: Jason Dillon Assignee: Hiram Chirino Fix For: 4.1 All of the unix scripts in the distro should have their mode set to 755, as in: cd bin/ chmod 755 activemq browse bstat list query shutdown Users should be able to unzip/untgz the distro and then run bin/activemq with out any extra steps. zipfileset supports a filemode attribute, and tarfileset suports a mode attribute that allow you to set the right mode on the archived files. See the release target here for a real example: http://svn.sourceforge.net/viewcvs.cgi/p4spam/p4spam/trunk/build.xml?view=markuprev=57 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (AMQ-806) Support a ?trace=true option on the http client side transport
[ https://issues.apache.org/activemq/browse/AMQ-806?page=all ] Hiram Chirino resolved AMQ-806: --- Resolution: Fixed implemented Support a ?trace=true option on the http client side transport -- Key: AMQ-806 URL: https://issues.apache.org/activemq/browse/AMQ-806 Project: ActiveMQ Type: New Feature Components: Transport Reporter: Hiram Chirino Assignee: Hiram Chirino Priority: Minor Fix For: 4.0.2, 4.1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (AMQ-807) JMS connections using the http:// protocol may not detect connections failures correctly.
[ https://issues.apache.org/activemq/browse/AMQ-807?page=all ] Hiram Chirino resolved AMQ-807: --- Resolution: Fixed fixed. JMS connections using the http:// protocol may not detect connections failures correctly. - Key: AMQ-807 URL: https://issues.apache.org/activemq/browse/AMQ-807 Project: ActiveMQ Type: Bug Reporter: Hiram Chirino Assignee: Hiram Chirino Fix For: 4.1, 4.0.2 If for example the broker is restarted, the broker will not inform a client using the broker again that it's connection state is gone. Also the client would startup a background poll thread before its' connection was established. This cause it to go into a busy loop hiting the server and the server sending back clientID not specified error messages until the ConnectionInfo was sent to the broker. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (AMQ-809) Make it easier to just enable the command trancing of the TransportLogger.
[ https://issues.apache.org/activemq/browse/AMQ-809?page=all ] Hiram Chirino resolved AMQ-809: --- Resolution: Fixed implemented. Make it easier to just enable the command trancing of the TransportLogger. -- Key: AMQ-809 URL: https://issues.apache.org/activemq/browse/AMQ-809 Project: ActiveMQ Type: Improvement Versions: 4.0 Reporter: Hiram Chirino Assignee: Hiram Chirino Fix For: 4.1, 4.0.2 The log4j category for trace logging of message currently org.apache.activemq.transport.TransportLogger:n this makes it hard to enable the debug logging of just the trace messages since org.apache.activemq.transport is too broad of a category and TransportLogger:n is a variable category name. We should make it org.apache.activemq.transport.TransportLogger.Connection:n so that it's easier to just enable the logging for this one component. Also log usage of the other request methods. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (AMQ-810) When using Topics with consumers with selectors over a network of brokers, only the first consumer gets messages delivered.
When using Topics with consumers with selectors over a network of brokers, only the first consumer gets messages delivered. --- Key: AMQ-810 URL: https://issues.apache.org/activemq/browse/AMQ-810 Project: ActiveMQ Type: Bug Versions: 4.0 Reporter: Hiram Chirino Assigned to: Hiram Chirino Fix For: 4.1, 4.0.2 The subscription conduit is blocking out subsequent subscriptions from being propagated over the network bridge -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (AMQ-803) The static discovery agent should include reconnect logic when it is notified that one of it's sevices failed.
[ https://issues.apache.org/activemq/browse/AMQ-803?page=all ] Hiram Chirino resolved AMQ-803: --- Resolution: Fixed implemented. The static discovery agent should include reconnect logic when it is notified that one of it's sevices failed. -- Key: AMQ-803 URL: https://issues.apache.org/activemq/browse/AMQ-803 Project: ActiveMQ Type: New Feature Reporter: Hiram Chirino Assignee: Hiram Chirino Fix For: 4.1, 4.0.2 This could substancially make the network connector code simpler since it does not need to deal with failover connections which cause problems for the connector. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (AMQ-805) Restart network bridges if they ever get stopped
[ https://issues.apache.org/activemq/browse/AMQ-805?page=all ] Hiram Chirino resolved AMQ-805: --- Resolution: Fixed Fixed. Restart network bridges if they ever get stopped Key: AMQ-805 URL: https://issues.apache.org/activemq/browse/AMQ-805 Project: ActiveMQ Type: Improvement Reporter: Hiram Chirino Assignee: Hiram Chirino Right now it seems like we only trap remote exceptions and then restart the bridge. I think we should restart the network bridge if the bridge fails for any reason. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (AMQ-802) Broker Network connections over SSH tunnels do not get established.
[ https://issues.apache.org/activemq/browse/AMQ-802?page=all ] Hiram Chirino resolved AMQ-802: --- Resolution: Fixed Fixed.. failover should not be used with static: connections anymore. Broker Network connections over SSH tunnels do not get established. --- Key: AMQ-802 URL: https://issues.apache.org/activemq/browse/AMQ-802 Project: ActiveMQ Type: Bug Components: Broker Versions: 4.0 Reporter: Hiram Chirino Assignee: Hiram Chirino Fix For: 4.1, 4.0.2 Due to the way that ssh tunnels accept a connection but then close a socket if they cannot establish a connection to the remote host, the network connector fails to re-connect to the remote host when it is started. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (AMQ-793) problem with auto-ack and messages being redelivered in Stomp clients
[ https://issues.apache.org/activemq/browse/AMQ-793?page=all ] Hiram Chirino resolved AMQ-793: --- Resolution: Fixed new stomp client which fixes this has been backported to 4.0 also. problem with auto-ack and messages being redelivered in Stomp clients - Key: AMQ-793 URL: https://issues.apache.org/activemq/browse/AMQ-793 Project: ActiveMQ Type: Bug Versions: 4.0.1 Reporter: james strachan Assignee: Hiram Chirino Fix For: 4.0.2, 4.1 For discussion see http://www.nabble.com/Stomp-and-ActiveMessaging-does-not-remove-messages-from-Queue-tf1889402.html#a5165844 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-787) The UdpTransport could potentialy fail to bind on linux.. caused the UdpTransportTest to fail sometimes.
[ https://issues.apache.org/activemq/browse/AMQ-787?page=all ] Hiram Chirino updated AMQ-787: -- Fix Version: 4.0.2 The UdpTransport could potentialy fail to bind on linux.. caused the UdpTransportTest to fail sometimes. Key: AMQ-787 URL: https://issues.apache.org/activemq/browse/AMQ-787 Project: ActiveMQ Type: Bug Versions: 4.0 Reporter: Hiram Chirino Assignee: Hiram Chirino Fix For: 4.1, 4.0.2 [junit] [ERROR] Test org.apache.activemq.transport.udp.UdpTransportTest FAILED -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (AMQ-787) The UdpTransport could potentialy fail to bind on linux.. caused the UdpTransportTest to fail sometimes.
[ https://issues.apache.org/activemq/browse/AMQ-787?page=comments#action_36523 ] Hiram Chirino commented on AMQ-787: --- Fix also applied to 4.0 branch rev 419025. The UdpTransport could potentialy fail to bind on linux.. caused the UdpTransportTest to fail sometimes. Key: AMQ-787 URL: https://issues.apache.org/activemq/browse/AMQ-787 Project: ActiveMQ Type: Bug Versions: 4.0 Reporter: Hiram Chirino Assignee: Hiram Chirino Fix For: 4.1, 4.0.2 [junit] [ERROR] Test org.apache.activemq.transport.udp.UdpTransportTest FAILED -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (AMQ-688) Avoid blocking producers
[ https://issues.apache.org/activemq/browse/AMQ-688?page=comments#action_36508 ] Hiram Chirino commented on AMQ-688: --- I think that the changes required to fix this are both in the research stange and substancial enought that we should create a new activemq branch where we explore solutions for this. How about we create a temporary development branch under /branches/tmp/AMQ-688 ??? Avoid blocking producers Key: AMQ-688 URL: https://issues.apache.org/activemq/browse/AMQ-688 Project: ActiveMQ Type: New Feature Components: Broker Versions: 4.0 RC2 Reporter: Christopher A. Larrieu Assignee: Christopher A. Larrieu Fix For: 4.1 Original Estimate: 8 weeks Remaining: 8 weeks Our main goal is to avoid stalled producers by addressing the main culprit: too many undispatched messages in the broker's memory. Our motivation is to handle significant --though temporary-- imbalances between production and consumption rates. Reaching this goal entails specific broker modifications: 1. When memory gets tight, start dropping undispatched non-persistent messages. This is the first-cut attempt to maintain throughput of persistent messages. Unlike the approach documented at http://docs.codehaus.org/display/ACTIVEMQ/Slow+Consumer+Handling, the message dropping will only occur after the UsageManager reaches capacity. Non-persistent messages in dispatch lists will be dropped according to per-destination policy. Subscriptions can purge their own messages triggered via callback from the UsageManager. 2. Evict messages if memory remains tight, to be fetched from backing store prior to dispatch. ActiveMQ already supports this for persistent messages on Topics with durable subscriptions. If a consumer's prefetch buffer is full, the splash-over messages remain as IndirectMessageReference objects in the dispatch list, with the actual message body loaded from store on demand. I believe we can extend this approach for Queues as well. 3. Improve the efficiency with which evicted messages are loaded back into memory. Currently, they are loaded one at a time as needed. It would make sense to batch-load message sets periodically. This will require a significant shift in responsibilities between objects, since an IndirectMessageReference doesn't know about other instances that can be loaded in mass. The goal will be to keep each subscription dispatch list stocked with a decent number of messages in-memory to reasonably trade-off between it's consumer's performance and resource usage in the broker. As with everything else, we can implement this as a strategy class with the first cut implementing a simple resource allocation strategy: divvy up available memory amongst all subscriptions and keep that memory filled with messages for dispatch. I envision a worker task assuming responsibility for keeping these lists filled. 4. Even with the above modifications, we still can't entirely avoid blocked producers, so we'd like to add client-configurable time-outs to provide a bound for the time a producer can remain stalled. Maybe this should be a new attribute of ActiveMQConnection: maxProducerFlowControlWait. Calls to UsageManager.waitForSpace can take this quantity as an argument. Failure to reach sufficient space for the new message will throw an exception back up the stack and across the wire, letting the producer know that the message was not delivered. 5. Finally, we need to extend disk support for Topics that have only non-durable subscribers, otherwise their dispatch lists can fill up with persistent messages. In order to maintain compliance with JMS, it would be nice to provide some alternative to dropping persistent messages. One possible first cut is to layer this on top of a DurableTopicSubscription by creating an anonymous subscriber for every Topic that has only non-durable subscriptions. When all such subscriptions terminate, the broker can remove the anonymous subscriber. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (AMQ-340) allow topics in particular but also queues to have a 'namespace URI' like WS-Notification
[ https://issues.apache.org/activemq/browse/AMQ-340?page=all ] Hiram Chirino reassigned AMQ-340: - Assign To: james strachan This sounds like WSN root then maps to a broker instance. Since a JVM can run more than 1 broker, the WSN layer just needs to route requests to different brokers based on the root. What do you think? allow topics in particular but also queues to have a 'namespace URI' like WS-Notification - Key: AMQ-340 URL: https://issues.apache.org/activemq/browse/AMQ-340 Project: ActiveMQ Type: New Feature Reporter: james strachan Assignee: james strachan Fix For: 4.1 This would allow a real clean mapping from WS-N topics and ActiveMQ at the protocol level. We could use the namespace as a level of indirection to map to a broker, a cluster of brokers or even a particular area of a network etc. The namespace could be a broker's name too. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (AMQ-724) Stomp client is not removed from the broker on client disconnect
[ https://issues.apache.org/activemq/browse/AMQ-724?page=comments#action_36495 ] Hiram Chirino commented on AMQ-724: --- Expanded your 'hack' so that it's less hacky. The connection and session state now keep track if they are being shutdown. Fix committed to trunk revision 418592. Stomp client is not removed from the broker on client disconnect Key: AMQ-724 URL: https://issues.apache.org/activemq/browse/AMQ-724 Project: ActiveMQ Type: Bug Components: Transport Versions: 4.0 Environment: Linux, Java 1.5.0_06 Reporter: Danielius Jurna Assignee: james strachan Attachments: StompSubscriptionRemoveTest.java If Stomp client crashes (or disconnects unexpectedly) when there are unconsumed messages in the broker, the subscriptions are not removed from the broker and some phantom consumer is still consuming messages. If you connect other client, it receives only half messages (other half messages goes to that phantom consumer still left afrter client disconnect). There are no error logs in activemq logs. We are using stomp client, whith client acknowledge mode, so on broker restart, all messages are delivered properly. You can also see in jmx console, that subscription still exists whithout any connection left. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (AMQ-517) Create a C++ client for ActiveMQ that can work with STOMP and OpenWire
[ https://issues.apache.org/activemq/browse/AMQ-517?page=all ] Hiram Chirino reassigned AMQ-517: - Assign To: Nathan Mittler (was: Hiram Chirino) Nathan, can we resolve this issue now? Create a C++ client for ActiveMQ that can work with STOMP and OpenWire -- Key: AMQ-517 URL: https://issues.apache.org/activemq/browse/AMQ-517 Project: ActiveMQ Type: Improvement Components: JMS client Reporter: Nathan Mittler Assignee: Nathan Mittler Priority: Minor Attachments: cms.tar.gz, cms_v2.tar.gz, cms_v3.tar.gz I've created this issue to post my code. Attached is my first cut at CMS (C++ Message Service) with a Stomp client. The idea is that CMS is the API (like JMS) and any messaging protocol can be used behind it (Stomp, OpenWire, etc). The docs folder contains the doxygen html for the source as well as a pdf document that gives a high-level overview. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (AMQ-768) Client and Broker hang trying to start a connection
[ https://issues.apache.org/activemq/browse/AMQ-768?page=all ] Hiram Chirino resolved AMQ-768: --- Fix Version: (was: 4.0.2) Resolution: Fixed Client and Broker hang trying to start a connection --- Key: AMQ-768 URL: https://issues.apache.org/activemq/browse/AMQ-768 Project: ActiveMQ Type: Bug Versions: 4.0 Environment: JDK 1.5.0_06, Windows XP SP2 Reporter: Jamie McCrindle Assignee: Hiram Chirino Fix For: 4.1 Every now and again a client hangs connecting to the broker. The broker is configured with the default activemq.xml. The stack dumps are as follows: ACTIVEMQ_HOME: C:\Java\incubator-activemq-4.0\bin\.. Loading message broker from: xbean:activemq.xml INFO BrokerService - ActiveMQ 4.0 JMS Message Broker (localhos t) is starting INFO BrokerService - For help or more information please see: http://incubator.apache.org/activemq/ INFO ManagementContext - JMX consoles can connect to service:jmx:r mi:///jndi/rmi://localhost:1099/jmxrmi INFO JDBCPersistenceAdapter - Database driver recognized: [apache_derby _embedded_jdbc_driver] INFO JournalPersistenceAdapter - Journal Recovery Started from: Active Jou rnal: using 5 x 20.0 Megs at: C:\Java\incubator-activemq-4.0\activemq-data\journ al INFO JournalPersistenceAdapter - Journal Recovered: 1 message(s) in transa ctions recovered. INFO TransportServerThreadSupport - Listening for connections at: tcp://SIM-J amesM:61616 WARN MulticastDiscoveryAgent- brokerName not set INFO TransportConnector - Connector default Started INFO TransportServerThreadSupport - Listening for connections at: tcp://SIM-J amesM:61613?wireFormat=stomp INFO TransportConnector - Connector stomp Started INFO NetworkConnector - Network Connector default Started INFO BrokerService - ActiveMQ JMS Message Broker (localhost, I D:SIM-JamesM-2205-1149180591980-1:0) started WARN ManagedTransportConnection - Failed to unregister mbean: org.apache.ac tivemq:BrokerName=localhost,Type=Connection,ConnectorName=default,Connection=9 the stack dump is: main prio=6 tid=0x000379d0 nid=0x93d0 in Object.wait() [0x0007e000..0x0007fc40 ] at java.lang.Object.wait(Native Method) - waiting on 0x02b66278 (a edu.emory.mathcs.backport.java.util.concurr ent.CountDownLatch) at java.lang.Object.wait(Object.java:474) at edu.emory.mathcs.backport.java.util.concurrent.CountDownLatch.await(C ountDownLatch.java:179) - locked 0x02b66278 (a edu.emory.mathcs.backport.java.util.concurrent. CountDownLatch) at org.apache.activemq.transport.WireFormatNegotiator.oneway(WireFormatN egotiator.java:73) at org.apache.activemq.transport.MutexTransport.oneway(MutexTransport.ja va:44) - locked 0x02b64098 (a java.lang.Object) at org.apache.activemq.transport.ResponseCorrelator.asyncRequest(Respons eCorrelator.java:68) at org.apache.activemq.transport.ResponseCorrelator.request(ResponseCorr elator.java:73) at org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnect ion.java:1131) at org.apache.activemq.ActiveMQConnection.ensureConnectionInfoSent(Activ eMQConnection.java:1219) - locked 0x02b602c0 (a org.apache.activemq.ActiveMQConnection) at org.apache.activemq.ActiveMQConnection.start(ActiveMQConnection.java: 435) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (AMQ-725) Messages Sent by JMS that contain header properties cause error when STOMP client registers a Subscriber
[ https://issues.apache.org/activemq/browse/AMQ-725?page=all ] Hiram Chirino resolved AMQ-725: --- Fix Version: (was: 4.0.2) Resolution: Fixed I just tested against 4.1-SNAPSHOT and this is working. Messages Sent by JMS that contain header properties cause error when STOMP client registers a Subscriber Key: AMQ-725 URL: https://issues.apache.org/activemq/browse/AMQ-725 Project: ActiveMQ Type: Bug Components: Transport Versions: 4.0 Environment: Running on WinXP with Sun JDK1.5.0_06 Reporter: William MacDonald Assignee: Hiram Chirino Priority: Blocker Fix For: 4.1 I am using the lastest 4.0 release build of ActiveMQ and I have been trying to produce messages in a JMS client and receive the messages in a STOMP client. What I have found is that if the JMS Client adds header properties to the message to be delivered to ActiveMQ then when I subscribe with the STOMP client I am receiving the Error listed below. If I remove all header properties then the message is transmitted correctly. I have also found that if I send messages with a STOMP client that has header properties then everything works correctly. java.lang.NullPointerException at java.util.Hashtable.put(Unknown Source) at java.util.Hashtable.putAll(Unknown Source) at org.apache.activemq.transport.stomp.FrameBuilder.addHeaders(FrameBuilder.java:65) at org.apache.activemq.transport.stomp.Subscription.receive(Subscription.java:76) at org.apache.activemq.transport.stomp.StompWireFormat.writeCommand(StompWireFormat.java:154) at org.apache.activemq.transport.stomp.StompWireFormat.marshal(StompWireFormat.java:305) at org.apache.activemq.transport.tcp.TcpTransport.oneway(TcpTransport.java:124) at org.apache.activemq.transport.InactivityMonitor.oneway(InactivityMonitor.java:141) at org.apache.activemq.transport.MutexTransport.oneway(MutexTransport.java:44) at org.apache.activemq.transport.ResponseCorrelator.oneway(ResponseCorrelator.java:60) at org.apache.activemq.broker.TransportConnection.dispatch(TransportConnection.java:211) at org.apache.activemq.broker.AbstractConnection.processDispatch(AbstractConnection.java:581) at org.apache.activemq.broker.AbstractConnection.iterate(AbstractConnection.java:597) at org.apache.activemq.thread.DedicatedTaskRunner.runTask(DedicatedTaskRunner.java:87) at org.apache.activemq.thread.DedicatedTaskRunner.access$000(DedicatedTaskRunner.java:24) at org.apache.activemq.thread.DedicatedTaskRunner$1.run(DedicatedTaskRunner.java:38) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (AMQ-406) enable the configuration of prefetch policies in the JNDI configuration file by allowing the prefetch values to be visible as properties on ActiveMQConnectionFactory
[ https://issues.apache.org/activemq/browse/AMQ-406?page=comments#action_36488 ] Hiram Chirino commented on AMQ-406: --- Fixed in trunk rev 418495. You can now configure the prefetchPolicy and redeliveryPolicy using the jndi properties. For example: properties.put(Context.INITIAL_CONTEXT_FACTORY, org.apache.activemq.jndi.ActiveMQInitialContextFactory); properties.put(Context.PROVIDER_URL, tcp://localhost:65432); properties.put(prefetchPolicy.queuePrefetch, 777); properties.put(redeliveryPolicy.maximumRedeliveries, 15); properties.put(redeliveryPolicy.backOffMultiplier, 32); InitialContext context = new InitialContext(properties); You can also do it using the Broker URL: new ActiveMQConnectionFactory(tcp://localhost:61616?jms.redeliveryPolicy.maximumRedeliveries=15); enable the configuration of prefetch policies in the JNDI configuration file by allowing the prefetch values to be visible as properties on ActiveMQConnectionFactory - Key: AMQ-406 URL: https://issues.apache.org/activemq/browse/AMQ-406 Project: ActiveMQ Type: Improvement Reporter: james strachan Fix For: 4.1 if we delegate all the properties on PrefetchPolicy as basisc properties on ActiveMQConnectionFactory we can configue the values in JNDI. e.g. in jndi.properties ConnectionFactory.queuePrefetch = 100 which would call ActiveMQConnectionFactory.setQueuePrefetch(100) = prefetchPolicy.setQueuePrefetch(100) etc -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-450) expired messages should be sent to some kind of dead letter queue
[ https://issues.apache.org/activemq/browse/AMQ-450?page=all ] Hiram Chirino updated AMQ-450: -- Fix Version: 4.2 (was: 4.1) Description: This could take a little bit of work reorganizing how the broker and the persistence store opperate. Targeting for 4.2 expired messages should be sent to some kind of dead letter queue - Key: AMQ-450 URL: https://issues.apache.org/activemq/browse/AMQ-450 Project: ActiveMQ Type: Improvement Components: Broker Versions: 4.0 Reporter: james strachan Assignee: Hiram Chirino Fix For: 4.2 This could take a little bit of work reorganizing how the broker and the persistence store opperate. Targeting for 4.2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-451) allow scheduled delivery of messages
[ https://issues.apache.org/activemq/browse/AMQ-451?page=all ] Hiram Chirino updated AMQ-451: -- Fix Version: 4.2 (was: 4.1) scheduling delivery of messages is very similar to expiring messages on a given date. Lets thing about how to do this for the 4.2 release. allow scheduled delivery of messages Key: AMQ-451 URL: https://issues.apache.org/activemq/browse/AMQ-451 Project: ActiveMQ Type: New Feature Reporter: james strachan Fix For: 4.2 rather than be dispatched immediately it would be good to support a custom header to indicate the delivery some time in the future. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (AMQ-789) WireFormatNegotiator could hang a client or server connection if the peer disconnects before sending the wire format info
WireFormatNegotiator could hang a client or server connection if the peer disconnects before sending the wire format info - Key: AMQ-789 URL: https://issues.apache.org/activemq/browse/AMQ-789 Project: ActiveMQ Type: Bug Versions: 4.0 Reporter: Hiram Chirino Assigned to: Hiram Chirino Fix For: 4.1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-608) Change logging level of some DemandForwardingBridge log messages.
[ https://issues.apache.org/activemq/browse/AMQ-608?page=all ] Hiram Chirino updated AMQ-608: -- Fix Version: 4.0.2 (was: 4.0.1) Change logging level of some DemandForwardingBridge log messages. - Key: AMQ-608 URL: https://issues.apache.org/activemq/browse/AMQ-608 Project: ActiveMQ Type: Improvement Components: Broker Versions: 4.0 Reporter: Kevin Yaussy Assignee: Hiram Chirino Fix For: 4.1, 4.0.2 Attachments: DemandForwardingBridge.java, DemandForwardingBridgeSupport.java, DemandForwardingBridgeSupport.patch, FailoverTransport.java, FailoverTransport.java, FailoverTransport.patch, InactivityMonitor.patch, InactivityMonitor.patch2 In DemandForwardingBridge, I'd like to be able to see subscription messages (and unsubscription messages), but not bridging messages. Both classes of log messages are log.trace. Seems like the bridging messages should remain trace, as you would want to look at that when you are doing pretty detailed debugging. However, I'd like to see subscribe/unsubscribe messages all the time. If those could be either info or debug, that would allow me to turn those on separately. I realize that I can see what is currently subscribed via the JMX console. However, seeing the subscribe/unsubscribe messages will allow diagnostics over time - who subscribed when type of questions. Mainly, I'm referring to messages logged as trace in: DemandForwardingBridge.serviceRemoteConsumerAdvisory DemandForwardingBridge.removeDemandSubscription -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-528) 4.0 M4 NullPointerException while shutting down
[ https://issues.apache.org/activemq/browse/AMQ-528?page=all ] Hiram Chirino updated AMQ-528: -- Fix Version: 4.0.2 4.1 (was: 4.0 RC2) Version: 4.0 (was: 4.0 M4) Ajusted target fix version so that it shows up on the roadmap right. 4.0 M4 NullPointerException while shutting down --- Key: AMQ-528 URL: https://issues.apache.org/activemq/browse/AMQ-528 Project: ActiveMQ Type: Bug Versions: 4.0 Environment: RedHat Linux Enterprise Server 3, Tomcat 5.5.15, MySQL 5.0.18 for Linux Reporter: Leon Hu Priority: Critical Fix For: 4.1, 4.0.2 Setup: 3 networked brokers, B1, B2, and B3, on 3 servers, connected using multicast discovery. activemq.xml: broker useJmx=false brokerName=B1 persistenceAdapter journaledJDBC journalLogFiles=5 dataDirectory=foo dataSource=#mysql-ds/ /persistenceAdapter transportConnectors transportConnector uri=tcp://localhost:61616 discoveryUri=multicast://default/ /transportConnectors networkConnectors networkConnector uri=multicast://default/ /networkConnectors /broker bean id=mysql-ds class=org.apache.commons.dbcp.BasicDataSource destroy-method=close property name=driverClassName value=com.mysql.jdbc.Driver/ property name=url value=jdbc:mysql://localhost/activemq?relaxAutoCommit=true/ property name=username value=activemqUser/ property name=password value=activemqPwd/ property name=poolPreparedStatements value=true/ /bean Similar for B2 and B3. Two queues: Q1 and Q2. Two producers, one for each queue, both producers connected to B1. One Q1 cosumer connected to B1, another Q1 consumer on B2. One Q2 consumer connected to B2, another Q2 consumer connected to B3. Steps: Start the brokers and start sending messages to the queue. After a while, stop the brokers (Sequence does not matter) See the errors in catalina.out of the Tomcat that has a broker with both producers and consumers connected The problems: 1. Exception in thread ActiveMQ Scheduler java.lang.NullPointerException at edu.emory.mathcs.backport.java.util.concurrent.helpers.Utils$SunPerfProvider.nanoTime(Utils.java:219) at edu.emory.mathcs.backport.java.util.concurrent.helpers.Utils.nanoTime(Utils.java:99) at edu.emory.mathcs.backport.java.util.concurrent.ScheduledThreadPoolExecutor.now(ScheduledThreadPoolExecutor.java:88) at edu.emory.mathcs.backport.java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.getDelay(ScheduledThreadPoolExecutor.java:137) Exception in thread ActiveMQ Scheduler Exception in thread ActiveMQ Scheduler Exception in thread ActiveMQ Scheduler at edu.emory.mathcs.backport.java.util.concurrent.DelayQueue.take(DelayQueue.java:154) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:470) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:667) at java.lang.Thread.run(Thread.java:595) java.lang.NullPointerException at edu.emory.mathcs.backport.java.util.concurrent.helpers.Utils$SunPerfProvider.nanoTime(Utils.java:219) Exception in thread ActiveMQ Scheduler Exception in thread ActiveMQ Scheduler Exception in thread ActiveMQ Scheduler at edu.emory.mathcs.backport.java.util.concurrent.helpers.Utils.nanoTime(Utils.java:99) at edu.emory.mathcs.backport.java.util.concurrent.ScheduledThreadPoolExecutor.now(ScheduledThreadPoolExecutor.java:88) at edu.emory.mathcs.backport.java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.getDelay(ScheduledThreadPoolExecutor.java:137) at edu.emory.mathcs.backport.java.util.concurrent.DelayQueue.take(DelayQueue.java:154) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:470) Exception in thread ActiveMQ Scheduler Exception in thread ActiveMQ Scheduler at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:667) at java.lang.Thread.run(Thread.java:595) 2. The same exception is logged to the log file (in my case catalina.out) for hundreds of times, resulting a log file exceeding 150 MB in 2 minutes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (AMQ-782) Support specifiying destinationOptions on the Ajax Sevlet
Support specifiying destinationOptions on the Ajax Sevlet - Key: AMQ-782 URL: https://issues.apache.org/activemq/browse/AMQ-782 Project: ActiveMQ Type: Improvement Reporter: Hiram Chirino Assigned to: Hiram Chirino Fix For: 4.1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (AMQ-782) Support specifiying destinationOptions on the Ajax Sevlet
[ https://issues.apache.org/activemq/browse/AMQ-782?page=all ] Hiram Chirino resolved AMQ-782: --- Resolution: Fixed Support a destinationOptions servlet parameter that configures the destination options used on a destination Commited in r 418311 on trunk Support specifiying destinationOptions on the Ajax Sevlet - Key: AMQ-782 URL: https://issues.apache.org/activemq/browse/AMQ-782 Project: ActiveMQ Type: Improvement Reporter: Hiram Chirino Assignee: Hiram Chirino Fix For: 4.1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
