2 Intern

 • 

212 Posts

November 3rd, 2009 10:00

Hmm, this got resolved the moment I switched to JDK 1.6.

I was using JDK 1.5 before this.

Have a feeling that some Java library classes being used in the signature generation logic have changed behavior from 1.5 -> 1.6

Thanks,

Aashish

281 Posts

November 16th, 2009 07:00

Hi All,

I tested with JDK 1.5.0_20 on both Mac OSX and Vista and was unable to reproduce this problem.  Can I get some more information?  Atmos OnLine or Atmos On Premise?  Version? JDK version?  A wireshark trace would be helpful too.

Thanks,

Jason

2 Intern

 • 

212 Posts

November 16th, 2009 15:00

Hi Jason,

Its

Java: Sun JDK 1.5.0_06

Atmos: Atmos onLine

OS: Windows Server 2003 SP2

Let me see if I can pull up a wireshark trace.

Thanks,

Aashish

281 Posts

November 17th, 2009 08:00

Would it be possible to upgrade your JDK?  That version is extremely old and has many security issues as well.  JDK 1.5 has also reached end-of-support status from Sun, so it is highly recommended that you consider moving to JDK6: http://java.sun.com/j2se/1.5/

2 Intern

 • 

212 Posts

November 17th, 2009 10:00

Hi Jason,

I've already upgraded. Was using 1.5 for some other apps.

However, its not clear from the Java Binding download page that JDK 1.6 is required (or preferred). As a result, I spent considerable time trying to debug my code before switching to 1.6. Might benefit future developers.

Thanks,

Aashish

No Events found!

Top