× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



So the rumor is correct - Tomcat connectors will not work...

-----Original Message-----
From: java400-l-bounces@xxxxxxxxxxxx
[mailto:java400-l-bounces@xxxxxxxxxxxx] On Behalf Of Haas, Matt (CL Tech
Sv)
Sent: Friday, February 26, 2010 1:38 PM
To: java400-l@xxxxxxxxxxxx
Subject: Re: Tomcat support on V6R1

IBM has announced that they are no longer offering support for Tomcat
but remember, the only version they supported was a very old version
(3.something or other, maybe an early 4 version) that they had removed
functionality from to make WebSphere Express look better feature-wise.
Tomcat is a pure Java program so as long as a standards compliant JDK is
provided, there shouldn't be any problem running it.

Last time I looked, the latest version of the connector (which is what
I'm assuming is meant by 'handlers') doesn't run on i/OS (I think it
gets an error when the server starts) but unless you are using several
Tomcat instances to do load balancing, you can set up the proxy server
to do the same thing.

As far as not supporting 'Apache' goes, you need to be very, very
careful about what you mean (and what the reader may think you mean)
since it a generic name for a lot of things. If you are thinking of the
HTTP server, than to the best of my knowledge, that is wrong. The Apache
HTTP server is supported and I haven't seen anything to suggest that
they are switching to something else. IBM did drop support for the
original HTTP server a few releases ago (V5R3?) but that was never based
on anything that came out of the Apache Software Foundation.

Matt

message: 10
date: Fri, 26 Feb 2010 10:35:12 -0700
from: Pete Helgren <Pete@xxxxxxxxxx>
subject: Re: Tomcat support on V6R1

Just a clarification:

I am running a Rails app using the Glassfish 3 gem. My attempt to
deploy Glassfish on i directly (well, in PASE) resulted in a stacktrace
that Sun is (supposedly) checking into. Probably need to rattle their
cage to find out what the deal is.

I am not familiar with using 'handlers' to run server jobs but I do know

that Tomcat runs fine on 7.1. IBM has been phasing out support for
*their* version of Tomcat for quite some time, haven't they, just like
they did with Apache?

Pete


James Perkins wrote:
I couldn't get V3 it to run. I got some jargon that printed out when
attempting to start it. I think Pete Helgren got Glassfish V2 running
with Ruby on Rails.

As long as you go with WebSphere 7, it's actually not that bad. They
seemed to stick to the standards a little better with that version. I
haven't used it much except for testing. I'm unfortunately stuck at
WebSphere 6.1 which I'm battling now.

--
James R. Perkins



On Fri, Feb 26, 2010 at 06:57, Glenn Holmer <gholmer@xxxxxxxxxxxxxx>
wrote:

On Fri, 2010-02-26 at 09:50 -0500, Alex Pinsky wrote:

We've got a whisper from IBM that starting from V6R1 Tomcat will not
be
supported on iSeries (there will be no 'handlers' to run a server
jobs)

Should we all get ready to migrate to Websphere? :-(

I don't suppose GlassFish runs on an iSeries...?


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.