[jira] [Commented] (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:comment-tabpanel&focusedCommentId=13894266#comment-13894266
]
liurui commented on AMQ-4998:
-
I also encountered the same problem.
when i used the feature :Networks of Brokers
http://activemq.apache.org/networks-of-brokers.html
static or multicast all lead to this issue.
> 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
> Attachments: connections.patch
>
>
> 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)
[jira] [Commented] (AMQ-5024) Add paging of messages to the webconsole when viewing a deep queue
[ https://issues.apache.org/jira/browse/AMQ-5024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13894138#comment-13894138 ] zmhassan commented on AMQ-5024: --- See this issue for more details of where this originated from: https://issues.apache.org/jira/browse/AMQ-4994 So far I've setup pagination and I am running on test send 200,000 jms messages to a queue. I will then paginate through it and then once I am satisfied I'll put in a pull request. > Add paging of messages to the webconsole when viewing a deep queue > -- > > Key: AMQ-5024 > URL: https://issues.apache.org/jira/browse/AMQ-5024 > Project: ActiveMQ > Issue Type: Improvement > Components: webconsole >Affects Versions: 5.9.0 >Reporter: Arthur Naseef >Assignee: Arthur Naseef > > It is not feasible to browse a deep Queue via the webconsole: navigating to > the webconsole's Queue list, then browsing the Queue, if there are a large > number of messages stored, the webpage takes a very long time, and may > timeout. > Adding pagination of messages so that the webconsole only displays a number > of messages per page will make it feasible to browse deep Queues. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Comment Edited] (AMQ-5024) Add paging of messages to the webconsole when viewing a deep queue
[ https://issues.apache.org/jira/browse/AMQ-5024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13894138#comment-13894138 ] zmhassan edited comment on AMQ-5024 at 2/7/14 2:45 AM: --- See this issue for more details of where this originated from: https://issues.apache.org/jira/browse/AMQ-4994 So far I've setup pagination and I am running one more test with 200,000 jms messages in queue. I will then paginate through it and then once I am satisfied I'll put in a pull request. was (Author: zmhassan): See this issue for more details of where this originated from: https://issues.apache.org/jira/browse/AMQ-4994 So far I've setup pagination and I am running on test send 200,000 jms messages to a queue. I will then paginate through it and then once I am satisfied I'll put in a pull request. > Add paging of messages to the webconsole when viewing a deep queue > -- > > Key: AMQ-5024 > URL: https://issues.apache.org/jira/browse/AMQ-5024 > Project: ActiveMQ > Issue Type: Improvement > Components: webconsole >Affects Versions: 5.9.0 >Reporter: Arthur Naseef >Assignee: Arthur Naseef > > It is not feasible to browse a deep Queue via the webconsole: navigating to > the webconsole's Queue list, then browsing the Queue, if there are a large > number of messages stored, the webpage takes a very long time, and may > timeout. > Adding pagination of messages so that the webconsole only displays a number > of messages per page will make it feasible to browse deep Queues. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (AMQ-5033) webconsole url and html encoding missing
Arthur Naseef created AMQ-5033: -- Summary: webconsole url and html encoding missing Key: AMQ-5033 URL: https://issues.apache.org/jira/browse/AMQ-5033 Project: ActiveMQ Issue Type: Bug Components: webconsole Affects Versions: 5.9.0 Reporter: Arthur Naseef Assignee: Arthur Naseef While working on AMQ-4813, many cases of passing text through to HTML without proper HTML and URL encoding. I believe this can cause security risks, failed operations, or a misformatted UI. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (AMQ-5028) Remove jetty and jsp compiler jars from web-console.war
[
https://issues.apache.org/jira/browse/AMQ-5028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13894085#comment-13894085
]
Arthur Naseef commented on AMQ-5028:
Patch committed f88043eaf7fc1c089b4ffe2770743e28e7b8f6fb.
Thanks!
> Remove jetty and jsp compiler jars from web-console.war
> ---
>
> Key: AMQ-5028
> URL: https://issues.apache.org/jira/browse/AMQ-5028
> Project: ActiveMQ
> Issue Type: Bug
> Components: webconsole
>Reporter: Daniel Kulp
>Assignee: Daniel Kulp
>
> The container that runs the war (like Jetty or Tomcat) will compile the JSP's
> so there is no need for the eclipse core compiler. Also, there isn't a need
> for the jetty jars. It looks like there was an attempt to exclude those from
> packaging anyway via maven-war-plugin configs, but those configs aren't
> working.
> patch:
> {code}
> diff --git a/activemq-web-console/pom.xml b/activemq-web-console/pom.xml
> index e5f2e94..93b7fad 100755
> --- a/activemq-web-console/pom.xml
>
>
> -
> - xpp3
> - xpp3
> -
> -
> - com.thoughtworks.xstream
> - xstream
> -
> -
>
>
>junit
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Resolved] (AMQ-5028) Remove jetty and jsp compiler jars from web-console.war
[
https://issues.apache.org/jira/browse/AMQ-5028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arthur Naseef resolved AMQ-5028.
Resolution: Fixed
> Remove jetty and jsp compiler jars from web-console.war
> ---
>
> Key: AMQ-5028
> URL: https://issues.apache.org/jira/browse/AMQ-5028
> Project: ActiveMQ
> Issue Type: Bug
> Components: webconsole
>Reporter: Daniel Kulp
>Assignee: Daniel Kulp
>
> The container that runs the war (like Jetty or Tomcat) will compile the JSP's
> so there is no need for the eclipse core compiler. Also, there isn't a need
> for the jetty jars. It looks like there was an attempt to exclude those from
> packaging anyway via maven-war-plugin configs, but those configs aren't
> working.
> patch:
> {code}
> diff --git a/activemq-web-console/pom.xml b/activemq-web-console/pom.xml
> index e5f2e94..93b7fad 100755
> --- a/activemq-web-console/pom.xml
>
>
> -
> - xpp3
> - xpp3
> -
> -
> - com.thoughtworks.xstream
> - xstream
> -
> -
>
>
>junit
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (AMQNET-470) Allow Setting Callback after sending command asynchronously via Transport.
[ https://issues.apache.org/jira/browse/AMQNET-470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13894019#comment-13894019 ] Jim Gomes commented on AMQNET-470: -- I vote for Tim's suggested implementation. > Allow Setting Callback after sending command asynchronously via Transport. > -- > > Key: AMQNET-470 > URL: https://issues.apache.org/jira/browse/AMQNET-470 > Project: ActiveMQ .Net > Issue Type: New Feature > Components: NMS >Reporter: Shani Elharrar >Assignee: Jim Gomes >Priority: Minor > Labels: easyfix, features, newbie > Original Estimate: 2h > Remaining Estimate: 2h > > Hi. > I have a "system" that processes a lot of messages (~3000 per second) > asynchronously. I'm trying to move to ActiveMQ as the primary message broker. > My configuration is that I consume messages from ActiveMQ queue (Using > individual Acks), I do some processing, And then send them to another queue > (In the ActiveMQ). Transactions aren't so Important to me since I can handle > message duplicates in case of crash. But I do want to Ack the messages only > after I send them to the ActiveMQ. > So I want to have a Callback after sending the message Asynchronously to > ActiveMQ. > I managed to edit NMS code to support this, What i've done is : > * Added "Callbackable" interface with one property (setter & getter) which is > a delegate equivalent to Action (void, empty arguments). > * Modified Command and IActiveMQMessage to "extend" that interface > * Modified CommandBase to implement the interface (Trivial setter/getter) > * Modified TCPTransport.Oneway method to check if the callback isn't null and > if not - invoke it (After it marshals the message). > And it worked flawlessly. > First of all, I need you to vote in/against the feature, And if it's accepted > - I'm willing to create a patch for this. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (AMQNET-470) Allow Setting Callback after sending command asynchronously via Transport.
[ https://issues.apache.org/jira/browse/AMQNET-470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13894004#comment-13894004 ] Timothy Bish commented on AMQNET-470: - If we wanted to add something like this I think we should go the route that was taken in: https://issues.apache.org/jira/browse/AMQ-3769 We could add a new send method to the NMS API that accepts a delegate to invoke on send completion. This is better than your suggested option as it ties the mechanics to specific transport and message objects. It would be better to make this an optional NMS API method where client's could throw OperationNotSupported or whatever the .NET exception is for that. > Allow Setting Callback after sending command asynchronously via Transport. > -- > > Key: AMQNET-470 > URL: https://issues.apache.org/jira/browse/AMQNET-470 > Project: ActiveMQ .Net > Issue Type: New Feature > Components: NMS >Reporter: Shani Elharrar >Assignee: Jim Gomes >Priority: Minor > Labels: easyfix, features, newbie > Original Estimate: 2h > Remaining Estimate: 2h > > Hi. > I have a "system" that processes a lot of messages (~3000 per second) > asynchronously. I'm trying to move to ActiveMQ as the primary message broker. > My configuration is that I consume messages from ActiveMQ queue (Using > individual Acks), I do some processing, And then send them to another queue > (In the ActiveMQ). Transactions aren't so Important to me since I can handle > message duplicates in case of crash. But I do want to Ack the messages only > after I send them to the ActiveMQ. > So I want to have a Callback after sending the message Asynchronously to > ActiveMQ. > I managed to edit NMS code to support this, What i've done is : > * Added "Callbackable" interface with one property (setter & getter) which is > a delegate equivalent to Action (void, empty arguments). > * Modified Command and IActiveMQMessage to "extend" that interface > * Modified CommandBase to implement the interface (Trivial setter/getter) > * Modified TCPTransport.Oneway method to check if the callback isn't null and > if not - invoke it (After it marshals the message). > And it worked flawlessly. > First of all, I need you to vote in/against the feature, And if it's accepted > - I'm willing to create a patch for this. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (AMQNET-469) Add support for self-signed broker certificates
[ https://issues.apache.org/jira/browse/AMQNET-469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQNET-469: Fix Version/s: 1.7.0 > Add support for self-signed broker certificates > --- > > Key: AMQNET-469 > URL: https://issues.apache.org/jira/browse/AMQNET-469 > Project: ActiveMQ .Net > Issue Type: Improvement >Reporter: Christoffer Sawicki >Assignee: Jim Gomes >Priority: Minor > Fix For: 1.7.0 > > Attachments: add-support-for-self-signed-broker-certificates.patch > > > ActiveMQ NMS does currently not support self-signed broker certificates since > doing so requires a custom > System.Net.Security.RemoteCertificateValidationCallback AFAIK. > The attached patch adds the new configuration option "brokerCertFilename" to > SslTransport(Factory) that when used enables an alternative > RemoteCertificateValidationCallback that supports self-signed certificates > through direct certificate comparison. > Note #1: The patch does currently not include an automated test, but I'm > willing to work on that if that's the only obstacle for integration. > Note #2: Apache.NMS.Stomp could/should be patched the same way. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (AMQNET-469) Add support for self-signed broker certificates
[ https://issues.apache.org/jira/browse/AMQNET-469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQNET-469. - Resolution: Fixed Assignee: Timothy Bish (was: Jim Gomes) Fix applied on trunk. > Add support for self-signed broker certificates > --- > > Key: AMQNET-469 > URL: https://issues.apache.org/jira/browse/AMQNET-469 > Project: ActiveMQ .Net > Issue Type: Improvement >Reporter: Christoffer Sawicki >Assignee: Timothy Bish >Priority: Minor > Fix For: 1.7.0 > > Attachments: add-support-for-self-signed-broker-certificates.patch > > > ActiveMQ NMS does currently not support self-signed broker certificates since > doing so requires a custom > System.Net.Security.RemoteCertificateValidationCallback AFAIK. > The attached patch adds the new configuration option "brokerCertFilename" to > SslTransport(Factory) that when used enables an alternative > RemoteCertificateValidationCallback that supports self-signed certificates > through direct certificate comparison. > Note #1: The patch does currently not include an automated test, but I'm > willing to work on that if that's the only obstacle for integration. > Note #2: Apache.NMS.Stomp could/should be patched the same way. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (AMQ-5025) activemq-admin help is misleading
[ https://issues.apache.org/jira/browse/AMQ-5025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13893957#comment-13893957 ] Damien B commented on AMQ-5025: --- Related to https://issues.apache.org/jira/browse/AMQ-3082 , it's in fact a bug. The fact that it's working with the non-JMX commands is because org.apache.activemq.console.command.AbstractCommand is cheating the java executable by parsing itself the -D JVM properties whereas org.apache.activemq.console.command.AbstractJmxCommand does not. > activemq-admin help is misleading > - > > Key: AMQ-5025 > URL: https://issues.apache.org/jira/browse/AMQ-5025 > Project: ActiveMQ > Issue Type: Improvement > Components: Documentation >Affects Versions: 5.8.0 >Reporter: Damien B > > When run without arguments, activemq-admin displays this: > [...] > JMX system property options: > -Dactivemq.jmx.url= (default is: > 'service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi') > -Dactivemq.jmx.user= > -Dactivemq.jmx.password= > Which leads to think that you can pass somehow those arguments on the command > line. > But either > ./activemq-admin bstat > -Dactivemq.jmx.url=service:jmx:rmi:///jndi/rmi://localhost:/jmxrmi > or > ./activemq-admin > -Dactivemq.jmx.url=service:jmx:rmi:///jndi/rmi://localhost:/jmxrmi bstat > are accepted by the script, and lead to the seame result: > Connecting to JMX URL: service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi > because activemq-admin does not forward those arguments to Main.class: > JVM args: -Dactivemq.classpath=/master/conf; -Dactivemq.home=/master > -Dactivemq.base=/master -Dactivemq.conf=/master/conf > -Dactivemq.data=/master/data -Djava.io.tmpdir=/master/tmp > Those arguments should either be forwarded, or there should be a prominent > warning that the help doesn't apply to the activemq-admin script. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (AMQ-4174) Deleting/moving a message from queue overview should redirect back to overview of the queue
[ https://issues.apache.org/jira/browse/AMQ-4174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp resolved AMQ-4174. -- Resolution: Fixed Fix Version/s: 5.10.0 Assignee: Daniel Kulp > Deleting/moving a message from queue overview should redirect back to > overview of the queue > --- > > Key: AMQ-4174 > URL: https://issues.apache.org/jira/browse/AMQ-4174 > Project: ActiveMQ > Issue Type: Improvement > Components: webconsole >Affects Versions: 5.7.0 >Reporter: Torbjørn Skyberg Knutsen >Assignee: Daniel Kulp >Priority: Minor > Fix For: 5.10.0 > > Attachments: AMQ4174.patch > > > When one deletes a message from the overview of a queue, one is redirected to > the overview showing all queues. This makes deleting multiple messages > tedious work, since you have to find the queue to delete from for each > message that you want to delete. The same goes for moving a message, you get > thrown back to start instead of the queue overview, which would be nice in > cases where you want to move multiple messages in the same queue (which is > quite often, specially for dead-letter queues). > Is it possible to change the redirect to the overview of the queue that was > moved/deleted from? -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (AMQ-5027) Using maven-eclipse-plugin to generate eclipse projects fails for leveldb
[ https://issues.apache.org/jira/browse/AMQ-5027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp resolved AMQ-5027. -- Resolution: Fixed Fix Version/s: 5.10.0 > Using maven-eclipse-plugin to generate eclipse projects fails for leveldb > - > > Key: AMQ-5027 > URL: https://issues.apache.org/jira/browse/AMQ-5027 > Project: ActiveMQ > Issue Type: Bug >Reporter: Daniel Kulp >Assignee: Daniel Kulp > Fix For: 5.10.0 > > > The scala stuff in activemq-leveldb-store causes problems if you generate an > eclipse project using the maven-eclipse-plugin. Couple things need to be > done: > 1) Add the scala nature so its created as a scala project instead of java > 2) Add the scala dirs as source dirs so eclipse see's them as source and will > compile them. > git pull request coming -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (AMQ-5029) embedded webconsole broker does not resolve activemq.data system property
[
https://issues.apache.org/jira/browse/AMQ-5029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Kulp resolved AMQ-5029.
--
Resolution: Fixed
Fix Version/s: 5.10.0
> embedded webconsole broker does not resolve activemq.data system property
> -
>
> Key: AMQ-5029
> URL: https://issues.apache.org/jira/browse/AMQ-5029
> Project: ActiveMQ
> Issue Type: Bug
> Components: webconsole
>Affects Versions: 5.9.0
>Reporter: Daniel Kulp
>Assignee: Daniel Kulp
> Fix For: 5.10.0
>
>
> When using jetty:run in activemq-web-console or deploying the war into
> tomcat, the activemq.data system property is not resolved into a directory
> name for the kahadb. Thus, a ${acitvemq.data} directory is created which is
> strange looking. The property placeholder thing needs to be added to the
> spring config.
--
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=13893753#comment-13893753 ] 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-connection-property-table-17.patch, > 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] [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-add-connection-property-table-17.patch This patch (-17) allows users to specify ConnectionFactory connection properties through a Hashtable in addition to the nonstandard params strings. > 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-connection-property-table-17.patch, > 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] [Resolved] (AMQ-4813) webconsole - Viewing message details when message ID contains a plus results in " No message could be found for ID {messageID}"
[
https://issues.apache.org/jira/browse/AMQ-4813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arthur Naseef resolved AMQ-4813.
Resolution: Fixed
Fix Version/s: 5.10.0
Fixed. Added url-encoding of the message view and delete links using .
> webconsole - Viewing message details when message ID contains a plus results
> in " No message could be found for ID {messageID}"
> ---
>
> Key: AMQ-4813
> URL: https://issues.apache.org/jira/browse/AMQ-4813
> Project: ActiveMQ
> Issue Type: Bug
> Components: webconsole
>Affects Versions: 5.8.0
>Reporter: Michael Bildner
>Assignee: Arthur Naseef
>Priority: Minor
> Fix For: 5.10.0
>
>
> Steps to reproduce:
> # Using the admin console, go to the Queues page.
> # Click on one of the queues to get to the queue's browse page.
> # Click on a message ID that contains a plus sign (+).
> Expected:
> See the message's headers, properties, actions, and details.
> Actual:
> Get a page with the error message "No message could be found for ID
> {messageID}", where {messageID} contains the message ID clicked on. Note
> that the message ID displayed in the error message replaces the plus sign (+)
> with a space.
> Underlying cause:
> The html link that is created for each message ID in the queue's browse page
> does not properly URL encode the message ID. In my particular example, the
> link for message ID "AgXkceW74zCq+kZB1llPos1QcmTfOziGAmWRuk1forI=" is:
>
> http://localhost:8161/admin/message.jsp?id=AgXkceW74zCq{color:red}+{color}kZB1llPos1QcmTfOziGAmWRuk1forI=&JMSDestination=AMQPTest
> when it should be:
>
> http://localhost:8161/admin/message.jsp?id=AgXkceW74zCq{color:red}%2B{color}kZB1llPos1QcmTfOziGAmWRuk1forI=&JMSDestination=AMQPTest
> The trouble area is shown with a red font.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
Re: git commit: Redo upgrade to mqtt-client, it's been synced to a public repo. Also use new releases of stompjms and hawtdispatch to pick up bug fixes in those components.
I get all that. We also release all the projects with a bunch of known bugs that get deferred to a later release. My proposal is to revert the change and work with the qpid community to issue a patch release. Given your contributions to qpid I think you deserve to be a committer there. Given the proton ties to activemq this will benefit both communities. My $0.02, Hadrian On 02/06/2014 11:15 AM, Timothy Bish wrote: The bugs with the Proton libs are tracked here: https://issues.apache.org/jira/browse/AMQ-5004 https://issues.apache.org/jira/browse/AMQ-5032 On 02/06/2014 11:10 AM, Hiram Chirino wrote: Qpid project has not done a release with the patches we need. Yes, we have filed issue /w the Qpid project. So I've done my my own patch release of 0.6 + the patches we need to fix some AMQP related bugs. As soon as qpid does a release with the fixes we need, we can switch out to Qpid releases. This has been done in the past to workaround 3rd party bugs without having to fork the 3rd party library inside of the ActiveMQ project and without having to hold up the ActiveMQ releases for the 3rd party to do a new release /w the bug fixes. In case you wondering, the patch set can be found at https://github.com/fusesource/qpid-proton/tree/0.6.redhat Yes, it's still ASL. I guess we could release with the 0.6 jar but then that means releasing /w known bugs (that we have fixes for). Regards, Hiram On Thu, Feb 6, 2014 at 10:24 AM, Hadrian Zbarcea wrote: Moved to the dev@ list. On 02/06/2014 10:23 AM, Hadrian Zbarcea wrote: I missed the proton change in this commit. What is the reason to switch from an ASF version to a commercially controlled version? All that without a discuss or an explanation (except the after the fact commit message, that I actually missed the first time. Are we starting again? -1 please revert. Hadrian On 02/06/2014 09:01 AM, chir...@apache.org wrote: Updated Branches: refs/heads/trunk 50e4d0784 -> 3105e4d91 Redo upgrade to mqtt-client, it's been synced to a public repo. Also use new releases of stompjms and hawtdispatch to pick up bug fixes in those components. Upgrade to patched version of qpid-proton to fix bugs that affect performance and TTL handling. Project: http://git-wip-us.apache.org/repos/asf/activemq/repo Commit: http://git-wip-us.apache.org/repos/asf/activemq/commit/3105e4d9 Tree: http://git-wip-us.apache.org/repos/asf/activemq/tree/3105e4d9 Diff: http://git-wip-us.apache.org/repos/asf/activemq/diff/3105e4d9 Branch: refs/heads/trunk Commit: 3105e4d91a6ab5aaf073057a789822a5853cc433 Parents: 50e4d07 Author: Hiram Chirino Authored: Thu Feb 6 09:01:49 2014 -0500 Committer: Hiram Chirino Committed: Thu Feb 6 09:01:49 2014 -0500 -- pom.xml | 17 + 1 file changed, 13 insertions(+), 4 deletions(-) -- http://git-wip-us.apache.org/repos/asf/activemq/blob/3105e4d9/pom.xml -- diff --git a/pom.xml b/pom.xml index bed9ddd..8bdb405 100755 --- a/pom.xml +++ b/pom.xml @@ -64,7 +64,7 @@ 1.0 1.0.0 1.9 - 1.19 + 1.20 0.1.8 1.8.0.12 4.2.5 @@ -90,7 +90,7 @@ 0.6 1.8 1.2.17 - 1.7 + 1.8 1.2.0 10.10.1.1 4.3.1 @@ -98,7 +98,7 @@ 0.4.0 1.4.0 3.4.5 - 0.6 + 0.6.redhat-002 0.26-SNAPSHOT 1.3 1.0 @@ -124,7 +124,7 @@ 3.15 2.11.0 0.6.4 -1.18 +1.19 2.6.0 1.0.0 @@ -1591,6 +1591,15 @@ true false + + + + jboss.org-fs-releases + https://repository.jboss.org/nexus/content/repositories/fs-releases/ + true + false + +
Re: git commit: Redo upgrade to mqtt-client, it's been synced to a public repo. Also use new releases of stompjms and hawtdispatch to pick up bug fixes in those components.
The bugs with the Proton libs are tracked here: https://issues.apache.org/jira/browse/AMQ-5004 https://issues.apache.org/jira/browse/AMQ-5032 On 02/06/2014 11:10 AM, Hiram Chirino wrote: Qpid project has not done a release with the patches we need. Yes, we have filed issue /w the Qpid project. So I've done my my own patch release of 0.6 + the patches we need to fix some AMQP related bugs. As soon as qpid does a release with the fixes we need, we can switch out to Qpid releases. This has been done in the past to workaround 3rd party bugs without having to fork the 3rd party library inside of the ActiveMQ project and without having to hold up the ActiveMQ releases for the 3rd party to do a new release /w the bug fixes. In case you wondering, the patch set can be found at https://github.com/fusesource/qpid-proton/tree/0.6.redhat Yes, it's still ASL. I guess we could release with the 0.6 jar but then that means releasing /w known bugs (that we have fixes for). Regards, Hiram On Thu, Feb 6, 2014 at 10:24 AM, Hadrian Zbarcea wrote: Moved to the dev@ list. On 02/06/2014 10:23 AM, Hadrian Zbarcea wrote: I missed the proton change in this commit. What is the reason to switch from an ASF version to a commercially controlled version? All that without a discuss or an explanation (except the after the fact commit message, that I actually missed the first time. Are we starting again? -1 please revert. Hadrian On 02/06/2014 09:01 AM, chir...@apache.org wrote: Updated Branches: refs/heads/trunk 50e4d0784 -> 3105e4d91 Redo upgrade to mqtt-client, it's been synced to a public repo. Also use new releases of stompjms and hawtdispatch to pick up bug fixes in those components. Upgrade to patched version of qpid-proton to fix bugs that affect performance and TTL handling. Project: http://git-wip-us.apache.org/repos/asf/activemq/repo Commit: http://git-wip-us.apache.org/repos/asf/activemq/commit/3105e4d9 Tree: http://git-wip-us.apache.org/repos/asf/activemq/tree/3105e4d9 Diff: http://git-wip-us.apache.org/repos/asf/activemq/diff/3105e4d9 Branch: refs/heads/trunk Commit: 3105e4d91a6ab5aaf073057a789822a5853cc433 Parents: 50e4d07 Author: Hiram Chirino Authored: Thu Feb 6 09:01:49 2014 -0500 Committer: Hiram Chirino Committed: Thu Feb 6 09:01:49 2014 -0500 -- pom.xml | 17 + 1 file changed, 13 insertions(+), 4 deletions(-) -- http://git-wip-us.apache.org/repos/asf/activemq/blob/3105e4d9/pom.xml -- diff --git a/pom.xml b/pom.xml index bed9ddd..8bdb405 100755 --- a/pom.xml +++ b/pom.xml @@ -64,7 +64,7 @@ 1.0 1.0.0 1.9 - 1.19 + 1.20 0.1.8 1.8.0.12 4.2.5 @@ -90,7 +90,7 @@ 0.6 1.8 1.2.17 -1.7 +1.8 1.2.0 10.10.1.1 4.3.1 @@ -98,7 +98,7 @@ 0.4.0 1.4.0 3.4.5 -0.6 + 0.6.redhat-002 0.26-SNAPSHOT 1.3 1.0 @@ -124,7 +124,7 @@ 3.15 2.11.0 0.6.4 -1.18 +1.19 2.6.0 1.0.0 @@ -1591,6 +1591,15 @@ true false + + + + jboss.org-fs-releases + https://repository.jboss.org/nexus/content/repositories/fs-releases/ + true + false + + -- Tim Bish Sr Software Engineer | RedHat Inc. tim.b...@redhat.com | www.fusesource.com | www.redhat.com skype: tabish121 | twitter: @tabish121 blog: http://timbish.blogspot.com/
Re: git commit: Redo upgrade to mqtt-client, it's been synced to a public repo. Also use new releases of stompjms and hawtdispatch to pick up bug fixes in those components.
Qpid project has not done a release with the patches we need. Yes, we have filed issue /w the Qpid project. So I've done my my own patch release of 0.6 + the patches we need to fix some AMQP related bugs. As soon as qpid does a release with the fixes we need, we can switch out to Qpid releases. This has been done in the past to workaround 3rd party bugs without having to fork the 3rd party library inside of the ActiveMQ project and without having to hold up the ActiveMQ releases for the 3rd party to do a new release /w the bug fixes. In case you wondering, the patch set can be found at https://github.com/fusesource/qpid-proton/tree/0.6.redhat Yes, it's still ASL. I guess we could release with the 0.6 jar but then that means releasing /w known bugs (that we have fixes for). Regards, Hiram On Thu, Feb 6, 2014 at 10:24 AM, Hadrian Zbarcea wrote: > Moved to the dev@ list. > > On 02/06/2014 10:23 AM, Hadrian Zbarcea wrote: >> >> I missed the proton change in this commit. What is the reason to switch >> from an ASF version to a commercially controlled version? >> All that without a discuss or an explanation (except the after the fact >> commit message, that I actually missed the first time. Are we starting >> again? >> >> -1 please revert. >> >> Hadrian >> >> >> On 02/06/2014 09:01 AM, chir...@apache.org wrote: >>> >>> Updated Branches: >>>refs/heads/trunk 50e4d0784 -> 3105e4d91 >>> >>> >>> Redo upgrade to mqtt-client, it's been synced to a public repo. >>> Also use new releases of stompjms and hawtdispatch to pick up bug fixes >>> in those components. >>> >>> Upgrade to patched version of qpid-proton to fix bugs that affect >>> performance and TTL handling. >>> >>> Project: http://git-wip-us.apache.org/repos/asf/activemq/repo >>> Commit: http://git-wip-us.apache.org/repos/asf/activemq/commit/3105e4d9 >>> Tree: http://git-wip-us.apache.org/repos/asf/activemq/tree/3105e4d9 >>> Diff: http://git-wip-us.apache.org/repos/asf/activemq/diff/3105e4d9 >>> >>> Branch: refs/heads/trunk >>> Commit: 3105e4d91a6ab5aaf073057a789822a5853cc433 >>> Parents: 50e4d07 >>> Author: Hiram Chirino >>> Authored: Thu Feb 6 09:01:49 2014 -0500 >>> Committer: Hiram Chirino >>> Committed: Thu Feb 6 09:01:49 2014 -0500 >>> >>> -- >>> pom.xml | 17 + >>> 1 file changed, 13 insertions(+), 4 deletions(-) >>> -- >>> >>> >>> http://git-wip-us.apache.org/repos/asf/activemq/blob/3105e4d9/pom.xml >>> -- >>> diff --git a/pom.xml b/pom.xml >>> index bed9ddd..8bdb405 100755 >>> --- a/pom.xml >>> +++ b/pom.xml >>> @@ -64,7 +64,7 @@ >>> 1.0 >>> 1.0.0 >>> 1.9 >>> - 1.19 >>> + 1.20 >>> 0.1.8 >>> 1.8.0.12 >>> 4.2.5 >>> @@ -90,7 +90,7 @@ >>> 0.6 >>> 1.8 >>> 1.2.17 >>> -1.7 >>> +1.8 >>> 1.2.0 >>> 10.10.1.1 >>> 4.3.1 >>> @@ -98,7 +98,7 @@ >>> 0.4.0 >>> 1.4.0 >>> 3.4.5 >>> -0.6 >>> + 0.6.redhat-002 >>> 0.26-SNAPSHOT >>> 1.3 >>> 1.0 >>> @@ -124,7 +124,7 @@ >>> 3.15 >>> 2.11.0 >>> 0.6.4 >>> -1.18 >>> +1.19 >>> 2.6.0 >>> 1.0.0 >>> @@ -1591,6 +1591,15 @@ >>> true >>> false >>> >>> + >>> + >>> + >>> + jboss.org-fs-releases >>> + >>> https://repository.jboss.org/nexus/content/repositories/fs-releases/ >>> + true >>> + false >>> + >>> + >>> >>> >>> >> >> > -- Hiram Chirino Engineering | Red Hat, Inc. hchir...@redhat.com | fusesource.com | redhat.com skype: hiramchirino | twitter: @hiramchirino
[jira] [Created] (AMQ-5032) AMQP Message Expiry Time not mapped correctly in many case to / from JMS
Timothy Bish created AMQ-5032: - Summary: AMQP Message Expiry Time not mapped correctly in many case to / from JMS Key: AMQ-5032 URL: https://issues.apache.org/jira/browse/AMQ-5032 Project: ActiveMQ Issue Type: Bug Components: AMQP Affects Versions: 5.9.0 Reporter: Timothy Bish Assignee: Timothy Bish Priority: Blocker Fix For: 5.10.0 The message mapping done in Proton to convert to / from JMS messages is not currently handling expiration time conversion correctly leading to message that expire immediately or have no set expiration time etc. Refer to: https://issues.apache.org/jira/browse/PROTON-474 -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (AMQ-5004) Dispatching large messages over AMQP is very slow.
[ https://issues.apache.org/jira/browse/AMQ-5004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13893443#comment-13893443 ] Timothy Bish commented on AMQ-5004: --- Opened: https://issues.apache.org/jira/browse/PROTON-508 The issue is internal to the Proton engine and with the current implementation there's not a whole lot we can do to workaround it short of lifting their SASL parsing code and doing the processing ourselves without trigger SASL support in the proton code. I was able to create a patch for the proton code that works although causes some of their tests to fail. The end result was that the time on my machine to send a 10mb message went from 30+ seconds to around 300ms or so. > Dispatching large messages over AMQP is very slow. > -- > > Key: AMQ-5004 > URL: https://issues.apache.org/jira/browse/AMQ-5004 > Project: ActiveMQ > Issue Type: Bug > Components: AMQP >Affects Versions: 5.9.0 >Reporter: Timothy Bish >Priority: Critical > Fix For: 5.10.0 > > > When testing against the QPid JMS client we see that a producer sending large > messages 10mb+ is quite fast but a consumer takes exponentially longer to > receive the message. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (AMQ-5004) Dispatching large messages over AMQP is very slow.
[ https://issues.apache.org/jira/browse/AMQ-5004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQ-5004: -- Priority: Blocker (was: Critical) > Dispatching large messages over AMQP is very slow. > -- > > Key: AMQ-5004 > URL: https://issues.apache.org/jira/browse/AMQ-5004 > Project: ActiveMQ > Issue Type: Bug > Components: AMQP >Affects Versions: 5.9.0 >Reporter: Timothy Bish >Priority: Blocker > Fix For: 5.10.0 > > > When testing against the QPid JMS client we see that a producer sending large > messages 10mb+ is quite fast but a consumer takes exponentially longer to > receive the message. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
Re: git commit: Redo upgrade to mqtt-client, it's been synced to a public repo. Also use new releases of stompjms and hawtdispatch to pick up bug fixes in those components.
Moved to the dev@ list. On 02/06/2014 10:23 AM, Hadrian Zbarcea wrote: I missed the proton change in this commit. What is the reason to switch from an ASF version to a commercially controlled version? All that without a discuss or an explanation (except the after the fact commit message, that I actually missed the first time. Are we starting again? -1 please revert. Hadrian On 02/06/2014 09:01 AM, chir...@apache.org wrote: Updated Branches: refs/heads/trunk 50e4d0784 -> 3105e4d91 Redo upgrade to mqtt-client, it's been synced to a public repo. Also use new releases of stompjms and hawtdispatch to pick up bug fixes in those components. Upgrade to patched version of qpid-proton to fix bugs that affect performance and TTL handling. Project: http://git-wip-us.apache.org/repos/asf/activemq/repo Commit: http://git-wip-us.apache.org/repos/asf/activemq/commit/3105e4d9 Tree: http://git-wip-us.apache.org/repos/asf/activemq/tree/3105e4d9 Diff: http://git-wip-us.apache.org/repos/asf/activemq/diff/3105e4d9 Branch: refs/heads/trunk Commit: 3105e4d91a6ab5aaf073057a789822a5853cc433 Parents: 50e4d07 Author: Hiram Chirino Authored: Thu Feb 6 09:01:49 2014 -0500 Committer: Hiram Chirino Committed: Thu Feb 6 09:01:49 2014 -0500 -- pom.xml | 17 + 1 file changed, 13 insertions(+), 4 deletions(-) -- http://git-wip-us.apache.org/repos/asf/activemq/blob/3105e4d9/pom.xml -- diff --git a/pom.xml b/pom.xml index bed9ddd..8bdb405 100755 --- a/pom.xml +++ b/pom.xml @@ -64,7 +64,7 @@ 1.0 1.0.0 1.9 - 1.19 + 1.20 0.1.8 1.8.0.12 4.2.5 @@ -90,7 +90,7 @@ 0.6 1.8 1.2.17 -1.7 +1.8 1.2.0 10.10.1.1 4.3.1 @@ -98,7 +98,7 @@ 0.4.0 1.4.0 3.4.5 -0.6 + 0.6.redhat-002 0.26-SNAPSHOT 1.3 1.0 @@ -124,7 +124,7 @@ 3.15 2.11.0 0.6.4 -1.18 +1.19 2.6.0 1.0.0 @@ -1591,6 +1591,15 @@ true false + + + + jboss.org-fs-releases + https://repository.jboss.org/nexus/content/repositories/fs-releases/ + true + false + +
[jira] [Resolved] (AMQ-5031) Allow isSameRM override from broker identity to connection identity to avoid xa.join
[ https://issues.apache.org/jira/browse/AMQ-5031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully resolved AMQ-5031. - Resolution: Fixed fix in http://git-wip-us.apache.org/repos/asf/activemq/commit/221a751d > Allow isSameRM override from broker identity to connection identity to avoid > xa.join > > > Key: AMQ-5031 > URL: https://issues.apache.org/jira/browse/AMQ-5031 > Project: ActiveMQ > Issue Type: Improvement > Components: JMS client >Affects Versions: 5.9.0 >Reporter: Gary Tully >Assignee: Gary Tully >Priority: Minor > Labels: 2pc, isSameRm, join, xa > Fix For: 5.10.0 > > > When two connection are involved in an xa transaction, 1pc is great and > basing the xaresource identity on the broker identity makes sense. However in > the cases that an joined xa association is not ended, which seems ok from an > xa perspective, a joined association is left in error. > To avoid this, we need a way to force 2pc across multiple connections to the > same broker. > A broker url param like jms.rmIdFromConnectionId=true will do the trick and > ensure that the RM identity is tied to the connection and not the broker. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (AMQ-5031) Allow isSameRM override from broker identity to connection identity to avoid xa.join
Gary Tully created AMQ-5031: --- Summary: Allow isSameRM override from broker identity to connection identity to avoid xa.join Key: AMQ-5031 URL: https://issues.apache.org/jira/browse/AMQ-5031 Project: ActiveMQ Issue Type: Improvement Components: JMS client Affects Versions: 5.9.0 Reporter: Gary Tully Assignee: Gary Tully Priority: Minor Fix For: 5.10.0 When two connection are involved in an xa transaction, 1pc is great and basing the xaresource identity on the broker identity makes sense. However in the cases that an joined xa association is not ended, which seems ok from an xa perspective, a joined association is left in error. To avoid this, we need a way to force 2pc across multiple connections to the same broker. A broker url param like jms.rmIdFromConnectionId=true will do the trick and ensure that the RM identity is tied to the connection and not the broker. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
Re: git commit: Redo upgrade to mqtt-client, it's been synced to a public repo. Also use new releases of stompjms and hawtdispatch to pick up bug fixes in those components.
Cool. Thanks Hiram and Tim. The builds were failing yesterday. Hadrian On 02/06/2014 09:01 AM, chir...@apache.org wrote: Updated Branches: refs/heads/trunk 50e4d0784 -> 3105e4d91 Redo upgrade to mqtt-client, it's been synced to a public repo. Also use new releases of stompjms and hawtdispatch to pick up bug fixes in those components. Upgrade to patched version of qpid-proton to fix bugs that affect performance and TTL handling. Project: http://git-wip-us.apache.org/repos/asf/activemq/repo Commit: http://git-wip-us.apache.org/repos/asf/activemq/commit/3105e4d9 Tree: http://git-wip-us.apache.org/repos/asf/activemq/tree/3105e4d9 Diff: http://git-wip-us.apache.org/repos/asf/activemq/diff/3105e4d9 Branch: refs/heads/trunk Commit: 3105e4d91a6ab5aaf073057a789822a5853cc433 Parents: 50e4d07 Author: Hiram Chirino Authored: Thu Feb 6 09:01:49 2014 -0500 Committer: Hiram Chirino Committed: Thu Feb 6 09:01:49 2014 -0500 -- pom.xml | 17 + 1 file changed, 13 insertions(+), 4 deletions(-) -- http://git-wip-us.apache.org/repos/asf/activemq/blob/3105e4d9/pom.xml -- diff --git a/pom.xml b/pom.xml index bed9ddd..8bdb405 100755 --- a/pom.xml +++ b/pom.xml @@ -64,7 +64,7 @@ 1.0 1.0.0 1.9 -1.19 +1.20 0.1.8 1.8.0.12 4.2.5 @@ -90,7 +90,7 @@ 0.6 1.8 1.2.17 -1.7 +1.8 1.2.0 10.10.1.1 4.3.1 @@ -98,7 +98,7 @@ 0.4.0 1.4.0 3.4.5 -0.6 +0.6.redhat-002 0.26-SNAPSHOT 1.3 1.0 @@ -124,7 +124,7 @@ 3.15 2.11.0 0.6.4 -1.18 +1.19 2.6.0 1.0.0 @@ -1591,6 +1591,15 @@ true false + + + + jboss.org-fs-releases + https://repository.jboss.org/nexus/content/repositories/fs-releases/ + true + false + + -- Hadrian Zbarcea Principal Software Architect Talend, Inc http://coders.talend.com/ http://camelbot.blogspot.com/
activemq pull request: [AMQ-5027] Get mvn eclipse:eclipse work for the leve...
Github user dkulp closed the pull request at: https://github.com/apache/activemq/pull/13
activemq pull request: [AMQ-4994] Remove site-mesh
Github user dkulp closed the pull request at: https://github.com/apache/activemq/pull/10
Re: [HEADS-UP] ActiveMQ 5.10.0 release
Will do. Looks like we're waiting for the vote on cxf 2.7.10 then. As soon as artifacts are published I'll release camel and then activemq. Hadrian On 02/06/2014 02:50 AM, Claus Ibsen wrote: On Thu, Feb 6, 2014 at 12:25 AM, Paul Gale wrote: Hi, If release 5.10.0 of ActiveMQ is going to be cut then you might as well update the bundled Camel from 2.12.1 to 2.12.2, no? According to the Camel site this dot release contains 145 fixes. Yes I have logged ticket for this https://issues.apache.org/jira/browse/AMQ-5030 We need to release Camel first and then upgrade AMQ to include the latest Camel release. The Camel source code on 2.12 branch is ready for release, so if you have free cycles then IMHO its better to start with Camel and then afterwards AMQ. Thanks, Paul On Wed, Feb 5, 2014 at 3:32 PM, wrote: Hi Hadrian, I have some OSGi related enhancements and fixes to push, but nothing blocker for the release (the blockers haven been already pushed). Regards JB On 2014-02-05 18:15, Hadrian Zbarcea wrote: I have enough cycles to cut a 5.10.0 this week off of the current trunk as Hiram suggested. Is there any issue/fix I should wait for? Thanks, 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] [Commented] (AMQNET-470) Allow Setting Callback after sending command asynchronously via Transport.
[ https://issues.apache.org/jira/browse/AMQNET-470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13893180#comment-13893180 ] Shani Elharrar commented on AMQNET-470: --- More on the use case : I have a "pipeline" of 4 service types (Each service may have more then one instance), The first service get's information from outside source,he does some processing, and sending it to a queue, which from the second service reads information, and it goes on until the last service, Which writes down the processed information to a database. The pieces of informations that runs between the services have updates, But we do know when the last update is arrived. The way we use to scale the services horizontally is using the "Message Groups" feature of Active MQ (Giving each message a message group id and sequence number, We do add "-1" on the last update). Because those services processes a lot of messages per second, We have inside those services a lot of (async) actors which processes the messages and pass them along, Until the last actor which sends the message to next "queue" (From which the next server read and continues the process). Because the asynchronous nature of those services, They have between 500 to 1000 messages (This can be modified) from the queue which they read from messages in every given moment that haven't been Ack'ed, We're going to use Individual Acks, And to "Ack" the messages after the've been sent to the following queue. We do use persistent messaging, But it's to slow for this rate of messages, So we want to force "async" send, And for this we need a callback for every message that is sent, And in the callback we'll call the Ack. Also I want to note that it's fine to process the same message again if one of the services has fallen down and a message has been sent to the following server but haven't been Ack'd. Those services can handle that. > Allow Setting Callback after sending command asynchronously via Transport. > -- > > Key: AMQNET-470 > URL: https://issues.apache.org/jira/browse/AMQNET-470 > Project: ActiveMQ .Net > Issue Type: New Feature > Components: NMS >Reporter: Shani Elharrar >Assignee: Jim Gomes >Priority: Minor > Labels: easyfix, features, newbie > Original Estimate: 2h > Remaining Estimate: 2h > > Hi. > I have a "system" that processes a lot of messages (~3000 per second) > asynchronously. I'm trying to move to ActiveMQ as the primary message broker. > My configuration is that I consume messages from ActiveMQ queue (Using > individual Acks), I do some processing, And then send them to another queue > (In the ActiveMQ). Transactions aren't so Important to me since I can handle > message duplicates in case of crash. But I do want to Ack the messages only > after I send them to the ActiveMQ. > So I want to have a Callback after sending the message Asynchronously to > ActiveMQ. > I managed to edit NMS code to support this, What i've done is : > * Added "Callbackable" interface with one property (setter & getter) which is > a delegate equivalent to Action (void, empty arguments). > * Modified Command and IActiveMQMessage to "extend" that interface > * Modified CommandBase to implement the interface (Trivial setter/getter) > * Modified TCPTransport.Oneway method to check if the callback isn't null and > if not - invoke it (After it marshals the message). > And it worked flawlessly. > First of all, I need you to vote in/against the feature, And if it's accepted > - I'm willing to create a patch for this. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (AMQ-4813) webconsole - Viewing message details when message ID contains a plus results in " No message could be found for ID {messageID}"
[
https://issues.apache.org/jira/browse/AMQ-4813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13893158#comment-13893158
]
Arthur Naseef commented on AMQ-4813:
I put a plus in my hostname for now to do the trick.
> webconsole - Viewing message details when message ID contains a plus results
> in " No message could be found for ID {messageID}"
> ---
>
> Key: AMQ-4813
> URL: https://issues.apache.org/jira/browse/AMQ-4813
> Project: ActiveMQ
> Issue Type: Bug
> Components: webconsole
>Affects Versions: 5.8.0
>Reporter: Michael Bildner
>Assignee: Arthur Naseef
>Priority: Minor
>
> Steps to reproduce:
> # Using the admin console, go to the Queues page.
> # Click on one of the queues to get to the queue's browse page.
> # Click on a message ID that contains a plus sign (+).
> Expected:
> See the message's headers, properties, actions, and details.
> Actual:
> Get a page with the error message "No message could be found for ID
> {messageID}", where {messageID} contains the message ID clicked on. Note
> that the message ID displayed in the error message replaces the plus sign (+)
> with a space.
> Underlying cause:
> The html link that is created for each message ID in the queue's browse page
> does not properly URL encode the message ID. In my particular example, the
> link for message ID "AgXkceW74zCq+kZB1llPos1QcmTfOziGAmWRuk1forI=" is:
>
> http://localhost:8161/admin/message.jsp?id=AgXkceW74zCq{color:red}+{color}kZB1llPos1QcmTfOziGAmWRuk1forI=&JMSDestination=AMQPTest
> when it should be:
>
> http://localhost:8161/admin/message.jsp?id=AgXkceW74zCq{color:red}%2B{color}kZB1llPos1QcmTfOziGAmWRuk1forI=&JMSDestination=AMQPTest
> The trouble area is shown with a red font.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (AMQ-4813) webconsole - Viewing message details when message ID contains a plus results in " No message could be found for ID {messageID}"
[
https://issues.apache.org/jira/browse/AMQ-4813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13893149#comment-13893149
]
Arthur Naseef commented on AMQ-4813:
Can you provide example code that creates a message with one of those IDs?
> webconsole - Viewing message details when message ID contains a plus results
> in " No message could be found for ID {messageID}"
> ---
>
> Key: AMQ-4813
> URL: https://issues.apache.org/jira/browse/AMQ-4813
> Project: ActiveMQ
> Issue Type: Bug
> Components: webconsole
>Affects Versions: 5.8.0
>Reporter: Michael Bildner
>Assignee: Arthur Naseef
>Priority: Minor
>
> Steps to reproduce:
> # Using the admin console, go to the Queues page.
> # Click on one of the queues to get to the queue's browse page.
> # Click on a message ID that contains a plus sign (+).
> Expected:
> See the message's headers, properties, actions, and details.
> Actual:
> Get a page with the error message "No message could be found for ID
> {messageID}", where {messageID} contains the message ID clicked on. Note
> that the message ID displayed in the error message replaces the plus sign (+)
> with a space.
> Underlying cause:
> The html link that is created for each message ID in the queue's browse page
> does not properly URL encode the message ID. In my particular example, the
> link for message ID "AgXkceW74zCq+kZB1llPos1QcmTfOziGAmWRuk1forI=" is:
>
> http://localhost:8161/admin/message.jsp?id=AgXkceW74zCq{color:red}+{color}kZB1llPos1QcmTfOziGAmWRuk1forI=&JMSDestination=AMQPTest
> when it should be:
>
> http://localhost:8161/admin/message.jsp?id=AgXkceW74zCq{color:red}%2B{color}kZB1llPos1QcmTfOziGAmWRuk1forI=&JMSDestination=AMQPTest
> The trouble area is shown with a red font.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
