I'm not sure if it's the specific version of SQL server that we're using, but
S*ELECT * FROM ACTIVEMQ_LOCK WHERE ID=1 FOR UPDATE* throws exception *"FOR
Update clause allowed only for DECLARE CURSOR" *...
I'm using 5.6.0 - Am I missing something in connection string or
configuration properties?
Hello,
Thanks for the answers.
I'll check however why it worked with the activeMQ 5.4 and only changing the
jar dependency to use the activeMQ 5.6 it stops working?
The activeMq is started inside a java application, using the BrokerService
class. How can I configure the annotatedClass property us
Hi Michael,
Please refer to the heart beating section of the STOMP 1.1 spec for more
details [1].
In short, since a STOMP 1.0 connection does send the 'heart-beat' header,
it's the same as if the client would have sent a 'heart-beat:0,0' which
means ti does not want any heart beats from the sever
Yes, it will try to keep the current cache until ldap server comes back.
Regards
--
Dejan Bosanac
Senior Software 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/sn
A few things to check:
1) Do you have you class mapping set in activemq.xml, like
org.apache.activemq.transport.stomp.SamplePojo
2) Do you have XStream dependency in your classpath?
Regards
--
Dejan Bosanac
Senior Software Engineer | FuseSource Corp.
dej...@fusesource.com
>From these log messages it looks like you're using amq store not kahadb?
Regards
--
Dejan Bosanac
Senior Software 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/sn
No, pulling messages (aka prefetch size 0) is generally not bad idea.
It can affect you performances but that depends on the loads you're
having.
Regards
--
Dejan Bosanac
Senior Software Engineer | FuseSource Corp.
dej...@fusesource.com | fusesource.com
skype: dejan.bosanac | twitter: @dejanb
blo
You can code a wise consumer that checks against the Topic message if its
name is in the list of consumers to be stopped.
Then all you have to do is publish a message with a List of consumers'
names.
*Bruno Borges*
(21) 7672-7099
*www.brunoborges.com*
On Fri, Jun 22, 2012 at 7:21 AM, Samuel Co
Are you using 5.6, this looks a bit like
https://issues.apache.org/jira/browse/AMQ-3706
The test case attached to that jira may provide a good starting point
for a junit test case for your scenario, that could help reproduce
http://svn.apache.org/viewvc/activemq/trunk/activemq-core/src/test/java/
