On 15 Mar 2012, at 20:23, morciuch wrote:
> I had similar problem on Windows Server 2008. After some research, I added
> the following JVM option to make it work:
>
> -Djava.net.preferIPv4Stack=true
A thread that's been dormant for 2 whole years lurches back into life...
p
> --
> View this me
I had similar problem on Windows Server 2008. After some research, I added
the following JVM option to make it work:
-Djava.net.preferIPv4Stack=true
--
View this message in context:
http://tomcat.10.n6.nabble.com/Socket-Error-in-tomcat-white-screen-in-browser-tp2053737p4622960.html
Sent from t
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
Note that http://wiki.eclipse.org/WTP_Tomcat_FAQ has gobs of
(sometimes opaque) information about Eclipse and Tomcat. If you
configure Eclipse to use an external (separate) Tomcat, it uses the
external Tomcat , but at minimum, distorts the logging configuration
to just run catalina.out thr
> From: millerKiller [mailto:smille8...@hotmail.com]
> Subject: RE: Socket Error in tomcat, white screen in browser
>
> 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.
Again, use Task Manager to ver
>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
diffic
> From: millerKiller [mailto:smille8...@hotmail.com]
> Subject: RE: Socket Error in tomcat, white screen in browser
>
> (1) On startup, does Tomcat have to set up these dormant
> sockets(inactive/listening/passive) or, does Tomcat create
> them upon a need base?
They
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? T
> From: millerKiller [mailto:smille8...@hotmail.com]
> Subject: Re: Socket Error in tomcat, white screen in browser
Sorry if you feel offended at anything said - it certainly wasn't intended.
> I know what connections and sockets are and infact, a
> socket is a connection!
No
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-tp2
2010/2/13 millerKiller :
>
> 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 do
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
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
> From: millerKiller [mailto:smille8...@hotmail.com]
> Subject: RE: Socket Error in tomcat, white screen in browser
> The socket I showed before is the socket that Tomcat is using
> when I open it.
That's not a socket, it's a connection. So where are the other two ports
millerKiller wrote:
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
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 th
> From: millerKiller [mailto:smille8...@hotmail.com]
> Subject: RE: Socket Error in tomcat, white screen in browser
>
> Here is my port information in conf/server.xml:
>
> redirectPort="8443" />
>
So there are three ports configured for this Tomcat: 8005,
Here is my port information in conf/server.xml:
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
> From: millerKiller [mailto:smille8...@hotmail.com]
> Subject: RE: Socket Error in tomcat, white screen in browser
>
> I believe I have Tomcat configured to go through port 80
That configuration is in conf/server.xml; be aware that Eclipse often uses its
own Tomcat config, not
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
> From: millerKiller [mailto:smille8...@hotmail.com]
> Subject: Socket Error in tomcat, white screen in browser
> I don't understand, my tomcat was working last week just fine and now
> it is acting weird? Is there anyone that can help me figure it out?
Welcome to the Wacky World of Windows.
1)
21 matches
Mail list logo
