RE: Re[2]: JRUN Stability
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]
RE: Re[2]: JRUN Stability
Are we simply talking glorified web-sites with a little processing behind them, or are we talking full hard-code business applications. We (and our clients) are running applications and content management systems with JRun. Both of these tend to be very dynamic. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ phone: 202-797-5496 fax: 202-797-5444 [Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
RE: Re[2]: JRUN Stability- reply
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]
RE: Re[2]: JRUN Stability - one more thing
Jon, One more thing is if you are using JRun web service, the service you may look into in jrun.xml is WebService. Good luck. 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]
RE: Re[2]: JRUN Stability- reply
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]
Re: JRUN Stability- reply
This is true; to achieve high levels of concurrency we run with attribute name=activeHandlerThreads2000/attribute attribute name=maxHandlerThreads2000/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]
Re: JRUN Stability- reply 2
Ben, How is the stability and performance of JRun server after you set activeHandlerThreads to 2000? Usually the number of the maxHandlerThreads should be bigger than activeHandlerThreads? As I understand, JRun would not perform well if the number of activeHandlerThreads is too big. Could you share your experience here? How busy would the traffic be on your site and is your site running in UNIX box? Thanks. Kathy --- Ben Groeneveld [EMAIL PROTECTED] wrote: This is true; to achieve high levels of concurrency we run with attribute name=activeHandlerThreads2000/attribute attribute name=maxHandlerThreads2000/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]