Author Topic: Sametime protocol  (Read 12852 times)

0 Members and 1 Guest are viewing this topic.

Offline phatmr

Sametime protocol
« on: 11 01 2016, 04:28:21 »
Hi,

i wanted to tell you about a (maybe old) Bug in the Sametime-Plugin.

I was glad to see that you have migrated this Plugin in Miranda NG too.
Thanks for that :)

The Problem is: somtimes (often) when i try to connect to the Sametimeserver it goes offline instantly.
Everytime that happened i noticed that the Serverentry in Options was deleted.
When i  put this Entry back and save the Options and try to reconnect it goes offline instantly again and also the Serverentry was deleted again too.

Mostly the first Connect is sucsessful. But when i have to Reconnect because (for Example) global ISP Disconnect or Miranda Crash that Bug happens.

Im using the newest Dev-Version of Miranda.

I know this Bug from the old Miranda (before NG).

So maybe some others know that Bug too?

If its nessary i can make a netlog later too.

phatmr
 

Offline Robyer

Re: Sametime protocol
« Reply #1 on: 12 01 2016, 18:37:25 »
phatmr, well if you say you can reproduce it all the time by putting some "Serverentry" in options then it sounds promising (maybe if you can share it with some developer). But I don't use this plugin and don't know how it works so...
I was developing mainly Facebook, Omegle, Steam, Dummy and MobileState plugins. Now I'm retired. Goodbye, everyone. ~ You can still find me on Facebook.
 

Offline phatmr

Re: Sametime protocol
« Reply #2 on: 12 01 2016, 23:25:10 »
Oh ok - im sorry.

I thought the other Devs look in here too sometimes? Or should i post it elsewhere?
Sure i can share more Information if needed.
 

Offline wsx22

Re: Sametime protocol
« Reply #3 on: 13 01 2016, 15:48:11 »
I've edopted this plugin from IM to NG and I'm using it now, but I've never seen that problem.

What fields in options -> Protocols -> SAMETIME was deleted after issue? (ID, Password, Server name, Port, others)?
Do Sametime options are still visable in data base settings after issue? (DBEditor plugin)

I think that it can be interaction with some other plugin, so make netlog when problem occurs (with all possible informations checked on),
describe what You do to reproduce problem and attach yours VersionInfo.
 

Offline phatmr

Re: Sametime protocol
« Reply #4 on: 13 01 2016, 18:23:17 »
Hi there,

here are the Answers to your Questions.
1. The Options -> Protocols -> Sametime "Server name" Field is empty after that Issue.
2. Via DBEditor this Server name Entry is still there.
3. I took and attached netlog.txt just when it happened
I think that will be the intresting part "file src\meanwhile\src\srvc_aware.c: line 963: assertion `list != NULL' failed"

After that happens i fill in the Servername in Options again and restart Miranda.
Then i try to connect again.
Sometimes (often) this happens 5 - 10 Times before a Connect is successful.

Miranda Version: 0.95.5 alpha #16030 x64
Plugin Version: 0.7.0.0

If u need more infos please tell.

And - thank you :)
 

Offline wsx22

Re: Sametime protocol
« Reply #5 on: 14 01 2016, 14:43:20 »
It's a problem when your Sametime server sends you login redirect packet when logging,
in this case the new host field in packet is empty, and Miranda has a problem.
I've tried to improve Miranda routines on login redirect (like other IM's using Meanwhile lib does)
Please retest new attached plugin version (x64 v 0.7.0.1), send netlog when any problems still exists here.

ps.
I see that you connect to server "messaging.ibm.com" but your login points to xx.ibm.com server,
this can be a cause of redirection try, maybe you can set your login server directly to xx.ibm.com
« Last Edit: 14 01 2016, 14:59:51 by wsx22 »
 

Offline phatmr

Re: Sametime protocol
« Reply #6 on: 14 01 2016, 16:27:10 »
The new Pluginversion failed to load when Miranda starts.

Miranda64.exe Systemerror
"The program cant start because msvcp140.dll is missing from your computer"

I downloaded 64bit Version of msvcp140.dll..
then

Miranda64.exe Systemerror
"The program cant start because vcruntime140.dll is missing from your computer"

