Idle-Time-Maximum Exceeding 2147483 Does Not Take Effect After Restarting Server
Last updated on DECEMBER 11, 2017
Applies to:Oracle WebLogic Server - Version 10.3.6 and later
Information in this document applies to any platform.
If idle-time-maximum is set higher than 2147483, it does not take effect after restarting the server. WebLogic Server continues to use the default value of 60 instead.
The symptoms can be reproduced as follows.
- Create messaging bridge instances as described at: http://docs.oracle.com/cd/E16764_01/apirefs.1111/e13952/taskhelp/bridge/bridge_instance/CreateJMSBridgeInstance.html
- Change the value of idle-time-maximum from 60 to 2147484. The following message is printed in server log.
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