Unrecognized Windows Sockets error: 0: recv failed #332

Comments

DavidSoong128 commented Nov 15, 2017

Caused by: java.net.SocketException: Unrecognized Windows Sockets error: 0: recv failed
at java.net.SocketInputStream.socketRead0(Native Method)

[na:1.8.0_73]
at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)

[na:1.8.0_73]
at java.net.SocketInputStream.read(SocketInputStream.java:170)

[na:1.8.0_73]
at java.net.SocketInputStream.read(SocketInputStream.java:141)

[na:1.8.0_73]
at java.io.BufferedInputStream.fill(BufferedInputStream.java:246)

[na:1.8.0_73]
at java.io.BufferedInputStream.read(BufferedInputStream.java:265)

[na:1.8.0_73]
at java.io.DataInputStream.readUnsignedByte(DataInputStream.java:288)

[na:1.8.0_73]
at com.rabbitmq.client.impl.Frame.readFrom(Frame.java:95)

[amqp-client-3.6.2.jar:na]
at com.rabbitmq.client.impl.SocketFrameHandler.readFrame(SocketFrameHandler.java:139) [amqp-client-3.6.2.jar:na]
at com.rabbitmq.client.impl.AMQConnection$MainLoop.run(AMQConnection.java:542)

[amqp-client-3.6.2.jar:na]
. 1 common frames omitted

Who can help deal with this problem?

The text was updated successfully, but these errors were encountered:

acogoluegnes commented Nov 15, 2017

Thank you for your time.

Team RabbitMQ uses GitHub issues for specific actionable items engineers can work on. This assumes two things:

1. GitHub issues are not used for questions, investigations, root cause analysis, discussions of potential issues, etc (as defined by this team)
2. We have a certain amount of information to work with

We get at least a dozen of questions through various venues every single day, often quite light on details.
At that rate GitHub issues can very quickly turn into a something impossible to navigate and make sense of even for our team. Because of that questions, investigations, root cause analysis, discussions of potential features are all considered to be mailing list material by our team. Please post this to rabbitmq-users.

Getting all the details necessary to reproduce an issue, make a conclusion or even form a hypothesis about what’s happening can take a fair amount of time. Our team is multiple orders of magnitude smaller than the RabbitMQ community. Please help others help you by providing a way to reproduce the behavior you’re
observing, or at least sharing as much relevant information as possible on the list:

• Server, client library and plugin (if applicable) versions used
• Server logs
• A code example or terminal transcript that can be used to reproduce
• Full exception stack traces (not a single line message)
• rabbitmqctl status (and, if possible, rabbitmqctl environment output)
• Other relevant things about the environment and workload, e.g. a traffic capture

Feel free to edit out hostnames and other potentially sensitive information.

When/if we have enough details and evidence we’d be happy to file a new issue.

java.net.SocketException: Unrecognized Windows Sockets error: 0: JVM_Bind (JBOSS)

I’m using JBoss 4.0.5 GA on Windows 7 with Java version 1.5 (I have to use older java version and a JBoss because I’m working with a legacy system). And when I’m starting the server I get the following error:

And I believe this causes many other exceptions:

I greatly appreciate if anyone could help. At least to figure out where I should look for the solution (e.g. Is this an error related to windows 7 and JBoss clustering incompatability? Is this because of a wrong port configuration? etc.)

11 Answers 11

This problem occurs on some Windows systems that have the IPv6 TCP Stack installed. If both IPv4 and IPv6 are installed on the computer, the Java Virtual Machine (JVM) may have problems closing or opening sockets at the operating system level.

Add the following JVM option: -Djava.net.preferIPv4Stack=true

I’ve seen this happen on Windows 7 and Windows 2008 systems which have both IPv4 and IPv6 stacks installed by default.

You have very likely another process already bound on a port that JBoss is using (8080?) and this prevent JBoss from starting correctly (see this page for a list of ports used by JBoss).

Either find the conflicting process and shut it down:

• use netstat -a -o -n and look for ports used by JBoss (e.g. 8080) and the corresponding pid
• then use tasklist /FI «PID eq

» to find the process

Or change JBoss defaults ports. There are several ways to do that but the best way is to use the Service Binding Manager (see detailed instructions in Configuring Multiple JBoss Instances On One Machine).

The default port in the example code is 4444. Using this port I got «Unrecognized Windows Sockets error: 0: JVM_Bind»

I changed the port to 44444 and tried again. I got a popup from the Windows Firewall service asking me if this application had permission to access the network. Selecting OK I no longer get the error message when I launch my server.

After some experimenting I found that with a port of 5000 or less I would get the JVM_Bind error. Any port of 5001 or above would bind without issue.

Minecraft Launcher Java Error- java.net.SocketException: Unrecognized Windows Sockets error: 10106: create

When I start my Minecraft Launcher I get an error specifically shown below:

The full error is shown below:

I kept looking for ways, and it didn’t work.

• Reinstalling/updating java.
• Messing with firewall/anti-malware stuff.
• Reinstalling the launcher.
• Getting the Windows Update

Other info you may want to know:

• I use malwarebytes to get rid of viruses because I had Adblocknwatch extension virus that couldn’t be uninstalled/removed.
• When I got malwarebytes my minecraft stopped working.
• I have AT&T u-verse and my computer [WAS] port-forwarded for my server, I unport-forwarded it to see if it would fix the problem, but it didn’t.
• I only have Java jre7 no higher/lower
• This was asked as of April 6th, 2014.

Here is the full bootstrap error thing:

