I don't understand anything

[Andrey Aristarkhov]

Hi!

I stop understanding my BAS behaviour.
I have EntityBeanA (EBA) and SessionBeanA (SBA) (wrapper for entity) in one
jar. Also I have EntityBeanB (EBB) and SessionBeanB (SBB).
EntityBeanA and EntityBeanB have on-to-one relation (by PK).
In some cases I need to update EBA when updating EBB.
A code for this operation looks like this (in SBB)
..
[1] ebb = EBBHome.findByPrymaryKey(PK);
[2] eba = SBA.getEBA(PK); // actually wrapper for
EBAHome.findByPrimaryKey(PK) in SBA.
[3] // updating EBB
[4] // updating EBA
[5] SBA.updateEBA(eba);
...
I has been working an hour ago. But now I got an exception for line 2 of
code above:

java.rmi.ServerException: Could not obtain JDBC Connection from datasource:
datasource/interbase; nested exception is:
java.sql.SQLException: ITS-7001: A transaction can only support one type of
url, username, and password

Datasource "datasource/interbase" points to the same database in both jars.
I did not modify anything that could leads to the error (I think... But I'm
sure th described method in SBB was not modified)

What did I miss? Have I change something accidentally?
Point me a digging direction at least.
Thank you in advance.

--
Andrey Aristarkhov

[Krishnan Subramanian]

Andrey,

Make sure the datasources are identical in case as well and
that one datasource does not use a name while the other
uses an IP for the machine name etc.

Or merge the jars into one or package them in an ear.

-krish

"Andrey Aristarkhov" <Arist...@jbuilder.ru> wrote in message news:3bd47761_2@dnews...

[Andrey Aristarkhov]

Krishnan,

datasources are completely identical. I have used "existing connection" from
DB Pilot for datasource creation.

Andrey

PS.
I've found a workaround by merging two jars in a sangle jar. But it's not
always possible.

"Krishnan Subramanian" <ksubra...@borland.com> wrote in message
news:3bdc471b_1@dnews...