[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Handle-info] Help with java handle system client library

Hi Sean,
For both the times, the error occurred because I was inserting some value that was too big with respect to the definition of the database column. In both cases, I had a SQL exception reported in the error.log file <<java.sql.SQLException: ORA-01401: inserted value too large for column>> followed by a sequence of

<<"Thu Mar 15 15:04:46 CET 2007" 100 Error committing transaction: HandleException (INTERNAL_ERROR) Error creating handle: java.sql.SQLException: ORA-01401: inserted value too large for column>>

At this point, the handle system hanged up and I had to restart it; after that restart, I got the error:

<<"Thu Mar 15 16:04:35 CET 2007" 75 Unable to insert transaction into queue>>

Hence, the errors are actually two instances of the same problem and occurred because I tried to insert some value that was violating the dimensions specified in the handle database definition.

Thank you very much again.

Best regards,
    nicola

Sean Reilly ha scritto:
Hi Nicola,

Can you send me the handle and/or values that seem to cause the transaction queue to stop working? This should not be possible, so I'm very interested in figuring out what might be going on.

Trying the latest release is definitely a good idea, even though the transaction log code hasn't changed much (if at all) since 5.3.

Thanks,
Sean

On Mar 21, 2007, at 9:28 AM, Nicola Mezzetti wrote:

Hi Sean,
I met the problem again, however I can exclude that it was a problem of permissions or a problem of disk space. As far as I understood, the problem occurs when one tries to store misformed handle values; in this case, the insertion obviously fails but it appears that the handle system cannot insert any further transaction (either correct or not) within the same transaction queue file.

For both the times that error occurred, the workaround for the problem was to wait the next day and then to restart the handle system in order for another transaction queue file to be initialized.

Now, I will try to understand whether it is a software problem or a problem caused by the transaction queue that gets corrupted. For the sake of precision, we still employ the handle system version 5.3. When I will find some spare time, I will check whether the problem occurs even with the current release. In any case, I will let you know more about this.

Thank you very much for your kindness and availability.

Best regards,
    nicola

Sean Reilly ha scritto:
Hi Nicola,
I don't think the error you are seeing has anything to do with the data in the handle value. I would check your server to make sure that the "txns" subdirectory of the server directory is writable by the server or that your server still has disk space available in the partition used by the server.
The "Unable to insert transaction into queue" shouldn't happen unless the server can't write to the replication log for some reason.
Thanks,
Sean
On Mar 16, 2007, at 8:24 AM, Nicola Mezzetti wrote:
Hi,
my name is Nicola Mezzetti and I write to have some information about an error that I encounter while developing with the java handle system client library.

Specifically, I need to register, together with other values, a handle value containing some metadata about the handle. In doing this, I defined a new data type whose utf8 encoding I employ to instantiate this new handle value, together with the utf8 encoding of the xml metadata (obtained using the encodeString method).

Now, when the handle request is processed, I get from the handle system an error 75, having description "Unable to insert transaction into queue". Could it be that I do something wrong while encoding the type and data? Or maybe do I have to follow some specific algorithm to encode data strings containing xml? Finally, could the error be caused by the self defined type?

Waiting for receiving your reply, I thank you all in advance for your kindness and availability.

Best regards,
     Nicola Mezzetti

----------------------------------------------------

Nicola Mezzetti, Ph.D.

Software Architect and IT Consultant at mEDRA
c/o    CINECA (http://www.cineca.it)
    Via Magnanelli 6/3,
    40033  Casalecchio di Reno (BO)
    Italy

e-mail: n.mezzetti@cineca.it
office: +39-051-6171382
mobile: +39-333-8420472
fax   : +39-51-6132198

--------------------------------------------------


_______________________________________________
Handle-Info mailing list
Handle-Info@cnri.reston.va.us
http://www.handle.net/mailman/listinfo/handle-info


----------------------------------------------------

Nicola Mezzetti, Ph.D.

Software Architect and IT Consultant at mEDRA
c/o    CINECA (http://www.cineca.it)
    Via Magnanelli 6/3,
    40033  Casalecchio di Reno (BO)
    Italy

e-mail: n.mezzetti@cineca.it
office: +39-051-6171382
mobile: +39-333-8420472
fax   : +39-51-6132198

--------------------------------------------------



--
--------------------------------------------------

Nicola Mezzetti, Ph.D.

Software Architect and IT Consultant at mEDRA
c/o	CINECA (http://www.cineca.it)
	Via Magnanelli 6/3,
	40033  Casalecchio di Reno (BO)
	Italy

e-mail: n.mezzetti@cineca.it
office: +39-051-6171382
mobile: +39-333-8420472
fax   : +39-51-6132198

--------------------------------------------------


_______________________________________________
Handle-Info mailing list
Handle-Info@cnri.reston.va.us
http://www.handle.net/mailman/listinfo/handle-info