Class NettyConfigPropertyNames
java.lang.Object
org.apache.synapse.transport.netty.config.NettyConfigPropertyNames
This class contains the names of Netty transport related configuration properties.
-
Field Summary
FieldsModifier and TypeFieldDescriptionstatic final Stringstatic final Stringstatic final Stringstatic final StringMax active connections per route(host:port).static final StringMaximum number of idle connections allowed per pool.static final StringMaximum amount of time, the client should wait for an idle connection before it sends an error when the pool is exhausted.static final StringDefines whether HTTP keep-alive is disabled.static final Stringstatic final StringCheck for invalid json message by parsing the input message.static final Stringstatic final StringValidate the bad formed xml message by building the whole xml document.static final Stringstatic final Stringstatic final StringDefines whether ESB needs to preserve the original Http header.static final StringDefines whether ESB needs to preserve the original Http header.static final Stringstatic final Stringstatic final Stringstatic final Stringstatic final Stringstatic final Stringstatic final Stringstatic final Stringstatic final Stringstatic final Stringstatic final StringDefines whether ESB needs to preserve the original Server header.static final Stringstatic final StringDefines whether ESB needs to preserve the original User-Agent header.static final StringDefines the length of the queue that is used to hold Runnable tasks to be executed by the worker pool.static final StringDefines the core size (number of threads) of the worker thread pool.static final StringDefines the maximum size (number of threads) of the worker thread pool.static final StringDefines the keep-alive time for extra threads in the worker pool. -
Constructor Summary
Constructors -
Method Summary
-
Field Details
-
WORKER_POOL_SIZE_CORE
Defines the core size (number of threads) of the worker thread pool.- See Also:
-
WORKER_POOL_SIZE_MAX
Defines the maximum size (number of threads) of the worker thread pool.- See Also:
-
WORKER_THREAD_KEEP_ALIVE_SEC
Defines the keep-alive time for extra threads in the worker pool.- See Also:
-
WORKER_POOL_QUEUE_LENGTH
Defines the length of the queue that is used to hold Runnable tasks to be executed by the worker pool.- See Also:
-
USER_AGENT_HEADER_PRESERVE
Defines whether ESB needs to preserve the original User-Agent header.- See Also:
-
SERVER_HEADER_PRESERVE
Defines whether ESB needs to preserve the original Server header.- See Also:
-
HTTP_RESPONSE_HEADERS_PRESERVE
Defines whether ESB needs to preserve the original Http header.- See Also:
-
HTTP_HEADERS_PRESERVE
Defines whether ESB needs to preserve the original Http header.- See Also:
-
DISABLE_KEEPALIVE
Defines whether HTTP keep-alive is disabled.- See Also:
-
TRANSPORT_LISTENER_SHUTDOWN_WAIT_TIME_SEC
- See Also:
-
FORCE_XML_MESSAGE_VALIDATION
Validate the bad formed xml message by building the whole xml document.- See Also:
-
FORCE_JSON_MESSAGE_VALIDATION
Check for invalid json message by parsing the input message.- See Also:
-
HTTP_GET_REQUEST_PROCESSOR
- See Also:
-
HTTP_SERVER_HOSTNAME
- See Also:
-
HTTP_TRANSPORT_MEDIATION_INTERCEPTOR
- See Also:
-
HTTP_BLOCK_SERVICE_LIST
- See Also:
-
FORCE_MESSAGE_BUILDER
- See Also:
-
ALLOWED_RESPONSE_PROPERTIES
- See Also:
-
REQUEST_LIMIT_VALIDATION
- See Also:
-
MAX_STATUS_LINE_LENGTH
- See Also:
-
MAX_HEADER_SIZE
- See Also:
-
MAX_ENTITY_BODY_SIZE
- See Also:
-
CLIENT_REQUEST_LIMIT_VALIDATION
- See Also:
-
MAX_CLIENT_REQUEST_STATUS_LINE_LENGTH
- See Also:
-
MAX_CLIENT_REQUEST_HEADER_SIZE
- See Also:
-
MAX_CLIENT_REQUEST_ENTITY_BODY_SIZE
- See Also:
-
HTTP_SOCKET_TIMEOUT
- See Also:
-
ENABLE_CUSTOM_CONNECTION_POOL_CONFIG
- See Also:
-
CONNECTION_POOLING_MAX_ACTIVE_CONNECTIONS
Max active connections per route(host:port). Default value is -1 which indicates unlimited.- See Also:
-
CONNECTION_POOLING_MAX_IDLE_CONNECTIONS
Maximum number of idle connections allowed per pool.- See Also:
-
CONNECTION_POOLING_WAIT_TIME
Maximum amount of time, the client should wait for an idle connection before it sends an error when the pool is exhausted.- See Also:
-
CLIENT_ENDPOINT_SOCKET_TIMEOUT
- See Also:
-
-
Constructor Details
-
NettyConfigPropertyNames
public NettyConfigPropertyNames()
-