YAWS, SOAP and SSL under load result in SSL socket closing with bad_info

Jan Jacobs <>
Thu Aug 12 21:14:50 CEST 2010


I have an application which uses YAWS(1.88) in embedded mode with SOAP 
over SSL.
It is using R13B04 on windows platforms (XP 32 Bit, Vista 32 Bit and 
Windows 2008 64 Bit).

I am getting the following error:

(It looks like a SSL error)
=ERROR REPORT==== 4-Aug-2010::11:37:19 ===
** State machine <0.7595.0> terminating
** Last message in was {tcp_error,#Port<0.17333>,econnaborted}
** When State == connection


** Reason for termination =
** bad_info

(which then kicks a yaws error)
=ERROR REPORT==== 4-Aug-2010::11:37:19 ===
Yaws process died: {bad_info,{gen_fsm,sync_send_all_state_event,

This happens under load or when more than 300000 SOAP transaction has 
been processed.
I then have to stop SSL and YAWS applications and start them again to 
accept more transactions.

YAWS Config:
  GL =
     {enable_soap,       true}
     ,{trace,            false}
     ,{tmpdir,           DirLog}
     ,{logdir,           DirLog}
     ,{ebin_dir,         [DirEbin]}
     ,{include_dir,      DirInc}
     ,{max_connections,  nolimit}
     ,{use_old_ssl,      false}
     ,{flags,            [
                           {auth_log,      true}
                           ,{tty_trace,    true}
                           ,{copy_errlog,  false}

   SL =
     {port,              PortYaws}
     ,{servername,       MyHostname}
     ,{dir_listings,     true}
     ,{listen,           {0,0,0,0}}
     ,{appmods,          [{"/OpenAPI",maxman_km_service_soap}]}
     ,{flags,            [

YAWS SSL Config:

Any suggestions and/or comments will be appreciated.


More information about the erlang-questions mailing list