Re: AMQ Browser Pagination

[Zakeria Hassan]

Hi Arthur,

I agree. I can make these fixes and push updated code in.


On Tue, Feb 18, 2014 at 11:13 PM, artnaseef  wrote:

> Also found this in the url creation for the DELETE action:
>
>
>
> http://localhost:8161/admin/deleteMessage.action?JMSDestination=TEST&messageId=
>
> Note the fixed destination name.
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Re-AMQ-Browser-Pagination-tp4677818p4678111.html
> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
>

Re: AMQ Browser Pagination

[artnaseef]

Also found this in the url creation for the DELETE action:

 
http://localhost:8161/admin/deleteMessage.action?JMSDestination=TEST&messageId=

Note the fixed destination name.



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/Re-AMQ-Browser-Pagination-tp4677818p4678111.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

Re: AMQ Browser Pagination

[artnaseef]

I have it working directly from your repo right now.  I like the way the list
of messages looks with the update.

A couple of questions:

* How is the progress meter supposed to work?  When I open the page, I see a
half-filled progress meter that disappears as soon as the messages are
displayed.  Otherwise, the progress bar doesn't move at all.

* What happened to the original message display page?  Now when I click on a
message, I see what appears to be an XML dump of the message.




--
View this message in context: 
http://activemq.2283324.n4.nabble.com/Re-AMQ-Browser-Pagination-tp4677818p4678110.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

[jira] [Commented] (AMQ-2040) Improve message browsing

