Last updated on NOVEMBER 04, 2016
Applies to:Oracle Tuxedo Jolt - Version 1.2 and later
Information in this document applies to any platform.
Information in this document applies to any platform
***Checked for relevance on 22-02-2011***
The Java client connects and disconnects from Tux on every logical function. A logical function may include 1 or more service calls. When we connect to Jolt through the jrly, every connection "eats up" a port. After about 100 ports have been lost we get a J_CHECKAUTH error. If we tmshutdown and tmboot the ports are recovered. If we connect directly to the JSL without the jrly, we don't see this problem.
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