[
https://issues.jboss.org/browse/WFCORE-4365?page=com.atlassian.jira.plugi...
]
Brian Stansberry commented on WFCORE-4365:
------------------------------------------
Is this about the EJB subsystem?
{code}
<remote connector-ref="http-remoting-connector"
thread-pool-name="default">
<channel-creation-options>
<option name="READ_TIMEOUT"
value="${prop.remoting-connector.read.timeout:20}" type="xnio"/>
<option name="MAX_OUTBOUND_MESSAGES"
value="1234" type="remoting"/>
</channel-creation-options>
</remote>
{code}
If so, please move to WFLY and change the component to EJB3. Thanks.
Remove READ_TIMEOUT from cannel configuration options
-----------------------------------------------------
Key: WFCORE-4365
URL:
https://issues.jboss.org/browse/WFCORE-4365
Project: WildFly Core
Issue Type: Bug
Components: Management
Affects Versions: 8.0.0.Final
Reporter: Teresa Miyar
Assignee: Teresa Miyar
Priority: Major
The only configuration options allowed on the channel are
RemotingOptions.TRANSMIT_WINDOW_SIZE,
RemotingOptions.MAX_OUTBOUND_MESSAGES
RemotingOptions.RECEIVE_WINDOW_SIZE
RemotingOptions.MAX_INBOUND_MESSAGES
RemotingOptions.MAX_OUTBOUND_MESSAGE_SIZE
RemotingOptions.MAX_INBOUND_MESSAGE_SIZE.
Standalone.xml/domain.xml file show READ_TIMEOUT as an example option and should be
removed.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)