[Arthur Naseef (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMQ-2040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13904810#comment-13904810
 ] 

Arthur Naseef commented on AMQ-2040:


Is this for browsing messages from the webconsole?

> Improve message browsing
> 
>
> Key: AMQ-2040
> URL: https://issues.apache.org/jira/browse/AMQ-2040
> Project: ActiveMQ
>  Issue Type: Improvement
>  Components: Broker
>Affects Versions: 5.2.0
>Reporter: Dejan Bosanac
>Assignee: Dejan Bosanac
> Fix For: 5.10.0
>
>
> Currently the browse() method returns 400 messages (or all if there are less 
> than that). Allow configuring the number of messages returned and fetching  
> messages beyond first page with the method such as browse(int page).



--
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

[Arthur Naseef (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMQ-4998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arthur Naseef updated AMQ-4998:
---

Component/s: webconsole

> 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
>  Components: webconsole
>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] (AMQNET-454) Add Apache Qpid provider to NMS

[Timothy Bish (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMQNET-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13904595#comment-13904595
 ] 

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-hello-world-to-vs2008-18.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, RELEASE.txt, 
> 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

[Chuck Rolke (JIRA)]

 [ 
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-hello-world-to-vs2008-18.patch

Rooted at Apache.NMS.AMQP/trunk this patch (-18) updates the vs2008 solution to 
have parity with the vs2010 solution.
1. Adds net-2.0 as nant target framework
2. Adds the HelloWorld project to the vs2008-amqp solution
3. Freshens stale source file list in v2008 provider project
4. Use new version of Apache.Qpid dependency

These fixes are prerequisites for the unit tests.


> 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-hello-world-to-vs2008-18.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, RELEASE.txt, 
> 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 release 5.10?

[Paul Gale]

I hear that it has dependencies on a security update to Camel.

With that in mind what is the effective ETA of this release?

Thanks,
Paul

Re: Hung Producer

[Ashwini Kuntamukkala]

As per your suggestion I repeated the tests with JConsole monitoring for
broker and producer app. 

 
 

The producers fail in the matter of 2 minutes. 

The broker uses the following GC settings

-Xmx1G –Xms1G -XX:+UseG1GC -XX:NewRatio=4
-XX:InitiatingHeapOccupancyPercent=75



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/Hung-Producer-tp4678060p4678103.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

[jira] [Updated] (AMQ-3621) Integrate Apache Shiro with ActiveMQ as "security solution"

[Les Hazlewood (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMQ-3621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Les Hazlewood updated AMQ-3621:
---

Attachment: AMQ-3621.git.patch

Latest (correct) patch attached.

> Integrate Apache Shiro with ActiveMQ as "security solution"
> ---
>
> Key: AMQ-3621
> URL: https://issues.apache.org/jira/browse/AMQ-3621
> Project: ActiveMQ
>  Issue Type: New Feature
>Reporter: Cservenak, Tamas
>Assignee: Christian Posta
> Fix For: 5.10.0
>
> Attachments: AMQ-3621.git.patch
>
>
> Integrate Apache Shiro with ActiveMQ as "security solution".
> This would benefit for ActiveMQ to have support for a vast amount of already 
> existing solution (Realm implementations) that are out there for Shiro.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Updated] (AMQ-3621) Integrate Apache Shiro with ActiveMQ as "security solution"

[Les Hazlewood (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMQ-3621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Les Hazlewood updated AMQ-3621:
---

Attachment: (was: AMQ-3621.git.patch)

> Integrate Apache Shiro with ActiveMQ as "security solution"
> ---
>
> Key: AMQ-3621
> URL: https://issues.apache.org/jira/browse/AMQ-3621
> Project: ActiveMQ
>  Issue Type: New Feature
>Reporter: Cservenak, Tamas
>Assignee: Christian Posta
> Fix For: 5.10.0
>
> Attachments: AMQ-3621.git.patch
>
>
> Integrate Apache Shiro with ActiveMQ as "security solution".
> This would benefit for ActiveMQ to have support for a vast amount of already 
> existing solution (Realm implementations) that are out there for Shiro.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Comment Edited] (AMQ-3621) Integrate Apache Shiro with ActiveMQ as "security solution"

[Les Hazlewood (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMQ-3621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13904302#comment-13904302
 ] 

Les Hazlewood edited comment on AMQ-3621 at 2/18/14 5:54 PM:
-

[~ceposta], I noticed I removed something from the root pom by accident when 
cleaning up my project.  The following needs to be added back into the root pom:

{code:xml}

  

activemq-website

${staging.siteURL}/maven/${project.version}

   
   
 apache.snapshots.https
 Apache Development Snapshot Repository
 https://repository.apache.org/content/repositories/snapshots
 false
   

{code}

I'm deleting the existing .patch file and uploading a new one with this change.


was (Author: lhazlewood):
[~ceposta], I noticed I removed something from the root pom by accident when 
cleaning up my project.  The following needs to be added back into the root pom:

{code:xml}

  

activemq-website

${staging.siteURL}/maven/${project.version}

   
   
 apache.snapshots.https
 Apache Development Snapshot Repository
 https://repository.apache.org/content/repositories/snapshots
 false
   

{code}

> Integrate Apache Shiro with ActiveMQ as "security solution"
> ---
>
> Key: AMQ-3621
> URL: https://issues.apache.org/jira/browse/AMQ-3621
> Project: ActiveMQ
>  Issue Type: New Feature
>Reporter: Cservenak, Tamas
>Assignee: Christian Posta
> Fix For: 5.10.0
>
> Attachments: AMQ-3621.git.patch
>
>
> Integrate Apache Shiro with ActiveMQ as "security solution".
> This would benefit for ActiveMQ to have support for a vast amount of already 
> existing solution (Realm implementations) that are out there for Shiro.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Commented] (AMQ-3621) Integrate Apache Shiro with ActiveMQ as "security solution"

[Les Hazlewood (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMQ-3621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13904302#comment-13904302
 ] 

Les Hazlewood commented on AMQ-3621:


[~ceposta], I noticed I removed something from the root pom by accident when 
cleaning up my project.  The following needs to be added back into the root pom:

{code:xml}

  

activemq-website

${staging.siteURL}/maven/${project.version}

   
   
 apache.snapshots.https
 Apache Development Snapshot Repository
 https://repository.apache.org/content/repositories/snapshots
 false
   

{code}

> Integrate Apache Shiro with ActiveMQ as "security solution"
> ---
>
> Key: AMQ-3621
> URL: https://issues.apache.org/jira/browse/AMQ-3621
> Project: ActiveMQ
>  Issue Type: New Feature
>Reporter: Cservenak, Tamas
>Assignee: Christian Posta
> Fix For: 5.10.0
>
> Attachments: AMQ-3621.git.patch
>
>
> Integrate Apache Shiro with ActiveMQ as "security solution".
> This would benefit for ActiveMQ to have support for a vast amount of already 
> existing solution (Realm implementations) that are out there for Shiro.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Re: AMQ Browser Pagination

[Zakeria Hassan]

No problem.


On Tue, Feb 18, 2014 at 12:20 PM, artnaseef  wrote:

> After improving my remote-repo-git-skills, and realizing activemq's git has
> "trunk" instead of "master", I am closer to getting this merged.  Just need
> to find more time to dedicate to this.
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Re-AMQ-Browser-Pagination-tp4677818p4678097.html
> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
>

Re: AMQ Browser Pagination

[artnaseef]

After improving my remote-repo-git-skills, and realizing activemq's git has
"trunk" instead of "master", I am closer to getting this merged.  Just need
to find more time to dedicate to this.



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/Re-AMQ-Browser-Pagination-tp4677818p4678097.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

[jira] [Resolved] (AMQ-5060) Upgrade to xstream 1.4.7

[Jonathan Anstey (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMQ-5060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jonathan Anstey resolved AMQ-5060.
--

Resolution: Fixed

http://git-wip-us.apache.org/repos/asf/activemq/commit/c1cedb5c

> Upgrade to xstream 1.4.7
> 
>
> Key: AMQ-5060
> URL: https://issues.apache.org/jira/browse/AMQ-5060
> Project: ActiveMQ
>  Issue Type: Task
>Reporter: Jonathan Anstey
>Assignee: Jonathan Anstey
> Fix For: 5.10.0
>
>
> Fix for CVE-2013-7285



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Re: Hung Producer

[artnaseef]

Inactivity errors (InactivityIOException) like that point to either a very 
large network delay or a very slow JVM - either broker or client. 

When running the test, how does the GC activity, CPU and memory on the JVM for 
the broker and client look?

Sent from my iPhone

> On Feb 18, 2014, at 1:43 AM, "Ashwini Kuntamukkala [via ActiveMQ]" 
>  wrote:
> 
> I repeated the test with the following settings 
> 
> activemq.xml openwire transport connector 
> 
>  uri="nio://0.0.0.0:61616?maximumConnections=1000&wireformat.maxFrameSize=104857600&useQueueForAccept=false&wireFormat.maxInactivityDuration=0&transport.socketBufferSize=131072&transport.ioBufferSize=65536&transport.soTimeout=1&transport.soWriteTimeout=15000"/>
> 
> Client URL 
> broker.url=tcp://broker-machine:61616?jms.useAsyncSend=false&soWriteTimeout=15000
>  
> 
> This time the producers crash with the following exception 
> 
> [WARNING] 
> org.springframework.jms.UncategorizedJmsException: Uncategorized exception 
> occured during JMS processing; nested exception is javax.jms.JMSException: 
> Cannot send, channel has already failed: tcp://broker-machine:61616 
> at 
> org.springframework.jms.support.JmsUtils.convertJmsAccessException(Jm 
> sUtils.java:316) 
> at 
> org.springframework.jms.support.JmsAccessor.convertJmsAccessException 
> (JmsAccessor.java:168) 
> at 
> org.springframework.jms.core.JmsTemplate.execute(JmsTemplate.java:469 
> ) 
> at 
> org.springframework.jms.core.JmsTemplate.send(JmsTemplate.java:543) 
> at producer.ProducerTask.run(ProducerTask.java:43) 
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>  
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>  
> at java.lang.Thread.run(Thread.java:744)Caused by: 
> javax.jms.JMSException: Cannot send, channel has already failed: tcp: 
> //broker-machine:61616 
> at 
> org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:62)
>  
> at 
> org.apache.activemq.ActiveMQConnection.doAsyncSendPacket(ActiveMQConnection.java:1306)
>  
> at 
> org.apache.activemq.ActiveMQConnection.asyncSendPacket(ActiveMQConnection.java:1298)
>  
> at 
> org.apache.activemq.ActiveMQSession.(ActiveMQSession.java:252) 
> at 
> org.apache.activemq.ActiveMQConnection.createSession(ActiveMQConnection.java:334)
>  
> at 
> org.apache.activemq.pool.ConnectionPool$2.makeObject(ConnectionPool.java:105) 
> at 
> org.apache.activemq.pool.ConnectionPool$2.makeObject(ConnectionPool.java:90) 
> at 
> org.apache.commons.pool.impl.GenericKeyedObjectPool.borrowObject(GenericKeyedObjectPool.java:1220)
>  
> at 
> org.apache.activemq.pool.ConnectionPool.createSession(ConnectionPool.java:142)
>  
> at 
> org.apache.activemq.pool.PooledConnection.createSession(PooledConnection.java:174)
>  
> at 
> org.springframework.jms.support.JmsAccessor.createSession(JmsAccessor.java:196)
>  
> at 
> org.springframework.jms.core.JmsTemplate.execute(JmsTemplate.java:457) 
> ... 5 more 
> Caused by: org.apache.activemq.transport.InactivityIOException: Cannot send, 
> cha 
> nnel has already failed: tcp://10.12.44.82:61616 
> at 
> org.apache.activemq.transport.AbstractInactivityMonitor.doOnewaySend(AbstractInactivityMonitor.java:315)
> at 
> org.apache.activemq.transport.AbstractInactivityMonitor.oneway(AbstractInactivityMonitor.java:304)
>  
> at 
> org.apache.activemq.transport.TransportFilter.oneway(TransportFilter.java:85) 
> at 
> org.apache.activemq.transport.WireFormatNegotiator.oneway(WireFormatNegotiator.java:104)
>  
> at 
> org.apache.activemq.transport.TransportFilter.oneway(TransportFilter.java:85) 
> at 
> org.apache.activemq.transport.WriteTimeoutFilter.oneway(WriteTimeoutFilter.java:73)
>  
> at 
> org.apache.activemq.transport.MutexTransport.oneway(MutexTransport.java:68) 
> at 
> org.apache.activemq.transport.ResponseCorrelator.oneway(ResponseCorrelator.java:60)
>  
> at 
> org.apache.activemq.ActiveMQConnection.doAsyncSendPacket(ActiveMQConnection.java:1304)
>  
> 
> If you reply to this email, your message will be added to the discussion 
> below:
> http://activemq.2283324.n4.nabble.com/Hung-Producer-tp4678060p4678063.html
> To start a new topic under ActiveMQ - Dev, email 
> ml-node+s2283324n2368404...@n4.nabble.com 
> To unsubscribe from ActiveMQ - Dev, click here.
> NAML




--
View this message in context: 
http://activemq.2283324.n4.nabble.com/Hung-Producer-tp4678060p4678093.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

[jira] [Resolved] (AMQ-5064) Update QPid client to v0.26

[Timothy Bish (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMQ-5064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Timothy Bish resolved AMQ-5064.
---

Resolution: Fixed

updated on trunk.

> Update QPid client to v0.26
> ---
>
> Key: AMQ-5064
> URL: https://issues.apache.org/jira/browse/AMQ-5064
> Project: ActiveMQ
>  Issue Type: Task
>  Components: AMQP
>Affects Versions: 5.9.0
>Reporter: Timothy Bish
>Assignee: Timothy Bish
> Fix For: 5.10.0
>
>
> Update to latest release.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Created] (AMQ-5064) Update QPid client to v0.26

[Timothy Bish (JIRA)]

Timothy Bish created AMQ-5064:
-

 Summary: Update QPid client to v0.26
 Key: AMQ-5064
 URL: https://issues.apache.org/jira/browse/AMQ-5064
 Project: ActiveMQ
  Issue Type: Task
  Components: AMQP
Affects Versions: 5.9.0
Reporter: Timothy Bish
Assignee: Timothy Bish
 Fix For: 5.10.0


Update to latest release.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Commented] (AMQ-5061) MQTT Hierarchical Destination names may start with a leading '/', which must be ignored when mapping to ActiveMQ destination name

[Roger Light (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMQ-5061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13904161#comment-13904161
 ] 

Roger Light commented on AMQ-5061:
--

The assumption is incorrect I'm afraid.

foo/bar and /foo/bar are distinct topic names. It is easiest to reconcile what 
is happening if you imagine that the topics are foo/bar and ""/foo/bar - i.e. 
there is an empty hierarchy element at the beginning. This is consistent with 
the expectation that foo/bar and foo//bar are distinct topics. Again, think of 
this as like foo/""/bar with a zero length hierarchy element in the middle.

This also influences the way wildcards work. Subscribing to a topic # returns 
messages from both foo/bar and /foo/bar, but subscribing to /# would only 
return messages from /foo/bar. Likewise a subscription to +/foo/bar would 
return messages from /foo/bar because + matches against the empty hierarchy 
element.

> MQTT Hierarchical Destination names may start with a leading '/', which must 
> be ignored when mapping to ActiveMQ destination name
> -
>
> Key: AMQ-5061
> URL: https://issues.apache.org/jira/browse/AMQ-5061
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: MQTT
>Affects Versions: 5.9.0
>Reporter: Dhiraj Bokde
> Fix For: 5.10.0
>
> Attachments: AMQ-5061.patch
>
>
> MQTT hierarchical destination names use the '/' character to separate levels. 
>  The name may start with a '/', which indicates root level, so it must be 
> ignored when mapping to ActiveMQ destination names. This is required so that 
> both 'TopicA' and '/TopicA' map to the same ActiveMQ destination name 
> 'TopicA'. 



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Commented] (AMQ-3621) Integrate Apache Shiro with ActiveMQ as "security solution"

[Christian Posta (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMQ-3621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13904129#comment-13904129
 ] 

Christian Posta commented on AMQ-3621:
--

Thx Claus will take a look tonight.

> Integrate Apache Shiro with ActiveMQ as "security solution"
> ---
>
> Key: AMQ-3621
> URL: https://issues.apache.org/jira/browse/AMQ-3621
> Project: ActiveMQ
>  Issue Type: New Feature
>Reporter: Cservenak, Tamas
>Assignee: Christian Posta
> Fix For: 5.10.0
>
> Attachments: AMQ-3621.git.patch
>
>
> Integrate Apache Shiro with ActiveMQ as "security solution".
> This would benefit for ActiveMQ to have support for a vast amount of already 
> existing solution (Realm implementations) that are out there for Shiro.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Assigned] (AMQ-3621) Integrate Apache Shiro with ActiveMQ as "security solution"

[Christian Posta (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMQ-3621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Posta reassigned AMQ-3621:


Assignee: Christian Posta

> Integrate Apache Shiro with ActiveMQ as "security solution"
> ---
>
> Key: AMQ-3621
> URL: https://issues.apache.org/jira/browse/AMQ-3621
> Project: ActiveMQ
>  Issue Type: New Feature
>Reporter: Cservenak, Tamas
>Assignee: Christian Posta
> Fix For: 5.10.0
>
> Attachments: AMQ-3621.git.patch
>
>
> Integrate Apache Shiro with ActiveMQ as "security solution".
> This would benefit for ActiveMQ to have support for a vast amount of already 
> existing solution (Realm implementations) that are out there for Shiro.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Updated] (AMQ-3621) Integrate Apache Shiro with ActiveMQ as "security solution"

[Claus Ibsen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMQ-3621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen updated AMQ-3621:
-

Assignee: (was: Claus Ibsen)

> Integrate Apache Shiro with ActiveMQ as "security solution"
> ---
>
> Key: AMQ-3621
> URL: https://issues.apache.org/jira/browse/AMQ-3621
> Project: ActiveMQ
>  Issue Type: New Feature
>Reporter: Cservenak, Tamas
> Fix For: 5.10.0
>
> Attachments: AMQ-3621.git.patch
>
>
> Integrate Apache Shiro with ActiveMQ as "security solution".
> This would benefit for ActiveMQ to have support for a vast amount of already 
> existing solution (Realm implementations) that are out there for Shiro.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Commented] (AMQ-3621) Integrate Apache Shiro with ActiveMQ as "security solution"

[Claus Ibsen (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMQ-3621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13904123#comment-13904123
 ] 

Claus Ibsen commented on AMQ-3621:
--

Christian feel free to take over, i got to much important work stuff going on.

> Integrate Apache Shiro with ActiveMQ as "security solution"
> ---
>
> Key: AMQ-3621
> URL: https://issues.apache.org/jira/browse/AMQ-3621
> Project: ActiveMQ
>  Issue Type: New Feature
>Reporter: Cservenak, Tamas
> Fix For: 5.10.0
>
> Attachments: AMQ-3621.git.patch
>
>
> Integrate Apache Shiro with ActiveMQ as "security solution".
> This would benefit for ActiveMQ to have support for a vast amount of already 
> existing solution (Realm implementations) that are out there for Shiro.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Commented] (AMQ-3621) Integrate Apache Shiro with ActiveMQ as "security solution"

[Christian Posta (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMQ-3621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13904107#comment-13904107
 ] 

Christian Posta commented on AMQ-3621:
--

This looks awesome Les, thanks for the contribution. I'll let Claus take it 
from here as he's assigned to it, but I look forward to trying this out.

> Integrate Apache Shiro with ActiveMQ as "security solution"
> ---
>
> Key: AMQ-3621
> URL: https://issues.apache.org/jira/browse/AMQ-3621
> Project: ActiveMQ
>  Issue Type: New Feature
>Reporter: Cservenak, Tamas
>Assignee: Claus Ibsen
> Fix For: 5.10.0
>
> Attachments: AMQ-3621.git.patch
>
>
> Integrate Apache Shiro with ActiveMQ as "security solution".
> This would benefit for ActiveMQ to have support for a vast amount of already 
> existing solution (Realm implementations) that are out there for Shiro.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Updated] (AMQ-5063) when restarted, slaves do not really sync

[anselme dewavrin (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMQ-5063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

anselme dewavrin updated AMQ-5063:
--

Description: 
Dear All,

I worked several days on replication tests with 5.9 (and snapshot 5.10), using 
replicatedLevelDB configuration as explained on activemq website (details 
follow). Everything is replicated well as long as every node is up.

But if I 
-stop a slave,
-inject messages,
-restart it,
then I see in the logs that it "caught up". But if I make it become the master, 
the messages are not there...

Did I misunderstood the goal of replication ? Is this normal ?

Thank you all,
Anselme


For instance the conf of 2nd node is :

 
 
   


  was:
Dear All,

I worked several days on replication tests with 5.9 (and snapshot 5.10), using 
replicatedLevelDB configuration as explained on activemq website (details 
follow). Everything is replicated well as long as every node is up.

But if I 
-stop a slave,
-inject messages,
-restart it,
then I see in the logs that it "caught up". But if I make it become the master, 
the new messages are not there...

Did I misunderstood the goal of replication ? Is this normal ?

Thank you all,
Anselme


 
 
   




> when restarted, slaves do not really sync
> -
>
> Key: AMQ-5063
> URL: https://issues.apache.org/jira/browse/AMQ-5063
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: activemq-leveldb-store
>Affects Versions: 5.9.0
> Environment: debian 6, x86-64, jdk1.7
>Reporter: anselme dewavrin
>
> Dear All,
> I worked several days on replication tests with 5.9 (and snapshot 5.10), 
> using replicatedLevelDB configuration as explained on activemq website 
> (details follow). Everything is replicated well as long as every node is up.
> But if I 
> -stop a slave,
> -inject messages,
> -restart it,
> then I see in the logs that it "caught up". But if I make it become the 
> master, the messages are not there...
> Did I misunderstood the goal of replication ? Is this normal ?
> Thank you all,
> Anselme
> For instance the conf of 2nd node is :
>  
>  directory="/usr2/talend/activemq/data"
>sync="quorum_disk"
>weight="2"
>replicas="3"
>bind="tcp://awas02:1"
>zkAddress="awas01:2190,awas02:2190,awas10:2190"
>zkPassword="password"
>zkPath="/activemq/leveldb-stores"
>   hostname="awas02"
>   verifyChecksums="true"
>   paranoidChecks="true"
>   />
>



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Comment Edited] (AMQ-4987) io wait on replicated levelDB slaves

[anselme dewavrin (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMQ-4987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13903946#comment-13903946
 ] 

anselme dewavrin edited comment on AMQ-4987 at 2/18/14 12:55 PM:
-

After 3 weeks this fsync impeachment still works perfectly.

Anselme


was (Author: adewavrin):
After 3 weeks this fsync impeachment works perfectly.

Anselme

> io wait on replicated levelDB slaves
> 
>
> Key: AMQ-4987
> URL: https://issues.apache.org/jira/browse/AMQ-4987
> Project: ActiveMQ
>  Issue Type: Test
>  Components: activemq-leveldb-store
>Affects Versions: 5.9.0
> Environment: debian VM 2.6.32-5-amd64, jdk7
>Reporter: anselme dewavrin
>Priority: Minor
> Fix For: 5.9.0
>
>
> Dear all,
> I set up a 3-nodes replicatedLevelDB activeMQ cluster on 3 different 
> machines, as explained on the activemq site (with zookeeper etc.).
> I made a message injector using the php stomp client described here : 
> http://stomp.fusesource.org/documentation/php/book.html
> Then I injected persistent messages as fast as possible (giving about 100 
> messages/s, each message is 10k).
> Everything works fine, then I measured the servers' activity with "vmstat 1". 
> I saw no iowait on the master node, but  20% on both slaves. This would 
> impeach scalabitity I suppose. And the iowait is justified by 3000 bo/s 
> (blocks out) in the vmstat report.
> The machines are not swapping (paging).
> Here is what I tried, without success :
> -specify explicitly sync="quorum_mem"
> -JNI implementation of the leveldb store (and verified it is used)
> -setting flushDelay to 2000
> Does anyone have an idea that I could try ? Why is the leveldb slaves writing 
> so much to disk ?
> Many thanks in advance
> Yours,
> Anselme



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Comment Edited] (AMQ-4987) io wait on replicated levelDB slaves

[anselme dewavrin (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMQ-4987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13903946#comment-13903946
 ] 

anselme dewavrin edited comment on AMQ-4987 at 2/18/14 12:54 PM:
-

After 3 weeks this fsync impeachment works perfectly.

Anselme


was (Author: adewavrin):
This fsync impeachment works perfectly.

Anselme

> io wait on replicated levelDB slaves
> 
>
> Key: AMQ-4987
> URL: https://issues.apache.org/jira/browse/AMQ-4987
> Project: ActiveMQ
>  Issue Type: Test
>  Components: activemq-leveldb-store
>Affects Versions: 5.9.0
> Environment: debian VM 2.6.32-5-amd64, jdk7
>Reporter: anselme dewavrin
>Priority: Minor
> Fix For: 5.9.0
>
>
> Dear all,
> I set up a 3-nodes replicatedLevelDB activeMQ cluster on 3 different 
> machines, as explained on the activemq site (with zookeeper etc.).
> I made a message injector using the php stomp client described here : 
> http://stomp.fusesource.org/documentation/php/book.html
> Then I injected persistent messages as fast as possible (giving about 100 
> messages/s, each message is 10k).
> Everything works fine, then I measured the servers' activity with "vmstat 1". 
> I saw no iowait on the master node, but  20% on both slaves. This would 
> impeach scalabitity I suppose. And the iowait is justified by 3000 bo/s 
> (blocks out) in the vmstat report.
> The machines are not swapping (paging).
> Here is what I tried, without success :
> -specify explicitly sync="quorum_mem"
> -JNI implementation of the leveldb store (and verified it is used)
> -setting flushDelay to 2000
> Does anyone have an idea that I could try ? Why is the leveldb slaves writing 
> so much to disk ?
> Many thanks in advance
> Yours,
> Anselme



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Created] (AMQ-5063) when restarted, slaves do not really sync

[anselme dewavrin (JIRA)]

anselme dewavrin created AMQ-5063:
-

 Summary: when restarted, slaves do not really sync
 Key: AMQ-5063
 URL: https://issues.apache.org/jira/browse/AMQ-5063
 Project: ActiveMQ
  Issue Type: Bug
  Components: activemq-leveldb-store
Affects Versions: 5.9.0
 Environment: debian 6, x86-64, jdk1.7
Reporter: anselme dewavrin


Dear All,

I worked several days on replication tests with 5.9 (and snapshot 5.10), using 
replicatedLevelDB configuration as explained on activemq website (details 
follow). Everything is replicated well as long as every node is up.

But if I 
-stop a slave,
-inject messages,
-restart it,
then I see in the logs that it "caught up". But if I make it become the master, 
the new messages are not there...

Did I misunderstood the goal of replication ? Is this normal ?

Thank you all,
Anselme


 
 
   





--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Resolved] (AMQ-4987) io wait on replicated levelDB slaves

[anselme dewavrin (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMQ-4987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

anselme dewavrin resolved AMQ-4987.
---

   Resolution: Fixed
Fix Version/s: 5.9.0

This fsync impeachment works perfectly.

Anselme

> io wait on replicated levelDB slaves
> 
>
> Key: AMQ-4987
> URL: https://issues.apache.org/jira/browse/AMQ-4987
> Project: ActiveMQ
>  Issue Type: Test
>  Components: activemq-leveldb-store
>Affects Versions: 5.9.0
> Environment: debian VM 2.6.32-5-amd64, jdk7
>Reporter: anselme dewavrin
>Priority: Minor
> Fix For: 5.9.0
>
>
> Dear all,
> I set up a 3-nodes replicatedLevelDB activeMQ cluster on 3 different 
> machines, as explained on the activemq site (with zookeeper etc.).
> I made a message injector using the php stomp client described here : 
> http://stomp.fusesource.org/documentation/php/book.html
> Then I injected persistent messages as fast as possible (giving about 100 
> messages/s, each message is 10k).
> Everything works fine, then I measured the servers' activity with "vmstat 1". 
> I saw no iowait on the master node, but  20% on both slaves. This would 
> impeach scalabitity I suppose. And the iowait is justified by 3000 bo/s 
> (blocks out) in the vmstat report.
> The machines are not swapping (paging).
> Here is what I tried, without success :
> -specify explicitly sync="quorum_mem"
> -JNI implementation of the leveldb store (and verified it is used)
> -setting flushDelay to 2000
> Does anyone have an idea that I could try ? Why is the leveldb slaves writing 
> so much to disk ?
> Many thanks in advance
> Yours,
> Anselme



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Resolved] (AMQ-5042) Session.commit() hangs when amqp+nio is used

[Kevin Earls (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMQ-5042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kevin Earls resolved AMQ-5042.
--

Resolution: Fixed

> Session.commit() hangs when amqp+nio is used
> 
>
> Key: AMQ-5042
> URL: https://issues.apache.org/jira/browse/AMQ-5042
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: AMQP
>Affects Versions: 5.9.0
>Reporter: Timothy Bish
>Assignee: Timothy Bish
>Priority: Critical
> Fix For: 5.10.0
>
> Attachments: testRollbackRececeivedMessage-NIO.txt, 
> testRollbackRececeivedMessage-non-NIO.txt, 
> testSessionTransactedCommit-NIO.txt, testSessionTransactedCommit-non-NIO.txt
>
>
> The follow test will cause a hang when run against amqp+nio transport.
> {code}
> @Test(timeout=3)
> public void testSessionTransactedCommit() throws JMSException, 
> InterruptedException {
> ActiveMQAdmin.enableJMSFrameTracing();
> Connection connection = createConnection();
> Session session = connection.createSession(true, 
> Session.AUTO_ACKNOWLEDGE);
> Queue queue = session.createQueue(name.toString());
> connection.start();
> // transacted producer
> MessageProducer pr = session.createProducer(queue);
> for (int i = 0; i < 10; i++) {
> Message m = session.createTextMessage("TestMessage" + i);
> pr.send(m);
> }
> // No commit in place, so no message should be dispatched.
> MessageConsumer consumer = session.createConsumer(queue);
> TextMessage m = (TextMessage) consumer.receive(5000);
> assertNull(m);
> session.commit();
> // Messages should be available now.
> for (int i = 0; i < 10; i++) {
> Message msg = consumer.receive(5000);
> assertNotNull(msg);
> }
> session.close();
> connection.close();
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Created] (AMQ-5062) JMSClientNioTest fails intermittently

[Kevin Earls (JIRA)]

Kevin Earls created AMQ-5062:


 Summary: JMSClientNioTest fails intermittently
 Key: AMQ-5062
 URL: https://issues.apache.org/jira/browse/AMQ-5062
 Project: ActiveMQ
  Issue Type: Bug
Reporter: Kevin Earls
Assignee: Kevin Earls


I'm not sure whether this is just a test issue.  All test cases pass if run 
individually, and sometimes the whole test suite passes.  Other times, however, 
it gets errors like those shown below.  Depending on the run, different test 
cases will fail.

---
 T E S T S
---
Running org.apache.activemq.transport.amqp.JMSClientNioTest
Tests run: 21, Failures: 3, Errors: 1, Skipped: 0, Time elapsed: 343.636 sec 
<<< FAILURE! - in org.apache.activemq.transport.amqp.JMSClientNioTest
testExecptionListenerCalledOnBrokerStop(org.apache.activemq.transport.amqp.JMSClientNioTest)
  Time elapsed: 21.063 sec  <<< FAILURE!
java.lang.AssertionError: No exception listener event fired.
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.assertTrue(Assert.java:41)
at 
org.apache.activemq.transport.amqp.JMSClientTest.testExecptionListenerCalledOnBrokerStop(JMSClientTest.java:715)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at 
org.junit.internal.runners.statements.FailOnTimeout$StatementThread.run(FailOnTimeout.java:74)

testTopicConsumerSync(org.apache.activemq.transport.amqp.JMSClientNioTest)  
Time elapsed: 77.172 sec  <<< ERROR!
java.lang.Exception: test timed out after 45000 milliseconds
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:503)
at 
org.apache.qpid.amqp_1_0.transport.ConnectionEndpoint.open(ConnectionEndpoint.java:154)
at 
org.apache.qpid.amqp_1_0.client.Connection.(Connection.java:284)
at 
org.apache.qpid.amqp_1_0.client.Connection.(Connection.java:143)
at 
org.apache.qpid.amqp_1_0.jms.impl.ConnectionImpl.connect(ConnectionImpl.java:115)
at 
org.apache.qpid.amqp_1_0.jms.impl.ConnectionImpl.start(ConnectionImpl.java:284)
at 
org.apache.activemq.transport.amqp.JMSClientTest.createConnection(JMSClientTest.java:794)
at 
org.apache.activemq.transport.amqp.JMSClientTest.createConnection(JMSClientTest.java:754)
at 
org.apache.activemq.transport.amqp.JMSClientTest.testTopicConsumerSync(JMSClientTest.java:626)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at 
org.junit.internal.runners.statements.FailOnTimeout$StatementThread.run(FailOnTimeout.java:74)

testConsumerReceiveTimedThrowsWhenBrokerStops(org.apache.activemq.transport.amqp.JMSClientNioTest)
  Time elapsed: 12.525 sec  <<< FAILURE!
java.lang.AssertionError: Should have thrown an IllegalStateException
at org.junit.Assert.fail(Assert.java:88)
at 
org.apache.activemq.transport.amqp.JMSClientTest.testConsumerReceiveTimedThrowsWhenBrokerStops(JMSClientTest.java:411)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)

[jira] [Commented] (AMQ-5042) Session.commit() hangs when amqp+nio is used

[Kevin Earls (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMQ-5042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13903910#comment-13903910
 ] 

Kevin Earls commented on AMQ-5042:
--

Fixed by da63f3f20a348b29b43ef84bb7a4f6b02d2cd35c.  Updated AmqpNioTransport to 
properly handle receiving multiple frames at once on an NIO Channel.



> Session.commit() hangs when amqp+nio is used
> 
>
> Key: AMQ-5042
> URL: https://issues.apache.org/jira/browse/AMQ-5042
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: AMQP
>Affects Versions: 5.9.0
>Reporter: Timothy Bish
>Assignee: Timothy Bish
>Priority: Critical
> Fix For: 5.10.0
>
> Attachments: testRollbackRececeivedMessage-NIO.txt, 
> testRollbackRececeivedMessage-non-NIO.txt, 
> testSessionTransactedCommit-NIO.txt, testSessionTransactedCommit-non-NIO.txt
>
>
> The follow test will cause a hang when run against amqp+nio transport.
> {code}
> @Test(timeout=3)
> public void testSessionTransactedCommit() throws JMSException, 
> InterruptedException {
> ActiveMQAdmin.enableJMSFrameTracing();
> Connection connection = createConnection();
> Session session = connection.createSession(true, 
> Session.AUTO_ACKNOWLEDGE);
> Queue queue = session.createQueue(name.toString());
> connection.start();
> // transacted producer
> MessageProducer pr = session.createProducer(queue);
> for (int i = 0; i < 10; i++) {
> Message m = session.createTextMessage("TestMessage" + i);
> pr.send(m);
> }
> // No commit in place, so no message should be dispatched.
> MessageConsumer consumer = session.createConsumer(queue);
> TextMessage m = (TextMessage) consumer.receive(5000);
> assertNull(m);
> session.commit();
> // Messages should be available now.
> for (int i = 0; i < 10; i++) {
> Message msg = consumer.receive(5000);
> assertNotNull(msg);
> }
> session.close();
> connection.close();
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Re: Hung Producer

[Ashwini Kuntamukkala]

I repeated the test with the following settings

activemq.xml openwire transport connector



Client URL
broker.url=tcp://broker-machine:61616?jms.useAsyncSend=false&soWriteTimeout=15000

This time the producers crash with the following exception

[WARNING]
org.springframework.jms.UncategorizedJmsException: Uncategorized exception
occured during JMS processing; nested exception is javax.jms.JMSException:
Cannot send, channel has already failed: tcp://broker-machine:61616
at
org.springframework.jms.support.JmsUtils.convertJmsAccessException(Jm
sUtils.java:316)
at
org.springframework.jms.support.JmsAccessor.convertJmsAccessException
(JmsAccessor.java:168)
at
org.springframework.jms.core.JmsTemplate.execute(JmsTemplate.java:469
)
at
org.springframework.jms.core.JmsTemplate.send(JmsTemplate.java:543)
at producer.ProducerTask.run(ProducerTask.java:43)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)Caused by:
javax.jms.JMSException: Cannot send, channel has already failed: tcp:
//broker-machine:61616
at
org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:62)
at
org.apache.activemq.ActiveMQConnection.doAsyncSendPacket(ActiveMQConnection.java:1306)
at
org.apache.activemq.ActiveMQConnection.asyncSendPacket(ActiveMQConnection.java:1298)
at
org.apache.activemq.ActiveMQSession.(ActiveMQSession.java:252)
at
org.apache.activemq.ActiveMQConnection.createSession(ActiveMQConnection.java:334)
at
org.apache.activemq.pool.ConnectionPool$2.makeObject(ConnectionPool.java:105)
at
org.apache.activemq.pool.ConnectionPool$2.makeObject(ConnectionPool.java:90)
at
org.apache.commons.pool.impl.GenericKeyedObjectPool.borrowObject(GenericKeyedObjectPool.java:1220)
at
org.apache.activemq.pool.ConnectionPool.createSession(ConnectionPool.java:142)
at
org.apache.activemq.pool.PooledConnection.createSession(PooledConnection.java:174)
at
org.springframework.jms.support.JmsAccessor.createSession(JmsAccessor.java:196)
at
org.springframework.jms.core.JmsTemplate.execute(JmsTemplate.java:457)
... 5 more
Caused by: org.apache.activemq.transport.InactivityIOException: Cannot send,
cha
nnel has already failed: tcp://10.12.44.82:61616
at
org.apache.activemq.transport.AbstractInactivityMonitor.doOnewaySend(AbstractInactivityMonitor.java:315)
at
org.apache.activemq.transport.AbstractInactivityMonitor.oneway(AbstractInactivityMonitor.java:304)
at
org.apache.activemq.transport.TransportFilter.oneway(TransportFilter.java:85)
at
org.apache.activemq.transport.WireFormatNegotiator.oneway(WireFormatNegotiator.java:104)
at
org.apache.activemq.transport.TransportFilter.oneway(TransportFilter.java:85)
at
org.apache.activemq.transport.WriteTimeoutFilter.oneway(WriteTimeoutFilter.java:73)
at
org.apache.activemq.transport.MutexTransport.oneway(MutexTransport.java:68)
at
org.apache.activemq.transport.ResponseCorrelator.oneway(ResponseCorrelator.java:60)
at
org.apache.activemq.ActiveMQConnection.doAsyncSendPacket(ActiveMQConnection.java:1304)



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/Hung-Producer-tp4678060p4678063.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.