3 Answers 3

I fixed this by reinstalling Java:

1. Go to Control Panel > Programs and Features
2. Uninstalled Java and all Java updates
3. Go to Java’s download site and reinstalled Java

and bam it worked

I found my problem and solution. It was a malware issue, for others, this maybe you too. So get Microsoft Security Essentials and scan on your computer. After scanning, I found a browser hijack hack thing that was hacking my connection. So when I quarantined it, I fixed it! 😀 But still have issues with connecting to google and youtube. Hope this helps other people. Even malware-bytes didn’t help.

I’d like too comment this, as this won’t be useful that much as first — but im still too jelly for this 😉 Sorry.

I’d like to see your Bootstrap or at least your Windows os + Version (32/64).

Without knowing this lets start low.

1. Take a laptop, install the same Version of Minecraft and put it in your Network exactly like you did with your PC. (you connected the pc vial ethernet — plug the pcs lan-Cable in your laptopor if you use w-lan-> use the same accesspoint)
2. If this works, try to alter your PCs ip-address. (some intelligent routers try to prevent you from unwanted ports after your virus-software informs them)
3. Probably your problem isn’t solved yet. The next thing to do is saving your .minecraft folder from appdata to any flashdrive and put it on your test-laptop
4. post your results below

I got my coffee now, lets go on 🙂 So you’re running Windows7 on a 64bit core — I am sorry, ‘ have not read this properly first.

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

means you are failing to open the port. Usually this has one of two reasons: either you (or any program you installed) blocked the port to protect you, or any program you have got is using the Port right now.

but IIRC the second possibility should have caused something like this:

But this may have changed due the new launcer, so lets scan the ports.

Windows + R —> cmd —> enter
netstat -b

This will give you a list of all active Ports and the matching programs using them.

Unrecognized Windows Sockets error #264

Comments

ghost commented Jul 5, 2017

Since the author of issue #257 deleted his account and I’m with the same issue. I created other issue and the previous issue should be closed.

Note that all code is the same of this wiki

Setup:

build.gradle:

Output:

The text was updated successfully, but these errors were encountered:

JoeHegarty commented Jul 5, 2017 •

From your log, it looks like it actually ran correctly so the warning is not actually causing the application to break.

I am not 100% sure what would cause the warning you’re seeing and unfortunately I don’t have access to a windows machine right now. You may need to set java.net.preferIPv4Stack=true or something similar.
The rest of the log messages look normal and are simple status reports. If you include an slf4j compatible logging library such as sl4j-simple you will see the Orbit output logs as well.

Please let me know if you have any other questions/issues and I’m happy to help.

JoeHegarty commented Jul 5, 2017

I believe @johnou develops on Windows and uses the JGroups/Infinispan module so he may have some additional insight.

ghost commented Jul 5, 2017 •

System.setProperty(«java.net.preferIPv4Stack» , «true»);
Solved the issue.

But I don’t believe this is the best method. @JoeHegarty

johnou commented Jul 6, 2017 •

@Lai0n if your machine has multiple interfaces your Jgroups configuration should bind to specific address(es) or interface(s). Here are some examples below, the Jgroups documentation contains more snippets for various use cases like Docker.

ghost commented Jul 6, 2017 •

@johnou I tried this config:

but no success. Can you give me a example?

johnou commented Jul 7, 2017

@Lai0n it would be helpful to know more about your environment, do you want a simple local host configuration? Multiple machines? Static ips / host names? Your jgroups tcpping tag is missing initial_hosts. You might want to keep an eye on #262 I am on holiday at the moment so apologies for the satellite delay.

ghost commented Jul 9, 2017 •

@johnou a simple local host configuration, one machine, static IP.

johnou commented Jul 9, 2017

Try something like this..

ghost commented Jul 12, 2017 •

JoeHegarty commented Jul 12, 2017

Glad to hear you resolved the issue!

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Confluence Support

Get started

Knowledge base

Products

Jira Software

Project and issue tracking

Jira Service Management

Service management and customer support

Jira Core

Manage any business project

Confluence

Bitbucket

Git code management

Resources

Documentation

Usage and admin help

Community

Answers, support, and inspiration

System Status

Cloud services health

Suggestions and bugs

Feature suggestions and bug reports

Marketplace

Billing and licensing

Frequently asked questions

Viewport

Confluence

Index queue won’t flush automatically, ‘Caused by: java.net.SocketException: Unrecognized Windows Sockets error: 0: recv failed’ errors thrown

Related content

Still need help?

The Atlassian Community is here for you.

Platform Notice: Server and Data Center Only — This article only applies to Atlassian products on the server and data center platforms .

Problem

Unable to clear indexing queue automatically, items sit in the queue even after:

You may also see this error:

Diagnosis

Environment

• Windows
• Server has both IPv4 and IPv6 enabled

Cause

The Java Virtual Machine (JVM) can have problems opening or closing sockets at the operating system level when both IPv4 and IPv6 are enabled on a Windows server.

Workaround

JVM will need to run over IPv4, if possible. To do this add this set the following JVM option:

Shutdown Confluence

Open /bin/setenv.bat

For Confluence 5.6 and later

Add the following below CATALINA_OPTS section

Save the file

Add the following below the JAVA_OPTS section

Save the file

Start Confluence

You may also need to adjust the prefix policy to prefer IPv4 over IPv6

If you are unfamiliar with the process you can refer to Microsoft’s Fix-its.

These Fix-its are provided by Microsoft and are not supported by Atlassian.