[joe-wyattmutualofomaha-com]

A new installation of Portal 9 with update of JDK to IBM JDK 8.0.6.10 fails on start up under MyEclipse with this message in portal log:

SSLHandshakeE E CWSSL0008E: Unable to initialize SSL connection. Unauthorized access was denied or security settings have expired. Exception is javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection?
at com.ibm.jsse2.c.a(c.java:106)
at com.ibm.jsse2.as.a(as.java:452)
at com.ibm.jsse2.as.unwrap(as.java:469)
at javax.net.ssl.SSLEngine.unwrap(SSLEngine.java:25)
at com.ibm.ws.ssl.channel.impl.SSLConnectionLink.readyInbound(SSLConnectionLink.java:586)
at com.ibm.ws.ssl.channel.impl.SSLConnectionLink.ready(SSLConnectionLink.java:346)
at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminators(NewConnectionInitialReadCallback.java:214)
at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:113)
at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:175)
at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138)
at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)
at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775)
at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1909)

This occurs on versions 2019 and 2018.12.0 CI of MyEclipse.

The portal server works without issue outside of MyEclipse.

Is there a configuration issue or a JDK issue with MyEclipse?

[Aaron Lara]

Hello Joe!

I’m sorry that you are running into this issue. This can happen due to the JDK the IDE is using. If you wish to change the JDK MyEclipse launches with, you can edit the myeclipse.ini file located at the root of the installation directory by adding this at the top:

-vm
/path/to/your/javaw.exe

It might work if you point it to your IBM JDK 8, but I haven’t tried it myself.

Do you happen which version of java your MyEclipse install is currently using?

Cheers!
Aaron Lara

• This reply was modified 4 years, 3 months ago by Aaron Lara.

[joe-wyattmutualofomaha-com]

This has been attempted with similar results. Other ideas?

[Brian Fernandes]

Joe,

Apologies for the delayed response.

We ran a few tests here and found the connection to be working fine – we tested WPS 9.0.0.2 which started with 8.0.3.20.

1) Was the connection working fine earlier and stopped on making some changes? You mentioned this was a new install but there was a JDK update. Did you happen to test with an earlier JDK, or do you have it still working with an earlier JDK on another system?

At our end, we can look into now trying an update to JDK 8.0.6.10.

2) Can you confirm that when the server is started externally, it’s using the same JRE version that’s configured in the portal server connector’s settings within MyEclipse?

3) Can you tell me what version of WPS you’re using exactly?

4) When the portal server is started externally, MyEclipse should pick it up within the servers view and show an updated “Started” state. Does this happen when you start externally?

[joe-wyattmutualofomaha-com]

We’ve run some tests as well and found that the server IS starting under the IDE. The SSL message appears to be a red herring. It seems that the issue is the IDE believes the server to be stopped.

[Brian Fernandes]

Good, that does give us some additional information – MyEclipse is able to successfully send the start command/request, but is then unable to establish a connection with the server for updates on the server state. Consequently you won’t be able to do much with the server in MyEclipse, as you no doubt already know.

Can you please answer the other questions (#1 – #3) in my previous post? That will help us hopefully replicate locally and work towards a fix.

[Brian Fernandes]

Joe,

Another factor to consider is that if the server is taking longer than usual to start, the timeout set may be too short. I believe the time out is 400 seconds by default. You could consider increasing that value to see if that makes a difference. The log files may give you a better idea of how long the server is actually taking to start as well.

[Brian Fernandes]

Joe,

Wanted to check in with you and your team – were you able to resolve this problem?

[Author]

Posts