Postgres problem "table xxx alredy exist"

[dzerzhinsky]

Hello all!
The problem I've faced with is that when I create simple app that has only 2 beans (I need just to test)
and then deploy it to JBoss I have a message:

table "xxx" alredy exist

(As you understood - "xxx" is a name of sample table).
Here some fingerprints:
1. One of tables was created succesfuly;
2. After second time deployment I has 2 messages like above for all beans' tables;
3. I'm using JBoss 3.02, Postgres 7.3 and newest driver for Postgres

I've been searching inet for this problem and couldn't
find ANY messages concerning this.

I hope someone has this problem and could help me, I
can't start working on my project without it!

P.S I've deployed postgres-service.xml with only changes from /doc/jca/postgres.xml is dbURL and user name.

Oleg.

[juhalindfors]

There is no problem here. It is just an informational message telling you that a table for your bean already exists, so it will not be created. On your first deployment there was no such table, so the CMP engine created it for you.

-- Juha

[dzerzhinsky]

No! There is problem! After deployment only one table
was created - not two, but I have 2 Entity beans. Furthermore not only my application failed to deploy but also all JBoss examples.
By the way, it works fine with mySQL and Hypersonic, so it seems to be a problem of JBoss+Postgres

[juhalindfors]

In that case there is a mistake somewhere in your configuration. Check what exception stack traces you get during deployment. This feature does work with JBoss + PostgreSQL also.

Did you remove hypersonic datasource? Are both beans correctly looking up the same datasource, etc.

-- Juha

[dzerzhinsky]

OK. I'll bring you my postgres-service.xml - that is only
file I've changed from standart JBoss configuration, maybe you'll find any mistakes there.
P.S I've created beans with XDoclet so I haven't changed files in META-INF manualy. It means that there is no mistakes in deployment descriptor.

[dzerzhinsky]

Sorry, forgot to attach file :)

[juhalindfors]

The datasource configuration has nothing to do with CMP table creation. That configuration is in standardjbosscmp-jdbc.xml and your bean's jbosscmp-jdbc.xml files.

Using XDoclet does not guarantee your deployment descriptors are semantically correct. There's only some guarantee that they are syntactically correct (and with XDoclet's numerous bugs even that is not guaranteed).

Please attach all the deployment descriptors of your beans, especially your ejb-jar.xml and jbosscmp-jdbc.xml files. Also any possible stack traces your server console shows when your trying to deploy the beans.

-- Juha

[dzerzhinsky]

OK, here this files.
Server says next:
[aritec/Category] table "category" created successfuly
[aritec/Country] table "country" already exists

[juhalindfors]

Which of the two tables is not created in the DB?

-- Juha

[dzerzhinsky]

Country table wasn't created.
I've tested application with only one bean CountryBean with same configuration and table "country" have been created! I can't figure out what does it mean.

[juhalindfors]

Also is it possible for you to test it with a more recent bugfix release (3.0.8) ?

-- Juha

[juhalindfors]

I can't spot anything obviosly wrong with your deployment descriptors. I'm mystified... :-/

-- Juha

[dzerzhinsky]

Could you tell me where I can find this bugfix.
But there is a some strange fact - I've taken my JBoss release from some my friend and he says that it works perfectly for him (with Postgres). All product versions are equivalent.

[juhalindfors]

http://sourceforge.net/project/showfiles.php?group_id=22866

It's still quite possible there's some config glitch somewhere, I just can't think of where.

-- Juha

[dzerzhinsky]

Juha, I want to ask you - are you in ICQ now, maybe it would be better to talk directly. It's seems to me that I've found you ICQ account but it's offline.