I am using iPlanet iAS 6.0 SP2. I may try other app servers out just to
see if that is the problem. Would it be worth giving it a shot on
Tomcat?
------------------
Jason Smith
[EMAIL PROTECTED]
----- Original Message -----
From: Jason Chaffee <[EMAIL PROTECTED]>
Date: Thursday, May 3, 2001 11:37 am
Subject: RE: i18n...
> I concur, Resin is an excellent app server. If you need EJBs as
> well, you
> can also use JBoss with Resin.
>
> -----Original Message-----
> From: Paul Tindall [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, May 02, 2001 9:09 PM
> To: [EMAIL PROTECTED]
> Subject: Re: i18n...
>
>
> Jason,
>
> I looked through the email trail for this and didn't see any
> mention of
> which servlet engine you are using. Outside of checking your
> environmentand configuration as Martin suggests (which is probably
> the root cause), you
> may want to take a look Resin (www.caucho.com). It is super-fast
> and very
> clean. I've had many strange problems (non-Struts) disappear after
> switching to it.
>
> Regards,
>
> Paul
>
> ----- Original Message -----
> From: "Martin Cooper" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Wednesday, May 02, 2001 10:46 PM
> Subject: Re: i18n...
>
>
> > This is very strange. We have some pages that have more than
> twice as many
> > <bean:message> instances as you mention. I just did a quick test
> on our
> > latest build, and it's really very fast. Certainly nothing that
> needs any
> > performance enhancement.
> >
> > You might want to poke around in your environment and see if there's
> > something going on in the container or the JVM that's causing
> the problem.
> I
> > don't think the issue is the <bean:message> tag itself.
> >
> > --
> > Martin Cooper
> >
> >
> > ----- Original Message -----
> > From: <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Friday, April 27, 2001 10:53 AM
> > Subject: i18n...
> >
> >
> > > I have a couple of questions.
> > >
> > > I had a JSP in which I had approximately 40 bean:message tags
> for i18n.
> > > This page was taking 15 seconds to load. If I had two
> requests for the
> > > page at the same time it would take 45 to 60 seconds.
> Obviously this is
> > > not acceptable. When I replaced the bean:message tags with
> the text,
> > > the response time goes to a respectable 3 to 5 seconds with
> multiple> > hits. Therefore, I have to come up with another
> method of
> > > internationalization.
> > >
> > > I am new to this so I am looking for suggestions. I have to
> support 4
> > > languages. My current thought is to detect the browser's
> settings and
> > > forward the request to the appropriate JSP that is specific to the
> > > language settings. I'm not sure exactly where this should be
> done. I
> > > would like it to be dynamic so that I can reuse FORM and
> ACTION beans
> > > for each related page.
> > >
> > > Again, any suggestions would be appreciated.
> > >
> > > ------------------
> > > Jason Smith
> > > [EMAIL PROTECTED]
> > >
> >
> >
> >
>
