On 6 Dec 00, at 10:19, Paul Reeves wrote:

> tengicki@... wrote:
> >
> > Hello,
> >
> > I have some problem with interclient 1.6 and interbase 6.0 under
> > Linux (FreeBSD).
> >
> > Our provider has organized the server in subsystems. Thats means
> > that there are logical system with own ip-adresses and access
> > rights on one physical system.
> >
> > for example the server has the ip 1.2.3.1 (and can be called as
> > localhost (127.0.0.1)
> >
> > an apache with jserv is runnung unser ip 1.2.3.2 on the same
> > server and make a connect to interclient
> > jdbc:interbase://localhost//usr/databases/db.gdb thats work fine
> >
> > now we have running a second apache with jserv under ip 1.2.3.3
> > on this
> > server. apache and jserv work well
> >
> > But if I try to connect the database from the second jserv
> > environment the
> > java statement
> >
> > java.sql.DriverManager.getConnection (databaseURL, user, password)
> >
> > didn't come back. No exception, or something like else.
> >
> > Because of the fact that all subsystem has the same physical server
> > localhost "pointed" to the same machine. If there is any call
> > identification via localhost it must fail. What uses interclient to
> > connect to interbase, what uses jdbc as local ip where the call come
> > from. How can interclient make differences between the calls from
> > subsystem on (1.2.3.2) and subsystem (1.2.3.3) if they have the same
> > localhost (127.0.0.1).
> >
> > Have anyone any idea, about what happens, what is to do, where I can
> > find more information. Thank you.
> >
>
> I am not entirely clear about what is going on, or why. Whose convenience
> is this setup for?

This setup is for a secure webserver with more than one domain.
Each domain has his own ip, apache, jserv etc, and should be
work with the same database in the main system. But you can't
reach the main system from the external network (internet), only
via the subsystems. The problem is all (logical) systems are on the
same computer (hardware).

> Anyway, I would start from first principles. Have subsystems 1.2.3.2 and
> 123.3 got names? Are they in the hosts file(s)?

Yes they are (now :-) ) but it didn't change anything

>Can you ping one from the
> other, and vice versa. Once you have reassured yourself that the tcp/ip
> transport is working properly then you should be able to connect in the
> normal way. ie: subsystemname:/path/to/database/database.gdb

I try the ping and it work, but the path to the database is
main systemname:/path/to/database/database.gdb

I believe the problem is, that the database client 1.2.3.2 send as is
own ip to the interbase on (localhost) the IP Adress 127.0.0.1.

And if there is the same connect from 1.2.3.3 then is there trouble,
becaus interbase didn't know where to send the data 127.0.0.1
(means 1.2.3.2) or 127.0.0.1 (means 1.2.3.3).

But I have a idea, I will try to connect via mainsystem:...gdb to the
database and not with localhost ....

By the way I be happy about any idea more, and thanks for your
help
Best regards from Griesheim, Germany
Andreas Tengicki

--- ----
SDCTec Software Development Consult GmbH
www.sdctec.net
Consulting, Training and Software Development
for InterBase, Oracle and Inter-/ Intranet
--- ----