agora inbox for pljava-dev@postgresql.org  
help / color / mirror / Atom feed
[Pljava-dev] crash due to huge load?
5+ messages / 0 participants
[nested] [flat]

* [Pljava-dev] crash due to huge load?
@ 2005-10-28 16:03  
  0 siblings, 2 replies; 5+ messages in thread

From:  @ 2005-10-28 16:03 UTC (permalink / raw)

Hi,

I'm using a recompiled last CVS-checkout of PLJAVA on PG8.0.3 and JDK1.5.0.

I build a thread-oriented trigger (make a thread which build a connection
to another
PG).

I obtain frequently this error msg:

 server closed the connection unexpectedly
        This probably means the server terminated abnormally
        before or while processing the request.

But I haven't any exception on thread-handled logs (LOG4J).

TIA
Roberto Colmegna


__________________________________________________________________
TISCALI ADSL
Solo con Tiscali Adsl navighi senza limiti e telefoni senza canone 
Telecom a partire da 19,95 Euro/mese.
Attivala subito, I PRIMI DUE MESI SONO GRATIS! CLICCA QUI:
http://abbonati.tiscali.it/adsl/sa/1e25flat_tc/







^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* [Pljava-dev] crash due to huge load?
@ 2005-10-28 18:38  
  parent: 
  1 sibling, 0 replies; 5+ messages in thread

From:  @ 2005-10-28 18:38 UTC (permalink / raw)

Roberto,
You have to supply the backend log. This doesn't tell me anything. And 
I'm not sure its such a good idea to use log4j with PL/Java. The 
standard Java logger (java.util.logging) is configured to use the 
backend logging utilities. Use that.

Regards,
Thomas Hallgren

rcolmegna at tiscali.it wrote:
> Hi,
>
> I'm using a recompiled last CVS-checkout of PLJAVA on PG8.0.3 and JDK1.5.0.
>
> I build a thread-oriented trigger (make a thread which build a connection
> to another
> PG).
>
> I obtain frequently this error msg:
>
>  server closed the connection unexpectedly
>         This probably means the server terminated abnormally
>         before or while processing the request.
>
> But I haven't any exception on thread-handled logs (LOG4J).
>
> TIA
> Roberto Colmegna
>
>
> __________________________________________________________________
> TISCALI ADSL
> Solo con Tiscali Adsl navighi senza limiti e telefoni senza canone 
> Telecom a partire da 19,95 Euro/mese.
> Attivala subito, I PRIMI DUE MESI SONO GRATIS! CLICCA QUI:
> http://abbonati.tiscali.it/adsl/sa/1e25flat_tc/
>
>
>
> _______________________________________________
> Pljava-dev mailing list
> Pljava-dev at gborg.postgresql.org
> http://gborg.postgresql.org/mailman/listinfo/pljava-dev
>   





^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* [Pljava-dev] crash due to huge load?
@ 2005-10-28 18:44  
  parent: 
  1 sibling, 0 replies; 5+ messages in thread

From:  @ 2005-10-28 18:44 UTC (permalink / raw)

I'm a bit curious. Why do you create a connection to another PG inside a 
trigger? That implies that you create another transaction that is not 
synchronized with the one your trigger is executing in. What happens if 
(when) your original transaction is rolled back?

Regards,
Thomas Hallgren

rcolmegna at tiscali.it wrote:
> Hi,
>
> I'm using a recompiled last CVS-checkout of PLJAVA on PG8.0.3 and JDK1.5.0.
>
> I build a thread-oriented trigger (make a thread which build a connection
> to another
> PG).
>
> I obtain frequently this error msg:
>
>  server closed the connection unexpectedly
>         This probably means the server terminated abnormally
>         before or while processing the request.
>
> But I haven't any exception on thread-handled logs (LOG4J).
>
> TIA
> Roberto Colmegna
>
>
> __________________________________________________________________
> TISCALI ADSL
> Solo con Tiscali Adsl navighi senza limiti e telefoni senza canone 
> Telecom a partire da 19,95 Euro/mese.
> Attivala subito, I PRIMI DUE MESI SONO GRATIS! CLICCA QUI:
> http://abbonati.tiscali.it/adsl/sa/1e25flat_tc/
>
>
>
> _______________________________________________
> Pljava-dev mailing list
> Pljava-dev at gborg.postgresql.org
> http://gborg.postgresql.org/mailman/listinfo/pljava-dev
>   





^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* [Pljava-dev] crash due to huge load?
@ 2005-10-29 06:52  
  0 siblings, 1 reply; 5+ messages in thread

From:  @ 2005-10-29 06:52 UTC (permalink / raw)

due to the fact that I can change my app-behaviour, I used a small "trick"!

When the app need to begin a transaction it must make two SQL calls:
1) BEGIN;
2) INSERT INTO distribtx.bound(state) VALUES('B');

the INSERT notify to PLJava the transaction begin.

At the commit:
1) COMMIT;
2) INSERT INTO distribtx.bound(state) VALUES('C');  [executed only without
commit except]

At the rollback:
1) ROLLBACK;
2) INSERT INTO distribtx.bound(state) VALUES('R');

As you can see the remote-DB coherence is assured.

