yea, but exclusive consumer should sort that.
2009/8/7 jerdavis
>
>
> I guess the edge case I'm thinking about is the Plain ol Single Consumer
> that crashes. If my crashed program quickly restarts, and starts consuming,
> I bet the broker would think there are two consumers (until TCP timeouts
Hi,
It seems that transaction states in the connection state tracker are not
cleaned up when doing rollback on a transaction.
>From what I understand, the
ConnectionStateTracker.processRollbackTransaction(TransactionInfo info)
returns a tracked response that should be handled asynchronously in t
I guess the edge case I'm thinking about is the Plain ol Single Consumer
that crashes. If my crashed program quickly restarts, and starts consuming,
I bet the broker would think there are two consumers (until TCP timeouts
etc)
Many thanks to all, I can sleep better now.
-JD
Gary Tully wrote:
If you want to create queues & topics (JMS administered objects) in code and
then later be able to have your clients locate them via jndi lookups, then
one thing you may want to consider is to use a LDAP directory server (e.g.,
Apache DS) as your centralized JNDI server. The two things that greatl
Wonder if we should just filter out our own log messages in the JMS
appender, that way users can never get bitten by this problem.
On Fri, Aug 7, 2009 at 5:00 AM, Gary Tully wrote:
> great. thanks for completing the loop on this by sharing your solution :-)
>
> 2009/8/7 Kinski
>
> >
> > I added
total ordering is only an issue when there are multiple consumers.
For a single consumer and for exclusive consumers, where there can only be a
single consumer, ordering 'is' guaranteed.
2009/8/6 jerdavis
>
> Thanks for your answer Rob, this is exactly what I was looking for. :)
> Total Ordering
great. thanks for completing the loop on this by sharing your solution :-)
2009/8/7 Kinski
>
> I added the suffix to the brokerURL
>
> I.e.
>
> log4j.appender.JMS.ProviderURL=tcp://localhost:61616?wireFormat.cacheEnabled=false
>
> but this made no difference.
>
> then finally found my needle in
2009/8/7 An An :
>
> Hi James,
> Thanks for the reply.
> I have set the JBoss jndi properties already.
> So I do this in the code :-
> <<
> Properties props = new Properties();
>
> props.setProperty(Context.INITIAL_CONTEXT_FACTORY,"org.apache.activemq.jndi.ActiveMQInitialContextFactory");
>
Hi James,
Thanks for the reply.
I have set the JBoss jndi properties already.
So I do this in the code :-
<<
Properties props = new Properties();
props.setProperty(Context.INITIAL_CONTEXT_FACTORY,"org.apache.activemq.jndi.ActiveMQInitialContextFactory");
props.setP
I added the suffix to the brokerURL
I.e.
log4j.appender.JMS.ProviderURL=tcp://localhost:61616?wireFormat.cacheEnabled=false
but this made no difference.
then finally found my needle in the haystack with this nugget of
information..
http://www.nabble.com/Log4J-ActiveMQ-JMS-Appender-td18840199.h
10 matches
Mail list logo
