Error #150 On Progress Solaris
transport endpointNext: /opt/bin/jws: /solaris/bin/locate_dirs: not foundOperation now in progress Cause An operation that takes a long time to complete (such as a connect) was attempted on a non-blocking object. Technical Notes The symbolic name for this error is EINPROGRESS, errno=150. Previous: Operation not supported on transport endpointNext: /opt/bin/jws: /solaris/bin/locate_dirs: not found © 2010, Oracle Corporation and/or its affiliates
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up What are possible reason for socket error EINPROGRESS in solaris? up vote 2 down vote favorite 1 What are possible reason for socket error EINPROGRESS in Solaris? How https://docs.oracle.com/cd/E19455-01/806-1075/msgs-1889/index.html we can check the root cause? tcp api is : connect c sockets tcp solaris share|improve this question edited Nov 26 '11 at 11:25 asked Nov 26 '11 at 11:01 Syedsma 2303820 1 It means you've got an asynchronous thing going on, and it's not done yet. Please specify what system call you're talking about if you want constructive answers. –Mat Nov 26 '11 at 11:09 I already pointed you to how to go http://stackoverflow.com/questions/8277970/what-are-possible-reason-for-socket-error-einprogress-in-solaris on by adding the man pages extract on how to get more detailed info on this here: stackoverflow.com/q/8277540/694576 –alk Nov 26 '11 at 11:19 Anyway, showing us at least your client's code would surely help ... –alk Nov 26 '11 at 11:24 add a comment| 2 Answers 2 active oldest votes up vote 8 down vote You have a non-blocking socket and you are calling connect() in it. Since connect() needs the 3-way handshake to happen (so a network roundtrip), it either blocks waiting for the SYN-ACK in blocking sockets, or gives you some indication that it hasn't succeded yet in non-blocking sockets. Normally, non-blocking sockets return EAGAIN/EWOULDBLOCK to tell you that they couldn't progress and you should try again: this is not exactly your case, connect() returns EAGAIN/EWOULDBLOCK when there are no free ephemeral ports to tell you that you should try again later; so there is another error for non-blocking connect: EINPROGRESS, which tells you that the operation is in progress and you should check its status later. To check the status later, the socket will become ready for writability, so you can use select()/poll()/... to test for that, after which you'll have to getsockopt(...SO_ERROR...) to get the success/failure status of your connect() operation. share|improve this answer answered Nov 26 '11 at 15:22 ninjalj 28.6k257100 Right now I am chking only for EAGAIN/EWOULDBLOCK erro
hand off client connection TNS-12547: TNS:lost contact TNS-12560: TNS:protocol adapter error TNS-00517: Lost contact IBM/AIX RISC System/6000 Error: http://emrebaransel.blogspot.com/2008/09/commonly-known-tns-errors.html 32: Broken pipe Cause: The error 32 indicates the communication has been broken while the listener is trying to hand off the client connection to the server process or dispatcher process. Action: 1. One of reason would be processes parameter being low, and can be verified by the v$resource_limit view. error #150 2. In Shared Server mode, check the 'lsnrctl services' output and see if the dispatcher has refused any connections, if so, then consider increasing the number of dispatchers. 3. Check the alert log for any possible errors. 4. Memory resource is also another cause for this issue. Check the swap, memory error #150 on usage of the OS. ______________________________________________________________________________________________________________________________________ Error: 11: Resource temporarily unavailable Error stack in listener log: TNS-12518: TNS:listener could not hand off client connection TNS-12549: TNS:operating system resource quota exceeded TNS-12560: TNS:protocol adapter error TNS-00519: Operating system resource quota exceeded IBM/AIX RISC System/6000 Error: 11: Resource temporarily unavailable Cause: As the error indicates operating system resource has exceeded. Action: 1. Increase the appropriate OS kernal parameters for 'maximum number of processes allowed per user'. For example for HP-UX the parameters are maxuprc and nproc. ______________________________________________________________________________________________________________________________________ Error: 12: Not enough space Error stack in listener log: TNS-12518: TNS:listener could not hand off client connection TNS-12549: TNS:operating system resource quota exceeded TNS-12560: TNS:protocol adapter error TNS-00519: Operating system resource quota exceeded IBM/AIX RISC System/6000 Error: 12: Not enough space Cause: This is a memory related issue. The error indicates that there is not enough memory available to spawn and hand off the cl