user6885664 wrote:Together those two make it unlikely that it has anything to do with code or VM.
...these 3 clients were sending huge traffic to our service,
while the remaining clients (25) were able to successfully send transactions (low volume transactions).
Any idea what can be the cause of it, the clients are authenticated using SSL Client authenticationI would suppose strongly that between 1.4 and 1.6 something changed in SSL in the API. For example didn't they fix the security bug that showed up in the SSL protocol specification?
user6885664 wrote:That has nothing to do with your original post.
I have noticed that when the web service get the EJBObject of session bean from deployed in application tier then the web service is encoding the EJBObject using sun.misc.BASE64Encoder and then decoding it back to sun.misc.BASE64Decoder before actual EJB method call. I have found that sun.* classes are not guarantee to work on all platforms of Java (http://www.oracle.com/technetwork/java/faq-sun-packages-142232.html).
So can someone tell me that sun.misc.BASE64Encoder and decoder can work without issues on Windows Server 2008 Standard Edition with JDK 1.6.0_29 x64?Yes.