[jira] Commented: (AMQNET-79) create a WCF provider for NMS (and so for ActiveMQ)

[ https://issues.apache.org/activemq/browse/AMQNET-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45341#action_45341 ] David Keaveny commented on AMQNET-79: - I'm having a go at writing a WCF implementation wit

Re: How to intercept the creation of ActiveMQConnections?

Then your going to have to stop/suspend the Accept thread for the server socket or accept the connection but then shut it down. On Tue, Sep 2, 2008 at 5:55 PM, Bruce Snyder <[EMAIL PROTECTED]> wrote: > On Tue, Sep 2, 2008 at 3:37 PM, Hiram Chirino <[EMAIL PROTECTED]> wrote: >> AOP won't help since

activemq 5.1 hanging when using spring container listener.

hi,friends, I meet a error when using activemq5.1. the cosumer hanged and do nothing,but there are still have messages in the queue.how can solve this problem? thanks a lot. my configure:

[jira] Commented: (AMQNET-78) ActiveMQ v5 Idle Connection Timeout does not throw an exception

[ https://issues.apache.org/activemq/browse/AMQNET-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45338#action_45338 ] Jim Gomes commented on AMQNET-78: - Chris, in your comment on 6 June 2008, you mention that you

[jira] Updated: (AMQNET-78) ActiveMQ v5 Idle Connection Timeout does not throw an exception

[ https://issues.apache.org/activemq/browse/AMQNET-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes updated AMQNET-78: Comment: was deleted > ActiveMQ v5 Idle Connection Timeout does not throw an exception > ---

[jira] Commented: (AMQNET-110) WireFormatNegotiator does not negotiate version

[ https://issues.apache.org/activemq/browse/AMQNET-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45337#action_45337 ] Jim Gomes commented on AMQNET-110: -- Taken from the [OpenWire Specification documentation|ht

[jira] Resolved: (AMQNET-110) WireFormatNegotiator does not negotiate version

[ https://issues.apache.org/activemq/browse/AMQNET-110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes resolved AMQNET-110. -- Resolution: Working as Designed > WireFormatNegotiator does not negotiate version > ---

Re: How to intercept the creation of ActiveMQConnections?

On Tue, Sep 2, 2008 at 3:37 PM, Hiram Chirino <[EMAIL PROTECTED]> wrote: > AOP won't help since the client is going to be in a different JVM the > server. So there is no server logic that can control the client until > the client connects.. and it seems your too late at that point. I'm not lookin

Re: How to intercept the creation of ActiveMQConnections?

AOP won't help since the client is going to be in a different JVM the server. So there is no server logic that can control the client until the client connects.. and it seems your too late at that point. On Tue, Sep 2, 2008 at 2:09 PM, Bruce Snyder <[EMAIL PROTECTED]> wrote: > On Thu, Aug 21, 200

New Java Protocol Buffers Parser/Code Generator

Hi Guys, First off, I want to thank Google for contributing such a great project. I wanted to let you guys know that there's now a new Java based parser/code generator which might interest some of you guys. The source for it is at: https://svn.apache.org/repos/asf/activemq/sandbox/activemq-proto

[jira] Commented: (AMQNET-110) WireFormatNegotiator does not negotiate version

[ https://issues.apache.org/activemq/browse/AMQNET-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45336#action_45336 ] Jim Gomes commented on AMQNET-110: -- I looked at the code, and the NMS client does check the

[jira] Updated: (AMQNET-110) WireFormatNegotiator does not negotiate version

[ https://issues.apache.org/activemq/browse/AMQNET-110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes updated AMQNET-110: - Assignee: Jim Gomes (was: James Strachan) Priority: Minor (was: Major) > WireFormatNegotiator d

[jira] Work logged: (AMQNET-109) NMS does not use TcpNoDelay which results in poor performance compared to Java

[ https://issues.apache.org/activemq/browse/AMQNET-109?page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#action_36776 ] Jim Gomes logged work on AMQNET-109: Author: Jim Gomes Created on: 02/Sep/08 02:06 P

[jira] Resolved: (AMQNET-109) NMS does not use TcpNoDelay which results in poor performance compared to Java

[ https://issues.apache.org/activemq/browse/AMQNET-109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes resolved AMQNET-109. -- Resolution: Fixed > NMS does not use TcpNoDelay which results in poor performance compared to Java

[jira] Updated: (AMQNET-109) NMS does not use TcpNoDelay which results in poor performance compared to Java

[ https://issues.apache.org/activemq/browse/AMQNET-109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes updated AMQNET-109: - Attachment: nmsspeedtest.cs Speed test framework that compares the difference between TcpNoDelayEnabl

[jira] Updated: (AMQ-1877) Invalid Topic Statistics

[ https://issues.apache.org/activemq/browse/AMQ-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Trevor Pounds updated AMQ-1877: --- Description: I'm not sure if this affects 5.0.0 directly but I imagine it does since I'm seeing th

[jira] Issue Comment Edited: (AMQ-1877) Invalid Topic Statistics

[ https://issues.apache.org/activemq/browse/AMQ-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45334#action_45334 ] tpounds edited comment on AMQ-1877 at 9/2/08 12:29 PM: - Fix expecte

[jira] Commented: (AMQ-1925) JDBC-Master/Slave Failover - Consumer stop after 1000 Messages

[ https://issues.apache.org/activemq/browse/AMQ-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45333#action_45333 ] Mario Siegenthaler commented on AMQ-1925: - Well the "just don't allow this value to bec

Re: How to intercept the creation of ActiveMQConnections?

On Thu, Aug 21, 2008 at 9:19 AM, Bruce Snyder <[EMAIL PROTECTED]> wrote: > On Wed, Aug 20, 2008 at 11:03 AM, Bruce Snyder <[EMAIL PROTECTED]> wrote: >> On Wed, Aug 20, 2008 at 10:43 AM, James Strachan >> <[EMAIL PROTECTED]> wrote: >>> The broker doesn't know about a client side connection object un

Re: Tests for the AMQ store?

On Thu, Aug 14, 2008 at 11:43 AM, Bruce Snyder <[EMAIL PROTECTED]> wrote: > I am trying to understand how the AMQ store works and how it uses the > systemUsage config, but I'm not finding any tests anywhere for the AMQ > store. Are there any tests for the AMQ store? Anyone? Bruce -- perl -e 'pri

[jira] Updated: (AMQ-1925) JDBC-Master/Slave Failover - Consumer stop after 1000 Messages

[ https://issues.apache.org/activemq/browse/AMQ-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mario Siegenthaler updated AMQ-1925: Attachment: (was: threaddump-1220371256910.tdump) > JDBC-Master/Slave Failover - Cons

[jira] Created: (AMQ-1925) JDBC-Master/Slave Failover - Consumer stop after 1000 Messages

JDBC-Master/Slave Failover - Consumer stop after 1000 Messages -- Key: AMQ-1925 URL: https://issues.apache.org/activemq/browse/AMQ-1925 Project: ActiveMQ Issue Type: Bug C

[jira] Updated: (AMQ-1925) JDBC-Master/Slave Failover - Consumer stop after 1000 Messages

[ https://issues.apache.org/activemq/browse/AMQ-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mario Siegenthaler updated AMQ-1925: Attachment: heapdump-1220373534484.hprof Consumer thread-dump > JDBC-Master/Slave Failov

[jira] Updated: (AMQ-1925) JDBC-Master/Slave Failover - Consumer stop after 1000 Messages

[ https://issues.apache.org/activemq/browse/AMQ-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mario Siegenthaler updated AMQ-1925: Attachment: threaddump-1220371256910.tdump Consumer memory dump > JDBC-Master/Slave Fail

[jira] Commented: (AMQ-1282) Bad conversion of nonexistent data in MapMessage

[ https://issues.apache.org/activemq/browse/AMQ-1282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45328#action_45328 ] Barry Kaplan commented on AMQ-1282: --- #getBytes also appears to be incorrect in two ways. Fi

[jira] Issue Comment Edited: (AMQ-1282) Bad conversion of nonexistent data in MapMessage

[ https://issues.apache.org/activemq/browse/AMQ-1282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45328#action_45328 ] memelet edited comment on AMQ-1282 at 9/2/08 9:35 AM: --- #getBytes also

[jira] Updated: (AMQNET-109) NMS does not use TcpNoDelay which results in poor performance compared to Java

[ https://issues.apache.org/activemq/browse/AMQNET-109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes updated AMQNET-109: - Assignee: Jim Gomes (was: James Strachan) Fix Version/s: 1.0 Affects Version/s:

[jira] Work logged: (AMQNET-109) NMS does not use TcpNoDelay which results in poor performance compared to Java

[ https://issues.apache.org/activemq/browse/AMQNET-109?page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#action_36775 ] Jim Gomes logged work on AMQNET-109: Author: Jim Gomes Created on: 02/Sep/08 09:27 A

[jira] Work started: (AMQNET-109) NMS does not use TcpNoDelay which results in poor performance compared to Java

[ https://issues.apache.org/activemq/browse/AMQNET-109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on AMQNET-109 started by Jim Gomes. > NMS does not use TcpNoDelay which results in poor performance compared to Java > --

[jira] Issue Comment Edited: (AMQ-1710) Failing over in JDBC Master/Slave topology does not preserve transaction state

[ https://issues.apache.org/activemq/browse/AMQ-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45325#action_45325 ] msiegenthaler edited comment on AMQ-1710 at 9/2/08 8:16 AM: - I

[jira] Updated: (AMQ-1710) Failing over in JDBC Master/Slave topology does not preserve transaction state

[ https://issues.apache.org/activemq/browse/AMQ-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mario Siegenthaler updated AMQ-1710: Attachment: AMQ-1710.patch I propose the attached patch for the issue. It allows produce

[jira] Updated: (AMQ-1924) Error: unexpected message type received - expected BytesMessage - While invoking the client program.

[ https://issues.apache.org/activemq/browse/AMQ-1924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] REJI R S updated AMQ-1924: -- Description: i am trying to invoke a webservice using JMS transport. (SOAP over JMS). i have configured Axis

[jira] Created: (AMQ-1924) Error: unexpected message type received - expected BytesMessage - While invoking the client program.

Error: unexpected message type received - expected BytesMessage - While invoking the client program. Key: AMQ-1924 URL: https://issues.apache.org/activemq/browse/

Re: ActiveMQ-CPP Version 2.2.1 RC2

Great, thanks for the feedback Regards Tim On Tue, 2008-09-02 at 06:22 -0700, Richard Gillingham wrote: > > Hi > > I'd like to confirm the fix to my transaction issue AMQCPP-195. > > Kind regards > > Richard Gillingham > > > Timothy Bish wrote: > > > > Hey everyone, > > It's official ... A

Re: ActiveMQ-CPP Version 2.2.1 RC2

Hi I'd like to confirm the fix to my transaction issue AMQCPP-195. Kind regards Richard Gillingham Timothy Bish wrote: > > Hey everyone, > It's official ... ActiveMQ-CPP v2.2.1 now has a second release candidate, > RC2. > This candidate includes a fix for the AMQCPP-165 issue's core dumps.

[jira] Issue Comment Edited: (AMQ-1909) QueueViewMBean.retryMessage() often seems to fail without retrying

[ https://issues.apache.org/activemq/browse/AMQ-1909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45293#action_45293 ] rajdavies edited comment on AMQ-1909 at 9/2/08 5:23 AM: - Fixed by SVN r

[jira] Resolved: (AMQ-1841) Network of pure master/slave synchronization issue

[ https://issues.apache.org/activemq/browse/AMQ-1841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Davies resolved AMQ-1841. - Fix Version/s: 5.2.0 Resolution: Fixed This is solved by SVN revision 691206? > Network of pure

[jira] Assigned: (AMQ-1832) Pure Master/Slave to allow shutdownOnSlaveFailure to be configured on master

[ https://issues.apache.org/activemq/browse/AMQ-1832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Davies reassigned AMQ-1832: --- Assignee: Rob Davies > Pure Master/Slave to allow shutdownOnSlaveFailure to be configured on master

[jira] Resolved: (AMQ-1832) Pure Master/Slave to allow shutdownOnSlaveFailure to be configured on master

[ https://issues.apache.org/activemq/browse/AMQ-1832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Davies resolved AMQ-1832. - Fix Version/s: 5.2.0 Resolution: Fixed Patch applied by SVN revision 691206 > Pure Master/Slave

[jira] Resolved: (AMQ-1820) Pure Master/Slave-kill the slave-master will not work

[ https://issues.apache.org/activemq/browse/AMQ-1820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Davies resolved AMQ-1820. - Resolution: Fixed Patch applied by SVN revision 691206 > Pure Master/Slave-kill the slave-master will

[jira] Resolved: (AMQ-596) allow a broker to be configured to start up as a 'Master' and refuse to perform any work until the 'Slave' has started

[ https://issues.apache.org/activemq/browse/AMQ-596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Davies resolved AMQ-596. Resolution: Fixed Patch applied by SVN revision 691206 > allow a broker to be configured to start up as a

[jira] Assigned: (AMQ-1820) Pure Master/Slave-kill the slave-master will not work

[ https://issues.apache.org/activemq/browse/AMQ-1820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Davies reassigned AMQ-1820: --- Assignee: Rob Davies > Pure Master/Slave-kill the slave-master will not work >

[jira] Resolved: (CAMEL-874) Add seralizable check on the MinaPayloadHolder to make sure the MinaPayloadHolder can be seralized by Mina

[ https://issues.apache.org/activemq/browse/CAMEL-874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang resolved CAMEL-874. Resolution: Fixed > Add seralizable check on the MinaPayloadHolder to make sure the > MinaPaylo

Re: camel spring xml restructure

2008/9/2 Vadim Chekan <[EMAIL PROTECTED]>: > Thanks for your comments James, > It is good to know that BNF is supported in eclipse out of the box. > I'll try not to concentrate on the grammar too much and implement from-to > syntax. And when it works, we can discuss the final syntax. Great stuff!

[jira] Assigned: (AMQ-1841) Network of pure master/slave synchronization issue

[ https://issues.apache.org/activemq/browse/AMQ-1841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Davies reassigned AMQ-1841: --- Assignee: Rob Davies > Network of pure master/slave synchronization issue > ---

[jira] Resolved: (AMQ-1887) Wrap the debugging variables in conditional expressions to enable them easier

[ https://issues.apache.org/activemq/browse/AMQ-1887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Davies resolved AMQ-1887. - Resolution: Fixed patch applied in SVN revision 691131 > Wrap the debugging variables in conditional e

[jira] Resolved: (AMQ-1915) ActiveMQConnectionFactory.setExclusiveConsumer has no effect

[ https://issues.apache.org/activemq/browse/AMQ-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Davies resolved AMQ-1915. - Fix Version/s: 5.2.0 Resolution: Fixed Fixed by SVN revision 691130 > ActiveMQConnectionFactory

[jira] Resolved: (AMQ-1860) soTimeout transport property- Incorrect documentation (or code, you pick)

[ https://issues.apache.org/activemq/browse/AMQ-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Davies resolved AMQ-1860. - Resolution: Fixed no problem! - updated in SVN revision 691129 > soTimeout transport property- Incorre