[jboss-jira] [JBoss JIRA] (AS7-6481) Allow ClientConfigurationImpl connection timeout to be configurable via system property

[Brian Stansberry (JIRA)]

    [ https://issues.jboss.org/browse/AS7-6481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12753043#comment-12753043 ] 

Brian Stansberry commented on AS7-6481:
---------------------------------------

How about we resolve it as Done, so it shows up as such in the release notes, searches etc? Since there's no other JIRA for the work. The URL for the commit in upstream master is https://github.com/jbossas/jboss-as/commit/55bd9ea33ae4e8bf7580810ea8baa19ac5a445dc, so people interested in the actual patch can find it via the comments in this issue.
                
> Allow ClientConfigurationImpl connection timeout to be configurable via system property
> ---------------------------------------------------------------------------------------
>
>                 Key: AS7-6481
>                 URL: https://issues.jboss.org/browse/AS7-6481
>             Project: Application Server 7
>          Issue Type: Feature Request
>          Components: CLI
>    Affects Versions: 7.1.1.Final
>         Environment: Mac OS X 10.8.2
>            Reporter: Tommy Odom
>            Assignee: Alexey Loubyansky
>
> Right now the ClientConfigurationImpl.getConnectionTimeout is hard coded to 5000ms.  I saw that master has it changed to allow that to be passed in from the ModelControllerClient.Factory but the new create method isn't used by the CLI classes.
> It would be really nice if I could set a system property like the DEFAULT_MAX_THREADS option.  That way I could set it as part of my maven options as well so the Cargo plugin would pick up the extra time too.
> The reason for this request is that I am experiencing problems with Oracle JDK 7 on Mac OS X because it takes 5 seconds for the SSLContext.createSSLEngine to complete.  It works with JDK 6 but it would be nice to start moving away from JDK 6 as a dependency.

--
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