powered by Jive Software

MSN NullPOinter Exception

HI! When i connect with a JID that have a registration on MSN gateway, i give this message on console and anything more happens. No buddy from MSN on my Buddy List.

Exception in thread “Thread-41” java.lang.NullPointerException

at java.util.regex.Matcher.getTextLength(Matcher.java:1127)

at java.util.regex.Matcher.reset(Matcher.java:284)

at java.util.regex.Matcher.(Matcher.java:205)

at java.util.regex.Pattern.matcher(Pattern.java:879)

at net.sf.jml.protocol.incoming.IncomingUSR$1.getPassportUrlSlow(IncomingUSR.java: 136)

at net.sf.jml.protocol.incoming.IncomingUSR$1.getPassportUrl(IncomingUSR.java:151)

at net.sf.jml.protocol.incoming.IncomingUSR$1.run(IncomingUSR.java:195)

Can anyone help me?

PS: sorry about my bad english!

nit wrote:

HI! When i connect with a JID that have a registration on MSN gateway, i give this message on console and anything more happens. No buddy from MSN on my Buddy List.

Exception in thread “Thread-41” java.lang.NullPointerException

at java.util.regex.Matcher.getTextLength(Matcher.java:1127)

at java.util.regex.Matcher.reset(Matcher.java:284)

at java.util.regex.Matcher.(Matcher.java:205)

at java.util.regex.Pattern.matcher(Pattern.java:879)

at net.sf.jml.protocol.incoming.IncomingUSR$1.getPassportUrlSlow(IncomingUSR.java: 136)

at net.sf.jml.protocol.incoming.IncomingUSR$1.getPassportUrl(IncomingUSR.java:151)

at net.sf.jml.protocol.incoming.IncomingUSR$1.run(IncomingUSR.java:195)

Can anyone help me?

PS: sorry about my bad english!

I believe someone else ran into this … I’‘m hoping they say something. =D I can only vaguely recall but there was a problem with using Gnu Java or an older JDK or something like that. The only other scenario I can think of that would cause that is if you had an empty password or username (which really -shouldn’'t -cause this, but that was a theory I had going for a bit)

here are some more logs after install wildfire 3.2.0 and gateway beta7. Still not working MSN for me:

2007.02.08 11:34:10 msn: Sending packet: …/logs/debug.log <==

2007.02.08 11:34:14 session 2 idle

I’‘m using Sun’'s JDK 1.5.09.

Thanks’’

As far as I know, Wildfire 3.2 requires Java 6!

anlumo wrote:

As far as I know, Wildfire 3.2 requires Java 6!

Actually it doesn’'t. But, using 1.6 does provide for a nice performance boost.

Hi!

I’'ve been upgraded JDK to Mustang, Wildfire to 3.2.2 and Gateway to beta8 and the same error occurs:

Exception in thread “Thread-73” java.lang.NullPointerException

at java.util.regex.Matcher.getTextLength(Matcher.java:1140)

at java.util.regex.Matcher.reset(Matcher.java:291)

at java.util.regex.Matcher.(Matcher.java:211)

at java.util.regex.Pattern.matcher(Pattern.java:885)

at net.sf.jml.protocol.incoming.IncomingUSR$1.getPassportUrlSlow(IncomingUSR.java: 136)

at net.sf.jml.protocol.incoming.IncomingUSR$1.getPassportUrl(IncomingUSR.java:151)

at net.sf.jml.protocol.incoming.IncomingUSR$1.run(IncomingUSR.java:195)

Any idea?

Forgive my ignorance, but what’'s Mustang? =)

Sorry!

Mustang is Java 6.

Hrm. Interesting. I’'m running java 6 and not seeing this with MSN/JML. Was it working before you upgraded?

Edit: reread your thing, looks like it was busted before too. Hrm.

Message was edited by: jadestorm

Ok, looking over JML’‘s code, it looks like … well first off JML’‘s code ought to be checking to make sure it got a successful connection. I’‘m going to file a bug report for myself on that. That said, it’'s trying to connect to:

https://nexus.passport.com/rdr/pprdr.asp

And I believe it’‘s getting a weird response back. Now why that is occuring I am not sure yet, but will look into it. The thing is, the interaction with MSN hasn’'t even gotten to a point where it knows anything about -you- yet, so it sounds like more of a connection between you and their nexus server issue. '‘cause the way it works is literally just an https connection and a look at the headers returned to figure out where to connect to. Unfortunately this isn’'t something I can duplicate on my end so I may build you a custom debugging version that can tell me more.

In my case, this error was caused by trying to run the gateway on a server inside a firewall.

Fixed it by adding java system properties on wildfire (erm openfire) startup:

-Dhttps.proxySet=true

-Dhttps.proxyHost=mycompanyproxyserver.org

-Dhttps.proxyPort=80

-Dhttp.proxySet=true

-Dhttp.proxyHost=mycompanyproxyserver.org

-Dhttp.proxyPort=80