db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dibyendu Majumdar" <dibye...@mazumdar.demon.co.uk>
Subject Re: Identifer 200 not registered
Date Tue, 31 May 2005 23:56:09 GMT
Hi Dan,

To reproduce this error, you have to do following:

1) Apply Kathey's patch for DERBY-246. This causes XA.end() to hang in the
test program attached.
2) Create a new database.
3) Create following table:
create table dept (
 deptno decimal(2) not null constraint dept_pk primary key,
 dname varchar(30),
 loc varchar(30)
);
4) Start network server.
5) Run attached test program. It should hang. Kill it.
6) Kill the network server.
7) Any attempt to restart the database after this will generate this error.

Regards

Dibyendu
----- Original Message ----- 
From: "Daniel John Debrunner" <djd@debrunners.com>
To: "Derby Development" <derby-dev@db.apache.org>
Sent: Tuesday, May 31, 2005 11:19 PM
Subject: Re: Identifer 200 not registered


> Daniel John Debrunner wrote:
>
> > A week or so ago there was some discussion of a problem with recovery
> > and format identifier 200 not being registered.
> >
> > That's a problem with one of my changes and I have a quick fix but was
> > there a way to reproduce this? I can't remember who had the problem.
>
> OK - I see now that it's Derby-325 (see the stack trace).
>
> http://issues.apache.org/jira/browse/DERBY-325
>
> Dan.
>

Mime
View raw message