Re: Wait event SQL*Net break/reset to client caused by duplicate insert?

From: amit poddar <amit.poddar_at_yale.edu>
Date: Thu, 10 Apr 2008 07:39:18 -0400
Message-ID: <47FDFC66.2030907@yale.edu>

The exception should not be propagated to the client to avoid this event. That would mean the exception needs to be handled on the database which can only happen in a PLSQL block.

Handling exception in java means the exception is propagated to the client and hence the wait event

amit

Peter Hitchman wrote:
> Hi,
> Just to follow up, having read your Blog entry ...
>
> The java code is handling the exception, so is there a difference in
> the way this event gets fired between a java JDBC programme and server
> side PL/SQL code, because of the client/server nature of the java?
>

--
http://www.freelists.org/webpage/oracle-l

Received on Thu Apr 10 2008 - 06:39:18 CDT

This message: [ Message body ]
Next message: Nigel Thomas: "Re: Wait event SQL*Net break/reset to client caused by duplicate insert?"
Previous message: Ian Cary: "IANS> var x numberRe: application deadlock ORA-00060"
In reply to: Peter Hitchman: "Re: Wait event SQL*Net break/reset to client caused by duplicate insert?"
Next in thread: Tanel Poder: "RE: Wait event SQL*Net break/reset to client caused by duplicate insert?"

Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ]

Original text of this message