Eclipse Community Forums: EMF » CDO make table DB bug

Help

Home

Home » Modeling » EMF » CDO make table DB bug

Show: Today's Messages :: Show Polls :: Message Navigator

CDO make table DB bug [message #423056]

Mon, 22 September 2008 11:23

Paul Richardson

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

Report message to a moderator

Re: CDO make table DB bug [message #423059 is a reply to message #423056]

Mon, 22 September 2008 13:31

Paul Richardson

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

Report message to a moderator

Re: CDO make table DB bug (NEW CONFIG PROPERTY) [message #423068 is a reply to message #423059]

Mon, 22 September 2008 15:05

Eike Stepper

Messages: 6690
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

Cheers
/Eike

----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper

Report message to a moderator

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

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Sep 26 02:26:05 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter