Hi Rick,

Thanks for your reply. As you suggested I tried to install Tomcat
5.5.17. The install went fine and tomcat was able to run fine. I did
configure the manager role to login, which also worked.

But when I added the context which I had on my Tomcat 5.5.9 install
the directory that used to show up is not coming up now.

This is how I have it set in the server.xml file, right above
</Host> entry.

++
<Context path="/picture" docBase="test" debug="0"
reloadable="true" />
</Host>
++

Where "test" is a directory located as $CATALINA_HOME/webapps/test

When I try to access www.mydomain.com/picture, I get the error
below. This used to work just fine with my Tomcat 5.5.9, but not on
5.5.17. I did bounce tomcat after these changes, but did not help. I
also read that you need to have the context entry in the context.xml
file for tomcat version 5.5.x, but not really clear on this.
++
HTTP Status 404 - /picture/
---------------------------------------------------------------------
-----------
type Status report
message /picture
description The requested resource (/picture) is not available.
---------------------------------------------------------------------
----------
Apache Tomcat/5.5.17
++

I would like to keep Tomcat 5.5.17, but before I could test my JDBC
connection I need this context entry to work. Any one who has ran
into this before can you please suggest what is the best fix or work
around here. Appreciate every one valuble time.

Thanks
Biji

--- In Firebird-Java@yahoogroups.com, Rick Fincher <rnf@...> wrote:
>
> Hi All,
>
> I'm using 2.0.1 with Tomcat 5.9.12 with no problems. I had
already
> updated to Tomcat 5.5.12 from 5.5.9 when JayBird 2.0 was released
so I
> haven't tried it with Tomcat 5.5.9.
>
> If that is the problem, the update to Tomcat 5.5.12 is painless.
Or go
> to 5.5.17, the current stable release. All the settings are the
same.
>
> This is on Fedora Core 3 (Redhat).
>
> Rick
>
>
> Catalin Florean wrote:
>
> >Jaybird 2.0.1 did not work with my Tomcat/Firebird enviroment but
> >Jaybird 1.5.6 worked just fine.
> >I did not have the time to investigate the cause.
> >
> >I am waiting for the release of the new Firebird 2.0 to migrate my
> >database and have another try with Jaybird 2.
> >
> >Catalin Florean.
> >
> >On 5/3/06, Roman Rokytskyy <rrokytskyy@...> wrote:
> >
> >
> >>>5. You should use Jaybird 1.5.6 JDBC driver.
> >>>
> >>>
> >>May I ask you what is the reason for such recommendation?
> >>
> >>Roman
> >>
> >>
> >>
> >
> >
> >
>
>
>
> [Non-text portions of this message have been removed]
>