[jira] [Commented] (AMQ-4996) org.apache.activemq.transport.RequestTimedOutIOException thrown by producer.send() for no obvious reason. Message is actually sent.
[ https://issues.apache.org/jira/browse/AMQ-4996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13890470#comment-13890470 ] Jonathan Graham commented on AMQ-4996: -- During the 5 seconds between the start of the send and the receipt of the timeout, the broker log is showing me that background things are happening. For example, I got a timeout at 05:08:48 (send started at 05:05:43) and the log looks like this: 28/01/2014 05:08:42,536 (Thread-38) DEBUG : Stopping transport tcp://localhost.localdomain/127.0.0.1:2348 28/01/2014 05:08:42,536 (ActiveMQ Task-15799) DEBUG : Stopping connection: /127.0.0.1:35791 28/01/2014 05:08:42,537 (ActiveMQ Task-15799) DEBUG : Stopping transport tcp:///127.0.0.1:35791 28/01/2014 05:08:42,538 (ActiveMQ Task-15799) DEBUG : Stopped transport: /127.0.0.1:35791 28/01/2014 05:08:42,539 (ActiveMQ Task-15799) DEBUG : Connection Stopped: /127.0.0.1:35791 28/01/2014 05:08:45,464 (InactivityMonitor WriteCheck) DEBUG : org.apache.activemq.transport.InactivityMonitor$2@46fff62d ms elapsed since last write check. 28/01/2014 05:08:45,653 (InactivityMonitor WriteCheck) DEBUG : org.apache.activemq.transport.InactivityMonitor$2@3f65bc68 10001 ms elapsed since last write check. 28/01/2014 05:08:45,753 (InactivityMonitor WriteCheck) DEBUG : org.apache.activemq.transport.InactivityMonitor$2@48ba57c4 10001 ms elapsed since last write check. 28/01/2014 05:08:45,905 (InactivityMonitor WriteCheck) DEBUG : org.apache.activemq.transport.InactivityMonitor$2@c28a9ee 10001 ms elapsed since last write check. 28/01/2014 05:08:45,982 (ActiveMQ Journal Checkpoint Worker) DEBUG : Checkpoint started. 28/01/2014 05:08:47,105 (InactivityMonitor ReadCheck) DEBUG : 2 ms elapsed since last read check. 28/01/2014 05:08:47,106 (InactivityMonitor WriteCheck) DEBUG : org.apache.activemq.transport.InactivityMonitor$2@4c28b3c3 10001 ms elapsed since last write check. 28/01/2014 05:08:47,295 (InactivityMonitor WriteCheck) DEBUG : org.apache.activemq.transport.InactivityMonitor$2@41383426 1 ms elapsed since last write check. 28/01/2014 05:08:47,295 (InactivityMonitor ReadCheck) DEBUG : 2 ms elapsed since last read check. 28/01/2014 05:08:49,563 (InactivityMonitor ReadCheck) DEBUG : 3 ms elapsed since last read check. 28/01/2014 05:08:49,563 (InactivityMonitor WriteCheck) DEBUG : org.apache.activemq.transport.InactivityMonitor$2@6f18ba62 1 ms elapsed since last write check. 28/01/2014 05:08:49,638 (InactivityMonitor ReadCheck) DEBUG : 2 ms elapsed since last read check. 28/01/2014 05:08:49,638 (InactivityMonitor WriteCheck) DEBUG : org.apache.activemq.transport.InactivityMonitor$2@2d1624be 10001 ms elapsed since last write check. 28/01/2014 05:08:50,665 (InactivityMonitor WriteCheck) DEBUG : org.apache.activemq.transport.InactivityMonitor$2@751e1ab5 10002 ms elapsed since last write check. 28/01/2014 05:08:50,862 (InactivityMonitor WriteCheck) DEBUG : org.apache.activemq.transport.InactivityMonitor$2@60d96f5b 1 ms elapsed since last write check. 28/01/2014 05:08:51,171 (InactivityMonitor WriteCheck) DEBUG : org.apache.activemq.transport.InactivityMonitor$2@6bf450a5 10001 ms elapsed since last write check. 28/01/2014 05:08:51,268 (ActiveMQ Journal Checkpoint Worker) DEBUG : Checkpoint done. 28/01/2014 05:08:51,771 (ActiveMQ Journal Checkpoint Worker) DEBUG : Checkpoint started. 28/01/2014 05:08:51,798 (ActiveMQ Journal Checkpoint Worker) DEBUG : Checkpoint done. Any insight would be helpful! Thanks > org.apache.activemq.transport.RequestTimedOutIOException thrown by > producer.send() for no obvious reason. Message is actually sent. > --- > > Key: AMQ-4996 > URL: https://issues.apache.org/jira/browse/AMQ-4996 > Project: ActiveMQ > Issue Type: Bug > Components: Broker, JMS client >Affects Versions: 5.5.1 > Environment: Redhat Linux >Reporter: Jonathan Graham > > In production we are getting > org.apache.activemq.transport.RequestTimedOutIOException exceptions thrown > sometimes when we execute the send command. The timeout is set to 5 seconds > and it blocks for 5 seconds and then throws the exception. The message is > actually sent to the broker successfully (I don't know if it's sent > immediately or if there was a delay before it gets there). > We are communicating with the broker via TCP but it is on the localhost. > This happens 'every so often' with no explanation that I can find. No errors > appear in the broker logs (and no clues when configured to DEBUG level). The > volume is very low; a message every 20-30 seconds or so, and they are > immediately handled by a consumer - the broker has not run out of storage or > memory. > It seems to happen
Re: ActiveMQ Console - let's get the problem defined
By the way, on the topic of using an external console to replace the current built-in console, there's very real concern with circular dependency. If the external console contains ActiveMQ-specific parts, such as listing Queues and Topics and giving operations on the same, then changes to ActiveMQ internals could necessitate changes to the external console. And visa versa. This would make releases of both difficult any time a change was made to either. Circular dependencies in software are a very bad thing. I've added a line in this regard on the "PROBLEM STATEMENT" doc. To try to make my position more clear: BAD external console code requests list of queues from broker GOOD external console code requests list of all entity types from broker user chooses Queue from the same list external console code requests list of all entities of type Queue (as chosen by the user) -- View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-Console-let-s-get-the-problem-defined-tp4677105p4677371.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
[jira] [Commented] (AMQ-5017) ActiveMQPrefetchPolicy.setAll sets inputStreamPrefetch incorrectly
[ https://issues.apache.org/jira/browse/AMQ-5017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13890316#comment-13890316 ] james commented on AMQ-5017: Also i just noticed that setAll() does not use "getMaxPrefetch()" to limit the new value. dunno if this should be filed as a separate bug. > ActiveMQPrefetchPolicy.setAll sets inputStreamPrefetch incorrectly > -- > > Key: AMQ-5017 > URL: https://issues.apache.org/jira/browse/AMQ-5017 > Project: ActiveMQ > Issue Type: Bug >Affects Versions: 5.9.0 >Reporter: james >Priority: Minor > > ActiveMQPrefetchPolicy.setAll() sets "this.inputStreamPrefetch" to "1", which > i assume is supposed to be "i". -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (AMQ-5017) ActiveMQPrefetchPolicy.setAll sets inputStreamPrefetch incorrectly
james created AMQ-5017: -- Summary: ActiveMQPrefetchPolicy.setAll sets inputStreamPrefetch incorrectly Key: AMQ-5017 URL: https://issues.apache.org/jira/browse/AMQ-5017 Project: ActiveMQ Issue Type: Bug Affects Versions: 5.9.0 Reporter: james Priority: Minor ActiveMQPrefetchPolicy.setAll() sets "this.inputStreamPrefetch" to "1", which i assume is supposed to be "i". -- This message was sent by Atlassian JIRA (v6.1.5#6160)
activemq pull request: Remove sitemesh/activemq-all
Github user dkulp closed the pull request at: https://github.com/apache/activemq/pull/12
Re: ActiveMQ Console - let's get the problem defined
Perhaps the "turd" part was the greater offense being raised. Clarification? :) On Monday, February 3, 2014, artnaseef wrote: > Crossed off the 22mb concern (strike-through in case anyone wants to make a > strong case for the concern, or take action to address it). > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/ActiveMQ-Console-let-s-get-the-problem-defined-tp4677105p4677355.html > Sent from the ActiveMQ - Dev mailing list archive at Nabble.com. >
Re: ActiveMQ Console - let's get the problem defined
Crossed off the 22mb concern (strike-through in case anyone wants to make a strong case for the concern, or take action to address it). -- View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-Console-let-s-get-the-problem-defined-tp4677105p4677355.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
Re: ActiveMQ Console - let's get the problem defined
What about the amount of effort to maintain the console? Are there any details or, optimally, metrics related to this (such as hours spent fixing bugs)? -- View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-Console-let-s-get-the-problem-defined-tp4677105p4677354.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
[jira] [Commented] (AMQNET-454) Add Apache Qpid provider to NMS
[ https://issues.apache.org/jira/browse/AMQNET-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13889971#comment-13889971 ] Timothy Bish commented on AMQNET-454: - Patch applied. > Add Apache Qpid provider to NMS > --- > > Key: AMQNET-454 > URL: https://issues.apache.org/jira/browse/AMQNET-454 > Project: ActiveMQ .Net > Issue Type: New Feature > Components: NMS >Affects Versions: 1.6.0 >Reporter: Chuck Rolke >Assignee: Jim Gomes > Attachments: Apache.NMS.AMQP-add-hello-world-example-11.patch, > Apache.NMS.AMQP-add-hello-world-example-retry-12.patch, > Apache.NMS.AMQP-add-message-conversions-06.patch, > Apache.NMS.AMQP-add-topic-05.patch, > Apache.NMS.AMQP-connectionProperties-07.patch, > Apache.NMS.AMQP-copyrights-conn-str-fix-09.patch, > Apache.NMS.AMQP-fix-destination-to-use-qpid-address-10.patch, > Apache.NMS.AMQP-fix-helloworld-13.patch, > Apache.NMS.AMQP-fix-list-message-body-15.patch, > Apache.NMS.AMQP-fix-map-message-body-14.patch, > Apache.NMS.AMQP-fix-replyTo-and-receive-timeouts-16.patch, > Apache.NMS.AMQP-object-lifecycle-04.patch, > Apache.NMS.AMQP-provider-configs-03.patch, > Apache.NMS.AMQP-qpid-object-lifecycle-02.patch, > Apache.NMS.AMQP-set-connection-credentials-08.patch, vendor-QPid-nant-01.patch > > > NMS includes various providers ActiveMQ, STOMP, MSMQ, EMS, and WCF. This > issue proposes to add [Apache Qpid|http://qpid.apache.org/index.html] as > another provider. > Qpid has a [Messaging .NET > Binding|http://qpid.apache.org/releases/qpid-0.24/programming/book/ch05.html] > that is layered on top of the native C++ Qpid Messaging client. The Qpid .NET > binding is attractive as the hook for tying in Qpid as an NMS provider. > The proposed NMS provider supports [AMQP > 1.0|http://qpid.apache.org/amqp.html] by including [Qpid > Proton|http://qpid.apache.org/proton/index.html] libraries. > From a high level this addition to Active.NMS would consist of two parts > * Add Qpid as a vendor kit. This includes both the Qpid .NET Binding and Qpid > Proton in a single kit. > * Add the new provider with code linking NMS to Qpid -- This message was sent by Atlassian JIRA (v6.1.5#6160)
Re: ActiveMQ Console - let's get the problem defined
+1 for Google Docs. On Sat, Feb 1, 2014 at 1:32 PM, artnaseef wrote: > The list of concerns for the current webconsole, and needs, are documented > on > the following google doc; I hope the use of a google doc is not a concern - > let me know if there's a better place for it. > > > https://docs.google.com/document/d/1UsFADaXFuahYdk_osNFnCCSBR9is_FjB6jmzQl53ou8/edit?usp=sharing > > This is a good start. Please let me know any changes you would like to > see, > or send me your google login and I'll grant you permission to edit the > document. > > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/ActiveMQ-Console-let-s-get-the-problem-defined-tp4677105p4677268.html > Sent from the ActiveMQ - Dev mailing list archive at Nabble.com. >
[jira] [Updated] (AMQNET-454) Add Apache Qpid provider to NMS
[ https://issues.apache.org/jira/browse/AMQNET-454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chuck Rolke updated AMQNET-454: --- Attachment: Apache.NMS.AMQP-fix-replyTo-and-receive-timeouts-16.patch Patch -16 adds a replyTo address to received messages. This address is calculated by the Qpid receiver after it connects to its peer entity and may or may not be identical to the original Destination used to create the Consumer. This patch also adds timeouts to the message receive functions. > Add Apache Qpid provider to NMS > --- > > Key: AMQNET-454 > URL: https://issues.apache.org/jira/browse/AMQNET-454 > Project: ActiveMQ .Net > Issue Type: New Feature > Components: NMS >Affects Versions: 1.6.0 >Reporter: Chuck Rolke >Assignee: Jim Gomes > Attachments: Apache.NMS.AMQP-add-hello-world-example-11.patch, > Apache.NMS.AMQP-add-hello-world-example-retry-12.patch, > Apache.NMS.AMQP-add-message-conversions-06.patch, > Apache.NMS.AMQP-add-topic-05.patch, > Apache.NMS.AMQP-connectionProperties-07.patch, > Apache.NMS.AMQP-copyrights-conn-str-fix-09.patch, > Apache.NMS.AMQP-fix-destination-to-use-qpid-address-10.patch, > Apache.NMS.AMQP-fix-helloworld-13.patch, > Apache.NMS.AMQP-fix-list-message-body-15.patch, > Apache.NMS.AMQP-fix-map-message-body-14.patch, > Apache.NMS.AMQP-fix-replyTo-and-receive-timeouts-16.patch, > Apache.NMS.AMQP-object-lifecycle-04.patch, > Apache.NMS.AMQP-provider-configs-03.patch, > Apache.NMS.AMQP-qpid-object-lifecycle-02.patch, > Apache.NMS.AMQP-set-connection-credentials-08.patch, vendor-QPid-nant-01.patch > > > NMS includes various providers ActiveMQ, STOMP, MSMQ, EMS, and WCF. This > issue proposes to add [Apache Qpid|http://qpid.apache.org/index.html] as > another provider. > Qpid has a [Messaging .NET > Binding|http://qpid.apache.org/releases/qpid-0.24/programming/book/ch05.html] > that is layered on top of the native C++ Qpid Messaging client. The Qpid .NET > binding is attractive as the hook for tying in Qpid as an NMS provider. > The proposed NMS provider supports [AMQP > 1.0|http://qpid.apache.org/amqp.html] by including [Qpid > Proton|http://qpid.apache.org/proton/index.html] libraries. > From a high level this addition to Active.NMS would consist of two parts > * Add Qpid as a vendor kit. This includes both the Qpid .NET Binding and Qpid > Proton in a single kit. > * Add the new provider with code linking NMS to Qpid -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (AMQNET-454) Add Apache Qpid provider to NMS
[ https://issues.apache.org/jira/browse/AMQNET-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13889866#comment-13889866 ] Timothy Bish commented on AMQNET-454: - Patch applied. > Add Apache Qpid provider to NMS > --- > > Key: AMQNET-454 > URL: https://issues.apache.org/jira/browse/AMQNET-454 > Project: ActiveMQ .Net > Issue Type: New Feature > Components: NMS >Affects Versions: 1.6.0 >Reporter: Chuck Rolke >Assignee: Jim Gomes > Attachments: Apache.NMS.AMQP-add-hello-world-example-11.patch, > Apache.NMS.AMQP-add-hello-world-example-retry-12.patch, > Apache.NMS.AMQP-add-message-conversions-06.patch, > Apache.NMS.AMQP-add-topic-05.patch, > Apache.NMS.AMQP-connectionProperties-07.patch, > Apache.NMS.AMQP-copyrights-conn-str-fix-09.patch, > Apache.NMS.AMQP-fix-destination-to-use-qpid-address-10.patch, > Apache.NMS.AMQP-fix-helloworld-13.patch, > Apache.NMS.AMQP-fix-list-message-body-15.patch, > Apache.NMS.AMQP-fix-map-message-body-14.patch, > Apache.NMS.AMQP-object-lifecycle-04.patch, > Apache.NMS.AMQP-provider-configs-03.patch, > Apache.NMS.AMQP-qpid-object-lifecycle-02.patch, > Apache.NMS.AMQP-set-connection-credentials-08.patch, vendor-QPid-nant-01.patch > > > NMS includes various providers ActiveMQ, STOMP, MSMQ, EMS, and WCF. This > issue proposes to add [Apache Qpid|http://qpid.apache.org/index.html] as > another provider. > Qpid has a [Messaging .NET > Binding|http://qpid.apache.org/releases/qpid-0.24/programming/book/ch05.html] > that is layered on top of the native C++ Qpid Messaging client. The Qpid .NET > binding is attractive as the hook for tying in Qpid as an NMS provider. > The proposed NMS provider supports [AMQP > 1.0|http://qpid.apache.org/amqp.html] by including [Qpid > Proton|http://qpid.apache.org/proton/index.html] libraries. > From a high level this addition to Active.NMS would consist of two parts > * Add Qpid as a vendor kit. This includes both the Qpid .NET Binding and Qpid > Proton in a single kit. > * Add the new provider with code linking NMS to Qpid -- This message was sent by Atlassian JIRA (v6.1.5#6160)
activemq pull request: Remove sitemesh/activemq-all
GitHub user dkulp opened a pull request: https://github.com/apache/activemq/pull/12 Remove sitemesh/activemq-all Remove the now unused sitemesh jar from the war/assembly. Also remove the activemq-all jar and use the little jars that are actually needed. You can merge this pull request into a Git repository by running: $ git pull https://github.com/dkulp/activemq remove-sitemesh Alternatively you can review and apply these changes as the patch at: https://github.com/apache/activemq/pull/12.patch commit cbc227cd1c626cf0ba74ff7d8eafe4d0deb1ab40 Author: Daniel Kulp Date: 2014-01-30T01:35:16Z [AMQ-4994] Remove site-mesh commit 127f82a4392caeec2913144a72a61f53c79d5625 Author: Daniel Kulp Date: 2014-02-03T19:37:46Z Remove sitemesh jar from assembly, not needed anymore commit f222741fdc5e5b8b5dc401e054abbf5a77ff63dc Author: Daniel Kulp Date: 2014-02-03T20:13:44Z More updates for removing sitemesh, remove activemq-all. commit f74a65f4f5e712051c33ed7b44605dc3cbb93f7f Author: Daniel Kulp Date: 2014-02-03T20:23:54Z Merge ../activemq into remove-sitemesh
Re: Work on Apollo
Hi Hiram, Is it possible to do JAAS authorization for apollo ? Examples are only for Authentication. I can develop JAAS interface for Shiro. Thanks -- View this message in context: http://activemq.2283324.n4.nabble.com/Work-on-Apollo-tp4676511p4677345.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
[jira] [Updated] (AMQNET-454) Add Apache Qpid provider to NMS
[ https://issues.apache.org/jira/browse/AMQNET-454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chuck Rolke updated AMQNET-454: --- Attachment: Apache.NMS.AMQP-fix-list-message-body-15.patch Patch -15 encodes/decodes AMQP list messages through NMS Object messages where the NMS message objects are arrays of the corresponding primitive data type. > Add Apache Qpid provider to NMS > --- > > Key: AMQNET-454 > URL: https://issues.apache.org/jira/browse/AMQNET-454 > Project: ActiveMQ .Net > Issue Type: New Feature > Components: NMS >Affects Versions: 1.6.0 >Reporter: Chuck Rolke >Assignee: Jim Gomes > Attachments: Apache.NMS.AMQP-add-hello-world-example-11.patch, > Apache.NMS.AMQP-add-hello-world-example-retry-12.patch, > Apache.NMS.AMQP-add-message-conversions-06.patch, > Apache.NMS.AMQP-add-topic-05.patch, > Apache.NMS.AMQP-connectionProperties-07.patch, > Apache.NMS.AMQP-copyrights-conn-str-fix-09.patch, > Apache.NMS.AMQP-fix-destination-to-use-qpid-address-10.patch, > Apache.NMS.AMQP-fix-helloworld-13.patch, > Apache.NMS.AMQP-fix-list-message-body-15.patch, > Apache.NMS.AMQP-fix-map-message-body-14.patch, > Apache.NMS.AMQP-object-lifecycle-04.patch, > Apache.NMS.AMQP-provider-configs-03.patch, > Apache.NMS.AMQP-qpid-object-lifecycle-02.patch, > Apache.NMS.AMQP-set-connection-credentials-08.patch, vendor-QPid-nant-01.patch > > > NMS includes various providers ActiveMQ, STOMP, MSMQ, EMS, and WCF. This > issue proposes to add [Apache Qpid|http://qpid.apache.org/index.html] as > another provider. > Qpid has a [Messaging .NET > Binding|http://qpid.apache.org/releases/qpid-0.24/programming/book/ch05.html] > that is layered on top of the native C++ Qpid Messaging client. The Qpid .NET > binding is attractive as the hook for tying in Qpid as an NMS provider. > The proposed NMS provider supports [AMQP > 1.0|http://qpid.apache.org/amqp.html] by including [Qpid > Proton|http://qpid.apache.org/proton/index.html] libraries. > From a high level this addition to Active.NMS would consist of two parts > * Add Qpid as a vendor kit. This includes both the Qpid .NET Binding and Qpid > Proton in a single kit. > * Add the new provider with code linking NMS to Qpid -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (AMQ-5002) AMQP: If a proton client only sets the ttl, and not the message timestamp, ActiveMQ does not handle the expiration correctly
[ https://issues.apache.org/jira/browse/AMQ-5002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13889732#comment-13889732 ] Hiram Chirino commented on AMQ-5002: To get it working when the timestamp is set, we need this issue fixed: https://issues.apache.org/jira/browse/PROTON-474 > AMQP: If a proton client only sets the ttl, and not the message timestamp, > ActiveMQ does not handle the expiration correctly > > > Key: AMQ-5002 > URL: https://issues.apache.org/jira/browse/AMQ-5002 > Project: ActiveMQ > Issue Type: Bug > Components: AMQP >Reporter: Hiram Chirino >Assignee: Hiram Chirino > Fix For: 5.10.0 > > -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (AMQ-2534) Broker gets stuck with an error about using a closed JDBC statement
[ https://issues.apache.org/jira/browse/AMQ-2534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13889722#comment-13889722 ] Marcelo Flores commented on AMQ-2534: - So, this was a non resolved issue for activemq version 5.3, but fixed since 5.4, is that it? > Broker gets stuck with an error about using a closed JDBC statement > --- > > Key: AMQ-2534 > URL: https://issues.apache.org/jira/browse/AMQ-2534 > Project: ActiveMQ > Issue Type: Bug > Components: Message Store >Affects Versions: 5.3.0 > Environment: Linux > Sun JDK 6, several different update versions > Mysql >Reporter: Marshall Pierce > Fix For: 5.x > > > This seems to happen after a period of several hours of inactivity. One > symptom of the problem is that in the web UI you can see that a queue has a > non-zero message count, but clicking on the queue to see the actual messages > shows nothing. > Config: > > > > destroy-method="close"> > > value="jdbc:mysql://dbserver/activeMQ?relaxAutoCommit=true&autoReconnect=true"/> > > > > > > Log: > 2009-11-27 07:40:25,026 | WARN | Close failed: Already closed. | > org.apache.activemq.store.jdbc.TransactionContext | > QueueThread:queue://(queue name) > java.sql.SQLException: Already closed. > at > org.apache.commons.dbcp.PoolableConnection.close(PoolableConnection.java:84) > at > org.apache.commons.dbcp.PoolingDataSource$PoolGuardConnectionWrapper.close(PoolingDataSource.java:181) > at > org.apache.activemq.store.jdbc.TransactionContext.close(TransactionContext.java:135) > at > org.apache.activemq.store.jdbc.JDBCMessageStore.getMessageCount(JDBCMessageStore.java:198) > at > org.apache.activemq.store.ProxyMessageStore.getMessageCount(ProxyMessageStore.java:83) > at > org.apache.activemq.broker.region.cursors.QueueStorePrefetch.getStoreSize(QueueStorePrefetch.java:63) > at > org.apache.activemq.broker.region.cursors.AbstractStoreCursor.remove(AbstractStoreCursor.java:185) > at > org.apache.activemq.broker.region.cursors.StoreQueueCursor.remove(StoreQueueCursor.java:141) > at org.apache.activemq.broker.region.Queue.doPageIn(Queue.java:1367) > at > org.apache.activemq.broker.region.Queue.pageInMessages(Queue.java:1503) > at org.apache.activemq.broker.region.Queue.iterate(Queue.java:1178) > at > org.apache.activemq.thread.DeterministicTaskRunner.runTask(DeterministicTaskRunner.java:84) > at > org.apache.activemq.thread.DeterministicTaskRunner$1.run(DeterministicTaskRunner.java:41) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown > Source) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) > at java.lang.Thread.run(Unknown Source) > 2009-11-27 07:40:25,027 | ERROR | Failed to get message count | > org.apache.activemq.broker.region.cursors.QueueStorePrefetch | > QueueThread:queue://(queue name) > java.io.IOException: Failed to get Message Count: queue://(queue name). > Reason: com.mysql.jdbc.exceptions.MySQLNonTransientConnectionException: No > operations allowed after statement closed. > at > org.apache.activemq.util.IOExceptionSupport.create(IOExceptionSupport.java:33) > at > org.apache.activemq.store.jdbc.JDBCMessageStore.getMessageCount(JDBCMessageStore.java:196) > at > org.apache.activemq.store.ProxyMessageStore.getMessageCount(ProxyMessageStore.java:83) > at > org.apache.activemq.broker.region.cursors.QueueStorePrefetch.getStoreSize(QueueStorePrefetch.java:63) > at > org.apache.activemq.broker.region.cursors.AbstractStoreCursor.remove(AbstractStoreCursor.java:185) > at > org.apache.activemq.broker.region.cursors.StoreQueueCursor.remove(StoreQueueCursor.java:141) > at org.apache.activemq.broker.region.Queue.doPageIn(Queue.java:1367) > at > org.apache.activemq.broker.region.Queue.pageInMessages(Queue.java:1503) > at org.apache.activemq.broker.region.Queue.iterate(Queue.java:1178) > at > org.apache.activemq.thread.DeterministicTaskRunner.runTask(DeterministicTaskRunner.java:84) > at > org.apache.activemq.thread.DeterministicTaskRunner$1.run(DeterministicTaskRunner.java:41) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown > Source) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) > at java.lang.Thread.run(Unknown Source) > Caused by: com.mysql.jdbc.exceptions.MySQLNonTransientConnectionException: No > operations allowed after statement closed. > at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:888) > at com.mysql.jdbc.Statement.checkClosed(Statement.java:380) >
Re: ActiveMQ Console - let's get the problem defined
If you do a “mvn install” in activemq-web-console, the resulting war file is about 22mb in size. Thus, if you you deploy that war into tomcat or something to remotely manage a broker, you would take the full 22mb hit. However, there are a couple issues with that: 1) That war does contain some stuff that I’m not sure should be there. Why would a war deployed into tomcat need all the jetty jars for example? It has the activemq-all jar, but it also has all the jars that make up activemq-all. Thus, that 22mb war should be WAY WAY less if someone would take a few minutes to look at it and pull the stuff that shouldn’t be there. 2) We don’t use that war when we do the activemq-admin command. As you pointed out, the incremental “cost” of the current console over the standalone broker is really about 1MB, no where near the 22mb. It’s not a lot. I believe most of the stuff in lib/web would also be used for the ws interface into the broker which is on by default. Thus, that hit isn’t part of the the admin console only hit. In any case, with 5.9.0, the hawt.io console would have a larger potential impact than the activemq console. From my perspective, just ignore the “22mb” number and lets just work on getting a nice, usable console in place. :-) Dan On Feb 3, 2014, at 12:45 AM, artnaseef wrote: > Thanks Johan. Looking a little more carefully, I see 13mb under lib/web. > > Under webapps, there's 14mb for hawtio. Then about 1mb for everything > else. Another 1mb lives under webapps-demo. > > That's closer. > >> >> >> It is probably the war file + jetty + spring + sitemesh and >> everything else. >> >> >> On Feb 2, 2014, at 9:52 PM, artnaseef wrote: >> >>> James S: >>> >>> Looking at the size of jar files, the web jar is tiny: >>> >>> 109K Jan 30 19:08 activemq-web-5.10-SNAPSHOT.jar >>> >>> Can you point me at more detail of the source of the 22mb number? >>> >>> >>> >>> -- >>> View this message in context: >>> http://activemq.2283324.n4.nabble.com/ActiveMQ-Console-let-s-get-the-problem-defined-tp4677105p4677289.html >>> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com. >> >> >> >> >> >> ___ >> If you reply to this email, your message will be added to the discussion >> below: >> http://activemq.2283324.n4.nabble.com/ActiveMQ-Console-let-s-get-the-problem-defined-tp4677105p4677290.html >> To start a new topic under ActiveMQ - Dev, email >> ml-node+s2283324n2368404...@n4.nabble.com >> To unsubscribe from ActiveMQ Console - let's get the problem defined, >> visit >> http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4677105&code=YXJ0QGFydG5hc2VlZi5jb218NDY3NzEwNXwtMjA1NDcyNjY5MQ== > > > > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/ActiveMQ-Console-let-s-get-the-problem-defined-tp4677105p4677294.html > Sent from the ActiveMQ - Dev mailing list archive at Nabble.com. -- Daniel Kulp dk...@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
Re: activemq 5.9.1
We tend to avoid dong adding the RC bits to the version since they voted on bits are held in a staging area. On Mon, Feb 3, 2014 at 11:54 AM, Hadrian Zbarcea wrote: > +1. I think we'd still have to do a 5.9.1, but it's a good idea. While I > sort through the issues for 5.9.1 I could cut a 5.10.0-RC1. Or should we go > straight to a 5.10.0 and redo it if necessary? > > Hadrian > > > > On 02/03/2014 10:41 AM, Hiram Chirino wrote: >> >> I think it's safest to to just call trunk 5.10 now since it is taking >> away some functionality. Would be nice to get some RCs going soon >> since trunk is stable right now. >> >> On Thu, Jan 30, 2014 at 3:38 PM, Hadrian Zbarcea >> wrote: >>> >>> Hi, >>> >>> I am still planning to release 5.9.1. We need to figure out if we want to >>> cut 5.9.1 off of the current trunk at a stable checkpoint, or branch it >>> off >>> 5.9.0 and just select the relevant patches. While the feedback on this >>> list >>> is not conclusive (and I personally favor the 1st approach) I believe >>> most >>> would favor the 2nd approach. Last week there were over 200 patches that >>> we'd have to look through and backport. The fastest we could get through >>> this the sooner we'll have the release, I hope before mid Feb. >>> >>> Cheers, >>> Hadrian >>> >>> >>> >>> On 01/30/2014 03:31 PM, kal123 wrote: There were post for cutting 5.9.1 any update on timeline for this? -- View this message in context: http://activemq.2283324.n4.nabble.com/activemq-5-9-1-tp4677074.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com. >>> >>> >> >> > -- Hiram Chirino Engineering | Red Hat, Inc. hchir...@redhat.com | fusesource.com | redhat.com skype: hiramchirino | twitter: @hiramchirino
Re: activemq 5.9.1
+1. I think we'd still have to do a 5.9.1, but it's a good idea. While I sort through the issues for 5.9.1 I could cut a 5.10.0-RC1. Or should we go straight to a 5.10.0 and redo it if necessary? Hadrian On 02/03/2014 10:41 AM, Hiram Chirino wrote: I think it's safest to to just call trunk 5.10 now since it is taking away some functionality. Would be nice to get some RCs going soon since trunk is stable right now. On Thu, Jan 30, 2014 at 3:38 PM, Hadrian Zbarcea wrote: Hi, I am still planning to release 5.9.1. We need to figure out if we want to cut 5.9.1 off of the current trunk at a stable checkpoint, or branch it off 5.9.0 and just select the relevant patches. While the feedback on this list is not conclusive (and I personally favor the 1st approach) I believe most would favor the 2nd approach. Last week there were over 200 patches that we'd have to look through and backport. The fastest we could get through this the sooner we'll have the release, I hope before mid Feb. Cheers, Hadrian On 01/30/2014 03:31 PM, kal123 wrote: There were post for cutting 5.9.1 any update on timeline for this? -- View this message in context: http://activemq.2283324.n4.nabble.com/activemq-5-9-1-tp4677074.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
[jira] [Updated] (AMQ-5016) BitArrayBin doesn't work well with index larger than Integer.MAX_VALUE
[
https://issues.apache.org/jira/browse/AMQ-5016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Yu updated AMQ-5016:
Description:
In BitArrayBin class, the index's unit type is long. It also has a variable
called firstIndex, which store the index where the window starts. And that
firstindex's unit is int. If the index is bigger than Integer.MAX_VALUE,
setBit() and getBit() starts to return bad value.
The defect causes activemq client to perform badly when receiving message that
sequence id is bigger than max interger. It spends most of the time to shift
window, and also blocks other consumer threads. Below is the jstack log that
shows the problem.
{code}
"ActiveMQ Session Task-869879" prio=10 tid=0x7f412d6ee000 nid=0x3cbe
runnable [0x7f405b7b6000]
java.lang.Thread.State: RUNNABLE
at java.util.LinkedList.linkLast(LinkedList.java:140)
at java.util.LinkedList.add(LinkedList.java:336)
at
org.apache.activemq.util.BitArrayBin.getBitArray(BitArrayBin.java:123)
at org.apache.activemq.util.BitArrayBin.setBit(BitArrayBin.java:59)
at org.apache.activemq.ActiveMQMessage
AuditNoSync.isDuplicate(ActiveMQMessageAuditNoSyn c.java:160)
at
org.apache.activemq.ActiveMQMessageAudit.isDuplicate(ActiveMQMessageAudit.java:59)
- locked <0x7f46a0138ab0> (a
org.apache.activemq.ActiveMQMessageAudit)
at org.apache.activemq.ActiveMQMessage
AuditNoSync.isDuplicate(ActiveMQMessageAuditNoSyn c.java:140)
at
org.apache.activemq.ConnectionAudit.isDuplicate(ConnectionAudit.java:52)
- locked <0x7f4881e6b968> (a org.apache.activemq.ConnectionAudit)
at
org.apache.activemq.ActiveMQConnection.isDuplicate(ActiveMQConnection.java:2291)
at
org.apache.activemq.ActiveMQMessageConsumer.dispatch(ActiveMQMessageConsumer.java:1223)
- locked <0x7f45db222fb8> (a java.lang.Object)
at
org.apache.activemq.ActiveMQSessionExecutor.dispatch(ActiveMQSessionExecutor.java:134)
at
org.apache.activemq.ActiveMQSessionExecutor.iterate(ActiveMQSessionExecutor.java:205)
at
org.apache.activemq.thread.PooledTaskRunner.runTask(PooledTaskRunner.java:127)
at
org.apache.activemq.thread.PooledTaskRunner$1.run(PooledTaskRunner.java:48)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
{code}
was:
In the BitArrayBin, the index's unit type is long. It also has a variable
called firstIndex, which store where the window starts. And that firstindex's
unit is int. If the index is bigger than Integer.MAX_VALUE, setBit() and
getBit() starts to return bad value.
The defect will cause activemq client to perform badly when receiving message
that sequence id is bigger than max interger. Below is the jstack log that
shows the problem.
{code}
"ActiveMQ Session Task-869879" prio=10 tid=0x7f412d6ee000 nid=0x3cbe
runnable [0x7f405b7b6000]
java.lang.Thread.State: RUNNABLE
at java.util.LinkedList.linkLast(LinkedList.java:140)
at java.util.LinkedList.add(LinkedList.java:336)
at
org.apache.activemq.util.BitArrayBin.getBitArray(BitArrayBin.java:123)
at org.apache.activemq.util.BitArrayBin.setBit(BitArrayBin.java:59)
at org.apache.activemq.ActiveMQMessage
AuditNoSync.isDuplicate(ActiveMQMessageAuditNoSyn c.java:160)
at
org.apache.activemq.ActiveMQMessageAudit.isDuplicate(ActiveMQMessageAudit.java:59)
- locked <0x7f46a0138ab0> (a
org.apache.activemq.ActiveMQMessageAudit)
at org.apache.activemq.ActiveMQMessage
AuditNoSync.isDuplicate(ActiveMQMessageAuditNoSyn c.java:140)
at
org.apache.activemq.ConnectionAudit.isDuplicate(ConnectionAudit.java:52)
- locked <0x7f4881e6b968> (a org.apache.activemq.ConnectionAudit)
at
org.apache.activemq.ActiveMQConnection.isDuplicate(ActiveMQConnection.java:2291)
at
org.apache.activemq.ActiveMQMessageConsumer.dispatch(ActiveMQMessageConsumer.java:1223)
- locked <0x7f45db222fb8> (a java.lang.Object)
at
org.apache.activemq.ActiveMQSessionExecutor.dispatch(ActiveMQSessionExecutor.java:134)
at
org.apache.activemq.ActiveMQSessionExecutor.iterate(ActiveMQSessionExecutor.java:205)
at
org.apache.activemq.thread.PooledTaskRunner.runTask(PooledTaskRunner.java:127)
at
org.apache.activemq.thread.PooledTaskRunner$1.run(PooledTaskRunner.java:48)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
{code}
> BitArrayBin doesn't work well with index larger than Integer.MAX_VALUE
> --
[jira] [Updated] (AMQ-5016) BitArrayBin doesn't work well with index larger than Integer.MAX_VALUE
[
https://issues.apache.org/jira/browse/AMQ-5016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Yu updated AMQ-5016:
Attachment: BitArrayBinTest.java
A unit test that expose the issue.
> BitArrayBin doesn't work well with index larger than Integer.MAX_VALUE
> --
>
> Key: AMQ-5016
> URL: https://issues.apache.org/jira/browse/AMQ-5016
> Project: ActiveMQ
> Issue Type: Bug
> Components: JMS client
>Affects Versions: 5.9.0
>Reporter: Dan Yu
> Attachments: BitArrayBinTest.java
>
>
> In the BitArrayBin, the index's unit type is long. It also has a variable
> called firstIndex, which store where the window starts. And that firstindex's
> unit is int. If the index is bigger than Integer.MAX_VALUE, setBit() and
> getBit() starts to return bad value.
> The defect will cause activemq client to perform badly when receiving message
> that sequence id is bigger than max interger. Below is the jstack log that
> shows the problem.
> {code}
> "ActiveMQ Session Task-869879" prio=10 tid=0x7f412d6ee000 nid=0x3cbe
> runnable [0x7f405b7b6000]
>java.lang.Thread.State: RUNNABLE
> at java.util.LinkedList.linkLast(LinkedList.java:140)
> at java.util.LinkedList.add(LinkedList.java:336)
> at
> org.apache.activemq.util.BitArrayBin.getBitArray(BitArrayBin.java:123)
> at org.apache.activemq.util.BitArrayBin.setBit(BitArrayBin.java:59)
> at org.apache.activemq.ActiveMQMessage
> AuditNoSync.isDuplicate(ActiveMQMessageAuditNoSyn c.java:160)
> at
> org.apache.activemq.ActiveMQMessageAudit.isDuplicate(ActiveMQMessageAudit.java:59)
> - locked <0x7f46a0138ab0> (a
> org.apache.activemq.ActiveMQMessageAudit)
> at org.apache.activemq.ActiveMQMessage
> AuditNoSync.isDuplicate(ActiveMQMessageAuditNoSyn c.java:140)
> at
> org.apache.activemq.ConnectionAudit.isDuplicate(ConnectionAudit.java:52)
> - locked <0x7f4881e6b968> (a org.apache.activemq.ConnectionAudit)
> at
> org.apache.activemq.ActiveMQConnection.isDuplicate(ActiveMQConnection.java:2291)
> at
> org.apache.activemq.ActiveMQMessageConsumer.dispatch(ActiveMQMessageConsumer.java:1223)
> - locked <0x7f45db222fb8> (a java.lang.Object)
> at
> org.apache.activemq.ActiveMQSessionExecutor.dispatch(ActiveMQSessionExecutor.java:134)
> at
> org.apache.activemq.ActiveMQSessionExecutor.iterate(ActiveMQSessionExecutor.java:205)
> at
> org.apache.activemq.thread.PooledTaskRunner.runTask(PooledTaskRunner.java:127)
> at
> org.apache.activemq.thread.PooledTaskRunner$1.run(PooledTaskRunner.java:48)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:722)
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Created] (AMQ-5016) BitArrayBin doesn't work well with index larger than Integer.MAX_VALUE
Dan Yu created AMQ-5016:
---
Summary: BitArrayBin doesn't work well with index larger than
Integer.MAX_VALUE
Key: AMQ-5016
URL: https://issues.apache.org/jira/browse/AMQ-5016
Project: ActiveMQ
Issue Type: Bug
Components: JMS client
Affects Versions: 5.9.0
Reporter: Dan Yu
In the BitArrayBin, the index's unit type is long. It also has a variable
called firstIndex, which store where the window starts. And that firstindex's
unit is int. If the index is bigger than Integer.MAX_VALUE, setBit() and
getBit() starts to return bad value.
The defect will cause activemq client to perform badly when receiving message
that sequence id is bigger than max interger. Below is the jstack log that
shows the problem.
{code}
"ActiveMQ Session Task-869879" prio=10 tid=0x7f412d6ee000 nid=0x3cbe
runnable [0x7f405b7b6000]
java.lang.Thread.State: RUNNABLE
at java.util.LinkedList.linkLast(LinkedList.java:140)
at java.util.LinkedList.add(LinkedList.java:336)
at
org.apache.activemq.util.BitArrayBin.getBitArray(BitArrayBin.java:123)
at org.apache.activemq.util.BitArrayBin.setBit(BitArrayBin.java:59)
at org.apache.activemq.ActiveMQMessage
AuditNoSync.isDuplicate(ActiveMQMessageAuditNoSyn c.java:160)
at
org.apache.activemq.ActiveMQMessageAudit.isDuplicate(ActiveMQMessageAudit.java:59)
- locked <0x7f46a0138ab0> (a
org.apache.activemq.ActiveMQMessageAudit)
at org.apache.activemq.ActiveMQMessage
AuditNoSync.isDuplicate(ActiveMQMessageAuditNoSyn c.java:140)
at
org.apache.activemq.ConnectionAudit.isDuplicate(ConnectionAudit.java:52)
- locked <0x7f4881e6b968> (a org.apache.activemq.ConnectionAudit)
at
org.apache.activemq.ActiveMQConnection.isDuplicate(ActiveMQConnection.java:2291)
at
org.apache.activemq.ActiveMQMessageConsumer.dispatch(ActiveMQMessageConsumer.java:1223)
- locked <0x7f45db222fb8> (a java.lang.Object)
at
org.apache.activemq.ActiveMQSessionExecutor.dispatch(ActiveMQSessionExecutor.java:134)
at
org.apache.activemq.ActiveMQSessionExecutor.iterate(ActiveMQSessionExecutor.java:205)
at
org.apache.activemq.thread.PooledTaskRunner.runTask(PooledTaskRunner.java:127)
at
org.apache.activemq.thread.PooledTaskRunner$1.run(PooledTaskRunner.java:48)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
{code}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
Re: activemq 5.9.1
I think it's safest to to just call trunk 5.10 now since it is taking away some functionality. Would be nice to get some RCs going soon since trunk is stable right now. On Thu, Jan 30, 2014 at 3:38 PM, Hadrian Zbarcea wrote: > Hi, > > I am still planning to release 5.9.1. We need to figure out if we want to > cut 5.9.1 off of the current trunk at a stable checkpoint, or branch it off > 5.9.0 and just select the relevant patches. While the feedback on this list > is not conclusive (and I personally favor the 1st approach) I believe most > would favor the 2nd approach. Last week there were over 200 patches that > we'd have to look through and backport. The fastest we could get through > this the sooner we'll have the release, I hope before mid Feb. > > Cheers, > Hadrian > > > > On 01/30/2014 03:31 PM, kal123 wrote: >> >> There were post for cutting 5.9.1 any update on timeline for this? >> >> >> >> -- >> View this message in context: >> http://activemq.2283324.n4.nabble.com/activemq-5-9-1-tp4677074.html >> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com. > > -- Hiram Chirino Engineering | Red Hat, Inc. hchir...@redhat.com | fusesource.com | redhat.com skype: hiramchirino | twitter: @hiramchirino
[jira] [Commented] (AMQNET-454) Add Apache Qpid provider to NMS
[ https://issues.apache.org/jira/browse/AMQNET-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13889541#comment-13889541 ] Timothy Bish commented on AMQNET-454: - Patch applied. > Add Apache Qpid provider to NMS > --- > > Key: AMQNET-454 > URL: https://issues.apache.org/jira/browse/AMQNET-454 > Project: ActiveMQ .Net > Issue Type: New Feature > Components: NMS >Affects Versions: 1.6.0 >Reporter: Chuck Rolke >Assignee: Jim Gomes > Attachments: Apache.NMS.AMQP-add-hello-world-example-11.patch, > Apache.NMS.AMQP-add-hello-world-example-retry-12.patch, > Apache.NMS.AMQP-add-message-conversions-06.patch, > Apache.NMS.AMQP-add-topic-05.patch, > Apache.NMS.AMQP-connectionProperties-07.patch, > Apache.NMS.AMQP-copyrights-conn-str-fix-09.patch, > Apache.NMS.AMQP-fix-destination-to-use-qpid-address-10.patch, > Apache.NMS.AMQP-fix-helloworld-13.patch, > Apache.NMS.AMQP-fix-map-message-body-14.patch, > Apache.NMS.AMQP-object-lifecycle-04.patch, > Apache.NMS.AMQP-provider-configs-03.patch, > Apache.NMS.AMQP-qpid-object-lifecycle-02.patch, > Apache.NMS.AMQP-set-connection-credentials-08.patch, vendor-QPid-nant-01.patch > > > NMS includes various providers ActiveMQ, STOMP, MSMQ, EMS, and WCF. This > issue proposes to add [Apache Qpid|http://qpid.apache.org/index.html] as > another provider. > Qpid has a [Messaging .NET > Binding|http://qpid.apache.org/releases/qpid-0.24/programming/book/ch05.html] > that is layered on top of the native C++ Qpid Messaging client. The Qpid .NET > binding is attractive as the hook for tying in Qpid as an NMS provider. > The proposed NMS provider supports [AMQP > 1.0|http://qpid.apache.org/amqp.html] by including [Qpid > Proton|http://qpid.apache.org/proton/index.html] libraries. > From a high level this addition to Active.NMS would consist of two parts > * Add Qpid as a vendor kit. This includes both the Qpid .NET Binding and Qpid > Proton in a single kit. > * Add the new provider with code linking NMS to Qpid -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (AMQ-5014) Broker uses kahadb for uri: vm:localhost?broker.persistent=false
[ https://issues.apache.org/jira/browse/AMQ-5014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider updated AMQ-5014: - Attachment: (was: PooledConnectionTempQueueTest.java) > Broker uses kahadb for uri: vm:localhost?broker.persistent=false > > > Key: AMQ-5014 > URL: https://issues.apache.org/jira/browse/AMQ-5014 > Project: ActiveMQ > Issue Type: Improvement >Affects Versions: 5.9.0 >Reporter: Christian Schneider > > I found that a slight error in the uri causes the broker to use kahadb > persistence instead of the intended memory persistence. > This uses kahadb: > vm:localhost?broker.persistent=false > This uses memory peristence: > vm://localhost?broker.persistent=false > So for the first case there should either be an error message or a warning > that the uri is not understood. It took me quite a while to find why it > behaved wrong. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (AMQ-5015) Temp Queue gets deleted on close of wrong connection
[ https://issues.apache.org/jira/browse/AMQ-5015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider updated AMQ-5015: - Attachment: PooledConnectionTempQueueTest.java > Temp Queue gets deleted on close of wrong connection > > > Key: AMQ-5015 > URL: https://issues.apache.org/jira/browse/AMQ-5015 > Project: ActiveMQ > Issue Type: Improvement >Affects Versions: 5.9.0 >Reporter: Christian Schneider > Attachments: PooledConnectionTempQueueTest.java > > > My scenario is this: > connection1: > create temp queue tq1 > send msg to qeue1 with replyTo tq1 > wait for reply on tq1 > connection2: > receive message on queue1 > send to replyTo address which is tq1 > In some cases the temp queue gets deleted in the close method of connection2. > The scenario is kind of an edge case as it only happens if I use a > PooledConnectionFactory and only if I before my scenario above open a > connection and session and close the connection before the session. > So strictly speaking my code has an error. > I think the problem is in the PooledConnection factory. It seems to reuse a > connection or session in the wrong way. I will attach a test case -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (AMQ-5015) Temp Queue gets deleted on close of wrong connection
Christian Schneider created AMQ-5015: Summary: Temp Queue gets deleted on close of wrong connection Key: AMQ-5015 URL: https://issues.apache.org/jira/browse/AMQ-5015 Project: ActiveMQ Issue Type: Improvement Affects Versions: 5.9.0 Reporter: Christian Schneider My scenario is this: connection1: create temp queue tq1 send msg to qeue1 with replyTo tq1 wait for reply on tq1 connection2: receive message on queue1 send to replyTo address which is tq1 In some cases the temp queue gets deleted in the close method of connection2. The scenario is kind of an edge case as it only happens if I use a PooledConnectionFactory and only if I before my scenario above open a connection and session and close the connection before the session. So strictly speaking my code has an error. I think the problem is in the PooledConnection factory. It seems to reuse a connection or session in the wrong way. I will attach a test case -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (AMQ-5014) Broker uses kahadb for uri: vm:localhost?broker.persistent=false
[ https://issues.apache.org/jira/browse/AMQ-5014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider updated AMQ-5014: - Attachment: PooledConnectionTempQueueTest.java > Broker uses kahadb for uri: vm:localhost?broker.persistent=false > > > Key: AMQ-5014 > URL: https://issues.apache.org/jira/browse/AMQ-5014 > Project: ActiveMQ > Issue Type: Improvement >Affects Versions: 5.9.0 >Reporter: Christian Schneider > Attachments: PooledConnectionTempQueueTest.java > > > I found that a slight error in the uri causes the broker to use kahadb > persistence instead of the intended memory persistence. > This uses kahadb: > vm:localhost?broker.persistent=false > This uses memory peristence: > vm://localhost?broker.persistent=false > So for the first case there should either be an error message or a warning > that the uri is not understood. It took me quite a while to find why it > behaved wrong. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (AMQNET-454) Add Apache Qpid provider to NMS
[ https://issues.apache.org/jira/browse/AMQNET-454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chuck Rolke updated AMQNET-454: --- Attachment: Apache.NMS.AMQP-fix-map-message-body-14.patch Patch -14. This patch enables Map message data bodies and conversions between Qpid amqp/map and NMS PrimitiveMap types. > Add Apache Qpid provider to NMS > --- > > Key: AMQNET-454 > URL: https://issues.apache.org/jira/browse/AMQNET-454 > Project: ActiveMQ .Net > Issue Type: New Feature > Components: NMS >Affects Versions: 1.6.0 >Reporter: Chuck Rolke >Assignee: Jim Gomes > Attachments: Apache.NMS.AMQP-add-hello-world-example-11.patch, > Apache.NMS.AMQP-add-hello-world-example-retry-12.patch, > Apache.NMS.AMQP-add-message-conversions-06.patch, > Apache.NMS.AMQP-add-topic-05.patch, > Apache.NMS.AMQP-connectionProperties-07.patch, > Apache.NMS.AMQP-copyrights-conn-str-fix-09.patch, > Apache.NMS.AMQP-fix-destination-to-use-qpid-address-10.patch, > Apache.NMS.AMQP-fix-helloworld-13.patch, > Apache.NMS.AMQP-fix-map-message-body-14.patch, > Apache.NMS.AMQP-object-lifecycle-04.patch, > Apache.NMS.AMQP-provider-configs-03.patch, > Apache.NMS.AMQP-qpid-object-lifecycle-02.patch, > Apache.NMS.AMQP-set-connection-credentials-08.patch, vendor-QPid-nant-01.patch > > > NMS includes various providers ActiveMQ, STOMP, MSMQ, EMS, and WCF. This > issue proposes to add [Apache Qpid|http://qpid.apache.org/index.html] as > another provider. > Qpid has a [Messaging .NET > Binding|http://qpid.apache.org/releases/qpid-0.24/programming/book/ch05.html] > that is layered on top of the native C++ Qpid Messaging client. The Qpid .NET > binding is attractive as the hook for tying in Qpid as an NMS provider. > The proposed NMS provider supports [AMQP > 1.0|http://qpid.apache.org/amqp.html] by including [Qpid > Proton|http://qpid.apache.org/proton/index.html] libraries. > From a high level this addition to Active.NMS would consist of two parts > * Add Qpid as a vendor kit. This includes both the Qpid .NET Binding and Qpid > Proton in a single kit. > * Add the new provider with code linking NMS to Qpid -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (AMQ-5014) Broker uses kahadb for uri: vm:localhost?broker.persistent=false
Christian Schneider created AMQ-5014: Summary: Broker uses kahadb for uri: vm:localhost?broker.persistent=false Key: AMQ-5014 URL: https://issues.apache.org/jira/browse/AMQ-5014 Project: ActiveMQ Issue Type: Improvement Affects Versions: 5.9.0 Reporter: Christian Schneider I found that a slight error in the uri causes the broker to use kahadb persistence instead of the intended memory persistence. This uses kahadb: vm:localhost?broker.persistent=false This uses memory peristence: vm://localhost?broker.persistent=false So for the first case there should either be an error message or a warning that the uri is not understood. It took me quite a while to find why it behaved wrong. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
Re: [VOTE] Move the ActiveMQ web-console to a sub-project.
Hi Hadrian. I'll officially cancel this vote since it could not achieve consensus. On Mon, Feb 3, 2014 at 8:47 AM, Hadrian Zbarcea wrote: > Hiram, > > There is no voting window specified for this vote. A it's way past the > default 72 hours do want to close it somehow? > > Cheers, > Hadrian > > > > On 01/28/2014 09:18 AM, Hiram Chirino wrote: >> >> Since there seems to be general agreement that the web-console should >> be moved to a sub-project, lets put it to a vote and make it official. >> >> [ ] +1 Create the activemq-web-console sub-project with the associated >> git, wiki, and jira spaces. >> [ ] -1 Veto the making it a sub-project >> > -- Hiram Chirino Engineering | Red Hat, Inc. hchir...@redhat.com | fusesource.com | redhat.com skype: hiramchirino | twitter: @hiramchirino
Re: [VOTE] Move the ActiveMQ web-console to a sub-project.
Hiram, There is no voting window specified for this vote. A it's way past the default 72 hours do want to close it somehow? Cheers, Hadrian On 01/28/2014 09:18 AM, Hiram Chirino wrote: Since there seems to be general agreement that the web-console should be moved to a sub-project, lets put it to a vote and make it official. [ ] +1 Create the activemq-web-console sub-project with the associated git, wiki, and jira spaces. [ ] -1 Veto the making it a sub-project
[jira] [Created] (AMQ-5013) RestPersistentTest sometimes hangs on CI boxes
Kevin Earls created AMQ-5013: Summary: RestPersistentTest sometimes hangs on CI boxes Key: AMQ-5013 URL: https://issues.apache.org/jira/browse/AMQ-5013 Project: ActiveMQ Issue Type: Bug Components: Test Cases Reporter: Kevin Earls Assignee: Kevin Earls This test hangs occasionally on CI boxes. I'm going to convert it to JUnit 4 and add timeouts as the first step in trying to resolve this. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (AMQ-4998) Old Web Admin console does not manage - new parameter messageTTL consumerTTL connections.jsp and connections Panel display error messages
[
https://issues.apache.org/jira/browse/AMQ-4998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guilhem RAMBAL updated AMQ-4998:
Environment:
CentOS release 6.4 (Final)
java version "1.6.0_45"
Java(TM) SE Runtime Environment (build 1.6.0_45-b06)
Java HotSpot(TM) 64-Bit Server VM (build 20.45-b01, mixed mode)
> Old Web Admin console does not manage - new parameter messageTTL
> consumerTTL connections.jsp and connections Panel display error messages
> ---
>
> Key: AMQ-4998
> URL: https://issues.apache.org/jira/browse/AMQ-4998
> Project: ActiveMQ
> Issue Type: Bug
>Affects Versions: 5.9.0
> Environment: CentOS release 6.4 (Final)
> java version "1.6.0_45"
> Java(TM) SE Runtime Environment (build 1.6.0_45-b06)
> Java HotSpot(TM) 64-Bit Server VM (build 20.45-b01, mixed mode)
>Reporter: Guilhem RAMBAL
>Priority: Critical
>
> 2014-01-29 13:03:31,358 | WARN | /admin/connections.jsp |
> org.eclipse.jetty.servlet.ServletHandler | qtp1721309039-46
> javax.el.PropertyNotFoundException: The class 'com.sun.proxy.$Proxy7' does
> not have the property 'networkTTL'.
> at javax.el.BeanELResolver.getBeanProperty(BeanELResolver.java:579)
> at javax.el.BeanELResolver.getValue(BeanELResolver.java:281)
> at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:175)
> at com.sun.el.parser.AstValue.getValue(AstValue.java:138)
> at
> com.sun.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:206)
> at
> org.apache.jasper.runtime.PageContextImpl.evaluateExpression(PageContextImpl.java:1001)
> at
> org.apache.jsp.connections_jsp._jspx_meth_c_forEach_1(org.apache.jsp.connections_jsp:213)
> at
> org.apache.jsp.connections_jsp._jspService(org.apache.jsp.connections_jsp:95)
> at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:109)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
> at
> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:389)
> at
> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:486)
> at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:380)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
> at
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:652)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1320)
> at
> org.springframework.web.filter.RequestContextFilter.doFilterInternal(RequestContextFilter.java:99)
> at
> org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1291)
> at
> org.apache.activemq.web.SessionFilter.doFilter(SessionFilter.java:45)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1291)
> at
> org.apache.activemq.web.filter.ApplicationContextFilter.doFilter(ApplicationContextFilter.java:102)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1291)
> at
> com.opensymphony.sitemesh.webapp.SiteMeshFilter.obtainContent(SiteMeshFilter.java:129)
> at
> com.opensymphony.sitemesh.webapp.SiteMeshFilter.doFilter(SiteMeshFilter.java:77)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1291)
> at
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:443)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137)
> at
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:521)
> at
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:227)
> This template seems to work :
>
>
>
> Name
> Message TTL
> Consumer TTL
> Dynamic Only
> Conduit Subscriptions
> Bridge Temps
> Decrease Priorities
> Dispatch Async
>
>
>
>
>
> ${nc.name}
> ${nc.messageTTL}
> ${nc.consumerTTL}
> ${nc.dynamicOnly}
> ${nc.conduitSubscriptions}
> ${nc.bridgeTempDestinations}
> ${nc.decreaseNetworkConsumerPriority}
> ${nc.dispatchAsync}
>
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
