Re: Fwd: Postgres JDBC, WS and commit

Hi,

This may means, but I'm not quite sure:
- you don't have commit, when you close connection rollback is fired if
connection is not in autocommit mode.
- I suspect you may lock row (this connection that have null), so check
if other request do not wait, you may do this with viusalvm, or any
debugger inspecting all threads stacks.

Or if you use multinode this may be root problem too, there was some
posts about syncing master-slave.

Regards,
Radek

On Mon, 14 May 2012 08:41:32 +0200, Mephysto wrote:
> Hi Radoslaw,
> I was referring to Glassfish threads. I dont run any other thread
> from
> my ejb.
>
> The problem is that sometimes, in this configuration, I retrieve null
> output from data from database, but indeed the real value is not
> null.
>
> Thank you very much.
>
> Meph
>
> On 13 May 2012 21:10, Radosław Smogura  wrote:
>
>> Sorry for replaying for self.
>>
>> Dnia niedziela, 13 maja 2012 21:01:16 Radosław Smogura pisze:
>>
>>> Dnia piÄ…tek, 11 maja 2012 06:08:11 mephysto pisze:
>> > > Hello newly,
>> > > I tried to enable "Non Transacitonal Connection" and my
>> function execute
>> > > commit as I want, but at the moment I have some little problems
>> with
>> > > threads and I dont know the reason of these problems.
>> >
>> > Actually non transactional connection makes connections unmanaged
>> by
>> > Glassfishs transaction manager, so EJB as well.
>> Threads? What kind of problems do you have? You should not use
>> threads in EJB
>> and Web.
>>
>> > > I would to know more about pgConnectionpoolDataSource and
>> pgXADataSource
>> > > to
>> > > set correct datasource in Glassfish connection pool. Where can
>> I find
>> > > documentation about these two kind of DataSource?
>> >
>> > Both are almost same (do not mix it with Polling data source), in
>> fact XA is
>> > build on top of PGConnectionPool. Difference between those is
>> transaction
>> > managment, XA requires transaction manager as every XA resource
>> and needs
>> > to implement specific interface, PGConnectionPool doesnt require
>> it. I
>> > cant imagine XA resource without transactions, probably this may
>> work like
>> > autocommit.
>> >
>> > > If I will use a multinode postgres managed by pgpool, which
>> DataSource
>> > > suits my needs?
>> >
>> > There should be no difference, both connection will connect to
>> pgpool.
>> >
>> > In any case I suggest you to try to use
>> @TransactionAttribute(REQUIRES_NEW)
>> > or @TransactionManagement(BEAN). Such application that relies on
>> Glassfish
>> > specific feature like non transactional connection will not be
>> portable.
>> > > Thanks in advance.
>> > >
>> > > Meph
>> > >
>> > >
>> > >
>> > >
>> > > --
>> > > View this message in context:
>> > >
>>
>
> http://postgresql.1045698.n5.nabble.com/Postgres-JDBC-WS-and-commit-tp5697
>> [1]
>> > > 6
>> > > 57p5702984.html Sent from the PostgreSQL - jdbc mailing list
>> archive at
>> > > Nabble.com.
>
>
>
> Links:
> ------
> [1]
>
> http://postgresql.1045698.n5.nabble.com/Postgres-JDBC-WS-and-commit-tp5697
> [2] mailto:rsmogura@softperience.eu