|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Re: Please Help! Pythondriver says: ERR -11608 COMMUNIC sql03_request: wrong connection state, state is 'requested'
From: Andre Reitz (reitz
inworks.de)
Date: Mon Feb 28 2005 - 12:36:25 CST
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Andre Reitz wrote:
> Andre Reitz wrote:
>
>> Dittmar, Daniel wrote:
>>
>>>> By the way: Why do I get the 700 Error
>>>> (700, 'Session inactivity timeout (work rolled back)', 'I888')
>>>
>>>
>>>
>>>
>>> When the connection is broken and the driver can reconnect, a timeout is
>>> assumed as there is no way of knowing what was the real reasong for the
>>> disconnect.
>>>
>>
>> so I am pretty sure that there is a big bug uin the python-driver
>> (Perhaps a threading-proble or a global variable , ....)
>>
>> could you please give me a hint where the problem could be located?
>>
>> It most times starts with an I8888
>>
>> and then it comes to a segfault.
>>
>> the server says that it is the applications fault:
>>
>> 2005-02-28 17:34:43 17809 11561 COMMUNIC Connecting T37
>> gemini.intra 752
>> 2005-02-28 17:34:43 17851 11561 COMMUNIC Connected T37
>> gemini.intra 752
>> 2005-02-28 17:34:49 17809 11561 COMMUNIC Connecting T38
>> gemini.intra 752
>> 2005-02-28 17:34:49 17847 11561 COMMUNIC Connected T38
>> gemini.intra 752
>> 2005-02-28 17:34:53 17809 11561 COMMUNIC Connecting T39
>> gemini.intra 752
>> 2005-02-28 17:34:53 17848 11561 COMMUNIC Connected T39
>> gemini.intra 752
>> 2005-02-28 17:34:59 17809 11561 COMMUNIC Connecting T40
>> gemini.intra 752
>> 2005-02-28 17:34:59 17847 11561 COMMUNIC Connected T40
>> gemini.intra 752
>> 2005-02-28 17:35:00 17809 11561 COMMUNIC Connecting T41
>> gemini.intra 752
>> 2005-02-28 17:35:00 17850 11561 COMMUNIC Connected T41
>> gemini.intra 752
>> 2005-02-28 17:35:02 17809 11561 COMMUNIC Connecting T42
>> gemini.intra 752
>> 2005-02-28 17:35:02 17851 11561 COMMUNIC Connected T42
>> gemini.intra 752
>> 2005-02-28 17:35:02 17809 11561 COMMUNIC Connecting T43
>> gemini.intra 752
>> 2005-02-28 17:35:02 17852 11561 COMMUNIC Connected T43
>> gemini.intra 752
>> 2005-02-28 17:35:03 17809 11561 COMMUNIC Connecting T44
>> gemini.intra 752
>> 2005-02-28 17:35:03 17847 11561 COMMUNIC Connected T44
>> gemini.intra 752
>> 2005-02-28 17:35:04 17809 11561 COMMUNIC Connecting T45
>> gemini.intra 752
>> 2005-02-28 17:35:04 17854 11561 COMMUNIC Connected T45
>> gemini.intra 752
>> 2005-02-28 17:35:04 17848 11509 COMMUNIC Connection broken by appl
>> state 10 T38 <<<<<<<<---------
>> 2005-02-28 17:35:04 17848 WNG 11824 COMMUNIC Releasing T38 connection
>> aborted
>> 2005-02-28 17:35:04 17848 12929 TASKING Task T38 started
>> 2005-02-28 17:35:04 17848 11007 COMMUNIC wait for connection T38
>> 2005-02-28 17:35:04 17847 11509 COMMUNIC Connection broken by appl
>> state 10 T37
>> 2005-02-28 17:35:04 17847 WNG 11824 COMMUNIC Releasing T37 connection
>> aborted
>> 2005-02-28 17:35:04 17847 12929 TASKING Task T37 started
>> 2005-02-28 17:35:04 17847 11007 COMMUNIC wait for connection T37
>> 2005-02-28 17:35:04 17852 11509 COMMUNIC Connection broken by appl
>> state 10 T42
>> 2005-02-28 17:35:04 17852 WNG 11824 COMMUNIC Releasing T42 connection
>> aborted
>> 2005-02-28 17:35:04 17852 12929 TASKING Task T42 started
>> 2005-02-28 17:35:04 17852 11007 COMMUNIC wait for connection T42
>> 2005-02-28 17:35:04 17849 11509 COMMUNIC Connection broken by appl
>> state 10 T39
>> 2005-02-28 17:35:04 17849 WNG 11824 COMMUNIC Releasing T39 connection
>> aborted
>> 2005-02-28 17:35:04 17849 12929 TASKING Task T39 started
>> 2005-02-28 17:35:04 17849 11007 COMMUNIC wait for connection T39
>> 2005-02-28 17:35:04 17850 11509 COMMUNIC Connection broken by appl
>> state 10 T40
>> 2005-02-28 17:35:04 17850 WNG 11824 COMMUNIC Releasing T40 connection
>> aborted
>> 2005-02-28 17:35:04 17850 12929 TASKING Task T40 started
>> 2005-02-28 17:35:04 17850 11007 COMMUNIC wait for connection T40
>> 2005-02-28 17:35:04 17851 11509 COMMUNIC Connection broken by appl
>> state 10 T41
>> 2005-02-28 17:35:04 17851 WNG 11824 COMMUNIC Releasing T41 connection
>> aborted
>> 2005-02-28 17:35:04 17851 12929 TASKING Task T41 started
>> 2005-02-28 17:35:04 17851 11007 COMMUNIC wait for connection T41
>> 2005-02-28 17:35:04 17854 11509 COMMUNIC Connection broken by appl
>> state 10 T44
>> 2005-02-28 17:35:04 17854 WNG 11824 COMMUNIC Releasing T44 connection
>> aborted
>> 2005-02-28 17:35:04 17854 12929 TASKING Task T44 started
>> 2005-02-28 17:35:04 17854 11007 COMMUNIC wait for connection T44
>> 2005-02-28 17:35:04 17855 11509 COMMUNIC Connection broken by appl
>> state 10 T45
>> 2005-02-28 17:35:04 17855 WNG 11824 COMMUNIC Releasing T45 connection
>> aborted
>> 2005-02-28 17:35:04 17855 12929 TASKING Task T45 started
>> 2005-02-28 17:35:04 17855 11007 COMMUNIC wait for connection T45
>> 2005-02-28 17:35:04 17853 11509 COMMUNIC Connection broken by appl
>> state 10 T43
>> 2005-02-28 17:35:04 17853 WNG 11824 COMMUNIC Releasing T43 connection
>> aborted
>> 2005-02-28 17:35:04 17853 12929 TASKING Task T43 started
>> 2005-02-28 17:35:04 17853 11007 COMMUNIC wait for connection T43
>>
>>
>>
>
> Also som additional information:
>
> My console where the multithreaded application runs:
>
> ERR -11608 COMMUNIC sql03_request: wrong connection state, state is
> 'requested'
>
> ERR -11608 COMMUNIC sql03_request: wrong connection state, state is
> 'requested'
>
> ERR -11608 COMMUNIC sql03_request: wrong connection state, state is
> 'requested'
>
> ERR -11608 COMMUNIC sql03_request: wrong connection state, state is
> 'requested'
>
> ERR -11607 COMMUNIC sql03_request: illegal reference: 214
> ERR -11607 COMMUNIC sql03_request: illegal reference: 214
> ERR -11607 COMMUNIC sql03_request: illegal reference: 214
> ERR -11607 COMMUNIC sql03_request: illegal reference: 214
> ERR -11607 COMMUNIC sql03_request: illegal reference: 214
> ERR -11607 COMMUNIC sql03_request: illegal reference: 214
> ERR -11607 COMMUNIC sql03_release: illegal reference: 214
> ERR -11607 COMMUNIC sql03_request: illegal reference: 214
> ERR -11607 COMMUNIC sql03_request: illegal reference: 214
> ERR -11607 COMMUNIC sql03_release: illegal reference: 214
> ERR -11607 COMMUNIC sql03_request: illegal reference: 214
> ERR -11607 COMMUNIC sql03_request: illegal reference: 214
> ERR -11607 COMMUNIC sql03_release: illegal reference: 214
> Speicherzugriffsfehler
>
>
... and sometimes I get this:
ERR -11608 COMMUNIC sql03_request: wrong connection state, state is 'requested'
ERR -11608 COMMUNIC sql03_request: wrong connection state, state is 'requested'
ERR -11608 COMMUNIC sql03_request: wrong connection state, state is 'requested'
ERR -11608 COMMUNIC sql03_request: wrong connection state, state is 'requested'
ERR -11607 COMMUNIC sql03_request: illegal reference: 235
ERR -11607 COMMUNIC sql03_request: illegal reference: 235
ERR -11607 COMMUNIC sql03_request: illegal reference: 235
ERR -11607 COMMUNIC sql03_release: illegal reference: 235
Fatal Python error: GC object already in linked list
Abgebrochen
>
>
>> Thank you very much in advance,
>> greetings, andre
>>
>>>
>>>> ... an why is the string I888 and not I8888?
>>>
>>>
>>>
>>>
>>> Because of an error in vin77.c:raiseSQLError. sizeof (sqlStateStr) is
>>> being used, but sizeof (tsp00_C5) would be the right thing, as
>>> sqlStateStr is an pointer. This has been already fixed in 7.5.
>>>
>>> Daniel Dittmar
>>>
>>
>>
>
>
--
__________________________________________________________________________
Als Technologieunternehmen konzipieren und entwickeln wir maßgeschneiderte Feedback- und
Monitoring-Systeme - wie beispielsweise Lösungen für Beschwerde- und Ideenmanagement.
Mit dem Inquery® Survey Server bieten wir eine der leistungsfähigsten Standardlösungen für
Online-Umfragen mit dem Schwerpunkt auf der Messung von Kundenzufriedenheit an.
__________________________________________________________________________
Inworks GmbH
Andre Reitz, Leiter Entwicklung
Hörvelsinger Weg 39, 89081 Ulm, Germany
Tel +49 (0) 731 / 93807-21
Fax +49(0)731/93807-18
Internet: http://www.inworks.de
--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]