Red Hat Training
A Red Hat training course is available for Red Hat JBoss Enterprise Application Platform
附录 A. 参考资料
A.1. JacORB 子系统迁移操作警告
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.
如果您在 migrate 操作的输出里看到 "Could not migrate" 或 "Can not migrate" 信息,表示服务器配置的迁移已成功完成,但它无法迁移所有的元素和属性。您必须根据 "migration-warnings" 提供的建议来修改这些配置。
| 警告信息 | 这意味着什么 / 如何进行修复 |
|---|---|
|
当服务器处于 |
$ EAP_HOME/bin/standalone.sh --admin-only |
|
属性 X 无法用 OpenJDK ORB 模拟且不被支持 |
指定的属性的配置不被支持也没有包含在新的
不支持的属性包括: |
|
属性 X 使用表达式。用于解析这些表达式的配置属性应该手动转换为新的 |
使用表达式的属性必须由管理员手动配置。
例如,JBoss EAP 6 里的 |
|
无法迁移:已经定义新的 |
这个消息包含了相关的解释。 |
A.2. Messaging 子系统迁移操作警告
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 messaging subsystem.
如果您在 migrate 操作的输出里看到 "Could not migrate" 或 "Can not migrate" 信息,表示服务器配置的迁移已成功完成,但它无法迁移所有的元素和属性。您必须根据 "migration-warnings" 提供的建议来修改这些配置。
| 警告信息 | 这意味着什么 / 如何进行修复 |
|---|---|
|
无法执行 |
$ EAP_HOME/bin/standalone.sh --admin-only |
|
无法从资源 X 迁移属性 |
这个消息包含了相关解释及如何进行修复。 |
|
无法从资源 X 迁移属性 |
这个消息包含了相关解释及如何进行修复。 |
|
无法从资源 X 迁移属性 |
这个消息包含了相关解释及如何进行修复。 |
|
无法从资源 X 迁移属性 |
|
|
在迁移过程中舍弃了提供 X 的类。要在新的 |
JBoss EAP 7 对消息拦截器的支持已明显不同。之前版本的子系统里配置的任何拦截器在迁移过程中已被舍弃。更多的信息请参考迁移消息拦截器。 |
|
无法迁移 X 的 HA 配置。它的 |
这意味着 |
|
无法从资源 X 迁移属性 |
这个消息包含了相关解释及如何进行修复。 |
|
无法从资源 X 迁移属性 |
这个消息包含了相关解释及如何进行修复。 |
|
无法从资源 X 迁移属性 |
这个消息包含了相关解释及如何进行修复。 |
|
无法从资源 X 迁移属性 |
|
|
无法创建基于 |
旧的 HornetQ 远程 |
|
无法从资源 Y 迁移属性 X。这个属性使用可以根据系统属性解析的表达式。在迁移后,您必须使用具体值而不是表达式再添加这个属性。 |
当在迁移过程种无法解析属性 X为具体值时这个警告会出现。这个值将被舍弃而属性必须手动迁移。它发生在下类情况下:
|
|
无法从资源 Y 迁移属性 X。新的 |
新的
|
|
无法从资源 X 迁移属性 |
这个消息包含了相关的解释。 |
替换已舍弃的 broadcast-group 或 discovery-group 属性
如果您被建议用 socket-binding 属性替代已舍弃的 broadcast-group 或 discovery-group 属性,您可以用管理 CLI 添加新的属性。
这个例子假定您在迁移在 messaging 子系统里包含下列 discovery-group 配置的独立服务器。
<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>
当你对 messaging 子系统运行 migrate 操作时,您会看到下列输出和警告:
[standalone@localhost:9999 /] /subsystem=me
"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."
]}
}
migrate 操作在新的 messaging-activemq 子系统里创建了一个名为 "my-discovery-group" 的 discovery-group,其配置如下。
<discovery-group name="my-discovery-group"/>
您现在必须使用下列管理 CLI 命令在名为 "my-discovery-group-socket-binding" 的服务器配置文件里创建 socket-binding 元素。
/socket-binding-group=standard-sockets/socket-binding=my-discovery-group-socket-binding:add(multicast-address=224.0.1.105, multicast-port=56789)
然后,通过下列 CLI 命令添加新创建的 socket-binding 至配置文件的 messaging-activemq 子系统里名为 "my-discovery-group" 的 discovery-group 里。
/subsystem=messaging-activemq/server=default/discovery-group=my-discovery-group:write-attribute(name=socket-binding,value=my-discovery-group-socket-binding)
这些命令在服务器配置文件里创建了下列 XML。
<subsystem xmlns="urn:jboss:domain:messaging-activemq:1.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 子系统迁移操作警告
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 web subsystem.
如果您在 migrate 操作的输出里看到 "Could not migrate" 或 "Can not migrate" 信息,表示服务器配置的迁移已成功完成,但它无法迁移所有的元素和属性。您必须根据 "migration-warnings" 提供的建议来修改这些配置。
| 警告信息 | 这意味着什么 / 如何进行修复 |
|---|---|
|
只有 admin-only 模式才允许迁移操作 |
$ EAP_HOME/bin/standalone.sh --admin-only |
|
无法迁资源 X |
这个资源在之前的 JBoss EAP 版本里展示的行为没有被迁移。管理员必须检验 JBoss EAP 7 里新的 |
|
无法从资源 Y 迁移属性 X。 |
这个资源属性在之前的 JBoss EAP 版本里展示的行为没有被迁移。管理员必须检验 JBoss EAP 7 里新的 See Web Subsystem Migration Operation Attribute Warnings for the list of attributes that are not migrated. |
|
无法迁移 SSL 连接器,因为没有定义 SSL 配置。 |
这个消息包含了相关的解释。 |
|
无法迁移 |
这个消息包含了相关的解释。 |
|
无法迁移 |
这个消息包含了相关的解释。 |
|
无法迁移阀 X |
这个阀在之前的 JBoss EAP 版本里展示的行为没有被迁移。管理员必须检验 JBoss EAP 7 里新的 This warning can occur for the following valves:
|
|
无法从阀 Y 迁移属性 X |
The behavior exhibited by this valve attribute in the previous release of JBoss EAP was not migrated. The administrator must verify if the new
|
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 | 描述 | 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 | 描述 | 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 |
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 | 描述 | 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 |
Web Access Log Attributes
| JBoss Web Attribute | 描述 | 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 | 描述 | 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 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 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.
表 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
It supports |
|
Management CLI command: /subsystem=undertow:write-attribute(name=instance-id,value=VALUE) | |
|
org.apache.tomcat.util.buf.StringCache.byte.enabled |
If |
|
No equivalent configuration | |
|
org.apache.tomcat.util.buf.StringCache.char.enabled |
If |
|
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 |
|
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 |
|
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 |
|
No equivalent configuration | |
|
org.apache.catalina.core.StandardService.DELAY_CONNECTOR_STARTUP |
If |
|
No equivalent configuration | |
|
org.apache.catalina.connector.Request.SESSION_ID_CHECK |
If |
|
No equivalent configuration | |
|
org.apache.coyote.Constants.USE_CUSTOM_STATUS_MSG_IN_HEADER |
If |
|
Must be enabled programmatically by implementing a custom | |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
No equivalent configuration | |
|
org.apache.tomcat.util.buf.StringCache.trainThreshold |
Specifies the number of times |
|
No equivalent configuration |
表 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 |
|
System property is still valid and processed by the EL |
表 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 |
|
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 |
|
System property has not changed | |
|
org.apache.jasper.compiler.Parser.STRICT_QUOTE_ESCAPING |
If |
|
System property has not changed | |
|
org.apache.jasper.Constants.DEFAULT_TAG_BUFFER_SIZE |
Any tag buffer that expands beyond |
|
System property has not changed | |
|
org.apache.jasper.runtime.JspFactoryImpl.USE_POOL |
If |
|
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 |
|
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 |
|
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 |
|
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 |
|
System property has not changed | |
|
org.apache.jasper.Constants.JSP_FILE |
The name of the request attribute for |
|
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 |
|
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 |
|
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 |
|
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 |
|
System property has not changed | |
|
org.apache.jasper.Constants.USE_INSTANCE_MANAGER_FOR_TAGS |
If |
|
System property has not changed | |
|
org.apache.jasper.Constants.INJECT_TAGS |
If |
|
System property has not changed |
表 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 |
|
No equivalent configuration | |
|
org.apache.catalina.connector.CoyoteAdapter.ALLOW_BACKSLASH |
If this is |
|
No equivalent configuration | |
|
org.apache.tomcat.util.buf.UDecoder.ALLOW_ENCODED_SLASH |
If this is |
|
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, |
|
Compliant by default | |
|
org.apache.catalina.core.StandardWrapperValve.SERVLET_STATS |
If |
|
No equivalent configuration | |
|
org.apache.catalina.session.StandardSession.ACTIVITY_CHECK |
If this is |
|
No equivalent configuration |
A.5. 版本间的兼容性和互用性
本节描述了 JBoss EAP 5、JBoss EAP 6 和 JBoss EAP 7 版本间的客户、服务器 EJB 和消息组件的兼容性和互用性。
使用 IIOP 的 EJB Remoting
对于下列配置您应该不会遇到任何问题。
- 从 JBoss EAP 5 客户连接至 JBoss EAP 7 服务器
- 从 JBoss EAP 6 客户连接至 JBoss EAP 7 服务器
- 从 JBoss EAP 7 客户连接至 JBoss EAP 6 服务器
- 从 JBoss EAP 7 客户连接至 JBoss EAP 5 服务器
使用 JNDI 的 EJB Remoting
对于下列配置您应该不会遇到任何问题。
- 从 JBoss EAP 6 客户连接至 JBoss EAP 7 服务器
- 从 JBoss EAP 7 客户连接至 JBoss EAP 6 服务器
JBoss EAP 6 提供对 EJB 3.1 规格的支持并引入了标准化的全局 JNDI 命名空间,这在 JBoss EAP 7 里仍被使用。由于 JNDI 命名空间名称的修改,下列配置是不兼容的:
- 从 JBoss EAP 5 客户连接至 JBoss EAP 7 或 JBoss EAP 6 服务器
- 从 JBoss EAP 7 或 JBoss EAP 6 客户连接至 JBoss EAP 5 服务器
关于标准化 JNDI 命名空间修改的详情,请参考《JBoss EAP 6 迁移指南》里的『JNDI 修改』章节。
使用 @WebService 的 EJB Remoting
对于下列配置您应该不会遇到任何问题。
- 从 JBoss EAP 5 客户连接至 JBoss EAP 7 服务器
- 从 JBoss EAP 6 客户连接至 JBoss EAP 7 服务器
- 从 JBoss EAP 7 客户连接至 JBoss EAP 6 服务器
- 从 JBoss EAP 7 客户连接至 JBoss EAP 5 服务器
消息独立客户
对于下列配置您应该不会遇到任何问题。
- 从 JBoss EAP 6 客户连接至 JBoss EAP 7 服务器
- 从 JBoss EAP 7 客户连接至 JBoss EAP 6 服务器
在下面的配置里,如果客户使用消息中介专有的 HornetQ API 而不是通用的 JMS API,连接是有可能实现的。然而,JNDI 查找必须用 JBoss EAP 7 附带的旧的 JBoss EAP JNDI 命名扩展来寻址。
- 从 JBoss EAP 5 客户连接至 JBoss EAP 7 服务器
由于协议的兼容性问题,JBoss EAP 7 内置的消息系统不能与 JBoss EAP 5 附带的 HornetQ 2.2.x。 因此,下列配置是不兼容的。
- 从 JBoss EAP 7 客户连接至 JBoss EAP 5 服务器
Messaging MDB
对于下列配置您应该不会遇到任何问题。
- 从 JBoss EAP 6 客户连接至 JBoss EAP 7 服务器
- 从 JBoss EAP 7 客户连接至 JBoss EAP 6 服务器
在下面的配置里,如果客户使用消息中介专有的 HornetQ API 而不是通用的 JMS API,连接是有可能实现的。然而,JNDI 查找必须用 JBoss EAP 7 附带的旧的 JBoss EAP JNDI 命名扩展来寻址。
- 从 JBoss EAP 5 客户连接至 JBoss EAP 7 服务器
由于协议的兼容性问题,JBoss EAP 7 内置的消息系统不能与 JBoss EAP 5 附带的 HornetQ 2.2.x。 因此,下列配置是不兼容的。
- 从 JBoss EAP 7 客户连接至 JBoss EAP 5 服务器
JMS 桥
对于下列配置您应该不会遇到任何问题。
- 从 JBoss EAP 5 客户连接至 JBoss EAP 7 服务器
- 从 JBoss EAP 6 客户连接至 JBoss EAP 7 服务器
- 从 JBoss EAP 7 客户连接至 JBoss EAP 6 服务器
- 从 JBoss EAP 7 客户连接至 JBoss EAP 5 服务器
Revised on 2018-01-12 05:23:39 EST