Bug #66572 [Com]: Crash / Suspended execution

From: Date: Mon, 27 Jan 2014 13:09:45 +0000
Subject: Bug #66572 [Com]: Crash / Suspended execution
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-184031@lists.php.net to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=66572&edit=1

 ID:                 66572
 Comment by:         jitesh dot prajapati at infostretch dot com
 Reported by:        jitesh dot prajapati at infostretch dot com
 Summary:            Crash / Suspended execution
 Status:             Open
 Type:               Bug
 Package:            Sockets related
 Operating System:   Cent OS 6
 PHP Version:        Irrelevant
 Block user comment: N
 Private report:     N

 New Comment:

socket_write() never returns? - <b>MY ANSWER</b> - Yes, Program execution suspended on
socket_write and hags up.

It's really just a call to write(3) so there's not much room for it to have problems. 

Could the socket be blocked - <b>MY ANSWER</b> - Not sure, it may block by php function
and have a some dead lock situation.

implying the client isn't reading everything from it? - <b>MY ANSWER</b> - client
is reading all information when it is delivered .


Previous Comments:
------------------------------------------------------------------------
[2014-01-27 06:36:45] jitesh dot prajapati at infostretch dot com

Thank you for your quick response.

Please find following URL containing code we have implemented.

http://202.131.96.147/test/wevsocketclass.php

Execution got suspended on "socket_write" function in "send" method, and till i
do not restart service it hangs up.

We do not implement explicit block/unblock of sockets. We have tried on different linux servers, and
same issue is producing on each servers.

------------------------------------------------------------------------
[2014-01-26 00:04:13] requinix@php.net

Still not enough info. We need to see demo code (a short sample that exhibits the same problem, not
your real thing), or error information, or backtraces, or something. A textual description of what
you observe is alright but doesn't really offer us much to go on.

You say "crash" but the process is running? Then it's not a crash. socket_write()
never returns? It's really just a call to write(3) so there's not much room for it to have
problems. Could the socket be blocked, implying the client isn't reading everything from it?

------------------------------------------------------------------------
[2014-01-25 10:41:22] jitesh dot prajapati at infostretch dot com

More Information
-----------------

We have implemented web socket server, and it is working fine, it able to handle so many
read/writes.

Now issue is after some time (around 20-30 mins and sometime longer than it), server got crash, it
shows service in process list but server does not able to request response.

We have placed different debugging points and found that server goes crash on executing function
socket_write.

------------------------------------------------------------------------
[2014-01-25 10:39:34] jitesh dot prajapati at infostretch dot com

More Information
-----------------

We have implemented web socket server, and it is working fine, it able to handle so many
read/writes.

Now issue is after some time (around 20-30 mins and sometime longer than it), server got crash, it
shows service in process list but server does not able to request response.

We have placed different debugging points and found that server goes hand on executing function
socket_write.

------------------------------------------------------------------------
[2014-01-25 04:02:04] requinix@php.net

Not enough information was provided for us to be able
to handle this bug. Please re-read the instructions at
http://bugs.php.net/how-to-report.php

If you can provide more information, feel free to add it
to this bug and change the status back to "Open".

Thank you for your interest in PHP.




------------------------------------------------------------------------


The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at

    https://bugs.php.net/bug.php?id=66572


-- 
Edit this bug report at https://bugs.php.net/bug.php?id=66572&edit=1


Thread (9 messages)

« previous php.bugs (#184031) next »