This is in theory ... in pratic I must dismiss this architecture due to pgsql
crash ...
(sigh! ... I don't want use JBoss)


---- Messaggio originale ----
Data: Fri Oct 28 20:44:32 CEST 2005
Da: Thomas Hallgren<thomas at tada.se>
A: rcolmegna at tiscali.it
Cc: pljava-dev at gborg.postgresql.org
Ccn: 
Ogg.: Re: [Pljava-dev] crash due to huge load?


I'm a bit curious. Why do you create a connection to another PG inside a
trigger? That implies that you create another transaction that is not
synchronized with the one your trigger is executing in. What happens if
(when) your original transaction is rolled back?

Regards,
Thomas Hallgren

rcolmegna at tiscali.it wrote:
> Hi,
>
> I'm using a recompiled last CVS-checkout of PLJAVA on PG8.0.3 and JDK1.5.0.
>
> I build a thread-oriented trigger (make a thread which build a connection
> to another
> PG).
>
> I obtain frequently this error msg:
>
> server closed the connection unexpectedly
> This probably means the server terminated abnormally
> before or while processing the request.
>
> But I haven't any exception on thread-handled logs (LOG4J).
>
> TIA
> Roberto Colmegna
>
>
> __________________________________________________________________
> TISCALI ADSL
> Solo con Tiscali Adsl navighi senza limiti e telefoni senza canone
> Telecom a partire da 19,95 Euro/mese.
> Attivala subito, I PRIMI DUE MESI SONO GRATIS! CLICCA QUI:
> http://abbonati.tiscali.it/adsl/sa/1e25flat_tc/
>
>
>
> _______________________________________________
> Pljava-dev mailing list
> Pljava-dev at gborg.postgresql.org
> http://gborg.postgresql.org/mailman/listinfo/pljava-dev
>

__________________________________________________________________
TISCALI ADSL
Solo con Tiscali Adsl navighi senza limiti e telefoni senza canone 
Telecom a partire da 19,95 Euro/mese.
Attivala subito, I PRIMI DUE MESI SONO GRATIS! CLICCA QUI:
http://abbonati.tiscali.it/adsl/sa/1e25flat_tc/







^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* [Pljava-dev] crash due to huge load?
@ 2005-10-29 08:26  
  parent: 
  0 siblings, 0 replies; 5+ messages in thread

From:  @ 2005-10-29 08:26 UTC (permalink / raw)

Roberto,
You can never guarantee coherence between two databases unless you use 
2-phase commits.
Think "what if I pull the plug at precisely this moment" (i.e. between 
#1 and #2 for instance).

Regarding the crash, I would really like to help you find the cause, but 
you will have to provide the backend log.

Regards,
Thomas Hallgren

rcolmegna at tiscali.it wrote:
> due to the fact that I can change my app-behaviour, I used a small "trick"!
>
> When the app need to begin a transaction it must make two SQL calls:
> 1) BEGIN;
> 2) INSERT INTO distribtx.bound(state) VALUES('B');
>
> the INSERT notify to PLJava the transaction begin.
>
> At the commit:
> 1) COMMIT;
> 2) INSERT INTO distribtx.bound(state) VALUES('C');  [executed only without
> commit except]
>
> At the rollback:
> 1) ROLLBACK;
> 2) INSERT INTO distribtx.bound(state) VALUES('R');
>
> As you can see the remote-DB coherence is assured.
>
> This is in theory ... in pratic I must dismiss this architecture due to pgsql
> crash ...
> (sigh! ... I don't want use JBoss)
>
>
> ---- Messaggio originale ----
> Data: Fri Oct 28 20:44:32 CEST 2005
> Da: Thomas Hallgren<thomas at tada.se>
> A: rcolmegna at tiscali.it
> Cc: pljava-dev at gborg.postgresql.org
> Ccn: 
> Ogg.: Re: [Pljava-dev] crash due to huge load?
>
>
> I'm a bit curious. Why do you create a connection to another PG inside a
> trigger? That implies that you create another transaction that is not
> synchronized with the one your trigger is executing in. What happens if
> (when) your original transaction is rolled back?
>
> Regards,
> Thomas Hallgren
>
> rcolmegna at tiscali.it wrote:
>   
>> Hi,
>>
>> I'm using a recompiled last CVS-checkout of PLJAVA on PG8.0.3 and JDK1.5.0.
>>
>> I build a thread-oriented trigger (make a thread which build a connection
>> to another
>> PG).
>>
>> I obtain frequently this error msg:
>>
>> server closed the connection unexpectedly
>> This probably means the server terminated abnormally
>> before or while processing the request.
>>
>> But I haven't any exception on thread-handled logs (LOG4J).
>>
>> TIA
>> Roberto Colmegna
>>
>>
>> __________________________________________________________________
>> TISCALI ADSL
>> Solo con Tiscali Adsl navighi senza limiti e telefoni senza canone
>> Telecom a partire da 19,95 Euro/mese.
>> Attivala subito, I PRIMI DUE MESI SONO GRATIS! CLICCA QUI:
>> http://abbonati.tiscali.it/adsl/sa/1e25flat_tc/
>>
>>
>>
>> _______________________________________________
>> Pljava-dev mailing list
>> Pljava-dev at gborg.postgresql.org
>> http://gborg.postgresql.org/mailman/listinfo/pljava-dev
>>
>>     
>
> __________________________________________________________________
> TISCALI ADSL
> Solo con Tiscali Adsl navighi senza limiti e telefoni senza canone 
> Telecom a partire da 19,95 Euro/mese.
> Attivala subito, I PRIMI DUE MESI SONO GRATIS! CLICCA QUI:
> http://abbonati.tiscali.it/adsl/sa/1e25flat_tc/
>
>
>
>   





^ permalink  raw  reply  [nested|flat] 5+ messages in thread


end of thread, other threads:[~2005-10-29 08:26 UTC | newest]

Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2005-10-28 16:03 [Pljava-dev] crash due to huge load? 
2005-10-28 18:38 ` 
2005-10-28 18:44 ` 
2005-10-29 06:52 [Pljava-dev] crash due to huge load? 
2005-10-29 08:26 ` 

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox