Re: AW: How many connections can be made to Tomcat on Windows?
On Tue, 14 Sep 2004 19:00:06 +0200, SH Solutions [EMAIL PROTECTED] wrote: Hi in the even you're using windows professional, it is limited to 10 inbound connections, which is easy to overlook and forget. NO. The limit of 10 inbound connections apply to _windows shares only_. It's a limitation to prevent usage of professional as server. However, the tcp/ip stack of professional and server are the _SAME_ and there is _NO_ limitation on incoming or outgoing connections, as long as the hardware can handle them. One exception: Windows xp sp2 has a limit for the rate of creating outgoing connection, which is suppost to slow down worms, but it can be disabled in registry. However, this does NOT apply to incoming connections. However, 1000 request/second is propably way to much for one system. Buy two and use load balancers, or do very good cashing in your webapp. But do not access the database for every page hit. Regards, Steffen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] From a *technical* standpoint, you are correct regarding socket connections. From a *legal* standpoint, however, the EULA for the Workstation product limits you to 10 concurrent socket connections, in order to try to force you to use Server instead. MS changed this back around NT 4.0 because people were putting http servers on NT Workstation instead of NT Server to save money. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Please help: Apache direct Servlet to Tomcat
On Mon, 13 Sep 2004 11:21:55 -0700, Daxin Zuo [EMAIL PROTECTED] wrote: [snip] For example I have a servlet TestServlet.class (package: myServlet) in [snip] servlet servlet-nameTestServlet/servlet-name servlet-classTestServlet/servlet-class /servlet I might be wrong, but I believe the servlet-class needs to be fully qualified, so it would be servlet-classmyServlet.TestServlet/servlet-class. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Please help: Apache direct Servlet to Tomcat
On Mon, 13 Sep 2004 14:57:31 -0400, Kelly Denehy [EMAIL PROTECTED] wrote: On Mon, 13 Sep 2004 11:21:55 -0700, Daxin Zuo [EMAIL PROTECTED] wrote: [snip] For example I have a servlet TestServlet.class (package: myServlet) in [snip] servlet servlet-nameTestServlet/servlet-name servlet-classTestServlet/servlet-class /servlet I might be wrong, but I believe the servlet-class needs to be fully qualified, so it would be servlet-classmyServlet.TestServlet/servlet-class. Hmmm, except you said it runs correctly when accessing directly through Tomcat on port 8008. I've always avoided accessing the ROOT webapp through Apache to avoid these kind of issues, because of the additional ambiguity that it introduces. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: error: duplicate local variable
You already had declared another List named values just a few lines
above, as shown in the edited version below:
On Sat, 11 Sep 2004 19:47:46 -0700, Jack Lauman [EMAIL PROTECTED] wrote:
I have the following piece of code that changes a password. Eclipse
gives the following
error message for line 11: duplicate local variable 'values'
List values = new ArrayList();
if(res != null res.getRowCount() 0)
{
List values = new ArrayList(); Error
duplicate local variable 'values'
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problably a simple problem - two instances of tomcat running at the same time
On Sun, 12 Sep 2004 14:53:43 -0600, Patricia Swarbrick [EMAIL PROTECTED] wrote: I've gone throught the server.xml files and the worker2.properties files to make sure that the two tomcat instances are not using the same port to communicate with the apache server. I think you're on the right track regarding ports. You need to also make sure that the 2 server.xml files aren't specifiying duplicate ports anywhere else - not just for communicating to Apache. An out-of-the-box Tomcat server.xml specifies a number of ports besides the jk2 connector. Especially make sure all the http connectors are different (or commented out or deleted, since you shouldn't need them). It's very common to run multiple Tomcat instances on 1 server. An easy way to tell whether a port conflict is causing your problem is to shut down the one that's working and then start up the failing one by itself. If it now works, you can be pretty sure it's a port conflict. There should be an error message somewhere - if not in a log file then in stdout or stderr. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
