• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

java.net.SocketException: Unrecognized Windows Sockets error: 10106: create

 
Greenhorn
Posts: 8
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello,
I am running client socket program which is supposed to get connected with a server socket. The server socket is running fine and netstat -a shows that my server socket port is listening.

But when client socket program is run: It fails by giving following error message.

Thread[main,5,main] : java.net.SocketException: Unrecognized Windows Sockets error: 10106: create
java.net.SocketException: Unrecognized Windows Sockets error: 10106: create
at java.net.Socket.createImpl(Socket.java:388)
at java.net.Socke

I am running this on Windows XP. Running on other platforms like solaris is working fine.

I am not running windows xp firewall too.

Can some one help me please.
 
Ranch Hand
Posts: 2308
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
This might be a known issue with Windows XP Home.

Check this bugreport.
 
Ranch Hand
Posts: 31
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I hate to reopen an issue from a few years ago, but I am running into this issue when attempting to run tomcat under Windows 7.

One interesting thing I noticed about Windows 7 is that it doesn't define a SystemRoot environment variable as it does in XP. Does anyone have any ideas. I understand my chances of finding a solution might be scarce due to how new Windows 7 is.

I made an attempt to create a system level environment variable called SystemRoot, but that didn't seem to resolve my issue.

Thanks!
Anthony

Edit:

Note - the original post differs from my post slightly in that the exception is a bit different:



I REALLY appreciate everyone's time and energy toward this.
 
Anthony Andras
Ranch Hand
Posts: 31
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Ok, Please disregard the post above. I was able to solve the issue. I was completely unaware and had an instance of Tomcat running the whole time. I didn't realize I had it installed as a service, then attempted to run the startup.bat script. I apologize to anyone who took any time to research this and assure you I will be more careful when posting next time.

Best,
Anthony
 
Ranch Hand
Posts: 43
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
i don't know about you, but i am still getting this error, i checked already no tomcat or java process is runining in my system.
I recently migrated to windows 7 and i am using tomcat 5.5
 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I had the same problem.
After I close Skype and restart TomCat, no problem. the problem should be skype, in my case
 
Ranch Hand
Posts: 36
Chrome Java Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

java.net.SocketException: Unrecognized Windows Sockets error: 0: JVM_Bind


JVM_Bind means the server socket could not connect to that port as its already being used by another server socket


Skype and other programs latch on to well known ports for their own communications. i guess they use port 80 cause in some offices/ lans other ports are fire walled

stupid for a dev as we start web servers on those on very ports for development !

so either use another port like 8181 or 8182 or shut down other program(s) that are using the port you want

netstat (with -b param ) should tell you the ports being used and the exe that started listening on it



 
Consider Paul's rocket mass heater.
reply
    Bookmark Topic Watch Topic
  • New Topic