[wsf-c-dev] [jira] Created: (WSFC-176) rm_echo_1_1.exe fails with server chash

[Dushshantha Chandradasa (JIRA)]

rm_echo_1_1.exe fails with server chash
---------------------------------------

                 Key: WSFC-176
                 URL: http://wso2.org/jira/browse/WSFC-176
             Project: WSO2 WSF/C
          Issue Type: Bug
          Components: Apache Sandesha/C (RM)
    Affects Versions: Current (nightly)
         Environment: Windows XP
MySQL Server 2005
            Reporter: Dushshantha Chandradasa


The sample gives the following error message. 

sql_stmt_update:update seq_property set seq_id='Sandesha2InternalSequence:http:/
/127.0.0.1:9090/axis2/services/RMSampleService:37967684-c302-4123-8546-2aec8b45a
1f5', name='LastActivatedTime',value='1196228843' where id='Sandesha2InternalSeq
uence:http://127.0.0.1:9090/axis2/services/RMSampleService:37967684-c302-4123-85
46-2aec8b45a1f5:LastActivatedTime'
update error_msg:Lock wait timeout exceeded; try restarting transaction

And after that, the client exits with the message "Error in my_thread_global_end(): 1 threads didn't exit"

Sometimes, axis2_http_server segfaults.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://wso2.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira