XMPP transports ( Yahoo ) providing wrong credentials for yahoo login ( IM Spark Client ) , response is not getting from Server , moreover it's taking long time for responding .
When we are entering wrong credentials for yahoo login, we are not getting
response from the sever ( IM Client Spark ). ( I.e i enabled Smack Debugger
mode in IMClient Spark to observe Raw Sent and Receive Packets ) . however
in case of gmail login and msn login , if we provide invalid credentials then
proper response is coming from server.
and moreover , when we entering wrong credentials for yahoo login using (
IMClient Spark ) , it 's take long time for responding.
kraken plugin for java
Hehe that error indicates that you've failed to log in so many times that Yahoo blocked you. I hope that's a temporary block.
Either way, currently, I can reproduce the problem, so I should have what I need to track it down.
Hi Daniel ,
below is the error log for yahoo :
Error Log : for yahoo when we are entering invalid credentials.
org.openymsg.network.LoginRefusedException: Login locked: Too many failed login attempts
Never logged in, sessionStatus is: FAILED
Exception in thread "Thread-153" java.lang.ClassCastException: org.openymsg.network.LoginRefusedException cannot be cast to org.openymsg.network.AccountLockedException
error during the dispatch of event: FireEvent [Exception: message="Source: InputThread" type=org.openymsg.network.LoginRefusedException: Login locked: Too many failed login attempts X_EXCEPTION]
java.lang.ClassCastException: org.openymsg.network.LoginRefusedException cannot be cast to org.openymsg.network.AccountLockedException
moreover for this issue, when we are entering correct login credentials ( especially for Yahoo Client ).
it takes long time for responding to get login, however we are able to login successfully ,so is there any problem with openfire server regarding responding to server bit slow. ( this is major cause as per my client requirement).
hope you can rectify this problem also if possible, i am really sorry for making you trouble.
hope you can consider my request.
Hrm. For whatever reason the exception was being thrown in a place where it did not used to get thrown. Updates have been made to correct for that HOWEVER there is still something going wrong.
If an attempt was made to log in that failed, your session gets "stuck" in some way shape or form. The only cure is a restart of Openfire at present. So that will need to be tracked down next. I am considering it a part of this issue though.
Probably won't have any more time to work on this today – have a lot to do for my actual job. And my free time will be lacking this evening. Perhaps tomorrow.
Apparently this is not fixed yet for Yahoo. Will do some testing. I'm flagging this as a blocker for 1.1.3 given that it could cause serious issues for folk.