Quantcast
Channel: Ignite Realtime : Discussion List - All Communities
Viewing all articles
Browse latest Browse all 10742

Username and JID contains only numbers.

$
0
0

Hi,

 

I am using Openfire 3.8.2 and jabber library with my C# client.

When I am connecting as username which contains only numbers (e.g. username is "1" and jid is "1@domain") I am getting "Unexpected exception".

 

Short log from my app output:

 

RECV: connected successfully

...

...

SEND: <iq id="JN_1" type="set" to="m1-pc"><bind xmlns="urn:ietf:params:xml:ns:xmpp-bind"><resource>TrainingRoom</resource></bin d></iq>

SEND: <iq id="JN_2" type="set" to="m1-pc"><session xmlns="urn:ietf:params:xml:ns:xmpp-session" /></iq>

RECV PRT: <iq from="m1-pc" to="m1-pc/ab3c9b45" type="result" id="JN_1"><binA first chance exception of type 'System.ArgumentOutOfRangeException' occurred in mscorlib.dll

A first chance exception of type 'System.Exception' occurred in jabber-net.dll

Close

d xmlns="urn:ietf:params:xml:ns:xmpp-bind"><jid>1@m1-pc/TrainingRoom</jid></bind> </iq>

RECV: authed successfully

auth

SEND: <iq id="JN_3" type="get"><query xmlns="jabber:iq:roster" /></iq>

RECV PRT: <iq from="m1-pc/" to="1@m1-pc/TrainingRoom" type="result" id="JN_2" />

SEND: <presence><status>online</status><priority>0</priority></presence>

RECV PRT: <iq to="1@m1-pc/TrainingRoom" type="result" id="JN_3"><query xmlns="jabber:iq:roster"><item name="10" jid="10@m1-pc" subscription="both"><group>People</group></item></query></iq>

RECV: ERROR: Unexpected exception

 

This exception I am getting always after sending the presence.

 

I know my question is not so clear but when I am using username like e.g. TestUsername1 everythink works perfect.

But today, when I started using usernames containing only numbers (which Is a must for me) I am getting that exception.

 

Mayby somebody had similar issue.

 

Thanks

 

 

 

Message: "A first chance exception of type 'System.ArgumentOutOfRangeException' occurred in mscorlib.dll"

I am getting all the time, so I don't think it is an issue. It works when Username is set to e.g. TestUsername1


Viewing all articles
Browse latest Browse all 10742

Trending Articles