Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Modeling » EMF » CDO make table DB bug
CDO make table DB bug [message #423056] Mon, 22 September 2008 11:23 Go to next message
Paul Richardson is currently offline Paul RichardsonFriend
Messages: 33
Registered: July 2009
Member
Guys,

Cannot file bugs at the moment. Bugzilla seems to not be working.

Anwyay this is the text of the bug:

Infinite loop found in
org.eclipse.emf.cdo.server.internal.db.ClassMapping.java

Steps To Reproduce:
Register a model with CDO containing a class called Project
Register a second model with CDO containing a different class called Project
Add a Project from the first model
Add a Project from the second model
Error

More information:
When an exception occurs in the following method, the catch shows a
tracer entry but fails to progress the loop resulting in an infinite
loop and a server hang. The client eventually throws a timeout
exception. Some kind of condition needs to be added to the for loop to
return the failure elegantly rather than bringing down the server?

protected IDBTable addTable(String name)

A correlary to this is that if the database tables are simply labelled
by their class names, does that mean that registering 2 different ecore
models with the same server that happen to have classes of the same name
will fail to be added to the database correctly? Can the db table names
be qualified with their namespace etc... to ensure this doesnt happen?

Regards

PGR
Re: CDO make table DB bug [message #423059 is a reply to message #423056] Mon, 22 September 2008 13:31 Go to previous messageGo to next message
Paul Richardson is currently offline Paul RichardsonFriend
Messages: 33
Registered: July 2009
Member
bug now filed as #248134.

phantomjinx wrote:
> Guys,
>
> Cannot file bugs at the moment. Bugzilla seems to not be working.
>
> Anwyay this is the text of the bug:
>
> Infinite loop found in
> org.eclipse.emf.cdo.server.internal.db.ClassMapping.java
>
> Steps To Reproduce:
> Register a model with CDO containing a class called Project
> Register a second model with CDO containing a different class called
> Project
> Add a Project from the first model
> Add a Project from the second model
> Error
>
> More information:
> When an exception occurs in the following method, the catch shows a
> tracer entry but fails to progress the loop resulting in an infinite
> loop and a server hang. The client eventually throws a timeout
> exception. Some kind of condition needs to be added to the for loop to
> return the failure elegantly rather than bringing down the server?
>
> protected IDBTable addTable(String name)
>
> A correlary to this is that if the database tables are simply labelled
> by their class names, does that mean that registering 2 different ecore
> models with the same server that happen to have classes of the same name
> will fail to be added to the database correctly? Can the db table names
> be qualified with their namespace etc... to ensure this doesnt happen?
>
> Regards
>
> PGR
Re: CDO make table DB bug (NEW CONFIG PROPERTY) [message #423068 is a reply to message #423059] Mon, 22 September 2008 15:05 Go to previous message
Eike Stepper is currently offline Eike StepperFriend
Messages: 6464
Registered: July 2009
Senior Member
phantomjinx schrieb:
> bug now filed as #248134.

An exception should be thrown now.
And I added a new "qualifiedNames" config property for the mapping strategy,
e.g.

<store type="db">
<mappingStrategy type="horizontal">
<property name="qualifiedNames" value="false"/>


Cheers
/Eike


> phantomjinx wrote:
>> Guys,
>>
>> Cannot file bugs at the moment. Bugzilla seems to not be working.
>>
>> Anwyay this is the text of the bug:
>>
>> Infinite loop found in
>> org.eclipse.emf.cdo.server.internal.db.ClassMapping.java
>>
>> Steps To Reproduce:
>> Register a model with CDO containing a class called Project
>> Register a second model with CDO containing a different class called
>> Project
>> Add a Project from the first model
>> Add a Project from the second model
>> Error
>>
>> More information:
>> When an exception occurs in the following method, the catch shows a
>> tracer entry but fails to progress the loop resulting in an infinite
>> loop and a server hang. The client eventually throws a timeout
>> exception. Some kind of condition needs to be added to the for loop
>> to return the failure elegantly rather than bringing down the server?
>>
>> protected IDBTable addTable(String name)
>>
>> A correlary to this is that if the database tables are simply
>> labelled by their class names, does that mean that registering 2
>> different ecore models with the same server that happen to have
>> classes of the same name will fail to be added to the database
>> correctly? Can the db table names be qualified with their namespace
>> etc... to ensure this doesnt happen?
>>
>> Regards
>>
>> PGR


Previous Topic:Manage compatibility between model files
Next Topic:[Teneo] How to model a map?
Goto Forum:
  


Current Time: Sat Jan 18 06:23:03 GMT 2020

Powered by FUDForum. Page generated in 0.01924 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top