RE: Re[2]: JRUN Stability- reply
When running from the command line, I get the following two errors appear when I first run it, The strange thing is, that the 51003 port is not active prior to starting JRUN, and when I do run this command, it does activate it. ~ Jon 04/14 14:50:01 error Exception thrown in operation start [1]java.net.BindException: Port in use by another service or process: 51003 at jrun.servlet.network.NetworkService.bindToSocket(NetworkService.java:341) at jrun.servlet.network.NetworkService.start(NetworkService.java:202) at jrun.servlet.jrpp.JRunProxyService.start(JRunProxyService.java:77) at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) at jrunx.kernel.ServiceAdapter.invokeMethod(ServiceAdapter.java:705) at jrunx.kernel.JRunServiceDeployer.invokeOnServices(JRunServiceDeployer.java:4 60) at jrunx.kernel.JRunServiceDeployer.startServices(JRunServiceDeployer.java:312) at jrunx.kernel.JRunServiceDeployer.startLifecycle(JRunServiceDeployer.java:260 ) at jrunx.kernel.JRunServiceDeployer.deployServices(JRunServiceDeployer.java:87) at jrunx.kernel.DeploymentService.loadServices(DeploymentService.java:46) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) at jrunx.kernel.JRun.startServer(JRun.java:558) at jrunx.kernel.JRun.init(JRun.java:476) at jrunx.kernel.JRun$1.run(JRun.java:329) at java.security.AccessController.doPrivileged(Native Method) at jrunx.kernel.JRun.start(JRun.java:326) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at jrunx.kernel.JRun.invoke(JRun.java:180) at jrunx.kernel.JRun.main(JRun.java:168) [0]javax.management.MBeanException: Exception thrown in operation start at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1644) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) at jrunx.kernel.ServiceAdapter.invokeMethod(ServiceAdapter.java:705) at jrunx.kernel.JRunServiceDeployer.invokeOnServices(JRunServiceDeployer.java:4 60) at jrunx.kernel.JRunServiceDeployer.startServices(JRunServiceDeployer.java:312) at jrunx.kernel.JRunServiceDeployer.startLifecycle(JRunServiceDeployer.java:260 ) at jrunx.kernel.JRunServiceDeployer.deployServices(JRunServiceDeployer.java:87) at jrunx.kernel.DeploymentService.loadServices(DeploymentService.java:46) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) at jrunx.kernel.JRun.startServer(JRun.java:558) at jrunx.kernel.JRun.init(JRun.java:476) at jrunx.kernel.JRun$1.run(JRun.java:329) at java.security.AccessController.doPrivileged(Native Method) at jrunx.kernel.JRun.start(JRun.java:326) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at jrunx.kernel.JRun.invoke(JRun.java:180) at jrunx.kernel.JRun.main(JRun.java:168) [Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
RE: Re[2]: JRUN Stability- reply
As is always the case, my timeframe for load-testing the server was diverted in favor of rising priorities, and so I have yet to get this going properly. I have had the metrics running overnight, but I'm still getting Zero for Zero, with Zero sessions.There are generally 3-5 people on most of the day, so I'm at a loss as to why no metrics are showing..And the other question, is if the box is really doing nothing, why does it crash? ;-) I've restarted the JRUN service from the command line, and I'm logging to out.txt, but it appears only STDOUT is going there, STDERR appears to be echoing on the console, so where will I need to capture the stack trace, when needed? Thanks, ~ Jon -Original Message- 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 [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- 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]
