Very Often - Error: Socket::Recv()

[Former Member]

Hello,

Very often I can find Socket::Recv error after an import process. Does anyone have the same problem? How it happens and how to solve?

(message from Server Log)

4752 2010/02/20 17:50:09.070 Timer: name: Record Matching 1 - Init total ms: 0.063929 35

4752 2010/02/20 17:50:09.070 Timer: name: Record Matching 2 - Source Filtering total ms: 0.049267 35

4752 2010/02/20 17:50:09.070 Timer: name: Record Matching 3 - Prepare total ms: 1.348688 35

4752 2010/02/20 17:50:09.070 Timer: name: Record Matching 4 - Field Match total ms: 7.868028 35

4752 2010/02/20 17:50:09.070 Timer: name: Record Matching 5 - Group BV total ms: 0.460759 35

4752 2010/02/20 17:50:09.070 Timer: name: Record Matching 6 - Calc Num total ms: 0.044427 35

4752 2010/02/20 17:50:09.070 Timer: name: Record Matching - Other total ms: 0.011378 35

5436 2010/02/20 17:50:09.102 Timer: name: Get Filtered Record Ids - 2 total ms: 0.117618 35

3228 2010/02/20 17:50:09.305 BulkImport: User IO created pre-launch workflow job10076

4752 2010/02/20 17:50:10.148 BulkImport received ImportManagerServiceStatus() to end import job.

4752 2010/02/20 17:50:10.398 BulkImport begins workflow launch processing.

4752 2010/02/20 17:50:10.398 BulkImport launch workflow job 10076

4752 2010/02/20 17:50:10.445 BulkImport completed successful launch of workflow job 10076

4752 2010/02/20 17:50:10.445 BulkImport ends workflow launch processing.

4972 2010/02/20 17:53:02.488 Error: Socket::Recv() (socket 509b8): Socket Error calling recv() (2733) The socket is nonblocking and the operation would block.

4972 2010/02/20 17:53:02.488 Error: Socket::Recv() (socket 509b8): Socket Error calling recv() (2733) The socket is nonblocking and the operation would block.

4972 2010/02/20 17:53:02.488 Error: Socket::Recv() (socket 509b8): Socket Error calling recv() (2733) The socket is nonblocking and the operation would block.

4972 2010/02/20 17:53:02.488 Error: Socket::Recv() (socket 509b8): Socket Error calling recv() (2733) The socket is nonblocking and the operation would block.

Thank you

Best regards,

Dale

Edited by: Dale Zhang on Feb 20, 2010 11:30 AM

[Former Member]

Hi,

Socket error ocuurs maily of two reasons:

1.IF you try to delete huge volume of data from the datamanager or at the same time if you try to import the data under same repository in the same table.That means if you perform two or more operations at time it will causes the socket error issues.

2.Port inconsistencies.

Solution is simple: If you open the port for the same rrpository in the console.It will solve your problem.Means goto console and open the port or change the port to some othe number.Generally it should be 4 digit number.

Hope It is helpful!

Thanks

Yugandhar

[Former Member]

Hello Yugandhar

Thanks for your response.

What do you mean by "open the port"??

Best regards,

Dale

[Former Member]

Hello,

I changed port number from 5100 to 9100. The problem still happens.

732 2010/02/23 09:52:40.997 Error: Socket::Recv() (socket 113198): Socket Error calling recv() (2733) The socket is nonblocking and the operation would block.

Do you have any other tips?

Best regards,

Dale

[Former Member]

Hi Dale did you resolve your socket issue?

were having a similiar error and are unable to access our Dev box

1. We are getting this error message in the Logs in MDM Console:

Error: Socket::Recv() (socket c): Socket Error calling recv() (b)

Resource temporarily unavailable

2. also when we try to connect to the repository there is logon screen error for usre name and password... we dont have a user name / password for our other systems for this same scenario

cheers

alex

[Former Member]

Hello Alex,

I was told by sap support such error message will not cause any function fail. Actually, we can still spot these messages in our P system but it doesn't cause any outage of MDM.

Best regards,

Dale

[Former Member]

Hi Dale,

There are so many reasons behind a socket error:

1. Application request/response failure

2. Hardware failure: Can check in Event Logs

3. Network Failure

4. Kernel Read/Write Time Out failure

5. If your repository is unloaded and users still trying to access it.

6. Number of users exceeds the limit in applications.

7. Same user trying to access a single server from two different machines and Application/OS trying to assign the same socket to both request.

8. Number of processes exceed the limit in Database.

9. Deadlock Situation in multiple write operations.

10. MDM Server Port is not open on network.

Socket failure messages are common in MDM Log file.

What i will suggest is check whether your MDM server is in backbone of 1GBPS network and if you are using EP iViews to access MDM server, set Session Timeout Minutes Parameter to 10 minutes in MDS.INI file and restart your MDM Server.

BR,

Alok Sharma

[Former Member]

Hi Alex,

I agree with Dale.

Please find the "SAP Note 1474008 - Large number of Socket Error calling recv() in Server log" for more details.

In it, you will find information There is no impact on MDM operations because the condition reported by this error is harmless

Kindly mark thread as answered if this solves your query.

Regards,

Mandeep Saini

[former_member153023]

Hi Dale,

Try to change the port number for your repository to some other number ,i mean higher one..

This may resolve the problem. Else sometimes if the import manger is being used by somebody else,it may block.

Reg,

bis