-
```
The asqs adapter (asqs.rb) has the incorrect message size constant. The
current version 2008-1-1
(for which the adapter is defaulting to) now has an 8k message size limit, not
256k.
asqs.rb
L…
-
```
The asqs adapter (asqs.rb) has the incorrect message size constant. The
current version 2008-1-1
(for which the adapter is defaulting to) now has an 8k message size limit, not
256k.
asqs.rb
L…
-
```
Hi,
Seems like a similar issue to described for other rails version. A
'vanilla' poller starts up ok 'script/poller run' but as soon as there is a
message to pick up and action it fails miserably…
-
```
Feature request or support request:
I enjoy the easy setup and usage of ActiveMessaging in my Rails apps, but
now I need messaging in a standalone Ruby application.
How do I best use ActiveMessa…
-
```
Hi,
Seems like a similar issue to described for other rails version. A
'vanilla' poller starts up ok 'script/poller run' but as soon as there is a
message to pick up and action it fails miserably…
-
```
Feature request or support request:
I enjoy the easy setup and usage of ActiveMessaging in my Rails apps, but
now I need messaging in a standalone Ruby application.
How do I best use ActiveMessa…
-
```
What steps will reproduce the problem?
1. create two processors that subscribe to the same topic
2. publish a message to a topic
3. Only the processor that has a class name that is alphabetical…
-
```
There are puts that should likely be using the default logger. Such as
subscribing to queues/topics in gateway.rb
```
Original issue reported on code.google.com by `ned.wolp...@gmail.com` on 9 J…
-
```
What steps will reproduce the problem?
1. Have an Amazon SQS queue with a name that contains a dash ('-').
2. Run the 'poller' script
What is the expected output? What do you see instead?
plugin…
-
```
What steps will reproduce the problem?
1. create two processors that subscribe to the same topic
2. publish a message to a topic
3. Only the processor that has a class name that is alphabetical…