Diagnosing JBossCMP issues is not for the faint of heart, in that one
of its main raison d'etre's is to hide SQL knowledge away from the
casual coder. Add into the mix the concurrency issues which naturally
occur since an EJB container is multithreaded and the overly
complicated JTA stuff a
Andy Dale wrote:
Hi,
I will explain in more details what the test (extremely simple) program is
actually doing. A session bean receives some data (roughly 3K) and then
persists this data to the database with EntityManager.persist() (using the
EJB 3.0 Persistence API that comes with JBoss). Onc
Andy Dale wrote:
Hi,
I have performed some tests earlier on today, and i think the problem lies
with Postgres and it's bad performance when being used with container
managed persistence.
Is your problem performance or an error? It sounded like you were
getting errors in your first post.
>
Hi,I have performed some tests earlier on today, and i think
the problem lies with Postgres and it's bad performance when being used
with container managed persistence. I am covinced of it being an issue
with postgres because it works really well with MySQL and Hypersonic,
but not with Postgres.
"Andy Dale" <[EMAIL PROTECTED]> writes:
> The current problem we seem to have is that the data is persisted ok
> (or at least it seems to be in there with pgadmin), but cannot be
> read back out of the database all the time (in fact for about 90% of
> the time), the current behaviour of the applic
