activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Raul Kripalani <r...@evosent.com>
Subject Re: Is there an timeout exception for session.commit() ?
Date Mon, 02 Sep 2013 18:52:03 GMT
Got it, thanks!

*Raúl Kripalani*
Apache Camel PMC Member & Committer | Enterprise Architect, Open Source
Integration specialist
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk

On Mon, Sep 2, 2013 at 5:36 PM, Christian Posta
<christian.posta@gmail.com>wrote:

> Raul,
>
> tx are sent async for everything except commit() which is sent sync.
>
> persistent messages sent without a tx are sent sync.
>
> everything else is async.
>
>
>
>
> On Mon, Sep 2, 2013 at 9:05 AM, Raul Kripalani <raul@evosent.com> wrote:
>
> > Hi Gary,
> >
> > Are you sure that asyncSends are enabled by default even in transacted
> > sessions?
> > From what I recall, due to JMS spec requirements, asyncSends are disabled
> > when messages are PERSISTENT or transacted.
> >
> > Regards,
> >
> > *Raúl Kripalani*
> > Apache Camel PMC Member & Committer | Enterprise Architect, Open Source
> > Integration specialist
> > http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
> > http://blog.raulkr.net | twitter: @raulvk
> >
> > On Mon, Sep 2, 2013 at 2:32 PM, Gary Tully <gary.tully@gmail.com> wrote:
> >
> > > pending transactions are retained in memory, so you need to ensure
> > > that your destination limits are > than a transaction batch size (in
> > > message size, not number of messages)
> > >
> > > you can use sendFailIfNoSpace [1] to have the commit or send fail, but
> > > you will need to use alwaysSyncSend [2] to see the exception on a send
> > > b/c that is async by default.
> > >
> > > [1] http://activemq.apache.org/producer-flow-control.html
> > > [2] http://activemq.apache.org/async-sends.html
> > >
> > > On 2 September 2013 02:16, HellKnight <hellknight@foxmail.com> wrote:
> > > > I am suing activemq 5.8.0 , .NET 4.0 . I wrote a producer program
> > > ,sending
> > > > 100000 messages in a for loop , then called session.commit() since I
> am
> > > > using transactional mode.
> > > >     After 10 minutes, I checked the web console , and found out the
> > > broker
> > > > received no messages. Activemq.log showed an warning: wait for space
> to
> > > send
> > > > transacted message.
> > > >     But I think there should be a timeout/overtime exception for
> > > > session.commit() , it should not just keep waiting as long as
> possible,
> > > > instead it should throw out timeout exception after a certain time
> > > period.
> > > > Is there such an exception ?  Please help me.
> > > >
> > > >
> > > >
> > > > --
> > > > View this message in context:
> > >
> >
> http://activemq.2283324.n4.nabble.com/Is-there-an-timeout-exception-for-session-commit-tp4671013.html
> > > > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
> > >
> > >
> > >
> > > --
> > > http://redhat.com
> > > http://blog.garytully.com
> > >
> >
>
>
>
> --
> *Christian Posta*
> http://www.christianposta.com/blog
> twitter: @christianposta
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message