[
https://issues.jboss.org/browse/JBWS-3202?page=com.atlassian.jira.plugin....
]
Sven-Erik Ceedigh commented on JBWS-3202:
-----------------------------------------
If this is a problem with JBoss Remoting and not JBossWS, shouldn't you create a new
JIRA for JBoss Remoting before rejecting this JIRA and treating it as Resolved?? As a
paying support customer using EAP 5.0.0 in production, we are concerned about this problem
being fixed in EAP 5.0.0 and not interested in whether or not the fix should be in JBossWS
or JBoss Remoting. Switching to JBossWS-CXF in order to make this work also sounds like we
are not getting full value from our support contract.
JBossWS does not reuse SSL sessions
-----------------------------------
Key: JBWS-3202
URL:
https://issues.jboss.org/browse/JBWS-3202
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-native-3.1.2
Environment: JBoss Enterprise Application Platform 5.x
JBossWS 3.1.2
Reporter: Mustafa Musaji
Assignee: Richard Opalka
Attachments: example.zip
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.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira