AccountManager Connection Problem

[BARRYC16]

Hi,

I am using the old sdk java server API code, trying to create a room.

I get an error when I try to construct the AccountManager class in the old server api file AFCS.java. When I turn on DEBUG here is what the log shows...

http_get: http://connectnow.acrobat.com/xoomxo?mode=xml&accountonly=true&;

{}

Redirecting to https://na2.connectnow.acrobat.com/xoomxo?mode=xml&accountonly=true&;

http_get: https://na2.connectnow.acrobat.com/xoomxo?mode=xml&accountonly=true&;

{}

Content-Type: text/xml;charset=UTF-8

Content-Length: 177

#

# An unexpected error has been detected by HotSpot Virtual Machine:

#

#  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x6d641e39, pid=5948, tid=5660

#

# Java VM: Java HotSpot(TM) Client VM (1.5.0_20-b02 mixed mode)

# Problematic frame:

# V  [jvm.dll+0x1e39]

#

# An error report file with more information is saved as hs_err_pid5948.log

#

# If you would like to submit a bug report, please visit:

#   http://java.sun.com/webapps/bugreport/crash.jsp

#

This was working about a week ago. Is is possible this is a problem with some of the old server API code or does it look like a bug?

Thanks,

Barry

[Raff_]

Wow! That's a new one!

So, it's your jvm crashing that way ?

I don't think it's a problem of old code vs. New code. That part is

exactly the same.

Can you quickly try to run the new jar ? Java -jar AFCS.jar, and then

add the correct parameters to access your account.

Sent from my iPhone

[BARRYC16]

Hi Raff,

I tested it with AFCS.jar outside of eclipse with JDK 1.5.0_20 and it worked fine.

However, I was able to reproduce it again inside eclipse and got the same error repeatedly.

I changed my eclipse project to use jdk 1.6 and it worked fine.

Also, just for curiosity I switched back to JDK 1.5.0_20 and now it also works fine with this JDK.

My conclusion is that it must have been some strange problem with eclipse. This project hasn't changed and has been working fine for a couple of months and I only started getting that error last night.

If I see it again I'll investigate more and update this post.

Thanks,

Barry