Unable to Access to Java Client Over T3s After Configuring SSL Error:"The server invalid or unavailable." (Doc ID 2127460.1)

Last updated on JUNE 09, 2016

Applies to:

Oracle Agile PLM Framework - Version 9.3.4.0 and later
Information in this document applies to any platform.

Symptoms

After configuring SSL to Agile, cannot login to Java Client with below error:

Error
"The server invalid or unavailable."

After enabling Java console (Goto Control Panel | Java | Advanced Tab | Console | Enable Show Console), can see below stack trace in the Java Console:
javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3s://agileserver:7002: Destination XXX.XXX.X.XXX, 7002 unreachable; nested exception is:
javax.net.ssl.SSLHandshakeException: General SSLEngine problem; No available router to destination]
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:40)
at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:808)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:363)
at weblogic.jndi.Environment.getContext(Environment.java:319)
at weblogic.jndi.Environment.getContext(Environment.java:288)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
at javax.naming.spi.NamingManager.getInitialContext(Unknown Source)
at javax.naming.InitialContext.getDefaultInitCtx(Unknown Source)
at javax.naming.InitialContext.init(Unknown Source)
at javax.naming.InitialContext.<init>(Unknown Source)
at com.agile.ui.java.security.weblogic.WeblogicSecurityAdapter.login(WeblogicSecurityAdapter.java:69)
at com.agile.ui.java.data.pc.PCEJBUtil.<init>(PCEJBUtil.java:276)
at com.agile.ui.java.data.pc.PCEJBUtil.createInstance(PCEJBUtil.java:238)
at com.agile.ui.java.data.pc.PCEJBConnection.login(PCEJBConnection.java:905)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.agile.ui.java.data.pc.PCInterfaceFactory$1.invoke(PCInterfaceFactory.java:27)
at com.sun.proxy.$Proxy1.login(Unknown Source)
at com.agile.ui.pcclient.CommandLogin.doExecute(CommandLogin.java:118)
at com.agile.ui.java.command.CommandManager$4.run(CommandManager.java:301)
at foxtrot.AbstractWorkerThread$2.run(AbstractWorkerThread.java:49)
at java.security.AccessController.doPrivileged(Native Method)
at foxtrot.AbstractWorkerThread.runTask(AbstractWorkerThread.java:45)
at foxtrot.workers.DefaultWorkerThread.run(DefaultWorkerThread.java:153)
at java.lang.Thread.run(Unknown Source)

 

Facts

- jndiurl.properties, agile.properties, ext.jnlp, pcclient.jnlp are updated appropriately as explained in "Agile Product Lifecycle Management Security Guide" Chapter "Configuring SSL" section "Configuring SSL in the Agile PLM Application"

- Can access to https://agileserver:7002/console (7002 is SSL port in this case) from the client machine

Steps to Reproduce

1. Create SSL Keystores and Truststore
2. Configure SSL on WebLogic Server
3. Configure SSL in the Agile PLM Application
4. Secure Agile PLM File Manager(s) Using SSL
5. Login to Java Client



Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms