Cannot Start Application Server After Applying an RU on OTM 5.5 CU5 With OAS

(Doc ID 759528.1)

Last updated on NOVEMBER 03, 2015

Applies to:

Oracle Transportation Management - Version 5.5.05 to 5.5.05.07 [Release 5.5]
Information in this document applies to any platform.
***Checked for relevance on 14-Mar-2011***
***Checked for relevance on 24-Oct-2012***


Symptoms

-- Problem Statement:
After upgrading to CU5 or any RU of CU5 from a previous release, ( i.e. Cu3 or CU4), there is a problem with  Oracle Application Server (OAS) starting. The error is:

INFO | jvm 1 | 2008/12/18 09:45:33 | 08/12/18 09:45:33 -- OTM Startup: preDeploy
INFO | jvm 1 | 2008/12/18 09:45:33 | 08/12/18 09:45:33 -- OTM Startup: initializing realm
INFO | jvm 1 | 2008/12/18 09:45:34 | 08/12/18 09:45:34 java.sql.SQLException: Protocol violation
INFO | jvm 1 | 2008/12/18 09:45:34 |
INFO | jvm 1 | 2008/12/18 09:45:34 | 08/12/18 09:45:34 java.sql.SQLException: Protocol violation
INFO | jvm 1 | 2008/12/18 09:45:34 | 08/12/18 09:45:34 at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
INFO | jvm 1 | 2008/12/18 09:45:34 | 08/12/18 09:45:34 at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:146)
INFO | jvm 1 | 2008/12/18 09:45:34 | 08/12/18 09:45:34 at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:208)
INFO | jvm 1 | 2008/12/18 09:45:34 | 08/12/18 09:45:34 at oracle.jdbc.driver.T4C7Ocommoncall.receive(T4C7Ocommoncall.java:150)
INFO | jvm 1 | 2008/12/18 09:45:34 | 08/12/18 09:45:34 at oracle.jdbc.driver.T4CConnection.logoff(T4CConnection.java:465)
INFO | jvm 1 | 2008/12/18 09:45:34 | 08/12/18 09:45:34 at oracle.jdbc.driver.PhysicalConnection.close(PhysicalConnection.java:1521)
INFO | jvm 1 | 2008/12/18 09:45:34 | 08/12/18 09:45:34 at glog.util.datasource.DataSource.release(DataSource.java:173)
INFO | jvm 1 | 2008/12/18 09:45:34 | 08/12/18 09:45:34 at glog.util.jdbc.noserver.T2SharedConnection$ReferencedConnection.release(T2SharedConnection.java:320)
INFO | jvm 1 | 2008/12/18 09:45:34 | 08/12/18 09:45:34 at glog.util.jdbc.noserver.T2SharedConnection.close(T2SharedConnection.java:55)
INFO | jvm 1 | 2008/12/18 09:45:34 | 08/12/18 09:45:34 at glog.database.security.dbrealm.RdbmsRealm.queryAll(RdbmsRealm.java:210)
INFO | jvm 1 | 2008/12/18 09:45:34 | 08/12/18 09:45:34 at glog.database.security.dbrealm.RdbmsRealm.getKnownGroups(RdbmsRealm.java:1041)
INFO | jvm 1 | 2008/12/18 09:45:34 | 08/12/18 09:45:34 at glog.database.security.dbrealm.RdbmsRealm.getKnownGroups(RdbmsRealm.java:1053)
INFO | jvm 1 | 2008/12/18 09:45:34 | 08/12/18 09:45:34 at glog.database.security.dbrealm.CachingRealm.readKnownGroups(CachingRealm.java:318)
INFO | jvm 1 | 2008/12/18 09:45:34 | 08/12/18 09:45:34 at glog.database.security.dbrealm.CachingRealm.initCaches(CachingRealm.java:186)
INFO | jvm 1 | 2008/12/18 09:45:34 | 08/12/18 09:45:34 at glog.database.security.dbrealm.CachingRealm.<init>(CachingRealm.java:134)
INFO | jvm 1 | 2008/12/18 09:45:34 | 08/12/18 09:45:34 at glog.database.security.dbrealm.CachingRealm.initialize(CachingRealm.java:122)
INFO | jvm 1 | 2008/12/18 09:45:34 | 08/12/18 09:45:34 at glog.util.j2ee.startup.OASStartup.startupRealm(OASStartup.java:43)
INFO | jvm 1 | 2008/12/18 09:45:34 | 08/12/18 09:45:34 at glog.util.j2ee.startup.OASStartup.onEvent(OASStartup.java:28)
INFO | jvm 1 | 2008/12/18 09:45:34 | 08/12/18 09:45:34 at glog.util.j2ee.startup.OASStartupShutdownManager.preDeploy(OASStartupShutdownManager.java:19)
INFO | jvm 1 | 2008/12/18 09:45:34 | 08/12/18 09:45:34 at com.evermind.util.ClassDescriptor.executeStartupClass(ClassDescriptor.java:73)
INFO | jvm 1 | 2008/12/18 09:45:34 | 08/12/18 09:45:34 at com.evermind.server.ApplicationServer.execStartupClassesPreDeploy(ApplicationServer.java:1408)
INFO | jvm 1 | 2008/12/18 09:45:34 | 08/12/18 09:45:34 at com.evermind.server.ApplicationServer.setConfig(ApplicationServer.java:1009)
INFO | jvm 1 | 2008/12/18 09:45:34 | 08/12/18 09:45:34 at com.evermind.server.ApplicationServerLauncher.run(ApplicationServerLauncher.java:131)
INFO | jvm 1 | 2008/12/18 09:45:34 | 08/12/18 09:45:34 at java.lang.Thread.run(Thread.java:534)
INFO | jvm 1 | 2008/12/18 09:45:34 | 08/12/18 09:45:34 java.sql.SQLException: Protocol violation


INFO | jvm 1 | 2008/12/18 09:45:34 | 08/12/18 09:45:34 Fatal Error: Realm Initialization failed!!
INFO | jvm 1 | 2008/12/18 09:45:35 | 08/12/18 09:45:34 Shutting down OC4J...
INFO | jvm 1 | 2008/12/18 09:45:36 | 08/12/18 09:45:36 Error: Could not connect to the remote server. Please check if the server is down or the client is using invalid host, ORMI port or password to connect: Connection refused

-- Steps To Reproduce:

1. Upgrade OTM  to CU5 or any RU on CU5 from a prior release of OTM 5.5 ( i.e. CU3 or CU4)  on an instance using the Oracle Application Server ( OAS)

2. Re-start the web and application servers as required and see that the application server will not start and error is found in the log


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