Eclipse Community Forums: Eclipse Platform

Home » Eclipse Projects » Eclipse Platform » 3.1 M4 & JSSE

Fri, 07 January 2005 08:12

Eclipse User

I have an application that uses SSL. It runs fine from the command line.
When I run it in eclipse, it bombs with the trace below. I'm using JDK
1.5.0_01.
Clearly, some library isn't being found. Anyone have any idea what it might
be?
Thanks much.

Steve Buroff

javax.net.ssl.SSLKeyException: RSA premaster secret error

at
com.sun.net.ssl.internal.ssl.PreMasterSecret.<init>(PreMasterSecret.java:86)

at
com.sun.net.ssl.internal.ssl.ClientHandshaker.serverHelloDon e(ClientHandshaker.java:514)

at
com.sun.net.ssl.internal.ssl.ClientHandshaker.processMessage (ClientHandshaker.java:160)

at com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Handshak er.java:495)

at
com.sun.net.ssl.internal.ssl.Handshaker.process_record(Hands haker.java:433)

at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSoc ketImpl.java:815)

at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHan dshake(SSLSocketImpl.java:1025)

at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SS LSocketImpl.java:1038)

at sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsCli ent.java:405)

at
sun.net.www.protocol.https.AbstractDelegateHttpsURLConnectio n.connect(AbstractDelegateHttpsURLConnection.java:170)

at
sun.net.www.protocol.http.HttpURLConnection.getOutputStream( HttpURLConnection.java:828)

at
sun.net.www.protocol.https.HttpsURLConnectionImpl.getOutputS tream(HttpsURLConnectionImpl.java:230)

at
com.omni.tradesports.comm.TradeSportsServer.sendRequest(Trad eSportsServer.java:445)

at
com.omni.tradesports.comm.TradeSportsServer.getLogin(TradeSp ortsServer.java:219)

at com.omni.tradesports.user.UserManager.login(UserManager.java :136)

at com.omni.tradesports.OmniTrade.<init>(OmniTrade.java:121)

at com.omni.tradesports.OmniTrade.main(OmniTrade.java:62)

Caused by: java.security.NoSuchAlgorithmException: Cannot find any provider
supporting RSA/ECB/PKCS1Padding

at javax.crypto.Cipher.getInstance(DashoA12275)

at com.sun.net.ssl.internal.ssl.JsseJce.getCipher(JsseJce.java: 90)

at com.sun.net.ssl.internal.ssl.RSACipher.<init>(RSACipher.java:35)

at com.sun.net.ssl.internal.ssl.RSACipher.getInstance(RSACipher .java:69)

at
com.sun.net.ssl.internal.ssl.PreMasterSecret.<init>(PreMasterSecret.java:82)

.... 16 more

Re: 3.1 M4 & JSSE [message #278822 is a reply to message #278800]

Fri, 07 January 2005 12:37

Eclipse User

Originally posted by: ya_xiang.hotmail.com

Hi,
please check out jdk docs
at guide/security directory
Java Secure Socket Extension(JSSE)
Reference Guide
for the java2 platform standard edition 5
at chapter TroubleShooting

Regards.

xiangya

"Steven Buroff" <sburoff@optonline.net> д

Re: 3.1 M4 & JSSE [message #278830 is a reply to message #278800]

Fri, 07 January 2005 17:39

Eclipse User

Originally posted by: ya_xiang.hotmail.com

Hi, maybe you can reference this:

If you are using JDK 1.4, or later, you must use the signed jar for the
provider and you must download the unrestricted policy files for the Sun JCE
if you want the provider to work properly. The policy files can be found at
the same place as the JDK download. Further information on this can be found
in the Sun documentation on the JCE. If you have not installed the policy
files you will see something like:
java.lang.SecurityException: Unsupported keysize or algorithm parameters
at javax.crypto.Cipher.init(DashoA6275)
Regards.xiangya"Steven Buroff" <sburoff@optonline.net> д

Re: 3.1 M4 & JSSE [message #278840 is a reply to message #278830]

Sat, 08 January 2005 08:54

Eclipse User

You missed the key fact: "the program runs correctly when executed from a
Windows cmd window". It only fails when run from Eclipse (an application
launcher). It must have something to do with how eclipse is setting up the
environment.

Steve
"xiangya" <ya_xiang@hotmail.com> wrote in message
news:crn337$p50$1@www.eclipse.org...
> Hi, maybe you can reference this:
>
> If you are using JDK 1.4, or later, you must use the signed jar for the
> provider and you must download the unrestricted policy files for the Sun
> JCE
> if you want the provider to work properly. The policy files can be found
> at
> the same place as the JDK download. Further information on this can be
> found
> in the Sun documentation on the JCE. If you have not installed the policy
> files you will see something like:
> java.lang.SecurityException: Unsupported keysize or algorithm parameters
> at javax.crypto.Cipher.init(DashoA6275)
> Regards.xiangya"Steven Buroff" <sburoff@optonline.net> д

Re: 3.1 M4 & JSSE [message #278850 is a reply to message #278840]

Sat, 08 January 2005 16:52

Eclipse User

Originally posted by: ya_xiang.hotmail.com

Hi,
1, set a new JRE to your jre home not jdk home.
2,configure your java application laucher item and set bootstrap entries to
null(remove default entries) and
3, run it, and you will see jre/bin/javaw.exe without bootstrap option and
just with only classpath option.

Addition, from stack trace message there should be an another message class
already in class path.

Regards.
xiangya

"Steven Buroff" <sburoff@optonline.net> д

Re: 3.1 M4 & JSSE [message #278864 is a reply to message #278850]

Sun, 09 January 2005 09:49

Eclipse User

That worked. Thank you very much for the help.

Steve

"xiangya" <ya_xiang@hotmail.com> wrote in message
news:crpkmp$4sp$1@www.eclipse.org...
> Hi,
> 1, set a new JRE to your jre home not jdk home.
> 2,configure your java application laucher item and set bootstrap entries
> to
> null(remove default entries) and
> 3, run it, and you will see jre/bin/javaw.exe without bootstrap option and
> just with only classpath option.
>
> Addition, from stack trace message there should be an another message
> class
> already in class path.
>
> Regards.
> xiangya
>
> "Steven Buroff" <sburoff@optonline.net> д

Previous Topic:	extension-point DocumentCreation
Next Topic:	3.1M4 build error

Goto Forum:

-=] Back to Top [=-

Current Time: Wed Nov 05 17:23:15 EST 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter