Language:
Format:

Appendix A. Reference Material

A.1. JacORB Subsystem Migration Operation Warnings

The migrate operation is not able to process all resources and attributes. The following table lists some of the warnings you might see when you run either the migrate or describe-migration operation for the jacorb subsystem.

Note

If you see "Could not migrate" or "Can not migrate" entries in the output of the migrate operation, this indicates the migration of the server configuration completed successfully but it was not able to automatically migrate all of the elements and attributes. You must follow the suggestions provided by the "migration-warnings" to modify those configurations.

Warning Message	What It Means / How to Fix It
The `iiop` migration can be performed when the server is in `admin-only` mode	The `migrate` operation requires starting the server in `admin-only` mode, which is done by adding `--start-mode=admin-only` to the server start command: $ EAP_HOME/bin/standalone.sh --start-mode=admin-only
Properties X cannot be emulated using OpenJDK ORB and are not supported	Configuration of the specified property is not supported and is not included in the new `iiop-openjdk` subsystem configuration. The behavior exhibited by this property in the previous release of JBoss EAP is not migrated and the administrator must verify that the new `iiop-openjdk` subsystem in JBoss EAP 7 is able to operate correctly without that behavior. Unsupported properties include: `cache-poa-names`, `cache-typecodes`, `chunk-custom-rmi-valuetypes`, `client-timeout`, `comet`, `indirection-encoding-disable`, `iona`, `lax-boolean-encoding`, `max-managed-buf-size`, `max-server-connections`, `max-threads`, `outbuf-cache-timeout`, `outbuf-size`, `queue-max`, `queue-min`, `poa-monitoring`, `print-version`, `retries`, `retry-interval`, `queue-wait`, `server-timeout`, `strict-check-on-tc-creation`, `use-bom`, `use-imr`.
The properties X use expressions. Configuration properties that are used to resolve those expressions should be transformed manually to the new `iiop-openjdk` subsystem format	Properties that use expressions must be configured manually by the administrator. For example, the `jacorb` subsystem in JBoss EAP 6 defined a `giop-minor-version` property. The `iiop-openjdk` subsystem in JBoss EAP 7 defines a `giop-version` property. Suppose the `jacorb` subsystem minor version attribute is set to `${iiop-giop-minor-version}` and the system property is configured in the `standalone.conf` file as `-Diiop-giop-minor-version=1`. After the `migrate` operation, the adminstrator must change the system property value to `1.1` to ensure the new subsystem is configured correctly.
Can not migrate: the new `iiop-openjdk` subsystem is already defined	The message contains the explanation.

A.2. Messaging Subsystem Migration Operation Warnings

Note

Warning Message	What It Means / How to Fix It
The `migrate` operation can not be performed: the server must be in `admin-only` mode	The `migrate` operation requires starting the server in `admin-only` mode, which is done by adding `--start-mode=admin-only` to the server start command: $ EAP_HOME/bin/standalone.sh --start-mode=admin-only
Can not migrate attribute `local-bind-address` from resource X. Use instead the `socket-binding` attribute to configure this `broadcast-group`.	The message contains the explanation and how to fix it.
Can not migrate attribute `local-bind-port` from resource X. Use instead the `socket-binding` attribute to configure this `broadcast-group`.	The message contains the explanation and how to fix it.
Can not migrate attribute `group-address` from resource X. Use instead the `socket-binding` attribute to configure this `broadcast-group`.	The message contains the explanation and how to fix it.
Can not migrate attribute `group-port` from resource X. Use instead the `socket-binding` attribute to configure this `broadcast-group`.	The `broadcast-group` resource no longer accepts the `local-bind-address`, `local-bind-port`, `group-address`, or `group-port` attributes. It only accepts a `socket-binding` attribute. The warning is notification that resource X has an unsupported attribute. You must manually set the `socket-binding` attribute on the resource and ensure it corresponds to a defined `socket-binding` resource.
Classes providing the X are discarded during the migration. To use them in the new `messaging-activemq` subsystem, you will have to extend the Artemis-based `Interceptor`.	Messaging interceptors support is significantly different in JBoss EAP 7. Any interceptors configured in the previous version of the subsystem are discarded during migration. See Migrate Messaging Interceptors for more information.
Can not migrate the HA configuration of X. Its `shared-store` and `backup` attributes holds expressions and it is not possible to determine unambiguously how to create the corresponding `ha-policy` for the messaging-activemq’s server.	This means the `hornetq-server` X’s `shared-store` or `backup` attributes contained an expression, such as ${xxx}, and the migration operation was not able to resolve it to a concrete expression. The value is discarded and the `ha-policy` for the `messaging-activemq` must be updated manually.
Can not migrate attribute `local-bind-address` from resource X. Use instead the `socket-binding` attribute to configure this `discovery-group`.	The message contains the explanation and how to fix it.
Can not migrate attribute `local-bind-port` from resource X. Use instead the `socket-binding` attribute to configure this `discovery-group`.	The message contains the explanation and how to fix it.
Can not migrate attribute `group-address` from resource X. Use instead the `socket-binding` attribute to configure this `discovery-group`.	The message contains the explanation and how to fix it.
Can not migrate attribute `group-port` from resource X. Use instead the `socket-binding` attribute to configure this `discovery-group`.	The `discovery-group` resources no longer accept `local-bind-address`, `local-bind-port`, `group-address`, or `group-port` attributes. It only accepts a `socket-binding`. The warning is notification that resource X has an unsupported attribute. You must manually set the `socket-binding` attribute on the resource and ensures it corresponds to a defined `socket-binding` resource.
Can not create a `legacy-connection-factory` based on `connection-factory` X. It uses a HornetQ `in-vm` connector that is not compatible with Artemis `in-vm` connector	The legacy HornetQ remote `connection-factory` resources are migrated into `legacy-connection-factory` resources to allow JBoss EAP 6 clients to connect to JBoss EAP 7. However, `legacy-connection-factory` resources are only created when the `connection-factory` is using remote connectors. Any `connection-factory` using `in-vm` is not migrated because `in-vm` clients are based on JBoss EAP 7, not JBoss EAP 6. This warning is notification that the `in-vm` `connection-factory` was not migrated.
Can not migrate attribute X from resource Y. The attribute uses an expression that can be resolved differently depending on system properties. After migration, this attribute must be added back with an actual value instead of the expression.	This warning appears when the migration can not resolve attribute X to a concrete value during the migration process. The value is discarded and the attribute must be migrated manually. This happens in the following cases: `cluster-connection` `forward-when-no-consumers`: This boolean attribute has been replaced by the `message-load-balancing-type` attribute, which is an enum with a value of `OFF`, `STRICT`, or `ON_DEMAND`. `broadcast-group` and `discovery-group`’s `jgroups-stack` and `jgroups-channel` attributes They reference other resources and JBoss EAP 7 no longer accepts these expressions.
Can not migrate attribute X from resource Y. This attribute is not supported by the new `messaging-activemq` subsystem.	Some attributes are no longer supported in the new `messaging-activemq` subsystem and are simply discarded: `hornetq-server`’s `failback-delay` `http-connector`’s `use-nio` attribute `http-acceptor`’s `use-nio` attribute `remote-connector`’s `use-nio` attribute `remote-acceptor`’s `use-nio` attribute
Can not migrate attribute `failback-delay` from resource X. Artemis detects failback deterministically and it no longer requires to specify a delay for failback to occur.	The message contains the explanation.

Replace the Deprecated broadcast-group or discovery-group Attributes

If you are advised to replace the deprecated broadcast-group or discovery-group attributes with the socket-binding attribute, you can add the new attribute using the management CLI.

This example assumes you are migrating a standalone server that contains the following discovery-group configuration in the messaging subsystem.

<discovery-groups>
    <discovery-group name="my-discovery-group">
        <group-address>224.0.1.105</group-address>
        <group-port>56789</group-port>
    </discovery-group>
</discovery-groups>

When you run the migrate operation for the messaging subsystem, you see the following output and warnings:

