RE: Socket Error in tomcat, white screen in browser
I do not mean to insult your intelligence on the matter, but we are not getting anywhere on the matter. I feel like we are going off on a tangent and are just wasting time (because you don't know the solution). Everything you have told me to do then I already know about and would like to correct you on some of the things you told me. First of all, I know what connections and sockets are and infact, a socket is a connection! (Don't argue with the intricate details of whether a unconnected socket is a connection or a dormant connection waiting to happen because anything valuable do with a socket is a connection!) I have programmed large concurrent/multithreading programming projects including torents and servers that deal with all kinds of sockets in many different contexts in many different languages. I know what a socket is! Anything valuable to do with a socket is a connection! And how do you define a socket without its port number and IPaddress? A socket is meaningless without this. If you don't believe me then here are some references from Sun's documentation and from RFC's (Request for comments from the internet): --- Definition: A socket is one endpoint of a two-way communication link between two programs running on the network. A socket is bound to a port number so that the TCP layer can identify the application that data is destined to be sent. An endpoint is a combination of an IP address and a port number. Every TCP connection can be uniquely identified by its two endpoints. That way you can have multiple connections between your host and the server. So don't get lost in technicalities that are meaningless to the situation. I mean sure, there can be other connections besides sockets (subset of), but dude, getting lost in these technicalities to try and show superiority does nothing to help figure out the situation. Now I am sure you know more about the architecture of Tomcat then I do(maybe not, but will give you the benefit of the doubt), I am not disputing that. I am a masters student in computer science with a bachelors in math and computer engineering and I feel very insulted by the last two posts. I mean, the way they were structured (especially the last one) have bothered me. My problem is not the logists of the science, but the Tomcat application itself. As far as the other replies then you say there is a problem since my windows machine (windows 7 ultimate) isn't showing the other ports being listened on (bound). Since they are redirect connections, then I wouldn't be surprised if a socket (connection), only opens up when a page is redirecting so I don't believe that is the problem. (Maybe it is, but I doubt it) And then as far as Root and ROOT, then come on, you know what I am talking about. Were not talking about case sensitive environmental operating system features / registry files. I feel like the comment on this was more of an insult then to inform me. (if you don't know what I am talking about then maybe I need to talk to someone else) And then as far as the other guy that posted: read all of the other posts and not just half of them? Yes, I did read the posts several times to see if I was missing something. They tell me nothing useful that I already did not know. Is everyone on your forums this stuck up. This is bullcrap! Once again I am not insulting you on your expertise of Tomcat, but I regret you cannot say the same for me. I feel like this forum is a waste of time for newbies in the realm of computer science / networking to try and show superiority over others because they know more on a specific applicaiton. The people here are not willing to get in and help if it includes more than the easy icing. What I am going to do next is either try another forum, reinstall my tomcat and eclipse, or go meet with some professionals that know tomcat. (my buddies up at the University). If there is anyone that is willing to help me then let me know, otherwise good day to everyone and good luck. Good luck and good day to you. -- View this message in context: http://old.nabble.com/Socket-Error-in-tomcat%2C-white-screen-in-browser-tp27567722p27576522.html Sent from the Tomcat - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Socket Error in tomcat, white screen in browser
I do not mean to insult your intelligence on the matter, but we are not getting anywhere on the matter. I feel like we are going off on a tangent and are just wasting time (because you don't know the solution). Everything you have told me to do then I already know about and would like to correct you on some of the things you told me. First of all, I know what connections and sockets are and infact, a socket is a connection! (Don't argue with the intricate details of whether a unconnected socket is a connection or a dormant connection waiting to happen because anything valuable do with a socket is a connection!) I have programmed large concurrent/multithreading programming projects including torents and servers that deal with all kinds of sockets in many different contexts in many different languages. I know what a socket is! Anything valuable to do with a socket is a connection! And how do you define a socket without its port number and IPaddress? A socket is meaningless without this. If you don't believe me then here are some references from Sun's documentation and from RFC's (Request for comments from the internet): --- Definition: A socket is one endpoint of a two-way communication link between two programs running on the network. A socket is bound to a port number so that the TCP layer can identify the application that data is destined to be sent. An endpoint is a combination of an IP address and a port number. Every TCP connection can be uniquely identified by its two endpoints. That way you can have multiple connections between your host and the server. So don't get lost in technicalities that are meaningless to the situation. I mean sure, there can be other connections besides sockets (subset of), but dude, getting lost in these technicalities to try and show superiority does nothing to help figure out the situation. Now I am sure you know more about the architecture of Tomcat then I do(maybe not, but will give you the benefit of the doubt), I am not disputing that. I am a masters student in computer science with a bachelors in math and computer engineering and I feel very insulted by the last two posts. I mean, the way they were structured (especially the last one) have bothered me. My problem is not the logists of the science, but the Tomcat application itself. As far as the other replies then you say there is a problem since my windows machine (windows 7 ultimate) isn't showing the other ports being listened on (bound). Since they are redirect connections, then I wouldn't be surprised if a socket (connection), only opens up when a page is redirecting so I don't believe that is the problem. (Maybe it is, but I doubt it) And then as far as Root and ROOT, then come on, you know what I am talking about. Were not talking about case sensitive environmental operating system features / registry files. I feel like the comment on this was more of an insult then to inform me. (if you don't know what I am talking about then maybe I need to talk to someone else) And then as far as the other guy that posted: read all of the other posts and not just half of them? Yes, I did read the posts several times to see if I was missing something. They tell me nothing useful that I already did not know. Is everyone on your forums this stuck up. This is bullcrap! Once again I am not insulting you on your expertise of Tomcat, but I regret you cannot say the same for me. I feel like this forum is a waste of time for newbies in the realm of computer science / networking to try and show superiority over others because they know more on a specific applicaiton. The people here are not willing to get in and help if it includes more than the easy icing. What I am going to do next is either try another forum, reinstall my tomcat and eclipse, or go meet with some professionals that know tomcat. (my buddies up at the University). If there is anyone that is willing to help me then let me know, otherwise good day to everyone and good luck. Good luck and good day to you. -- View this message in context: http://old.nabble.com/Socket-Error-in-tomcat%2C-white-screen-in-browser-tp27567722p27576555.html Sent from the Tomcat - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Socket Error in tomcat, white screen in browser
Thanks for the reply. I will look into closer and see what I come up with. When I figure out the solution, if I do, then I will let post a comment so that it is available to everyone. -- View this message in context: http://old.nabble.com/Socket-Error-in-tomcat%2C-white-screen-in-browser-tp27567722p27576781.html Sent from the Tomcat - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Socket Error in tomcat, white screen in browser
I accept your apology and owe you one to. The post that threw me off the rocker was the post that told me to look through all of the messages and not just parts of. I apologize... ,but now that we are on the same page and using the same terminology, would you mind if I ask you some questions? The last post was interesting and I had some questions: If so, here they are: (1) On startup, does Tomcat have to set up these dormant sockets(inactive/listening/passive) or, does Tomcat create them upon a need base? (2) This one might answer number (1). Why does Tomcat use the three different sockets, doesn't it just need a single server listening socket? (3) Proto Local Address Foreign AddressState PID TCP0.0.0.0:80 0.0.0.0:0 LISTENING 6104 TCP0.0.0.0:8009 0.0.0.0:0 LISTENING 6104 TCP[::]:80[::]:0 LISTENING 6104 TCP[::]:8009 [::]:0 LISTENING 6104 The Foreign Address will always be 0.0.0.0 for passive open (LISTENING) ports. I am testing the server on localHost and am getting Proto Local Address Foreign AddressState PID TCP127.0.0.1:8005 0.0.0.0:0 LISTENING 520 Is this valid since I using localHost? (4)If nothing else is using the ports that I mentioned earlier when I use netstat -ano, then why does it think there is a bind somewhere? Thanks -- View this message in context: http://old.nabble.com/Socket-Error-in-tomcat%2C-white-screen-in-browser-tp27567722p27579336.html Sent from the Tomcat - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Socket Error in tomcat, white screen in browser
No - it shows that *something* is listening on 8005, but it's not likely to be Tomcat. Use the Task Manager to find out what PID 520 is. As I mentioned before, lots of products have Tomcat embedded in them, and at least one (VMware) leaves the shutdown port set to the default, creating difficulty for anyone trying to run an out-of-the-box Tomcat. Something *is* using 8005, which will interfere with a Tomcat configured with the default shutdown port. And again, be wary of running Tomcat under Eclipse, since Eclipse likes to use its own Tomcat configuration, not the one you thing you've set up. The wierd thing about all of this is whenever I shut my tomcat down then the 127.0.0.1:8005 dissapears from the netstat list. This leads me to believe that it is Tomcat which is using this. This also leads me to believe there is something funky with eclipse's setup with Tomcat. Maybe the best solution is to reinstall it? (I need to use it under eclipse for the application I am creating JavaServlets/JSPs) If Eclipse uses its own settings, then how do I make it use Tomcat's or vice versa or is there a manual on this specific problem with eclipse and Tomcat getting confused with one anothers configuration settings? -- View this message in context: http://old.nabble.com/Socket-Error-in-tomcat%2C-white-screen-in-browser-tp27567722p27579543.html Sent from the Tomcat - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Socket Error in tomcat, white screen in browser
Maybe I should move this to the eclipse forums. Before I go though, then could we finish up with a few more things that I found and see if anyone knows? I looked at my netstat and saw the following: 127.0.0.1:2402 127.0.0.1:2403 Established 4360 127.0.0.1:2403 127.0.0.1:2402 Established 3140 127.0.0.1:8005 0.0.0.0:0 Listening3140 This only appears when I start Tomcat in eclipse. It looks to me like 2402 and 2403 are connected to each other through PID 4360.8005 then attempts to connect, but PID 3140 is allready being used. Is this look like the problem? If it is, then what can I do to fix it? In the task manager then PID 3140 is javaw.exe and PID 4360 is eclipse.exe. When I kill either of these then they dont appear in netstat anymore. any ideas? -- View this message in context: http://old.nabble.com/Socket-Error-in-tomcat%2C-white-screen-in-browser-tp27567722p27579882.html Sent from the Tomcat - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Socket Error in tomcat, white screen in browser
I am having a problem a strange problem in my Tomcat application. Before I
get started then here is my system information:
- Eclipse 3.4.2
- apache-tomcat-6.0.20
It used to work, but now it doesn't. The problem is when I try to view my
tomcat pages in my browser then it goes straight to a white screen. Tomcat
appears to be starting, but it lists some problems before starting. Here is
what my console says:
Feb 12, 2010 10:47:44 AM org.apache.catalina.core.AprLifecycleListener init
INFO: The APR based Apache Tomcat Native library which allows optimal
performance in production environments was not found on the
java.library.path: C:\Program
Files\Java\jre6\bin;.;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:/Program
Files/Java/jre6/bin/client;C:/Program Files/Java/jre6/bin;C:\Program
Files\Common Files\Microsoft Shared\Windows
Live;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\MinGW\bin;C:\Program
Files\QuickTime\QTSystem\C:\Program Files\QuickTime\QTSystem\;C:\Program
Files\Java\jdk1.6.0_17\bin;C:\Program Files\QuickTime\QTSystem\;C:\Program
Files\Common Files\Microsoft Shared\Windows Live;C:\Program Files\Nmap
Feb 12, 2010 10:47:44 AM org.apache.coyote.http11.Http11Protocol init
SEVERE: Error initializing endpoint
java.net.SocketException: Unrecognized Windows Sockets error: 0: JVM_Bind
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.PlainSocketImpl.bind(Unknown Source)
at java.net.ServerSocket.bind(Unknown Source)
at java.net.ServerSocket.init(Unknown Source)
at java.net.ServerSocket.init(Unknown Source)
at
org.apache.tomcat.util.net.DefaultServerSocketFactory.createSocket(DefaultServerSocketFactory.java:50)
at org.apache.tomcat.util.net.JIoEndpoint.init(JIoEndpoint.java:503)
at org.apache.coyote.http11.Http11Protocol.init(Http11Protocol.java:176)
at
org.apache.catalina.connector.Connector.initialize(Connector.java:1058)
at
org.apache.catalina.core.StandardService.initialize(StandardService.java:677)
at
org.apache.catalina.core.StandardServer.initialize(StandardServer.java:795)
at org.apache.catalina.startup.Catalina.load(Catalina.java:535)
at org.apache.catalina.startup.Catalina.load(Catalina.java:555)
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 org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:260)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:412)
Feb 12, 2010 10:47:44 AM org.apache.catalina.startup.Catalina load
SEVERE: Catalina.start
LifecycleException: Protocol handler initialization failed:
java.net.SocketException: Unrecognized Windows Sockets error: 0: JVM_Bind
at
org.apache.catalina.connector.Connector.initialize(Connector.java:1060)
at
org.apache.catalina.core.StandardService.initialize(StandardService.java:677)
at
org.apache.catalina.core.StandardServer.initialize(StandardServer.java:795)
at org.apache.catalina.startup.Catalina.load(Catalina.java:535)
at org.apache.catalina.startup.Catalina.load(Catalina.java:555)
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 org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:260)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:412)
Feb 12, 2010 10:47:44 AM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 503 ms
Feb 12, 2010 10:47:44 AM org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
Feb 12, 2010 10:47:44 AM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.20
Feb 12, 2010 10:47:45 AM org.apache.catalina.loader.WebappClassLoader
validateJarFile
INFO:
validateJarFile(C:\Users\Steven\EclipseWorkSpaces\TomcatWorkspace\workspace\ps1-semiller\WEB-INF\lib\servlet-api.jar)
- jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class:
javax/servlet/Servlet.class
Feb 12, 2010 10:47:45 AM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive standard-examples.war
Feb 12, 2010 10:47:45 AM org.apache.catalina.core.ApplicationContext log
INFO: ContextListener: contextInitialized()
Feb 12, 2010 10:47:45 AM org.apache.catalina.core.ApplicationContext log
INFO: SessionListener: contextInitialized()
Feb 12, 2010 10:47:45 AM org.apache.catalina.core.ApplicationContext log
INFO: ContextListener: attributeAdded('org.apache.catalina.Registry',
RE: Socket Error in tomcat, white screen in browser
Thanks for the quick response Chuck. I might need a little guidance on some of the things you mentioned. I believe I have Tomcat configured to go through port 80 and it is going through my machine locally. Where do I check to make sure? I checked windows firewall and it is allowing eclipse to go through the firewall. If port 80 shows up on netstat, then is this a problem? I though multiple things could use port 80. (i.e. assign dynamically) thanks, millerkiller -- View this message in context: http://old.nabble.com/Socket-Error-in-tomcat%2C-white-screen-in-browser-tp27567722p27568110.html Sent from the Tomcat - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Socket Error in tomcat, white screen in browser
Here is my port information in conf/server.xml: Server port=8005 shutdown=SHUTDOWN Connector port=80 protocol=HTTP/1.1 connectionTimeout=2 redirectPort=8443 / Connector port=8009 protocol=AJP/1.3 redirectPort=8443 / I pull up netstat -ano Here is the only thing that relates to these port numbers: Local Address Foreign Address - 127.0.0.1:8005 0.0.0.0.0 So it appears that nothing is using the same port, any other ideas? (Also, what is the correct way to respond in this forum, should I post message or send an email to you?) -- View this message in context: http://old.nabble.com/Socket-Error-in-tomcat%2C-white-screen-in-browser-tp27567722p27568387.html Sent from the Tomcat - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Socket Error in tomcat, white screen in browser
I apologize, I put across my last post a little misleading. The socket I showed before is the socket that Tomcat is using when I open it. Local Address Foreign Address - 127.0.0.1:8005 0.0.0.0.0 I am running tomcat through the loop back address. When I start the server then the above shows up in netstat -ano.When I close the server then it goes away. This means that the only program that is using this socket is the Tomcat that should be using it. So it isn't a problem with sockets (IP addresses and port numbers) as far as I can tell. BTW, a blank page in the browser is often the result of the ROOT webapp either not being present or failing to deploy properly. Make sure you have a ROOT webapp (case matters, even on Windows), and check the logs for any deployment errors. As far as this last comment, then I am aware that individual projects have a webapp folder and the tomcat program has its own webapp. When you talk about Root webapp, then you are talking about the Tomcat one right? What should be in this webapp folder? Here is what I have: Folders: docs examples host-manager manager Root Standard-examples Files: standard-examples.war -- View this message in context: http://old.nabble.com/Socket-Error-in-tomcat%2C-white-screen-in-browser-tp27567722p27568758.html Sent from the Tomcat - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
