[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-developers] Sun Cobalt Developer Kit for Java
- Subject: Re: [cobalt-developers] Sun Cobalt Developer Kit for Java
- From: "O-S Inc. Support" <support@xxxxxxxxxxxxxxxxxxxx>
- Date: Mon Aug 13 05:37:19 2001
- Organization: Obsidian-Studios Inc.
- List-id: Discussion Forum for developers on Sun Cobalt Networks products <cobalt-developers.list.cobalt.com>
I manually installed and tested Jakarta_Tomcat-3.2.2 prior to installing
the Sun Cobalt Raq4 Java Developer Kit.
It is a perfect installation and we have not ran into any problems with
the pkg version as compared to our manually installed version.
I would recommend sticking with the pkg file from Cobalt, before
manually installing. If you do manually install, do it on a test
machine first, if one is available.
Otherwise I am not sure what you are experiencing. Is it a OEM system
with all current patches applied, or have you installed and modified the
software on the RaQ?.
One thing I found that you still must manually do is forward certain
file type to Tomcat. That may be your problem. In each virtual host
that you want Tomcat to work for you must manually add the following
lines to your httpd.conf Apache configuration file.
JkMount /*.jsp ajp13
JkMount /servlet/* ajp13
JkMount /*.swt ajp13
The last one you won't need unless you are running some sort of servlet
for a given file type. In our case, we use Macromedia's Generator 2.
Which is a Java Servlet run by Tomcat. Now for apache to forward all
.swt request to Tomcat, the line had to be added to Apache's virtual
host conf. You would do something similar for what ever file
extensions, or directory prefixs, or just in general what Apahce should
forward over to Tomcat.
Good luck hope that helps.
Otherwise check log files.
Peter Vines wrote:
> Has anyone had any experience of the Sun Cobalt Developer Kit for Java
>
> We've been trying to get it to work on a RAQ4 with little success.
>
> It installs Tomcat 3.2.1 (which is not the current stable production
> release!) plus a bunch of scripts. What we've found is that Tomcat and
> Apache don't seem to communicate. We've been able to get the
configuration
> to work by messing around with the scripts (essentially hard coding
> everything) and upgrading to 3.2.2 but even now its not very stable,
> certainly not good enough for use in a production environment.
>
> I haven't tried this yet, but my inclination is to install Tomcat 3.2.2
> manually and avoid using Sun's software completely. Has anyone tried
this?
>
> Thanks, Peter vines.
>
>
>
> --------------------------------------------------------
>
> Callido Limited
> 10 Upper Wimpole Street
> London W1M 7TD
>
> Tel +44 (0) 20 7224 5408
> Fax +44 (0) 20 7935 2485
>
> http://www.callido.com
>
>
> _______________________________________________
> cobalt-developers mailing list
> cobalt-developers@xxxxxxxxxxxxxxx
> http://list.cobalt.com/mailman/listinfo/cobalt-developers
--
Sincerely,
William L. Thomson Jr.
Support Group
Obsidian-Studios Inc.
439 Amber Way
Petaluma, Ca. 94952
Phone/fax 707.766.9509
http://www.obsidian-studios.com