<attribute name="activeHandlerThreads">2000</attribute>
<attribute name="maxHandlerThreads">2000</attribute>
Hope that helps, BenG.
[EMAIL PROTECTED] wrote:
> Thanks for the advice!..
>
> I have Metrics turned on currently, monitoring every 20 seconds, and I get
> 0/0, 0 Sessions..
>
> It does specifically say Web-Threads so, I looked for an additional
> setting
> for the proxy, (as we're using the JRUN connector via IIS on another
> server)
> but that was the only metrics option in the jrun.xml file.
>
> ~ Jon
>
> -----Original Message-----
> From: Kathy Vance [mailto:[EMAIL PROTECTED]
>
> Jon,
>
> I have the same problem while I did loading testing on
> JRun 4. We spent $500 for macromedia tech support in
> order to solve the issue.
>
> Please check your jrun.xml. There is a service called
> "ProxyService". You need to increase the value of the
> attribute named "activeHandlerThreads" to a number
> based on how busy your app is. I remember the default
> value is 15.
>
> Also, You can turn on Metrics logging to decide how
> many threads you need.
>
> Sometimes you could get the same error mentioned while
> using jsp forward tag. But I believe that Updater 3
> may solve forwarding issue on JRun 4.
>
> for your info,
>
> Kathy
>
>
> --- Jon Austin <[EMAIL PROTECTED]> wrote:
> > Thanks to all for their input on this topic,
> >
> > I am getting more resource directed to this in the
> > next day or, so, and will
> > be running through some of the troubleshooting tips
> > given here.
> >
> > I understand that many of you are running
> > successfully, with many concurrent
> > users, the question now, I have for those people, is
> > what kind of scope is
> > your application?
> >
> > Are we simply talking glorified web-sites with a
> > little processing behind
> > them, or are we talking full hard-code business
> > applications.
> >
> > Our application falls heavily on the latter, and
> > before I base conclusions
> > on other peoples abilities to produce results under
> > this environment, I want
> > to be sure that we're in the same ballpark.
> >
> >
> > One error which a user did capture during a
> > server-halt the other day, was :
> >
> > Too many concurrent requests,
> > jcp.endpoint.main.max.threads exceeded.
> >
> > I found documents on how to resolve this on JRUN3..
> > but none of the files
> > that are referenced in that document, exist on my
> > JRUN4 implimenation. Does
> > anyone know where I can find the new settings fro
> > JRUN4.
> >
> > Thanks
> >
> > ~ Jon
> >
> >
> >
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
