[
https://issues.apache.org/activemq/browse/AMQ-1847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=44097#action_44097
]
vguna edited comment on AMQ-1847 at 7/8/08 11:45 PM:
-
Thanks Claus.
Su
[
https://issues.apache.org/activemq/browse/AMQ-1847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=44097#action_44097
]
Veit Guna commented on AMQ-1847:
Thanks Claus.
Sure, here's my applicationContext.xml:
http:
[
https://issues.apache.org/activemq/browse/AMQ-1796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Davies resolved AMQ-1796.
-
Resolution: Fixed
Resolved by SVN revision 675104
> expired messages not moved to DLQ on trunk (5.2)
>
I'm testing ActiveMQ 5.1 and I found a strange behaviour. There is a single
message producer firing 10 messages in 1 second and message consumer that
listens on the same destination. Here is the code:
import javax.jms.Connection;
import javax.jms.ConnectionFactory;
import javax.jms.DeliveryMod
[
https://issues.apache.org/activemq/browse/AMQ-1847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=44092#action_44092
]
Claus Ibsen commented on AMQ-1847:
--
Veit. I managed to move the issue from Camel to ActiveMQ p
[
https://issues.apache.org/activemq/browse/AMQ-1847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen moved CAMEL-683 to AMQ-1847:
Project: ActiveMQ (was: Apache Camel)
Key: AMQ-1847
[
https://issues.apache.org/activemq/browse/AMQ-1847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=44093#action_44093
]
Claus Ibsen commented on AMQ-1847:
--
Veit. Can you add your new configuration etc. for the Acti
[
https://issues.apache.org/activemq/browse/AMQ-1847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reopened AMQ-1847:
--
Assignee: (was: Claus Ibsen)
> Redelivery on a failure doesn't respect the initialRedeliveryDel
translate Chinese from Cms to nms is garbled
--
View this message in context:
http://www.nabble.com/translate-Chinese--from-Cms--to-nms--is-garbled-tp18352571p18352571.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
Hello all
I've been thinking about Silverlight and decided tonight to try my NMS
client assemblies in a Silverlight 2 Beta project. The IDE complains that
the assemblies were not built against the Silverlight runtime.
Has anyone tried this before??
If not, I'll go ahead and report back :)
kin
Provide tags to set defaultPrefetchSize in activemq.xml
---
Key: AMQ-1846
URL: https://issues.apache.org/activemq/browse/AMQ-1846
Project: ActiveMQ
Issue Type: Task
Components: Br
[
https://issues.apache.org/activemq/browse/AMQ-1796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully reopened AMQ-1796:
-
Regression: [Regression] (was: [Broken Unit Test, Regression])
reopen till classcast exception is reso
[
https://issues.apache.org/activemq/browse/AMQ-1844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=44078#action_44078
]
Bryan Shaw commented on AMQ-1844:
-
I upgraded to 5.1 and this problem gone.
> Message acknowle
Message loss in network of brokers when network connection break
Key: AMQ-1845
URL: https://issues.apache.org/activemq/browse/AMQ-1845
Project: ActiveMQ
Issue Type: Bug
Message acknowledgement failed to send back to the producing broker
---
Key: AMQ-1844
URL: https://issues.apache.org/activemq/browse/AMQ-1844
Project: ActiveMQ
Issue Type: Bug
On Tue, Jul 8, 2008 at 1:48 AM, James Strachan <[EMAIL PROTECTED]> wrote:
> It might not be quite as fast as OpenWire (though should beat STOMP)
> but I wonder if it might be interesting creating a Protocol Buffer
> transport; using the current OpenWire beans as input to generate the
> .proto file
Yeah! Protocol Buffers is purely a marshalling mechanism only
2008/7/8 Rob Davies <[EMAIL PROTECTED]>:
> +1 - we need to update the on-the-wire format anyways (version 6) - and the
> more protocols the better - as long as they are wire format only and do not
> dictate how the broker must be imple
+1 - we need to update the on-the-wire format anyways (version 6) -
and the more protocols the better - as long as they are wire format
only and do not dictate how the broker must be implemented ;)
On 8 Jul 2008, at 08:48, James Strachan wrote:
It might not be quite as fast as OpenWire (th
It might not be quite as fast as OpenWire (though should beat STOMP)
but I wonder if it might be interesting creating a Protocol Buffer
transport; using the current OpenWire beans as input to generate the
.proto file for Protocol Buffer...
http://code.google.com/apis/protocolbuffers/docs/overview.
support a Protocol Buffer protocol for easier binary interop with other
languages and systems
-
Key: AMQ-1843
URL: https://issues.apache.org/activemq/browse/AMQ-1843
20 matches
Mail list logo
