Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Date: Tue, 15 Nov 2011 08:07:35 -0800 (PST)
From: bvahdat <babak.vahdat@swissonline.ch>
To: users@camel.apache.org
Message-ID: <1321373255714-4994753.post@n5.nabble.com>
In-Reply-To: 
 <CAGB5yNmbC=_oyaHqigJDdMO9uAWD_SaLpiaFjs0-xtQij0nduw@mail.gmail.com>
References: <4EB3B700.2050301@die-schneider.net>
 <CAGB5yNk7qvb+2r-sUigdEai+qCygmVPtfqT_bdLNJKC-6DqzTg@mail.gmail.com>
 <1320430916315-4964858.post@n5.nabble.com>
 <CAGB5yNkmsTjzV2QDPMoPwPVm-hybRr6_mOVwdDJZwZ0yA27bFQ@mail.gmail.com>
 <1321103009298-4986867.post@n5.nabble.com>
 <CAGB5yNmwWSPQ5F1m=qRuUO4RK7MATqkMS64E1wTtM6mYXkLhFQ@mail.gmail.com>
 <CAGB5yNm6WTh2Hg_hzjsfp8Jwd1MEEtnfyLL1MEuN35KKpViO6Q@mail.gmail.com>
 <CAD0r13fe7zbw8E70QwOALyeuP-tUxC3AKepbkUi0fzQzYZOXmw@mail.gmail.com>
 <CAGB5yNk2pA-v71x3+r_r-isWMGKYVGKnyScdT8GWLX4AGgLjyA@mail.gmail.com>
 <CAGB5yNmbC=_oyaHqigJDdMO9uAWD_SaLpiaFjs0-xtQij0nduw@mail.gmail.com>
Subject: Re: Misleading jmx statistics on jpa component
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

@Claus,

That's for sure may be not correct, but it's how I see it:

To my understanding in the sense of the CRUD operation one can C, U or D an
entity through the JpaProducer, however
only R through a JpaConsumer, so don't get the point why JpaConsumer should
do entityManager.flush() at all, for
example while polling! Other than that I don't think that calling
entityManager.flush() could help in any way in
the case the JPA-Provider throws PersistenceException in JpaConsumer.poll()
and that gets just swallowed & flush()
gets called afterwards. To me that PersistenceException would mean that some
serious problems on the DB occured while
reading through a JPA or Native Query on the JpaConsumer from which we could
ever/never recover ourself:

                PersistenceException cause = null;
                int messagePolled = 0;
                try {
                    messagePolled = processBatch(CastUtils.cast(answer));
                } catch (Exception e) {
                    if (e instanceof PersistenceException) {
                        cause = (PersistenceException) e;
                    } else {
                        cause = new PersistenceException(e);
                    }
                }

                if (cause != null) {
                    if (!isTransacted()) {
                        LOG.warn("Error processing last message due: {}.
Will commit all previous successful processed message, and ignore this last
failure.", cause.getMessage(), cause);
                        entityManager.flush();
                    } else {
                        // rollback all by throwning exception
                        throw cause;
                    }
                }

In the sense of the expected ACID properties I think having that
consumer.transacted default to false would violate the A (all or nothing).
Maybe true would be better. Again that's just my 2 cents which may be not
correct at all.

Thanks, Babak

--
View this message in context: http://camel.465427.n5.nabble.com/Misleading-jmx-statistics-on-jpa-component-tp4960503p4994753.html
Sent from the Camel - Users mailing list archive at Nabble.com.