Hi Roland I tried it with no success. renaming/removing IBMJSSE.. nothing seems to fix the issue. The task from the article sounds simple and straight, but still it dosent fix my problem.
good sign is that, now I am getting com.sun.net.ssl.internal.ssl.SSLSocketFactoryImpl as the default socket. I created my own trustmanager and keystore with my own certs... yet getting the exception. tyring to resolve it. Will let u know if somehow I get it to work. if something comesup please let me know. Thanks Regards NRR --- Roland Weber <[EMAIL PROTECTED]> wrote: > Hello NR, > > I have not yet found the time to run a test program. > But I have found this posting on developerWorks, > which seems to relate to your problems: > > http://www-106.ibm.com/developerworks/forums/dw_thread.jsp?message=49752&cat=10&thread=10122&forum=178#49752 > > Abstract: > There is an intended restriction concerning > alternate > SSL implementations in the exportable JDK. This > results in problems if the IBM JSSE is loaded > before the Sun JSSE during startup of the JDK. > You'll have to relocate the IBM JSSE jar in order > to make sure it is loaded second, and you can't > remove it completely because WAS/WSAD won't > work without it. > > regards, > Roland > __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
