You're agree.
But to use commit/rollback session, i need to use TRANSACTED session.
So the performance cost is very expensive and i really need performance.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/INDIVIDUAL-ACKNOWLEDGE-with-a-durable-consumer-tp4680403p4680624.h
you can reuse a session after a commit/rollback so no need to close.
On 28 April 2014 08:46, meurwinn wrote:
> Sounds the only one solution but the problem is that open and close a session
> for each message wil have a performance cost or not ?
>
>
>
>
> --
> View this message in context:
> http
Sounds the only one solution but the problem is that open and close a session
for each message wil have a performance cost or not ?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/INDIVIDUAL-ACKNOWLEDGE-with-a-durable-consumer-tp4680403p4680609.html
Sent from the ActiveM
maybe use a transacted session for your consumer and only commit when
you are happy.
On 24 April 2014 16:15, meurwinn wrote:
> Hi, thanks.
> We persist messages in LevelDB storage.
>
> We needs this functionnality pretty soon in production so i think we have to
> find another solution while you'r
Hi, thanks.
We persist messages in LevelDB storage.
We needs this functionnality pretty soon in production so i think we have to
find another solution while you're working.
Do you have any idea for an other way to do this or not ?
Thanks for your help.
--
View this message in context:
http:/
hmm. this is a problem - see https://issues.apache.org/jira/browse/AMQ-3486
I reopened because I think kahadb can now handle this case ok but it
needs some tests and some work to verify.
On 24 April 2014 14:35, meurwinn wrote:
> Ok, that's what i was thinking.
>
> So as i said, i want to ack or
Ok, that's what i was thinking.
So as i said, i want to ack or not each message received in a session.
The AUTO_ACK is not the good way and the CLIENT_ACK neither ("Acknowledging
a consumed message automatically acknowledges the receipt of all messages
that have been consumed by its session.").
the ack mode is only relevant to message consumers.
have a read of http://docs.oracle.com/javaee/1.4/tutorial/doc/JMS6.html
On 24 April 2014 13:41, meurwinn wrote:
> Sorry but i really don't understand.
>
> I just need to ack or not each message received in a session that stay open
> all the time
Sorry but i really don't understand.
I just need to ack or not each message received in a session that stay open
all the time.
So when in send a message to a durable topic, wich one ack mode does i need
to use ?
When i received a message from this durable topic, wich one ack mode does i
need to
s/Session.AUTO_ACKNOWLEDGE/Session.CLIENT_ACKNOWLEDGE/
and call javax.jms.Message#acknowledge when you are done with a received message
On 24 April 2014 10:25, meurwinn wrote:
> Hi, not shure to understand what you mean.
> In my client code to consume the messages, i have :
>
> /ActiveMQConnecti
Hi, not shure to understand what you mean.
In my client code to consume the messages, i have :
/ActiveMQConnectionFactory factory = new
ActiveMQConnectionFactory(serverUrl);
connection = factory.createTopicConnection(userName, password);
session = ((TopicConnection) connection).createTopicSession(
Use client ack mode?
On 24 Apr 2014 09:36, "meurwinn" wrote:
> Up,
> any idea about how to process ? Or any explain.
> I can't find any documentation about the way to follow...
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/INDIVIDUAL-ACKNOWLEDGE-with-a-durable
Up,
any idea about how to process ? Or any explain.
I can't find any documentation about the way to follow...
--
View this message in context:
http://activemq.2283324.n4.nabble.com/INDIVIDUAL-ACKNOWLEDGE-with-a-durable-consumer-tp4680403p4680505.html
Sent from the ActiveMQ - User mailing list
Hi,
i'm a newbie with AMQ achnolegment.
AMQ 5.8.0 (soon upgrading to 5.9.1)
I have a durable subscriber on a TOPIC. There is no transaction.
I need to ACK or NOT each consumed message after a short process.
I've tried to configure in INDIVIDUAL_ACK that seems to be a good way but
it's seems al
14 matches
Mail list logo
