SocketException: Connection reset - Tomcat 5.0.27
When using Tomcat 5.0.27 the following error shows up in the catalina.log file; SEVERE: Remote Host 12.159.66.150 SocketException: Connection reset org.apache.tomcat.util.net.TcpWorkerThread runIt The ip address 12.159.66.150 is a load balancer that front-ends Tomcat and checks periodically to make sure tomcat is running. It logs this error every time it checks. When I switch to Tomcat 5.0.16 under the same exact conditions this error does not show up in the log file. Questions; Is there a way to prevent this from being logged? Why does this occur under Tomcat 5.0.27 and not Tomcat 5.0.16? If Tomcat cant be set up to not log this error, is there a way to log in as INFO instead? alan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Upgrading from Java 1.3 and Tomcat 4.0 to Java 1.4 and Tomcat 5.0.27
Are both instances of Tomcat trying to run on the same port? You cannot have two processes trying to run on the same port for the same ip address. -Original Message- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Stephen Souness Sent: Saturday, August 14, 2004 7:53 PM To: [EMAIL PROTECTED] Subject: Upgrading from Java 1.3 and Tomcat 4.0 to Java 1.4 and Tomcat 5.0.27 Test environment is Windows 2000 pro, live environment is Windows 2000 server. On my test system I've struck a problem when trying to install Tomcat 5 when the system is currently still running Tomcat 4. During installation there is a failure installing the Tomcat5 service - possibly a clash with the existing Tomcat service? When I try to run the newly installed Tomcat 5 from a dos shell it closes immediately with no feedback presented or logged. Has anyone encountered this before, or does anyone have some tips as to what I could be doing wrong? -- Stephen Souness - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
SEVERE: Remote Host 12.159.66.150 SocketException: Connection reset
When using Tomcat 5.0.27 the following error shows up in the catalina.log file; SEVERE: Remote Host 12.159.66.150 SocketException: Connection reset org.apache.tomcat.util.net.TcpWorkerThread runIt The ip address 12.159.66.150 is a load balancer that front-ends Tomcat and checks every 5 secs to make sure tomcat is running (by checking the port tomcat runs on). When I switch to Tomcat 5.0.16 under the same exact conditions this does not show up in the log file. It does not hurt the performance of Tomcat but it is causing a huge and unreadable log file, and in addition, we monitor the log files for SEVERE errors and send out an email when any occur Questions; What exactly does this mean? (I believe it to mean a client closed the connection to tomcat before tomcat had a chance to reply to it.) Is there a way to prevent this from being logged? Why does this occur under Tomcat 5.0.27 and not Tomcat 5.0.16? If Tomcat cant be set up to not log this error, is there a way to log in as INFO instead?
Tomcat 5.0.16 causes; java.lang.ArrayIndexOutOfBoundsException
I am running Tomcat 5.0.16 standalone, front-ended by a load balancer. It runs on a Debian Linux 2.4.26 SMP i686 server. It threw the following error to the catalina.log file. After throwing this exception, Tomcat still appears to be working and servicing requests but it stopped writing to the catalina.log file. In researching this issue all I could find were references to this problem being fixed in an earlier version of Tomcat (I believe 4.1.16). This was on a production box so I have no idea what request or user caused this exception. java.lang.ArrayIndexOutOfBoundsException: 49152 at org.apache.coyote.http11.InternalOutputBuffer.write(InternalOutputBuffer.jav a:731) at org.apache.coyote.http11.InternalOutputBuffer.write(InternalOutputBuffer.jav a:659) at org.apache.coyote.http11.InternalOutputBuffer.sendHeader(InternalOutputBuffe r.java:539) at org.apache.coyote.http11.Http11Processor.prepareResponse(Http11Processor.jav a:1515) at org.apache.coyote.http11.Http11Processor.action(Http11Processor.java:898) at org.apache.coyote.Response.action(Response.java:226) at org.apache.coyote.Response.sendHeaders(Response.java:418) at org.apache.coyote.tomcat5.OutputBuffer.doFlush(OutputBuffer.java:364) at org.apache.coyote.tomcat5.OutputBuffer.close(OutputBuffer.java:325) at org.apache.coyote.tomcat5.CoyoteResponse.finishResponse(CoyoteResponse.java: 497) at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:213) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:805) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConne ction(Http11Protocol.java:696) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:605) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav a:677) at java.lang.Thread.run(Thread.java:534) Aug 12, 2004 7:09:48 PM org.apache.coyote.http11.Http11Processor process SEVERE: Error finishing response java.lang.ArrayIndexOutOfBoundsException: 49153 at org.apache.coyote.http11.InternalOutputBuffer.write(InternalOutputBuffer.jav a:731) at org.apache.coyote.http11.InternalOutputBuffer.sendStatus(InternalOutputBuffe r.java:471) at org.apache.coyote.http11.Http11Processor.prepareResponse(Http11Processor.jav a:1511) at org.apache.coyote.http11.Http11Processor.action(Http11Processor.java:898) at org.apache.coyote.Response.action(Response.java:224) at org.apache.coyote.http11.InternalOutputBuffer.endRequest(InternalOutputBuffe r.java:431) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:842) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConne ction(Http11Protocol.java:696) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:605) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav a:677) at java.lang.Thread.run(Thread.java:534)
RE: Tomcat 5.0.16 causes; java.lang.ArrayIndexOutOfBoundsException
How long ago? Im using Tomcat 5.0.16!!! -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: Friday, August 13, 2004 11:46 AM To: Tomcat Users List Subject: RE: Tomcat 5.0.16 causes; java.lang.ArrayIndexOutOfBoundsException Hi, Fixed long ago, update to a more modern release. Yoav Shapira Millennium Research Informatics -Original Message- From: alan sparago [mailto:[EMAIL PROTECTED] Sent: Friday, August 13, 2004 2:39 PM To: [EMAIL PROTECTED] Subject: Tomcat 5.0.16 causes; java.lang.ArrayIndexOutOfBoundsException I am running Tomcat 5.0.16 standalone, front-ended by a load balancer. It runs on a Debian Linux 2.4.26 SMP i686 server. It threw the following error to the catalina.log file. After throwing this exception, Tomcat still appears to be working and servicing requests but it stopped writing to the catalina.log file. In researching this issue all I could find were references to this problem being fixed in an earlier version of Tomcat (I believe 4.1.16). This was on a production box so I have no idea what request or user caused this exception. java.lang.ArrayIndexOutOfBoundsException: 49152 at org.apache.coyote.http11.InternalOutputBuffer.write(InternalOutputBuffe r.ja v a:731) at org.apache.coyote.http11.InternalOutputBuffer.write(InternalOutputBuffe r.ja v a:659) at org.apache.coyote.http11.InternalOutputBuffer.sendHeader(InternalOutput Buff e r.java:539) at org.apache.coyote.http11.Http11Processor.prepareResponse(Http11Processo r.ja v a:1515) at org.apache.coyote.http11.Http11Processor.action(Http11Processor.java:89 8) at org.apache.coyote.Response.action(Response.java:226) at org.apache.coyote.Response.sendHeaders(Response.java:418) at org.apache.coyote.tomcat5.OutputBuffer.doFlush(OutputBuffer.java:364) at org.apache.coyote.tomcat5.OutputBuffer.close(OutputBuffer.java:325) at org.apache.coyote.tomcat5.CoyoteResponse.finishResponse(CoyoteResponse. java : 497) at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:213) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:8 05) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process Conn e ction(Http11Protocol.java:696) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:6 05) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPoo l.ja v a:677) at java.lang.Thread.run(Thread.java:534) Aug 12, 2004 7:09:48 PM org.apache.coyote.http11.Http11Processor process SEVERE: Error finishing response java.lang.ArrayIndexOutOfBoundsException: 49153 at org.apache.coyote.http11.InternalOutputBuffer.write(InternalOutputBuffe r.ja v a:731) at org.apache.coyote.http11.InternalOutputBuffer.sendStatus(InternalOutput Buff e r.java:471) at org.apache.coyote.http11.Http11Processor.prepareResponse(Http11Processo r.ja v a:1511) at org.apache.coyote.http11.Http11Processor.action(Http11Processor.java:89 8) at org.apache.coyote.Response.action(Response.java:224) at org.apache.coyote.http11.InternalOutputBuffer.endRequest(InternalOutput Buff e r.java:431) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:8 42) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process Conn e ction(Http11Protocol.java:696) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:6 05) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPoo l.ja v a:677) at java.lang.Thread.run(Thread.java:534) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat 5.0.16 causes; java.lang.ArrayIndexOutOfBoundsException
Thanks! -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: Friday, August 13, 2004 12:02 PM To: Tomcat Users List Subject: RE: Tomcat 5.0.16 causes; java.lang.ArrayIndexOutOfBoundsException Hi, 5.0.16 was released in November 2003, and 5.0.19 which I think has the fix was released in February 2004. Use 5.0.27 if you can, which is the latest stable release. Yoav Shapira Millennium Research Informatics -Original Message- From: alan sparago [mailto:[EMAIL PROTECTED] Sent: Friday, August 13, 2004 2:58 PM To: 'Tomcat Users List' Subject: RE: Tomcat 5.0.16 causes; java.lang.ArrayIndexOutOfBoundsException How long ago? Im using Tomcat 5.0.16!!! -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: Friday, August 13, 2004 11:46 AM To: Tomcat Users List Subject: RE: Tomcat 5.0.16 causes; java.lang.ArrayIndexOutOfBoundsException Hi, Fixed long ago, update to a more modern release. Yoav Shapira Millennium Research Informatics -Original Message- From: alan sparago [mailto:[EMAIL PROTECTED] Sent: Friday, August 13, 2004 2:39 PM To: [EMAIL PROTECTED] Subject: Tomcat 5.0.16 causes; java.lang.ArrayIndexOutOfBoundsException I am running Tomcat 5.0.16 standalone, front-ended by a load balancer. It runs on a Debian Linux 2.4.26 SMP i686 server. It threw the following error to the catalina.log file. After throwing this exception, Tomcat still appears to be working and servicing requests but it stopped writing to the catalina.log file. In researching this issue all I could find were references to this problem being fixed in an earlier version of Tomcat (I believe 4.1.16). This was on a production box so I have no idea what request or user caused this exception. java.lang.ArrayIndexOutOfBoundsException: 49152 at org.apache.coyote.http11.InternalOutputBuffer.write(InternalOutputBuff e r.ja v a:731) at org.apache.coyote.http11.InternalOutputBuffer.write(InternalOutputBuff e r.ja v a:659) at org.apache.coyote.http11.InternalOutputBuffer.sendHeader(InternalOutpu t Buff e r.java:539) at org.apache.coyote.http11.Http11Processor.prepareResponse(Http11Process o r.ja v a:1515) at org.apache.coyote.http11.Http11Processor.action(Http11Processor.java:8 9 8) at org.apache.coyote.Response.action(Response.java:226) at org.apache.coyote.Response.sendHeaders(Response.java:418) at org.apache.coyote.tomcat5.OutputBuffer.doFlush(OutputBuffer.java:364) at org.apache.coyote.tomcat5.OutputBuffer.close(OutputBuffer.java:325) at org.apache.coyote.tomcat5.CoyoteResponse.finishResponse(CoyoteResponse . java : 497) at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:213 ) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java: 8 05) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.proces s Conn e ction(Http11Protocol.java:696) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java: 6 05) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPo o l.ja v a:677) at java.lang.Thread.run(Thread.java:534) Aug 12, 2004 7:09:48 PM org.apache.coyote.http11.Http11Processor process SEVERE: Error finishing response java.lang.ArrayIndexOutOfBoundsException: 49153 at org.apache.coyote.http11.InternalOutputBuffer.write(InternalOutputBuff e r.ja v a:731) at org.apache.coyote.http11.InternalOutputBuffer.sendStatus(InternalOutpu t Buff e r.java:471) at org.apache.coyote.http11.Http11Processor.prepareResponse(Http11Process o r.ja v a:1511) at org.apache.coyote.http11.Http11Processor.action(Http11Processor.java:8 9 8) at org.apache.coyote.Response.action(Response.java:224) at org.apache.coyote.http11.InternalOutputBuffer.endRequest(InternalOutpu t Buff e r.java:431) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java: 8 42) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.proces s Conn e ction(Http11Protocol.java:696) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java: 6 05) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPo o l.ja v a:677) at java.lang.Thread.run(Thread.java:534) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional
RE: how to deploy ejb in tomcat
I haven't used it and don't know much about it but you might be able to use Tomcat with OpenEJB. http://openejb.sourceforge.net/tomcat.html -Original Message- From: Mike Coughlan [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 06, 2004 1:35 PM To: Tomcat Users List Subject: Re: how to deploy ejb in tomcat I made the same mistake. This matrix will help to clarify the issue. http://www.theserverside.com/reviews/matrix.jsp The funny thing is that Sun now bundles the J2EE SDK with the Netbeans IDE. The Netbeans IDE in turn comes with Tomcat bundled inside for easy local development. And yet Tomcat still is not a J2EE server. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Tomcat Manager- field called; Error Count: #
When using the 'manager' web app to monitor Tomcat ( url; http://... /manager/status/all ) the page titled 'Complete Server Status' has a field on it called 'Error count:' followed by a number. This field exists under all the section headings. Intuitively, I would assume that the number under the individual sections totaled up would equal the number under the HTTP-SSL and HTTP-NonSSL sections but they don't. What is Error Count? What does a non-zero number represent? Is there some documentation that explains the page? I tried looking at the documentation ( http://jakarta.apache.org/tomcat/tomcat-5.0-doc/manager-howto.html http://jakarta.apache.org/tomcat/tomcat-5.0-doc/manager-howto.html) but could find nothing that talks about Error Count.
RE: All threads (150) are currently busy, waiting. Increase maxThreads (150) or check the servlet status
We are using RedHat 9, Kernel 2.4.20-20.9. JVM 1.4.2_01-b06. We are using Postgres and created our own database connection pooling api. I will try setting the environment variable LD_ASSUME_KERNEL=2.4.1. When you refer to a 'thread dump' are you referring to running netstat and viewing the threads running on the ports Tomcat is set up on? Or is there another way to get a thread dump? (sorry, for my ignorance on linux) Thanks for the help. -Original Message- From: Remy Maucherat [mailto:[EMAIL PROTECTED] Sent: Thursday, December 25, 2003 2:11 AM To: Tomcat Users List Subject: Re: All threads (150) are currently busy, waiting. Increase maxThreads (150) or check the servlet status alan sparago wrote: I am using Tomcat 5.0.16 standalone serving as both an http/https web server and servlet container. This error occurred in our QA environment and has caused Tomcat to hang and not service any requests. This error seemed to occur when no users were using the site at the time, but about 4 DAYS earlier we preformed a stress test simulating 1200 semi-simultaneous users and everything worked perfectly without any errors. Since the stress test we are only accessing the application as an occasional single user, the last time being about 8 hours prior to this error happening. Most parameters in the server.xml file are the default values (the maxThreads value is set to 150). Our log file is in xml format and contains the following error; loggerorg.apache.tomcat.util.threads.ThreadPool/logger levelSEVERE/level classorg.apache.tomcat.util.threads.ThreadPool/class methodlogFull/method thread13/thread messageAll threads (150) are currently busy, waiting. Increase maxThreads (150) or check the servlet status/message fyi. Nowhere in my application is the code creating any threads. If running Linux 2.4 with tweaks, and esp RH 9, use LD_ASSUME_KERNEL=2.4.1. This kind of report is not very useful without a thread dump once the issue occurs and all threads appear deadlocked, BTW. If there's actually a bug in the Tomcat code, then it's the only way to identify where it is. We are very close to our site being live so any help or information would be greatly appreciated. Would tomcat 4.1.29 be more stable? No, it is the same connector anyway. -- x Rémy Maucherat Senior Developer Consultant JBoss Group (Europe) SàRL x - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
All threads (150) are currently busy, waiting. Increase maxThreads (150) or check the servlet status
I am using Tomcat 5.0.16 standalone serving as both an http/https web server and servlet container. This error occurred in our QA environment and has caused Tomcat to hang and not service any requests. This error seemed to occur when no users were using the site at the time, but about 4 DAYS earlier we preformed a stress test simulating 1200 semi-simultaneous users and everything worked perfectly without any errors. Since the stress test we are only accessing the application as an occasional single user, the last time being about 8 hours prior to this error happening. Most parameters in the server.xml file are the default values (the maxThreads value is set to 150). Our log file is in xml format and contains the following error; loggerorg.apache.tomcat.util.threads.ThreadPool/logger levelSEVERE/level classorg.apache.tomcat.util.threads.ThreadPool/class methodlogFull/method thread13/thread messageAll threads (150) are currently busy, waiting. Increase maxThreads (150) or check the servlet status/message fyi. Nowhere in my application is the code creating any threads. We are very close to our site being live so any help or information would be greatly appreciated. Would tomcat 4.1.29 be more stable?
RE: expression ALWAYS evaluates to if... NEVER to else
Actually, you can use == to compare strings but only if the strings are
created by; String x = ; and not by; String x = new String().
It has to do with the where java stores the string object (literal pool
vs programmers space).
But either way, you should always use the equals method to compare two
object as long as the overriding equals method your using compares what
you want it to compare.
Alan Sparago
[EMAIL PROTECTED]
602 494 9596
-Original Message-
From: Jacob Kjome [mailto:hoju;visi.com]
Sent: Thursday, October 17, 2002 11:06 AM
To: Tomcat Users List
Subject: Re: expression ALWAYS evaluates to if... NEVER to else
Hello Z.BEAT,
If these are both java String objects then all you are comparing is if
the memory location of string object #1 is the same as that of String
object #2. This is probably not true. You need to compare like this.
if (paramPassword.equals(secretCode)) {
} else {
}
You can only count on the == operator to compare an object to null
or to compare simple data types such as int, boolean, long, etc
Jake
Thursday, October 17, 2002, 12:57:35 PM, you wrote:
ZB In the following code snippet, the expression ALWAYS
ZB evaluates to the if statement block:
ZB String paramPassword =
ZB request.getParameter(paramPassword);
ZB String secretCode = secret;
ZB if(paramPassword != secretCode)
ZB {
ZB }
ZB else
ZB {
ZB }
ZB However, my debugging flags that I send in an HTML
ZB comment CLEARLY show that the two variables have the
ZB same value:
ZB !-- DEBUG FLAGS
ZB paramPassword: secret
ZBsecretCode: secret
--
ZB What is going on? Am I missing something obvious?
ZB Thanks!
ZB __
ZB Do you Yahoo!?
ZB Faith Hill - Exclusive Performances, Videos More
ZB http://faith.yahoo.com
ZB --
ZB To unsubscribe, e-mail:
mailto:tomcat-user-unsubscribe;jakarta.apache.org
ZB For additional commands, e-mail:
mailto:tomcat-user-help;jakarta.apache.org
--
Best regards,
Jacobmailto:hoju;visi.com
--
To unsubscribe, e-mail:
mailto:tomcat-user-unsubscribe;jakarta.apache.org
For additional commands, e-mail:
mailto:tomcat-user-help;jakarta.apache.org
--
To unsubscribe, e-mail: mailto:tomcat-user-unsubscribe;jakarta.apache.org
For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org
tomcat and apache vs tomcat standalone
I have a very basic question. What are the advantages/disadvantages of using Apache connected with Tomcat compared to just using Tomcat Standalone? Assuming I'm just using Java and don't need any other connector or module like PHP, Perl or C. Are there any scalability, flexibility or efficiency differences between those two options? Alan Sparago [EMAIL PROTECTED] 602 494 9596
RE: LDAP Authentication
Im not sure what you mean by BASIC/Form based authentication but if your looking for an LDAP compliant API look into JNDI http://java.sun.com/products/jndi/ or into Novells LDAP Classes for Java http://developer.novell.com/ndk/doc/jldap/index.html?page=/ndk/doc/jldap /jldapenu/data/a9032ak.html Alan Sparago [EMAIL PROTECTED] 602 494 9596 -Original Message- From: Fred So [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 16, 2002 7:31 AM To: [EMAIL PROTECTED] Subject: LDAP Authentication Hi All Has anyone successfully implemented BASIC/Form-based authentication against an LDAP data source? Are there any external libraries available and what are the configuration settings? Thanks in advance F __ Do you Yahoo!? Faith Hill - Exclusive Performances, Videos More http://faith.yahoo.com -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Servlets: Differences between Linux and Windows?
The File.seperatorCharacter should be used to handle any differences in the character used to separate a path. Alan Sparago [EMAIL PROTECTED] 602 494 9596 -Original Message- From: Steven J. Owens [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 16, 2002 7:50 AM To: Tomcat Users List Subject: Re: Servlets: Differences between Linux and Windows? [EMAIL PROTECTED] 10/16/02 08:29 AM Hi! I'm having some problems running servlets in Tomcat 4.1.12 under Linux RedHat 7.3 I've done a simple servlet and I was running it in Tomcat 4.0.4 under Win98 without problems. If I copy the folder mySimpleServlet from windows tomcat webapps folder to linux tomcat webapps folder and start linux tomcat, then the application works, but the servlet does not. It says: the requested resource (.) not available Are there any differences in configuration under linux? (in the web.xml or the server.xml). On Wed, Oct 16, 2002 at 08:43:25AM -0600, Larry Meadors wrote: Do you have different cases in file/dir names - myfolder, MyFolder, and myFolder are all the same in Win32, but all are different in linux/unix. Also the file path separator (it's / under linux, but \ under windows). On a project I was on last year, we were building an app to run on Solaris servers, but I was the only guy working testing under Solaris. The rest were under windows. These were sharp programmers, but it was quite typical for me to do a CVS update, get their new code, and have it break in mysterious ways because of either foreslash/backslash issues or filename case issues. It's very easy to slip into. Steven J. Owens [EMAIL PROTECTED] I'm going to make broad, sweeping generalizations and strong, declarative statements, because otherwise I'll be here all night and this document will be four times longer and much less fun to read. Take it all with a grain of salt. - Me -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
