My Oracle Support Banner

SQL Developer Web Times Out On DBCS / OCI - Classic With VPN (Doc ID 2498051.1)

Last updated on JANUARY 23, 2019

Applies to:

Oracle Database Cloud Service - Version N/A and later
Information in this document applies to any platform.

Symptoms


A SQL Develper Web (SDW) session gets timed out even though the customer is actively running queries / doing other work. In the middle of an active session,a popup window with this message:

'Your session has expired. Please sign in again.'

This occurs on a system that is using Corente / VPN.

The ords.log in /u01/app/oracle/product/ords/log shows no error at the time of the timeout.

When clicking OK on the expire message, this was written to the log:

Oct 31, 2018 8:22:07 AM
WARNING: Error occurred when sending response for:
404 GET https://fdsm-cdbdfm.anthem.com/ords/PDB1/pdbadmin/sign-in/css/signIn.css
Oct 31, 2018 8:22:07 AM
WARNING: null
java.nio.channels.ClosedChannelException
  at org.eclipse.jetty.util.IteratingCallback.close(IteratingCallback.java:427)
  at org.eclipse.jetty.server.HttpConnection.onClose(HttpConnection.java:492)
  at org.eclipse.jetty.io.ssl.SslConnection.onClose(SslConnection.java:255)
  at org.eclipse.jetty.io.SelectorManager.connectionClosed(SelectorManager.java:375)
  at org.eclipse.jetty.io.ManagedSelector$DestroyEndPoint.run(ManagedSelector.java:814)
  at org.eclipse.jetty.io.ManagedSelector$SelectorProducer.nextAction(ManagedSelector.java:328)
  at org.eclipse.jetty.io.ManagedSelector$SelectorProducer.produce(ManagedSelector.java:293)
  at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:179)
...


ORDS version: 18.1
SDW Version: 18.1


Sequence of events:
* I connected at around 1PM PT. I ran several queries.
* The last query ran at 1:58PM PT.
* When I tried to run a query at 2:05PM PT I got the message saying my session was terminated.

According to development, the timeout should not have occurred.
Confirmed through internal testing. The same series of events prevent the session timeout, so something in the customer environment is causing a hard stop after 1 hour regardless of activity in the session.

Other information
_________________
* Customer is running through VPN / Corrente
* Customer tested through SQL Developer (ssh tunnel), and the error does not occur.
  When trying to create an SSH tunnel for testing using MabaXterm rather than putty, he gets the error:


Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.