I downloaded 64bit Version of vcruntime140.dll..

Now Miranda starts correctly but the Bug is still the same as in Version x64 0.7.0.0
Also the Server name Entry was deleted again.

And the Server is realy just only messaging.ibm.com. I have tried messaging.xx.ibm.com too but that server doesnt exist.

Additionally i attached the netlog.txt again.

Hope u can find anything.
Thank you
 

Offline phatmr

Re: Sametime protocol
« Reply #7 on: 14 01 2016, 17:02:44 »
Oh Im sorry the Error with the new plugin is another as i said before.

Now Miranda crashes short after Connect to Sametime.

I attached the new netlog.txt

It seems like an overflow or something like that.
 

Offline wsx22

Re: Sametime protocol
« Reply #8 on: 14 01 2016, 19:27:57 »
At this netlog there is normal Sametime connection without redirection and i can't see any errors or crashes here.
If there is crash please attach crashlog (from CrashDumper plugin)
Please try Sametime0702.zip version (it's properly recompiled and do not require msvcp140.dll - remove it) with last Miranda development version.
If your server sends you server redirect packet, there will be "OnLogInRedirect()" lines in netlog, this is case witch we are interested in.
I can't reproduce this situation on my environment so i rely on your tests.
 

Offline phatmr

Re: Sametime protocol
« Reply #9 on: 15 01 2016, 13:01:45 »
OK now i tested again.

-updated MirandaCore to #16085
-used the new 0.7.0.2 Version of Plugin

Miranda crashes again short after successful Connect to the Sametimeserver

I attached the new netlog.txt and crash.txt and options.jpg

Maybe u can find anything and Thank You
 

Offline wsx22

Re: Sametime protocol
« Reply #10 on: 15 01 2016, 15:24:50 »

At current netlog, the login redirect server message seems to be properly handled now, and Sametime connects without errors,
so i've commited this fix to SVN.
Crash occured 3 sec after my fix, and its crashlog does not suggest Sametime protocol.
Does same crash occured with current development version of Sametime (0.7.0.0) ?
Does same crash occured with new development version of Sametime after fix (0.7.0.3) ?
If yes make crashlog with debug symbols: http://wiki.miranda-ng.org/index.php?title=Crash_reports#Update_plugins_and_debug_symbols

 
 

Offline phatmr

Re: Sametime protocol
« Reply #11 on: 15 01 2016, 16:08:59 »
Hi again,

The Crash don't occure with current dev-version of Sametime (0.7.0.0) - Just only the Bug i posted in first.
You written there is a Version 0.7.0.3? Where can i get it?
I have only your last Version 0.7.0.2 you have attached here.

I downloaded latest debug symbols too an made a new crash.txt on Miranda-Crash with Sametimeplugin 0.7.0.2
But it seems the its like the same as before.
 

Offline wsx22

Re: Sametime protocol
« Reply #12 on: 15 01 2016, 16:55:41 »
0.7.0.3 will be tomorrow as newest development version with my changes

ps
try to use other contact list. clist Nicer or clist modern.
this crash occured in standard clist std
« Last Edit: 15 01 2016, 17:05:00 by wsx22 »
 

Offline phatmr

Re: Sametime protocol
« Reply #13 on: 15 01 2016, 17:53:10 »
Hmm OK.

Tryed clist nicer and clist modern with plugin 0.7.0.2 - Miranda crashed too.

The Crashlog is the same

Exception: Access Violation at address 00000000121A6A34. Reading from address FFFFFFFF800323C8.
Stack Trace:
00000000121A6A34 (mir_app 0000000012140000): e:\sources\miranda_ng_compilation\src\mir_app\src\clc.cpp (100): ClcSettingChanged

The strange thing is that this crash dont happen with 0.7.0.0 u know?

I will test the new 0.7.0.3 when its up and post my results.

« Last Edit: 15 01 2016, 21:10:03 by phatmr »
 

Offline wsx22

Re: Sametime protocol
« Reply #14 on: 16 01 2016, 19:38:04 »
This crash occurs even if old version 0.7.0.0 connects properly (no server redirect) ?
Is "get contacts from server" option disabled as on screenshot ?