Subject | Re: FB 1.5.3 localhost error on JBoss 4.0.4 CR 2 |
---|---|
Author | hi_feroz |
Post date | 2006-05-09T12:19:46Z |
hi helen,
thanks for the reply. it really helped a lot.
i did a fresh installation of Mandrake 10.1 and followed step-by-
step procedure and all worked fine, though there were few problems
like glibstd++.so.5. i had so.6, it still requires so.5 to be there.
it is definitely linux + firebird, know how issue. Nothing related
to JBoss.
now, on the coming week-end, i hope to get production server up and
running.
will keep you posted.
btw: am using FirebirdCS-1.5.3.4870, Mandrake 10.1, JBoss 4.0.4CR2,
EJB3 and application will go live by end of this month;)
thanks again!
--- In Firebird-Java@yahoogroups.com, Helen Borrie <helebor@...>
wrote:
thanks for the reply. it really helped a lot.
i did a fresh installation of Mandrake 10.1 and followed step-by-
step procedure and all worked fine, though there were few problems
like glibstd++.so.5. i had so.6, it still requires so.5 to be there.
it is definitely linux + firebird, know how issue. Nothing related
to JBoss.
now, on the coming week-end, i hope to get production server up and
running.
will keep you posted.
btw: am using FirebirdCS-1.5.3.4870, Mandrake 10.1, JBoss 4.0.4CR2,
EJB3 and application will go live by end of this month;)
thanks again!
--- In Firebird-Java@yahoogroups.com, Helen Borrie <helebor@...>
wrote:
>here
> At 12:11 PM 9/05/2006, hi_feroz wrote:
>
> I am clueless about JBoss but I'll comment on a couple of things
> relating to Linux installations and Mandriva.more
>
> >i can ping localhost. localhost is working fine.
> >
> >i got it working on another linux box (Mandrake 10.1). here are
> >details.option
> >
> >My First Server is Mandriva 2006 (Admin guy installed with the
> >of high security)between "whenever
> >1) Can ping localhost 127.0.0.1 (he allowed it)
> >2) Firebird Installed -> Working fine -> tested thru isql
>
> 2 important questions here:
>
> 1) Which model of Firebird did you install (Classic/Superserver)?
> 2) Exactly what the successful connection string you gave to isql?
>
> >4) Configured firebird-ds.xml in JBoss. Whenever I user localhost
> >inside there, it would give error. Then i gave the full path, it
> >didn't give any errors when starting JBoss.
>
> It is not at all clear what the difference is here
> I use localhost" and "I gave the full path". Are you saying that,your
> when you use localhost (which is a host name) you are expecting
> application to connect to the database with no path?error,
>
> >5) I deployed my application in JBoss, and it gives localhost
> >even though i am not using localhost in firebird-ds.xml file. Itried
> >giving ip address, full path but it would still give localhosterror
> >(Please note that i cleared Jboss cache everytime i did a change)on
>
> Do you understand that
> 1) localhost is applicable only when the client and the server are
> the same machine?connections.
> 2) localhost accesses the TCP/IP local loopback server. As far as
> the Firebird connection protocol is concerned, it is *not* a local
> connection but a remote one.
>
> --> If it is the case that you were able to access the database
> locally *without* the remote protocol, then you are using Classic,
> not Superserver. Superserver on Linux does not accept hostless
>a
> >So, I gaveup and installed Mandrake 10.1 on my laptop:
> >1) Can ping localhost
> >2) Firebird CS 1.5.3 -> OK
> >3) JBoss -> OK
> >4) Installed my app, it didn't give any localhost errors, but got
> >different error with saying username and password not defined(even
> >though i am using default SYSDBA and masterky).can
>
> First, 'masterkey' is NOT the default sysdba password on
> Linux. During installation, a sysdba password is created. You
> cat the file SYSDBA.password in /opt/firebird to find out what itis,
> and change it using gsec.you
>
> Note that, when you log in directly to a database under Classic
> don't need the username and password because the sysdba usernameand
> password are available through the environment variables ISC_USERand
> ISC_PASSWORD.are
>
> However, with SS (which I don't think you are using) the envvars
> no use to you, since a remote connection is mandatory with SS andone
> remote connections must supply username and password.
>
> Second, last week when I did a full install of Mandriva 10.2 on
> of my servers using the "typical" install from the distributionroot)
> disks, I discovered (after much frustration) that xinetd was not
> installed. You can test this on your installation by doing (as
>will
> service xinetd restart
>
> If it comes up with a message to the effect that 'module xinetd
> cannot be found' then you have the same problem. The cure is to
> install the xinetd package from Disk 1. Then, to be certain it
> start automatically next time you boot the machine, dolocal
>
> chkconfig xinetd
>
> If it doesn't error, then your problem re the localhost connection
> almost certainly relates to the client version. A "hostless"
> connect (which, on the Linux Classic server, is a directconnection
> to the database) uses libfbembed.so. A remote connection, i.e.using
> localhost, requires libfbclient.so. When I installed Fb 1.5.3 onis
> this new server installation via the RPM installer, libfbclient.so
> was missing and I couldn't use localhost. (I think libfbclient.so
> in the .tar.bz2 kit though...)Classic
>
> This doesn't worry me. I could grab libfbclient.so from the
> or Superserver tarball kit (.tar.bz2) and symlink to it. But Idon't
> care, because with Classic I can just use a hostless connectionrunning,
> locally from my web app or the tools. As long as xinetd is
> connections from remote clients work just fine.guest
>
> >I searched thru web
> >and found out that Linux and JBoss security options. JBoss has a
> >user, so i created guest user in Firebird and assigned to SYSDBArole.
> >I also used this user in congiguring web.xml file.
>
> If you created a role named SYSDBA then this is another possible
> source of your problems. When there is a role named SYSDBA, the
> sysdba user cannot access the database.
>
> I think you have a mixture of "things gone wrong" here....
>
> Helen
>