Oracle Transportation Management - Version 6.2.6 and later Information in this document applies to any platform.
OTM Production instance suddenly became slowThe login page was appearing, but the users were experiencing extreme slowness while logging-in to the Application. At this point of time, the production Database was accessible as usual through SQL Developer/TOAD. There was no resource intensive activity going on at that moment. The message processing via the Integration also began to slow down.
After sometime, the users were not able to login to the Application itself. The login screen was hanging and the message processing became further slow. We could see that the transmissions were moving from DEFAULT Appserver to the FAILOVER Appserver. On the FAILOVER Appserver also the message processing was extremely slow. No object locks were observed at the Application level, and other servlets like Mediator, ProcessWalker, ObjectLock were not accessible for any kind of analysis. The Database was still accessible through SQL Developer/TOAD.
It could be seen that transmissions were toggling between the DEFAULT Appserver and the FAILOVER Appserver. Overall, the transmissions processing had become extremely slow. When the message processing via Integration had almost stopped, the Integration had to be shut down. Connection errors were seen in the Appserver logs
After the bounce, things were back to normal i.e. login to the Application, message processing etc. started to happen as usual.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!