/subsystem=messaging:migrate
{
    "outcome" => "success",
    "result" => {"migration-warnings" => [
        "WFLYMSG0084: Can not migrate attribute group-address from resource [
    (\"subsystem\" => \"messaging-activemq\"),
    (\"server\" => \"default\"),
    (\"discovery-group\" => \"my-discovery-group\")
]. Use instead the socket-binding attribute to configure this discovery-group.",
        "WFLYMSG0084: Can not migrate attribute group-port from resource [
    (\"subsystem\" => \"messaging-activemq\"),
    (\"server\" => \"default\"),
    (\"discovery-group\" => \"my-discovery-group\")
]. Use instead the socket-binding attribute to configure this discovery-group."
    ]}
}

The migrate operation creates a discovery-group named "my-discovery-group" in the new messaging-activemq subsystem that is now configured like the following.

<discovery-group name="my-discovery-group"/>

You must now use the following management CLI command to create a socket-binding element in the server configuration file named "my-discovery-group-socket-binding".

/socket-binding-group=standard-sockets/socket-binding=my-discovery-group-socket-binding:add(multicast-address=224.0.1.105, multicast-port=56789)

Next, add the newly created socket-binding to the discovery-group named "my-discovery-group" in the messaging-activemq subsystem in the server configuration file using the following management CLI command.

/subsystem=messaging-activemq/server=default/discovery-group=my-discovery-group:write-attribute(name=socket-binding,value=my-discovery-group-socket-binding)

These commands create the following XML in the server configuration file.

<subsystem xmlns="urn:jboss:domain:messaging-activemq:4.0">
    <server name="default">
        ...
        <discovery-group name="my-discovery-group" socket-binding="my-discovery-group-socket-binding"/>
        ...
    </server>
</subsystem>
...
<socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}">
    ...
    <socket-binding name="my-discovery-group-socket-binding" multicast-address="224.0.1.105" multicast-port="56789"/>
    ...
</socket-binding-group>

A.3. Web Subsystem Migration Operation Warnings

Note

Warning Message	What It Means / How to Fix It
Migrate operation only allowed in admin only mode	The `migrate` operation requires starting the server in `admin-only` mode, which is done by adding parameter `--admin-only` to the server start command: $ EAP_HOME/bin/standalone.sh --admin-only
Could not migrate resource X	The behavior exhibited by this resource in the previous release of JBoss EAP was not migrated. The administrator must verify if the new `undertow` subsystem in JBoss EAP 7 is able to operate correctly without that behavior or whether the behavior must be migrated manually.
Could not migrate attribute X from resource Y.	The behavior exhibited by this resource attribute in the previous release of JBoss EAP was not migrated. The administrator must verify if the new `undertow` subsystem in JBoss EAP 7 is able to operate correctly without that behavior or whether the behavior must be migrated manually. See Web Subsystem Migration Operation Attribute Warnings for the list of attributes that are not migrated.
Could not migrate SSL connector as no SSL config is defined	The message contains the explanation.
Could not migrate `verify-client` attribute X to the Undertow equivalent	The message contains the explanation.
Could not migrate `verify-client` expression X	The message contains the explanation.
Could not migrate valve X	The behavior exhibited by this valve in the previous release of JBoss EAP was not migrated. The administrator must verify if the new `undertow` subsystem in JBoss EAP 7 is able to operate correctly without that behavior or whether the behavior must be migrated manually. This warning can occur for the following valves: `org.apache.catalina.valves.RemoteAddrValve` It must have at least one allowed or denied value. `org.apache.catalina.valves.RemoteHostValve` It must have at least one allowed or denied value. `org.apache.catalina.authenticator.BasicAuthenticator` `org.apache.catalina.authenticator.DigestAuthenticator` `org.apache.catalina.authenticator.FormAuthenticator` `org.apache.catalina.authenticator.SSLAuthenticator` `org.apache.catalina.authenticator.SpnegoAuthenticator` custom valves
Could not migrate attribute X from valve Y	The behavior exhibited by this valve attribute in the previous release of JBoss EAP was not migrated. The administrator must verify if the new `undertow` subsystem in JBoss EAP 7 is able to operate correctly without that behavior or whether the behavior must be migrated manually. This warning can occur for the following valve attributes: `org.apache.catalina.valves.AccessLogValve` `resolveHosts` `fileDateFormat` `renameOnRotate` `encoding` `locale` `requestAttributesEnabled` `buffered` `org.apache.catalina.valves.ExtendedAccessLogValve` `resolveHosts` `fileDateFormat` `renameOnRotate` `encoding` `locale` `requestAttributesEnabled` `buffered` `org.apache.catalina.valves.RemoteIpValve` `httpServerPort` `httpsServerPort` `remoteIpHeader` If it is defined but not set to "x-forwarded-for" `protocolHeader` If it is defined but not set to "x-forwarded-proto"

Web Subsystem Migration Operation Attribute Warnings

The migrate operation is not able to process all JBoss Web attributes. See the following reference tables for information about how to migrate the unprocessed attributes manually.

Web SSL Connector Attributes

The following attributes were used in JBoss EAP 6 to configure the SSL connector. OpenSSL native libraries are not supported in JBoss EAP 7 so there are no equivalent settings.

Attribute	Description	Undertow Equivalent
ca-revocation-url	The file or URL that contains the revocation list.	No equivalent in Undertow.
certificate-file	When using OpenSSL encryption, the path to the file containing the server certificate.	No equivalent in Undertow.
ssl-protocol	The SSL protocol string.	No equivalent in Undertow.
verify-depth	The maximum number of intermediate certificate issuers checked before deciding that the clients do not have a valid certificate.	No equivalent in Undertow.

Web Static Resource Attributes

The following static-resources element attributes were used to describe how static resources were handled by the DefaultServlet or by the WebdavServlet. There are no equivalents for these attributes because WebDAV is not supported by Undertow. For more information, see https://issues.jboss.org/browse/JBEAP-1036.

Attribute	Description	Undertow Equivalent
disabled	Enable the default Servlet mapping.	No equivalent setting in Undertow.
file-encoding	File encoding to be used when reading static files.	No equivalent setting in Undertow.
max-depth	Maximum recursion for `PROPFIND`.	This is a WebDAV setting and WebDAV is not supported by Undertow.
read-only	Allow write HTTP methods (PUT, DELETE).	This is a WebDAV setting and WebDAV is not supported by Undertow.
secret	Secret for WebDAV locking operations.	This is a WebDAV setting and WebDAV is not supported by Undertow.
sendfile	Enable sendfile if possible, for files bigger than the specified byte size.	This is set to a sensible default value in Undertow and is not configurable.
webdav	Enable WebDAV functionality.	WebDAV is not supported by Undertow.

Web SSO Resource Attributes

SSO is handled differently than in the previous release and there are no equivalent attribute settings in JBoss EAP 7.

JBoss Web Attribute	Description	Undertow Equivalent
cache-container	Name of the cache container to use for clustered SSO.	This setting is no longer needed in Undertow. This works by default across a distributed clustered environment.
cache-name	Name of the cache to use for clustered SSO.	This setting is no longer needed in Undertow. This works by default across a distributed clustered environment.
reauthenticate	Whether each request should cause a reauthentication.	There is no equivalent setting in Undertow, which behaves similarly to the `reauthenticate=true` setting in JBoss EAP 6. While `reauthenticate=false` could possibly improve performance, it could also create security issues.

Web Access Log Attributes

JBoss Web Attribute	Description	Undertow Equivalent
resolve-hosts	Whether to enable resolving hosts for access logging.	Use the setting on the connector to accomplish the same behavior.

Web Connector Attributes

JBoss Web Attribute Description Undertow Equivalent

JBoss Web Attribute	Description	Undertow Equivalent
executor	The name of the executor that should be used to process the threads of this connector.	You now reference a worker that is defined in the `io` subsystem. See Migrate the Threads Subsystem Configuration for more information.
proxy-binding	The socket binding to define the host and port that is used when sending a redirect.	There is no direct equivalent. See https-listener Attributes in the JBoss EAP Configuration Guide for available configuration options.
redirect-port	The port for redirection to a secure connector.	This attribute was deprecated in JBoss EAP 6 and replaced with `redirect-binding`. Undertow provides the `redirect-socket` attribute on the `http-listener` element, which is a replacement for `redirect-binding`. See https-listener Attributes in the JBoss EAP Configuration Guide for more information.

executor

The name of the executor that should be used to process the threads of this connector.

You now reference a worker that is defined in the io subsystem.

See Migrate the Threads Subsystem Configuration for more information.

proxy-binding

The socket binding to define the host and port that is used when sending a redirect.

There is no direct equivalent.

See https-listener Attributes in the JBoss EAP Configuration Guide for available configuration options.

redirect-port

The port for redirection to a secure connector.

This attribute was deprecated in JBoss EAP 6 and replaced with redirect-binding. Undertow provides the redirect-socket attribute on the http-listener element, which is a replacement for redirect-binding.

See https-listener Attributes in the JBoss EAP Configuration Guide for more information.

A.4. Migrate JBoss Web System Properties Reference

This reference describes how to map system properties previously used for JBoss Web configuration to the equivalent configuration for Undertow in JBoss EAP 7.

Table A.1. Map Servlet Container and Connectors System Properties

JBoss EAP 6 System Property	Description
	Equivalent in JBoss EAP 7
jvmRoute	Provides a default value for the `jvmRoute` attribute. It does not override the automatically generated value when using the `standalone-ha.xml` configuration file. It supports `reload`.
	Management CLI command: /subsystem=undertow:write-attribute(name=instance-id,value=VALUE)
org.apache.tomcat.util.buf.StringCache.byte.enabled	If `true`, the String cache is enabled for `ByteChunk`. If the value is not specified, the default value of `false` is used.
	No equivalent configuration
org.apache.tomcat.util.buf.StringCache.char.enabled	If `true`, the String cache is enabled for `CharChunk`. If the value is not specified, the default value of `false` is used.
	No equivalent configuration
org.apache.tomcat.util.buf.StringCache.cacheSize	The size of the String cache. If the value is not specified, the default value of `5000` is used.
	No equivalent configuration
org.apache.tomcat.util.buf.StringCache.maxStringSize	The maximum length of String that will be cached. If the value is not specified, the default value of `128` is used.
	No equivalent configuration
org.apache.tomcat.util.http.FastHttpDateFormat.CACHE_SIZE	The size of the cache to use parsed and formatted date value. If the value is not specified, the default value of `1000` is used.
	No equivalent configuration
org.apache.catalina.core.StandardService.DELAY_CONNECTOR_STARTUP	If `true`, the connector startup is not done automatically. It is useful in embedded mode.
	No equivalent configuration
org.apache.catalina.connector.Request.SESSION_ID_CHECK	If `true`, the Servlet container verifies that a session exists in a context with the specified session ID before creating a session with that ID.
	No equivalent configuration
org.apache.coyote.USE_CUSTOM_STATUS_MSG_IN_HEADER	If `true`, custom HTTP status messages are used within HTTP headers. Users must ensure that any such message is `ISO-8859-1` encoded, particularly if user provided input is included in the message, to prevent a possible XSS vulnerability. If value is not specified the default value of `false` is used.
	Must be enabled programmatically by implementing a custom `io.undertow.servlet.ServletExtension`. Then use the extension to call `setSendCustomReasonPhraseOnError(true)` on the `io.undertow.servlet.api.DeploymentInfo` structure instance.
org.apache.tomcat.util.http.Parameters.MAX_COUNT	The maximum number of parameters that can be parsed in a post body. If exceeded, parsing fails using an `IllegalStateException`. The default value is `512` parameters.
	Management CLI command: /subsystem=undertow/server=default-server/http-listener=default:write-attribute(name=max-parameters,value=VALUE) /subsystem=undertow/server=default-server/https-listener=default:write-attribute(name=max-parameters,value=VALUE) /subsystem=undertow/server=default-server/ajp-listener=default:write-attribute(name=max-parameters,value=VALUE)
org.apache.tomcat.util.http.MimeHeaders.MAX_COUNT	The maximum number of headers that can be sent in the HTTP request. If exceeded, parsing will fail using an `IllegalStateException`. The default value is `128` headers.
	Management CLI command: /subsystem=undertow/server=default-server/http-listener=default:write-attribute(name=max-headers,value=VALUE) /subsystem=undertow/server=default-server/https-listener=default:write-attribute(name=max-headers,value=VALUE) /subsystem=undertow/server=default-server/ajp-listener=default:write-attribute(name=max-headers,value=VALUE)
org.apache.tomcat.util.net.MAX_THREADS	The maximum number of threads a connector is going to use to process requests. The default value is `32` x `512`. (`512` x `Runtime.getRuntime().availableProcessors()` for the `JIO` connector)
	Management CLI command: /subsystem=io/worker=default:write-attribute(name=task-max-threads, value=VALUE)
org.apache.coyote.http11.Http11Protocol.MAX_HEADER_SIZE	The maximum size of the HTTP headers, in bytes. If exceeded, parsing will fail using an `ArrayOutOfBoundsException`. The default value is `8192` bytes.
	Management CLI command: /subsystem=undertow/server=default-server/http-listener=default:write-attribute(name=max-header-size,value=VALUE) /subsystem=undertow/server=default-server/https-listener=default:write-attribute(name=max-header-size,value=VALUE) /subsystem=undertow/server=default-server/ajp-listener=default:write-attribute(name=max-header-size,value=VALUE)
org.apache.coyote.http11.Http11Protocol.COMPRESSION	Allows using simple compression with the HTTP connector. The default value is `off`, and compression can be enabled using the value `on` to enable it conditionally, or force to always enable it.
	Configure a filter using the management CLI: # Create a filter /subsystem=undertow/configuration=filter/gzip=gzipfilter:add() /subsystem=undertow/server=default-server/host=default-host/filter-ref=gzipfilter:add()
org.apache.coyote.http11.Http11Protocol.COMPRESSION_RESTRICTED_UA	User agents regexps that will not receive compressed content. The default value is empty.
	Configure a predicate in a filter using the management CLI: # Use a predicate in a filter /subsystem=undertow/configuration=filter/gzip=gzipfilter:add() /subsystem=undertow/server=default-server/host=default-host/filter-ref=gzipfilter:add(predicate="regex[pattern='AppleWebKit',value=%{i,User-Agent}]")
org.apache.coyote.http11.Http11Protocol.COMPRESSION_MIME_TYPES	Content type prefixes of compressible content. The default value is `text/html,text/xml,text/plain`.
	Configure a predicate in a filter using the management CLI: # Use a predicate in a filter /subsystem=undertow/configuration=filter/gzip=gzipfilter:add() /subsystem=undertow/server=default-server/host=default-host/filter-ref=gzipfilter:add(predicate="regex[pattern='text/html',value=%{o,Content-Type}]")
org.apache.coyote.http11.Http11Protocol.COMPRESSION_MIN_SIZE	Minimum size of content that will be compressed. The default value is `2048` bytes.
	Configure a predicate in a filter using the management CLI: # Use a predicate in a filter /subsystem=undertow/configuration=filter/gzip=gzipfilter:add() /subsystem=undertow/server=default-server/host=default-host/filter-ref=gzipfilter:add(predicate="max-content-size[value=MIN_SIZE]")
org.apache.coyote.http11.DEFAULT_CONNECTION_TIMEOUT	Default socket timeout. The default value is `60000` ms.
	Management CLI command: /subsystem=undertow/server=default-server/http-listener=default:write-attribute(name=no-request-timeout,value=VALUE) /subsystem=undertow/server=default-server/https-listener=default:write-attribute(name=no-request-timeout,value=VALUE) /subsystem=undertow/server=default-server/ajp-listener=default:write-attribute(name=no-request-timeout,value=VALUE)
org.jboss.as.web.deployment.DELETE_WORK_DIR_ONCONTEXTDESTROY	Use this property to remove `.java` and `.class` files to ensure that JSP sources are recompiled. The default value is `false`. Default socket timeout for `keep-alive`. The default value is `-1` ms, which means it will use the default socket timeout.
	No equivalent configuration
org.apache.tomcat.util.buf.StringCache.trainThreshold	Specifies the number of times `toString()` must be invoked before activating cache. The default value is `100000`.
	No equivalent configuration

Table A.2. Map EL System Properties

JBoss EAP 6 System Property	Description
	Equivalent in JBoss EAP 7
org.apache.el.parser.COERCE_TO_ZERO	If `true`, when coercing expressions to numbers, empty strings ("") and null will be coerced to zero as required by the specification. If a value is not specified, the default value of `true` is used.
	System property is still valid and processed by the EL

Table A.3. Map JSP System Properties

JBoss EAP 6 System Property	Description
	Equivalent in JBoss EAP 7
org.apache.jasper.compiler.Generator.VAR_EXPRESSIONFACTORY	The name of the variable to use for the expression language expression factory. If value is not specified, the default value of `_el_expressionfactory` is used.
	System property has not changed
org.apache.jasper.compiler.Generator.VAR_INSTANCEMANAGER	The name of the variable to use for the instance manager factory. If value is not specified, the default value of `_jsp_instancemanager` is used.
	System property has not changed
org.apache.jasper.compiler.Parser.STRICT_QUOTE_ESCAPING	If `false`, the requirements for escaping quotes in JSP attributes are relaxed so that a missing required quote does not cause an error. If value is not specified, the specification compliant default of `true` is used.
	System property has not changed
org.apache.jasper.Constants.DEFAULT_TAG_BUFFER_SIZE	Any tag buffer that expands beyond `org.apache.jasper.Constants.DEFAULT_TAG_BUFFER_SIZE` is destroyed and a new buffer is created of the default size. If value is not specified, the default value of `512` is used.
	System property has not changed
org.apache.jasper.runtime.JspFactoryImpl.USE_POOL	If `true`, a ThreadLocal PageContext pool is used. If value is not specified, the default value of `true` is used.
	System property has not changed
org.apache.jasper.runtime.JspFactoryImpl.POOL_SIZE	The size of the ThreadLocal PageContext. If value is not specified, the default value of `8` is used.
	System property has not changed
org.apache.jasper.Constants.JSP_SERVLET_BASE	The base class of the Servlets generated from the JSPs. If value is not specified, the default value of `org.apache.jasper.runtime.HttpJspBase` is used.
	System property has not changed
org.apache.jasper.Constants.SERVICE_METHOD_NAME	The name of the service method called by the base class. If value is not specified, the default value of `_jspService` is used.
	System property has not changed
org.apache.jasper.Constants.SERVLET_CLASSPATH	The name of the ServletContext attribute that provides the class path for the JSP. If value is not specified, the default value of `org.apache.catalina.jsp_classpath` is used.
	System property has not changed
org.apache.jasper.Constants.JSP_FILE	The name of the request attribute for `<jsp-file>` element of a servlet definition. If present on a request, this overrides the value returned by `request.getServletPath()` to select the JSP page to be executed. If value is not specified, the default value of `org.apache.catalina.jsp_file` is used.
	System property has not changed
org.apache.jasper.Constants.PRECOMPILE	The name of the query parameter that causes the JSP engine to just pregenerate the servlet but not invoke it. If value is not specified, the default value of `org.apache.catalina.jsp_precompile` is used.
	System property has not changed
org.apache.jasper.Constants.JSP_PACKAGE_NAME	The default package name for compiled JSP pages. If value not specified, the default value of `org.apache.jsp` is used.
	System property has not changed
org.apache.jasper.Constants.TAG_FILE_PACKAGE_NAME	The default package name for tag handlers generated from tag files. If value is not specified, the default value of `org.apache.jsp.tag` is used.
	System property has not changed
org.apache.jasper.Constants.TEMP_VARIABLE_NAME_PREFIX	Prefix to use for generated temporary variable names. If value is not specified, the default value of `_jspx_temp` is used.
	System property has not changed
org.apache.jasper.Constants.USE_INSTANCE_MANAGER_FOR_TAGS	If `true`, the instance manager is used to obtain tag handler instances. If value is not specified, `true` is used.
	System property has not changed
org.apache.jasper.Constants.INJECT_TAGS	If `true`, annotations specified in tags will be processed and injected. This can have a performance impact when using simple tags, or if tag pooling is disabled. If value is not specified, `false` is used.
	System property has not changed

Table A.4. Map Security System Properties

JBoss EAP 6 System Property	Description
	Equivalent in JBoss EAP 7
org.apache.catalina.connector.RECYCLE_FACADES	If this is `true` or if a security manager is in use a new facade object is created for each request. If value is not specified, the default value of `false` is used.
	No equivalent configuration
org.apache.catalina.connector.CoyoteAdapter.ALLOW_BACKSLASH	If this is `true` the '\' character is permitted as a path delimiter. If value is not specified, the default value of `false` is used.
	No equivalent configuration
org.apache.tomcat.util.buf.UDecoder.ALLOW_ENCODED_SLASH	If this is `true`, '%2F' and '%5C' is permitted as path delimiters. If value is not specified, the default value of `false` is used.
	Management CLI command: /subsystem=undertow/server=default-server/http-listener=default:write-attribute(name=allow-encoded-slash,value=VALUE) /subsystem=undertow/server=default-server/https-listener=default:write-attribute(name=allow-encoded-slash,value=VALUE) /subsystem=undertow/server=default-server/ajp-listener=default:write-attribute(name=allow-encoded-slash,value=VALUE)
org.apache.catalina.STRICT_SERVLET_COMPLIANCE	If value is not specified, `true` is used. If this is `true` the following actions will occur: any wrapped request or response object passed to an application dispatcher is checked to ensure that it has wrapped the original request or response. (SRV.8.2 / SRV.14.2.5.1) a call to `Response.getWriter()` if no character encoding has been specified results in subsequent calls to `Response.getCharacterEncoding()` returning `ISO-8859-1` and the `Content-Type` response header will include a `charset=ISO-8859-1` component. (SRV.15.2.22.1) every request that is associated with a session causes the session’s last accessed time to be updated regardless of whether or not the request explicity accesses the session. (SRV.7.6)
	Compliant by default
org.apache.catalina.core.StandardWrapperValve.SERVLET_STATS	If `true` or if org.apache.catalina.STRICT_SERVLET_COMPLIANCE is `true`, the wrapper will collect the JSR-77 statistics for individual servlets. If value is not specified, the default value of `false` is used.
	No equivalent configuration
org.apache.catalina.session.StandardSession.ACTIVITY_CHECK	If this is `true` or if `org.apache.catalina.STRICT_SERVLET_COMPLIANCE` is `true` Tomcat tracks the number of active requests for each session. When determining if a session is valid, any session with at least one active request is always be considered valid. If value is not specified, the default value of `false` is used.
	No equivalent configuration

A.5. Compatibility and Interoperability Between Releases

This section describes the compatibility and interoperability of client and server EJB and messaging components between the JBoss EAP 5, JBoss EAP 6, and JBoss EAP 7 releases.

EJB remoting over IIOP

You should not encounter problems with any of the following configurations.

Connecting from a JBoss EAP 5 client to a JBoss EAP 7 server
Connecting from a JBoss EAP 6 client to a JBoss EAP 7 server
Connecting from a JBoss EAP 7 client to a JBoss EAP 6 server
Connecting from a JBoss EAP 7 client to a JBoss EAP 5 server

EJB remoting Using JNDI

You should not encounter problems with any of the following configurations.

Connecting from a JBoss EAP 6 client to a JBoss EAP 7 server
Connecting from a JBoss EAP 7 client to a JBoss EAP 6 server

JBoss EAP 6 provided support for the EJB 3.1 specification and introduced the use of standardized global JNDI namespaces, which are still used in JBoss EAP 7. Due to the change in JNDI namespace names, the following configurations are not compatible:

Connecting from a JBoss EAP 5 client to a JBoss EAP 7 or a JBoss EAP 6 server
Connecting from a JBoss EAP 7 or JBoss EAP 6 client to a JBoss EAP 5 server

For more information about standardized JNDI namespace changes, see JNDI Changes in the JBoss EAP 6 Migration Guide.

EJB remoting Using @WebService

You should not encounter problems with any of the following configurations.

Connecting from a JBoss EAP 5 client to a JBoss EAP 7 server
Connecting from a JBoss EAP 6 client to a JBoss EAP 7 server
Connecting from a JBoss EAP 7 client to a JBoss EAP 6 server
Connecting from a JBoss EAP 7 client to a JBoss EAP 5 server

Messaging Standalone Client

You should not encounter problems with any of the following configurations.

Connecting from a JBoss EAP 6 client to a JBoss EAP 7 server
Connecting from a JBoss EAP 7 client to a JBoss EAP 6 server

In the following configuration, if the client is using the messaging broker-specific HornetQ API rather than the generic JMS API, the connection is possible. However, JNDI lookups must be addressed using the JBoss EAP legacy JNDI naming extension that is delivered with JBoss EAP 7.

Connecting from a JBoss EAP 5 client to a JBoss EAP 7 server

JBoss EAP 7 built-in messaging is not able to connect to HornetQ 2.2.x that shipped with JBoss EAP 5 due to protocol compatibility issues. For this reason, the following configurations are not compatible.

Connecting from a JBoss EAP 7 client to a JBoss EAP 5 server

Messaging MDBs

You should not encounter problems with any of the following configurations.

Connecting from a JBoss EAP 6 client to a JBoss EAP 7 server
Connecting from a JBoss EAP 7 client to a JBoss EAP 6 server

Connecting from a JBoss EAP 5 client to a JBoss EAP 7 server

Connecting from a JBoss EAP 7 client to a JBoss EAP 5 server

JMS bridges

You should not encounter problems with any of the following configurations.

Connecting from a JBoss EAP 5 client to a JBoss EAP 7 server
Connecting from a JBoss EAP 6 client to a JBoss EAP 7 server
Connecting from a JBoss EAP 7 client to a JBoss EAP 6 server
Connecting from a JBoss EAP 7 client to a JBoss EAP 5 server

Revised on 2019-09-26 10:41:40 UTC

Select Your Language

Appendix A. Reference Material

A.1. JacORB Subsystem Migration Operation Warnings

A.2. Messaging Subsystem Migration Operation Warnings

Replace the Deprecated broadcast-group or discovery-group Attributes

A.3. Web Subsystem Migration Operation Warnings

Web Subsystem Migration Operation Attribute Warnings

Web SSL Connector Attributes

Web Static Resource Attributes

Web SSO Resource Attributes

Web Access Log Attributes

Web Connector Attributes

A.4. Migrate JBoss Web System Properties Reference

A.5. Compatibility and Interoperability Between Releases

EJB remoting over IIOP

EJB remoting Using JNDI

EJB remoting Using @WebService

Messaging Standalone Client

Messaging MDBs

JMS bridges

Quick Links

Help

Site Info

Related Sites

About

Red Hat legal and privacy links

Red Hat legal and privacy links

Language and Page Formatting Options

Appendix A. Reference Material

A.1. JacORB Subsystem Migration Operation Warnings

A.2. Messaging Subsystem Migration Operation Warnings

Replace the Deprecated broadcast-group or discovery-group Attributes

A.3. Web Subsystem Migration Operation Warnings

Web Subsystem Migration Operation Attribute Warnings

Web SSL Connector Attributes

Web Static Resource Attributes

Web SSO Resource Attributes

Web Access Log Attributes

Web Connector Attributes

A.4. Migrate JBoss Web System Properties Reference

A.5. Compatibility and Interoperability Between Releases

EJB remoting over IIOP

EJB remoting Using JNDI

EJB remoting Using @WebService

Messaging Standalone Client

Messaging MDBs

JMS bridges

Quick Links

Help

Site Info

Related Sites

Systems Status

About

Red Hat legal and privacy links

Red Hat legal and privacy links