Discussions
Categories
- 17.9K All Categories
- 3.4K Industry Applications
- 3.4K Intelligent Advisor
- 75 Insurance
- 537.7K On-Premises Infrastructure
- 138.7K Analytics Software
- 38.6K Application Development Software
- 6.1K Cloud Platform
- 109.6K Database Software
- 17.6K Enterprise Manager
- 8.8K Hardware
- 71.3K Infrastructure Software
- 105.4K Integration
- 41.6K Security Software
OAS 10.1.3.1 - SSL causes http sessions to expire - conn. forcibly closed

518063
Member Posts: 31
Hi,
I have an installation of my Java application on an Oracle Application Server 10.1.3.1 at a client site. The application was deployed to an oc4j instance without any problems. The client then configured SSL on that server. The client followed directions from http://download-west.oracle.com/docs/cd/B32110_01/web.1013/b28957/configssl.htm
under the paragraph "Using SSL with Standalone OC4J".
After enabling SSL, the application starts, but after user clicks a few buttons, especially after opening a popup, he gets "Session has expired" message. in the browser window. In the log we see the SSL exception saying the connection has been forcibly closed. Session timout is set 1200...
Did our client miss some important configuration step? We know our application works fine with JBoss and SSL, what could it be?
Any help will be greatly appreciated as this is a production issue.
Thanks in advance.
Nadia
Edited by: user515060 on Jul 30, 2009 9:17 PM
I have an installation of my Java application on an Oracle Application Server 10.1.3.1 at a client site. The application was deployed to an oc4j instance without any problems. The client then configured SSL on that server. The client followed directions from http://download-west.oracle.com/docs/cd/B32110_01/web.1013/b28957/configssl.htm
under the paragraph "Using SSL with Standalone OC4J".
After enabling SSL, the application starts, but after user clicks a few buttons, especially after opening a popup, he gets "Session has expired" message. in the browser window. In the log we see the SSL exception saying the connection has been forcibly closed. Session timout is set 1200...
Did our client miss some important configuration step? We know our application works fine with JBoss and SSL, what could it be?
Any help will be greatly appreciated as this is a production issue.
Thanks in advance.
Nadia
Edited by: user515060 on Jul 30, 2009 9:17 PM
This discussion has been closed.