Just for posterity, this was me being a bonehead - I didn't have a JMS
connection pool in my camel config - once I added one things got MUCH
happier.
Larry
On Mon, May 12, 2014 at 11:07 AM, Larry Meadors wrote:
> Thanks for your time, Christian!
>
> Firewall/networking betw
I'm running AMQ 5.7.0 with a camel application (using camel 2.10.7, in
case that's relevant) and recently, the app has started logging these
messages:
WARN o.a.c.c.j.DefaultJmsMessageListenerContainer - Setup of JMS
message listener invoker failed for destination 'play.save' - trying
to recover.
Thanks for your time, Christian!
Firewall/networking between them: None. :-\
They are running on the same (virtual) machine - it's an EC2 host
running ubuntu.
I am running 3 instances of AMQ on it (it's a dev/test/qa type of
environment) - the AMQ endpoints are configured as localhost:61617,
loc
No hints?
This is killing me - I'm restarting AMQ several times a week now. :-/
On Wed, May 7, 2014 at 11:18 AM, Larry Meadors wrote:
> I'm running AMQ 5.7.0 with a camel application (using camel 2.10.7, in
> case that's relevant) and recently, the app has started log
Wow, that was quick. Thanks. :)
Larry
It appears to be buggered up:
http://activemq.apache.org/redelivery-policy.html
The sample code there is visible if you view the source, but doesn't seem
to show up in chrome, safari, or firefox on OSX.
Larry
tware Engineer | FuseSource Corp.
> dej...@fusesource.com | fusesource.com
> skype: dejan.bosanac | twitter: @dejanb
> blog: http://www.nighttale.net
> ActiveMQ in Action: http://www.manning.com/snyder/
>
>
>
> On Wed, Mar 7, 2012 at 1:55 PM, Larry Meadors
> wrote:
>&
I think I found a bug in the the bin/activemq script. It's simple to
fix, and looks like someone was just trying to be too careful. :)
When trying to determine the Active MQ installation dir, it does this:
saveddir=`pwd`
...then later it does this:
cd "$saveddir"
In my case, I call the scrip
On Thu, Nov 17, 2011 at 10:19 AM, James Green
wrote:> Sounds like one for Apache Camel
(using ActiveMQ).
Yup - we're using camel for the receiving end of it - the sending end
is not my concern. :)
Larry
I'm looking at a process where we are moving around 2000 pdf files per
day (not sure of the size yet - I'd guess < 2MB) to an alternate
location.
We'd have a process that sent the pdf files to our queue, and a second
process that would get them from there and push them to their new
home.
I am won
10 matches
Mail list logo