You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by "Pier P. Fumagalli" <pi...@betaversion.org> on 2001/07/26 21:47:38 UTC
Re: Different approach to TC as a service (was:
SeparatingServicecode from Tomcat 4.0)
Andy Armstrong at andy@tagish.com wrote:
> "Pier P. Fumagalli" wrote:
>>
>> Andy Armstrong at andy@tagish.com wrote:
>>>
>>> I only used JServ briefly before switching to Tomcat and "it worked for
>>> me"(tm). Can you recall any of the specific problems?
>>
>> It was back in 1997, and I remember several patches across 2 months from Ed
>> Korthof just to "make it work". But you should get back and see the
>> archives.
>>
>> I remember it was a big pain in the ass (and that for Jserv 1.0 I was
>> always starting Jserv stand alone!)
>
> I'll do some reading. Do you recall whether the problems where specific
> to that implementation of the startup code or more generically related
> to having the servlet container autostart?
Oh, I remember it was about invoking the startup script, and also one big
hassle was to shut down JServ from Apache, connecting to the port to issue a
shutdown command...
Pier
Re: Different approach to TC as a service (was:SeparatingServicecode
from Tomcat 4.0)
Posted by Andy Armstrong <an...@tagish.com>.
"Pier P. Fumagalli" wrote:
[snip]
> > I'll do some reading. Do you recall whether the problems where specific
> > to that implementation of the startup code or more generically related
> > to having the servlet container autostart?
>
> Oh, I remember it was about invoking the startup script, and also one big
> hassle was to shut down JServ from Apache, connecting to the port to issue a
> shutdown command...
For the Domino connector I just do bin/tomcat.sh start or bin/tomcat.sh
stop appropriately. It seems to work OK and is very simple to implement.
--
Andy Armstrong, Tagish
Re: Different approach to TC as a service (was:SeparatingServicecode
from Tomcat 4.0)
Posted by jean-frederic clere <jf...@fujitsu-siemens.com>.
"Pier P. Fumagalli" wrote:
>
> Andy Armstrong at andy@tagish.com wrote:
>
> > "Pier P. Fumagalli" wrote:
> >>
> >> Andy Armstrong at andy@tagish.com wrote:
> >>>
> >>> I only used JServ briefly before switching to Tomcat and "it worked for
> >>> me"(tm). Can you recall any of the specific problems?
> >>
> >> It was back in 1997, and I remember several patches across 2 months from Ed
> >> Korthof just to "make it work". But you should get back and see the
> >> archives.
> >>
> >> I remember it was a big pain in the ass (and that for Jserv 1.0 I was
> >> always starting Jserv stand alone!)
Things improved ApacheJServ-1.1.2 works without problems on our BS2000 EBCDIC
mainframes.
The idea to have:
httpd <--> "watchdog process" <--> service <--> JVM with Tomcat
Sounds Ok for me.
> >
> > I'll do some reading. Do you recall whether the problems where specific
> > to that implementation of the startup code or more generically related
> > to having the servlet container autostart?
>
> Oh, I remember it was about invoking the startup script, and also one big
> hassle was to shut down JServ from Apache, connecting to the port to issue a
> shutdown command...
Good that remains me that I have to patch mod_jserv, that "watchdog" process
holds the listen socket and it should not. (That does "Address already in use"
making apachectl graceful when using mod_jserv).
That is the only problem I have with mod_jserv :-)
>
> Pier