[jdev] Re: Re: Problem with PyMSN-t

[Daniel Henninger]

Just FYI, this threat is being taken over to the py-transports mailing list.

Daniel

-- 
"The most addictive drug in the world is music."
     - The Lost Boyz

> Hey Daniel,
>
> So I have more information about the problem I'm having with PyAIM. From
> the command line window I execute "python main.py" and it seems that the
> process is launched in background since I have again the command line.
> Checking at the Windows Task Manager I see the python process running.
> However, I don't see any connection being established to the server.
> FYI, I'm using the same configuration I used for PyMSN (ie. same
> mainServer and port).
>
> Here is more weird information. I'm running McAfee and when I launched
> PyAIM the mcshield.exe process was consuming 60% of the CPU. I closed
> the command line window (thus killing the python process) and the
> mcshield.exe process went back to 0%. So my next step was to disable
> McAfee. This time the CSRSS.EXE process was consuming 80% of the CPU
> when I launched PyAIM. None of this happens when using PyMSN. BTW, I'm
> now using Twisted 2.0.1 for Python 2.3.
>
> Regards,
>
>   -- Gato
>
>
> "Daniel Henninger" <jadestorm at nc.rr.com> wrote in message
> news:<40915.10.0.0.1.1119532767.squirrel at www.vorpalcloud.org>...
>> I'm using PyMSNt with JM. However, I failed to start up PyAIMt. :(
>
> Define "failed to start".  =)  Does PyAIM not work with Jive Messenger
> or
> is it not starting up period?
>
> Daniel
>
>>
>> Which client are you using? I'm using Exodus for my tests. If you want
> you
>> can try connecting to my local server just to isolate the variables
> and
>> confirm that it's not a client issue.
>>
>> Regards,
>>
>>   -- Gato
>>
>>
>> "Patrick Dalla Bernardina" <patrick at jfes.trf2.gov.br> wrote in message
>> news:42B9CE4B.2070100 at jfes.trf2.gov.br...
>>> Hi,
>>>
>>> does anybody uses JIVE with PyMSNt or PyAIMt?
>>>
>>> I couldn't make them work..
>>>
>>> Every message I sent to an MSN or AIM user I receive a response that
> it
>>> is
>>> necessary to log in the transport. But I have already registered and
>>> entered my credentials
>>>
>>> How do I do this?
>>>
>>>
>>> Tim Fulcher - Clickatell wrote:
>>>
>>>>Hi All
>>>> I've been seating with this for a few days now. After finally
>>>> succeeding
>>>>to complile both mu-conference 0.6.0 and yahoo-transport 2.3.2 I run
>>>>into a segfault problem on yahoo-transport. Looking into the problem
> I
>>>>noticed that, with the exception of the "component" call both mu and
>>>>yahoo's main.c are identical (well that shouldn't be a surprise!).
> The
>>>>error occurs when the g_main_loop_run procedure is called. But the
>>>>segfault does not manifest itself if I comment out the
>>>>jcr_main_new_stream proc.
>>>> Is this a common fault and if so how can it be fixed?
>>>> I have attached both logs:
>>>> mu-conference:
>>>>main.c:148 (main): Jabber Component Runtime -- 0.2.4 starting.
>>>>
>>>>main.c:194 (main): Main loop starting.
>>>>
>>>>jcr_main_stream_error.c:50 (jcr_main_new_stream): Server stream
>>>>connected.
>>>>
>>>>jcr_deliver.c:51 (jcr_queue_deliver): packet delivery thread
> starting.
>>>>
>>>>jcr_shutdown.c:43 (jcr_server_shutdown): Server shutting down
>>>>
>>>>jcr_deliver.c:97 (jcr_queue_deliver): packet delivery thread exiting.
>>>>
>>>>jcr_deliver.c:98 (jcr_queue_deliver): Last DvryQ Buffer=''
>>>>
>>>>
>>>>Yahoo-Transport:
>>>>
>>>>main.c:148 (main): Jabber Component Runtime -- 0.2.4 starting.
>>>>
>>>>yahoo.localhost: Yahoo! Transport v2.3.2-JCR [stable] starting.
>>>>
>>>>jcr_base_connect.c:34 (jcr_socket_connect): Attempting connection to
>>>>127.0.0.1:5347
>>>>
>>>>main.c:194 (main): Main loop starting.
>>>>
>>>>jcr_base_connect.c:34 (jcr_socket_connect): Attempting connection to
>>>>127.0.0.1:5347
>>>>
>>>>jcr_base_connect.c:81 (jcr_send_start_stream): Opening XML stream:
> sent
>>>>161 bytes
>>>>
>>>>jcr_main_stream_error.c:50 (jcr_main_new_stream): Server stream
>>>>connected.
>>>>
>>>>jcr_deliver.c:51 (jcr_queue_deliver): packet delivery thread
> starting.
>>>>
>>>>jcr_deliver.c:92 (jcr_queue_deliver): wrote 1 packets of 63 bytes
>>>>
>>>>jcr_elements.c:177 (jcr_read_data): Main Channel Error: rc=2
>>>>
>>>>jcr_main_stream_error.c:56 (jcr_main_close_stream): Server stream
> error,
>>>>resetting
>>>>
>>>>jcr_deliver.c:97 (jcr_queue_deliver): packet delivery thread exiting.
>>>>
>>>>jcr_deliver.c:98 (jcr_queue_deliver): Last DvryQ Buffer=''
>>>>
>>>>jcr_base_connect.c:34 (jcr_socket_connect): Attempting connection to
>>>>127.0.0.1:5347
>>>>
>>>>jcr_base_connect.c:81 (jcr_send_start_stream): Opening XML stream:
> sent
>>>>161 bytes
>>>>
>>>>jcr_main_stream_error.c:50 (jcr_main_new_stream): Server stream
>>>>connected.
>>>>
>>>>jcr_deliver.c:51 (jcr_queue_deliver): packet delivery thread
> starting.
>>>>
>>>>jcr_deliver.c:92 (jcr_queue_deliver): wrote 1 packets of 63 bytes
>>>>
>>>>jcr_elements.c:177 (jcr_read_data): Main Channel Error: rc=2
>>>>
>>>>jcr_main_stream_error.c:56 (jcr_main_close_stream): Server stream
> error,
>>>>resetting
>>>>
>>>>jcr_deliver.c:97 (jcr_queue_deliver): packet delivery thread exiting.
>>>>
>>>>jcr_deliver.c:98 (jcr_queue_deliver): Last DvryQ Buffer=''
>>>>
>>>> TIA
>>>> Tim Fulcher
>>>>_______________________________________________
>>>>jdev mailing list
>>>>jdev at jabber.org
>>>>http://mail.jabber.org/mailman/listinfo/jdev
>>>>
>>>>
>>
>>
>>
>> _______________________________________________
>> jdev mailing list
>> jdev at jabber.org
>> http://mail.jabber.org/mailman/listinfo/jdev
>>
>>
>>
> ----------
> _______________________________________________
> jdev mailing list
> jdev at jabber.org
> http://mail.jabber.org/mailman/listinfo/jdev
>
>
>