Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-5858

Document new property - [JBossWS] Configure remoting to reuse SSL sessions

XMLWordPrintable

    • Hide

      Attached a zip which contains

      Deploy: helloWorld-ejb.jar

      helloWorld-ejb.jar.zip - the source for the code above

      mustafa-jbossws-remoting.zip - contains a Java Project from Eclipse with
      the client code

      Set JVM arguments so it uses the JBossWS classes instead of Sun JAXWS in
      JDK6
      -Djava.endorsed.dirs=/home/bmaxwell/applications/jboss/active/lib/endorsed/
      -Djavax.net.debug=all

      It also has a Server Runtime Library that is EAP 5.0 in it.

      $JBOSS_HOME/bin/run.conf - I added -Djava.net.debug=all to it. I was
      testing with the default server profile.

      JAVA_OPTS="-Xms1303m -Xmx1303m -XX:MaxPermSize=256m
      -Dorg.jboss.resolver.warning=true
      -Dsun.rmi.dgc.client.gcInterval=3600000
      -Dsun.rmi.dgc.server.gcInterval=3600000
      -Dsun.lang.ClassLoader.allowArraySyntax=true -Djavax.net.debug=all"

      Show
      Attached a zip which contains Deploy: helloWorld-ejb.jar helloWorld-ejb.jar.zip - the source for the code above mustafa-jbossws-remoting.zip - contains a Java Project from Eclipse with the client code Set JVM arguments so it uses the JBossWS classes instead of Sun JAXWS in JDK6 -Djava.endorsed.dirs=/home/bmaxwell/applications/jboss/active/lib/endorsed/ -Djavax.net.debug=all It also has a Server Runtime Library that is EAP 5.0 in it. $JBOSS_HOME/bin/run.conf - I added -Djava.net.debug=all to it. I was testing with the default server profile. JAVA_OPTS="-Xms1303m -Xmx1303m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Dsun.lang.ClassLoader.allowArraySyntax=true -Djavax.net.debug=all"
    • Documentation (Ref Guide, User Guide, etc.)
    • Low
    • Not Required
    • VERIFIED

      When creating a web service client and sending multiple requests over SSL to JBoss EAP the client doesn't reuse the already established connection and instead a SSL handshake takes place on every request.

      SSL session id is shown in ssl debug log but this is different on every request. Using Sun JAXWS libraries (remove endorsed libraries) you can see the SSL connection session id being reused on every subsequent request being made.

      JBossWS should reuse the already established connection and not do the expensive SSL handshake on every request.

        1. example.zip
          2.03 MB
        2. JBPAPP_5858.diff
          4 kB

              elspeth_jira Elspeth Thorne (Inactive)
              rhn-support-bmaxwell Brad Maxwell
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: