Exception when closing

13 views
Skip to first unread message

Anders Persson

unread,
Jan 8, 2019, 7:48:30 AM1/8/19
to Eiffel Web Framework
I got this exception when ending the application. I am not sure how I triggered the problem.


Broken pipe: OPERATING_SYSTEM_SIGNAL_FAILURE raised (OPERATING_SYSTEM_SIGNAL_FAILURE)
******************************** Thread exception *****************************
In thread           Child thread           0x7F270EFFD700 (thread id)
*******************************************************************************
-------------------------------------------------------------------------------
Class / Object      Routine                Nature of exception           Effect
-------------------------------------------------------------------------------
SSL                 c_ssl_shutdown         Broken pipe:                 
<00007F2715DF6FE8>                         Operating system signal.      Fail
-------------------------------------------------------------------------------
SSL                 c_ssl_shutdown                                      
<00007F2715DF6FE8>                         Routine failure.              Fail
-------------------------------------------------------------------------------
SSL                 shutdown @1                                         
<00007F2715DF6FE8>                         Routine failure.              Fail
-------------------------------------------------------------------------------
HTTPD_STREAM_SECURE_SOCKET
                    shutdown @2            
<00007F2715DF6C78>  (From SSL_NETWORK_STREAM_SOCKET)
                                           Routine failure.              Fail
-------------------------------------------------------------------------------
HTTPD_STREAM_SECURE_SOCKET
                    close @3               
<00007F2715DF6C78>  (From SOCKET)          Routine failure.              Fail
-------------------------------------------------------------------------------
WGI_HTTPD_REQUEST_HANDLER
                    execute @26            
<00007F2715DF6BE8>  (From HTTPD_REQUEST_HANDLER_I)
                                           Routine failure.              Fail
-------------------------------------------------------------------------------
WGI_HTTPD_REQUEST_HANDLER
                    safe_execute @4        
<00007F2715DF6BE8>  (From HTTPD_REQUEST_HANDLER_I)
                                           Routine failure.              Fail
-------------------------------------------------------------------------------
APPLICATION_TODO    root's creation                                     
<00007F27160B0038>                         Routine failure.              Exit
-------------------------------------------------------------------------------




It is at "shutdown" below


close
-- Close socket for all context.
-- (from SOCKET)
require -- from IO_MEDIUM
medium_is_open: not is_closed
do
if is_open_read or is_open_write then
shutdown
end
if exists then
close_socket
end
end

Another question. Why does we do shutdown before clsoing sockets?


Jocelyn Fiat

unread,
Jan 14, 2019, 10:54:46 AM1/14/19
to eiffel-web-framework
Hi Anders,

Is it easy to reproduce?

Regards
-- Jocelyn

--
--
You received this message because you are subscribed to the Google
Groups "Eiffel Web Framework" group.
 
To post to this group, send email to
eiffel-web...@googlegroups.com
To unsubscribe from this group, send email to
eiffel-web-frame...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/eiffel-web-framework
 
See the site for the Eiffel-Web-Framework project at
https://github.com/EiffelWebFramework/EWF
---
You received this message because you are subscribed to the Google Groups "Eiffel Web Framework" group.
To unsubscribe from this group and stop receiving emails from it, send an email to eiffel-web-frame...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


--
Jocelyn
------------------------------------------------------------------------
Eiffel Software
https://www.eiffel.com
Customer support: https://support.eiffel.com
User group: https://groups.google.com/forum/#!forum/eiffel-users
------------------------------------------------------------------------

Anders Persson

unread,
Jan 15, 2019, 4:42:11 AM1/15/19
to Eiffel Web Framework
No, it is not easy to reproduce, I got it about 10 times but never understood 100% what I did. Then it disappeared and I can not reproduce it now.

If I remember correct it happened when I was at a page that had created a socket connection. Then I, in the browser, moved to another page, then I got it.

Anders

For more options, visit this group at
http://groups.google.com/group/eiffel-web-framework
 
See the site for the Eiffel-Web-Framework project at
https://github.com/EiffelWebFramework/EWF
---
You received this message because you are subscribed to the Google Groups "Eiffel Web Framework" group.
To unsubscribe from this group and stop receiving emails from it, send an email to eiffel-web-framework+unsub...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Jocelyn Fiat

unread,
Jan 21, 2019, 4:57:23 AM1/21/19
to eiffel-web-framework
Ok, did you experienced any issue in production ? (i.e not during development?)
I think EiffelWeb standalone implementation is protected against such crash (i.e a rescue should catch this, and just consider the socket closed, then continue to next request).

-- Jocelyn


For more options, visit this group at
http://groups.google.com/group/eiffel-web-framework
 
See the site for the Eiffel-Web-Framework project at
https://github.com/EiffelWebFramework/EWF
---
You received this message because you are subscribed to the Google Groups "Eiffel Web Framework" group.
To unsubscribe from this group and stop receiving emails from it, send an email to eiffel-web-frame...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.


--
Jocelyn
------------------------------------------------------------------------
Eiffel Software
https://www.eiffel.com
Customer support: https://support.eiffel.com
User group: https://groups.google.com/forum/#!forum/eiffel-users
------------------------------------------------------------------------

--
--
You received this message because you are subscribed to the Google
Groups "Eiffel Web Framework" group.
 
To post to this group, send email to
eiffel-web...@googlegroups.com
To unsubscribe from this group, send email to

For more options, visit this group at
http://groups.google.com/group/eiffel-web-framework
 
See the site for the Eiffel-Web-Framework project at
https://github.com/EiffelWebFramework/EWF
---
You received this message because you are subscribed to the Google Groups "Eiffel Web Framework" group.
To unsubscribe from this group and stop receiving emails from it, send an email to eiffel-web-frame...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Anders Persson

unread,
Jan 21, 2019, 5:42:00 AM1/21/19
to eiffel-web...@googlegroups.com
On Mon, 21 Jan 2019 at 10:57, Jocelyn Fiat <jf...@eiffel.com> wrote:
Ok, did you experienced any issue in production ? (i.e not during development?)

I have not seen this in production. It might have been temporary during development, e.g. melting many times etc.

In production I have noted that it one time the server was "looping", e.g. consuming 100% of a CPU and not responding, but I do not think that that is related. I will try to gather more information about the looping if it happens again. Any suggestion of how to track that kind of problems in a freezed version? I can of add prints, build it differently if you think that would help to pinpoint that kind of problems.
 
I think EiffelWeb standalone implementation is protected against such crash (i.e a rescue should catch this, and just consider the socket closed, then continue to next request).

Yes, I agree.
Reply all
Reply to author
Forward
0 new messages