RE: [cobalt-developers] Tomcat Problem

["Scott K. Moore" <scott@xxxxxxxxxxxxxx>]

Hi Timothy,

We are using the Java Development Kit 1.3a that your group put together and
for the most part it works extremely well.  Our normal JDBC calls work, and
we're even using Poolman to pool our connections.... but whenever Tomcat
tries to use the connection for user authentication it doesn't work.

Any ideas?
-Scott


-----Original Message-----
From: cobalt-developers-admin@xxxxxxxxxxxxxxx
[mailto:cobalt-developers-admin@xxxxxxxxxxxxxxx]On Behalf Of Timothy
Stonis
Sent: Friday, December 14, 2001 2:45 PM
To: cobalt-developers@xxxxxxxxxxxxxxx
Subject: Re: [cobalt-developers] Tomcat Problem



 I would recommend installing the developer kit we've put together for the
RaQ4. You can get it at developer.cobalt.com/java. This kit will make all
the necessary modifications to the Apache config for you. There is also an
instruction manual that comes with it that tells you exactly how to connect
to an Interbase DB.

On 12/14/01 1:04 PM, "Scott K. Moore" <scott@xxxxxxxxxxxxxx> wrote:

> Hey Everyone,
>
> We are developing a Java Application that uses Apache-Tomcat 3.2.3 and
JDBC
> to connect to our InterBase Server on a Cobalt Raq4. We have been
developing
> the code in a Windows environment running InterBase and Apache-Tomcat 4.0,
> and everything works well there.  However, we can't seem to get things
> working properly on the Cobalt.
>
> The problem occurs when we use the Tomcat JDBC Realm to provide user
> authentication from the InterBase database.  We get the following message:
>
> 404 File Not Found...  j_security_check
>
> We found some references to this problem that said to modify the
mod_jk.conf
> file and the httpd.conf file so that the Apache-Tomcat connector knows how
> to handle the request.  However, we followed their suggestions and tried
> modifying the mod_jk.conf files that are created - but nothing seemed to
> work.  In addition, if we modify the httpd.conf file then Apache doesn't
> load correctly, and disables the Apache server altogether.
>
> We are incredibly frustrated with this issue, and we've been working full
> time on this problem for the last 3 days.  If anyone has experienced this
we
> would love to know how to fix it...  Thanks in advance for your help!
>
> Scott Moore
>
>
>
> _______________________________________________
> cobalt-developers mailing list
> cobalt-developers@xxxxxxxxxxxxxxx
> http://list.cobalt.com/mailman/listinfo/cobalt-developers
>

_______________________________________________
cobalt-developers mailing list
cobalt-developers@xxxxxxxxxxxxxxx
http://list.cobalt.com/mailman/listinfo/cobalt-developers