First of all, I would like to mention that JBoss 3 is very old and you should start considering an upgrade plan.
As you know, support for TLS is provided by the JDK, not JBoss.
However the connector must allow the use of the protocols through a valid configuration. I am pretty sure that Jboss 3 does not support TLSv1.1/1.2.
You can enable SSL debug logging by using the following system property "-Djavax.net.debug=ssl" and see exactly what is going on.
Thank you for the response. I tried enabling the debug in jboss & I see TLSv1 connection is sent instead of their higher version.
As you said support for TLS is provided by the JDK, not JBoss, how does JBoss comes into the picture of not supporting, Sorry not understanding this part.
Maybe your WS client library (or dependencies) is hardcoding the TLSv1 as it the case with libraries like Apache HttpClient 4.2.5 which hardcodes the usage of TLSv1 by default (tested on Java 7 only).
jdk.tls.client.protocols system property was introduced in java 1.7.0_95 . You can try to upgrade java.
Probably you should share your debug log -Djavax.net.debug=all . To see if it cant be a problem of cipher suite selection.
What is the difference between "https.protocols" system property and "jdk.tls.client.protocols" that you mention?, because the first one does actually allow to enable TLSv1.1 and TLSv1.2 in Java 7., see https://tonyyan.wordpress.com/2015/07/17/enabled-tls-1-2-and-tls-1-1-on-java-7/.
PS: Anywa, the OP's problem could be related to a hardcoded TLSv1 dependency in one of the libraries he is using , for example, take a look at the way Apache HttpClient 4.2.5 hardcodes TLSv1 usage, httpclient/SSLSocketFactory.java at 4.2.5 · apache/httpclient · GitHub .