[
https://issues.jboss.org/browse/WFLY-1423?page=com.atlassian.jira.plugin....
]
Stuart Douglas resolved WFLY-1423.
----------------------------------
Resolution: Rejected
This is dependent upon the context. If the underlying external context provider provides
the option then the user can just set the appropriate property (for LDAP I belive this is
com.sun.jndi.ldap.read.timeout)
Provide configurable timeout for
ExternalContextObjectFactory.createContext
---------------------------------------------------------------------------
Key: WFLY-1423
URL:
https://issues.jboss.org/browse/WFLY-1423
Project: WildFly
Issue Type: Feature Request
Components: Naming
Affects Versions: 8.0.0.Alpha1
Reporter: Jan Martiska
Assignee: Stuart Douglas
An ExternalContextObjectFactory's createContext method might take a long time to
complete, because usually it will communicate over the network. It would be useful to be
able to cap the waiting time, and there should be a timeout enabled by default -- it might
happen that the remote server will get stuck during the context creation and the external
context will never be successfully created (or it will just take too much time). If a
timeout occurs, createContext can for example return null, or throw an exception, not sure
which is better.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira