[
https://issues.jboss.org/browse/JBWS-3202?page=com.atlassian.jira.plugin....
]
Richard Opalka commented on JBWS-3202:
--------------------------------------
Dear Erik, there's difference between community projects and commercial products.
JBWS is about community and JBPAPP is about products.
You just need to care about your support related issues.
If it's not closed you can be sure someone's still working on it.
I didn't create JBREM issue because JBoss Remoting is
considered obsolete from community point of view.
Its successor/mainline is JBoss Netty nowadays.
However I discussed my conclusions with our support guys that are working on yours
'customer' issues.
(Unfortunately I still don't have access to our support portal system, so I
couldn't comment there directly).
Our support guys will discuss mine conclusions with JBoss Remoting team (if not done
yet).
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